JP2011138416A - Information processing device, control method, program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a mechanism for recording an updated content in time series and exhaustively grasping it, when update processing on a table managed by a database server is performed from an application. <P>SOLUTION: When update processing arises in a job terminal 200 for an application table group 004 of a database server 300 in synchronization with the execution timing of an application 001, a recording device 006 exhaustively records information related to the updated content in a recording table 007, and then the update content recorded in the recording table 007 is inquired by an inquiry terminal 500. Thus, the cause of a system failure, etc. is effectively investigated. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for recording update contents in a time series and inquiring the recorded update contents when an update process is performed on a table managed by a database server.

  In recent systems, the database is an essential element function. In particular, relational databases (RDB) are widely used in the world.

  As a database usage in the system, it is used as a container for storing consistent data, and provides services to execute processing for requests such as inquiries and updates or to present results from programs such as applications. Yes.

  However, access to the database is done by a language called SQL, and how the data stored in the database is updated is black-boxed, and comprehensively grasping the update contents is Currently it is difficult.

  The update contents described here are when, who (user), where (computer name), which program (program name), in which table (table name), and what operation (Insert, Update, Delete) , In what order (managed by serial number), for which record (table record data), what data item value was updated to what value, or updated record This indicates that the value of the item other than the corresponding item is specified.

  In particular, when constructing a system, when testing, evaluating, and investigating the cause of a failure in the constructed system, it is an important and labor-intensive work to carefully examine the contents updated to the database.

  This work occurs during the testing phase at the time of system construction, the acceptance inspection after introduction, and the investigation of the cause when a failure / security incident occurs. As a result of spending a lot of work time, the update contents may be grasped. However, the current situation is that we cannot grasp it comprehensively.

  In the prior art, it is impossible to comprehensively grasp the update contents to the database.

  Here, the specific work contents at the time of carrying out the test will be described. In this work, problems at present are listed, and it will be explained that it is difficult to realize with the conventional technology. As work contents, (1) Identify and grasp the table to be updated from the design document, (2) Manually record the data of the table in the electronic file, (3) Update to the database in the test target application (4) Manually record the data in the table in the electronic file. (5) Manually compare the results of (2) and (4).

  However, to carry out these tasks, the following assumptions are necessary: (A) A design document that is consistent with the application is essential. (B) Only one process can be tested at a time. The premise that it cannot be implemented is necessary.

  If the work is carried out based on this premise, the following problems occur at present.

  In relation to assumption (A), the completeness of the table updated by the application depends on the accuracy of the design document and the consistency between the application and the design document. If there is a description, it will leak from the test case, and the update order of each update target table cannot be grasped, and whether the update order is correct cannot be determined without looking at the program source. To do.

  In addition, in relation to premise (B), the update user and program cannot be identified, and if the information is not recorded on the application side, it cannot be identified. Since the order cannot be grasped and the centrally managed database is simultaneously updated by a plurality of users and programs, it is difficult to specify unless such information is recorded on the application side. There is a problem.

  Furthermore, it is necessary to manually record the data content before and after the processing of the test target application, resulting in labor and work errors.

  Therefore, as one of the techniques for improving the work efficiency of the user's test, a large amount of test data can be retroactively used for the database update that occurs during online processing using the data before and after the update. A technique for performing the creation is disclosed (for example, see Patent Document 1).

JP 2009-074949 A

  However, the technique disclosed in Patent Document 1 is intended to provide a test execution environment for improving the efficiency of test work, and describes that test data is created retrospectively, such as updating a database. There is no description or suggestion about how to investigate the cause of a failure, etc. caused by the occurrence of a transaction, and the information is insufficient to investigate the cause when a failure, etc. occurs in the system. difficult.

  Furthermore, one of the problems is that there is a possibility that the load on the operator when the mechanism for supporting the test data creation is increased.

  The present invention has been made to solve the above-described problem, and is information that can efficiently investigate the cause of the failure in the system from the update history of the database without imposing a burden on the operator. It is an object to provide a processing device, a control method, a program, and a recording medium.

  According to a first aspect of the invention for achieving the above object, there is provided display selection means for selecting and displaying at least one application table, and update contents for the application table selected by the display selection means at an update timing to the application table. It is characterized by comprising recording means for recording, and display means for displaying the updated contents recorded by the recording means.

  According to a second aspect of the invention for achieving the above object, there is provided a display selection step for selecting and displaying at least one application table, and update contents for the application table selected by the display selection step at the update timing to the application table. A recording step for recording, and a display step for displaying the updated contents recorded by the recording step are provided.

  A third invention for achieving the above object is a computer-readable program that can be executed together, and the program includes display selection means for displaying and selecting at least one or more application tables, and It functions as recording means for recording the update contents for the application table selected by the display selection means at the update timing to the application table, and display means for displaying the update contents recorded by the recording means, To do.

  A fourth invention for achieving the above object is a computer-readable recording medium on which the program described in the third invention is recorded.

  According to the present invention, it is possible to efficiently investigate the cause of the failure without burdening the operator by comprehensively recording information related to the update history for the database. Play.

It is a figure which shows the structure of the information processing system in embodiment of this invention. It is a figure which shows the hardware constitutions of each apparatus which comprises the information processing system in embodiment of this invention. It is a flowchart which shows the flow of the operation | work in embodiment of this invention. It is a flowchart which shows the whole schematic process in embodiment of this invention. It is a block diagram which shows the structure of the recording table for memorize | stored the update content in embodiment of this invention. It is a block diagram which shows an example of the screen for producing | generating the recording table in embodiment of this invention. It is a block diagram which shows an example of the screen for producing | generating the recording device in embodiment of this invention. It is a flowchart which shows the process at the time of carrying out the list display of the monitoring object candidate table in embodiment of this invention. It is a flowchart which shows the process which produces | generates the recording device in embodiment of this invention. 6 is a flowchart illustrating processing relating to recording processing of the recording apparatus according to the embodiment of the present invention. It is explanatory drawing for demonstrating the content of the recording table at the time of the data addition by the application in embodiment of this invention. It is explanatory drawing for demonstrating the content of the recording table at the time of the data update by the application in embodiment of this invention. It is explanatory drawing for demonstrating the content of the recording table at the time of the data deletion by the application in embodiment of this invention. It is explanatory drawing for demonstrating the content of the recording table at the time of the update process by the some application and user in embodiment of this invention. It is a block diagram which shows an example of the search condition designation | designated screen in the inquiry apparatus in embodiment of this invention. It is a block diagram which shows an example of the search result screen of the inquiry apparatus in embodiment of this invention. It is a flowchart which shows the process regarding the process which displays the search result of the inquiry apparatus in embodiment of this invention. It is a block diagram which shows that what was recorded on the recording table at the time of label use in embodiment of this invention is displayed on the search result screen. It is a flowchart regarding the process which registers a label in the inquiry apparatus in embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  First, the system configuration and the role of each function according to an embodiment of the present invention will be described.

  FIG. 1 is a configuration diagram showing a system configuration in an information processing system according to an embodiment of the present invention.

  As illustrated in FIG. 1, the information processing system 100 includes a business terminal 200, a database server 300, a management terminal 400, and an inquiry terminal 500. However, the functions of the business terminal 200, the management terminal 400, and the inquiry terminal 500 are not limited. For example, all functions can be provided on the database server 300.

  The business terminal 200 is a terminal on which an application 001 for performing update processing on a database is introduced and a user performs an operation. In the business terminal 200, the application 001 is operated to update the application table group 004 on the database server 300.

  The application 001 indicates software that performs update processing on the database, is positioned outside the provided function of the present invention, and is not specified as long as it performs update processing on the database.

  Next, the database server 300 will be described. In the database server 300, an RDB (Relational Database) product is introduced as a database and plays a role of providing various database services. In the present invention, a database of update content grasp targets (monitor targets) is stored.

  The database server 300 has an application table group 004 that the application 001 refers to and updates. In the implementation of the present invention, it is assumed to exist in advance, and is outside the provided function of the present invention. It is assumed that there are no restrictions on the layout of this table group. The table group is a table of targets (monitoring targets) for monitoring the update processing in the present invention and grasping the update contents.

  The database server 300 includes RDB definition information 005, and this information indicates a group of information necessary for realizing the RDB function. In the present invention, table definition information and item definition information are required. .

  The table definition information is a table list to which attribute information of each table managed on the database server 300 is added. The item definition information is an item list to which item attribute information for each table defined in the previous table list is added. It also holds attribute information such as item type information. As mentioned earlier, RDB products hold about this information as standard RDB functions.

  In the present invention, the recording device 006 is automatically generated based on the RDB definition information 005. The recording device 006 becomes basic information that can provide a function for grasping update contents in a general and comprehensive manner regardless of the implementation form of the application 001 and the application table 004. Therefore, in an environment where such information cannot be collected on the RDB, automatic generation of the recording device 006 cannot be realized.

  The management terminal 400 is a terminal for the administrator to operate, in which the recording base generation device 002 of the present invention is introduced. From the management terminal 400, the recording device 006 and the recording table 007 are generated for the database server 300 using the recording base generation device 002.

  The inquiry terminal 500 is a terminal in which the inquiry device 003 of the present invention is introduced and operated by the user. The inquiry terminal 500 uses the inquiry device 003 to inquire the recording table 007 on the database server 300 and inquire about the updated contents. With this inquiry work, the update contents to RDB are grasped.

  Next, the recording table 007 existing on the database server 300 will be described. One recording table 007 exists in the RDB to be monitored.

  The recording table 007 is generated by operating the recording base generation device 002 on the management terminal 400.

  Update contents to the application table group 004 are recorded in the recording table 007 in time series. The recording device 006 takes charge of the update content recording process.

  Next, the recording device 006 will be described. The recording device 006 is generated by operating the recording base generation device 002 on the management terminal 400 and is registered on the database server 300 by a trigger mechanism that is a standard base function implemented in the RDB. The recording device 006 is registered for each table existing in the application table group 004.

  As a feature of the trigger mechanism, when update processing (Insert, Update, Delete) for the application table occurs on the database server 300, the trigger mechanism can be executed in units of records in accordance with the update timing.

  Using this trigger mechanism, the recording device 006 is activated from the standard function of the RDB. The recording device 006 records data at the time of Insert and Delete, data before update at the time of Update, and data after the update in the recording table 007 in time series.

  FIG. 2 is a diagram showing an example of a hardware configuration of a computer incorporated in each business terminal 200, database server 300, management terminal 400, and inquiry terminal 500 in the information processing system according to the embodiment of the present invention.

The CPU 201 comprehensively controls each device and controller connected to the system bus 204. In addition, the ROM 202 or the external memory 211 has a BIOS (Basic
Input / Output System), an operating system program (hereinafter referred to as OS), and various programs to be described later that are necessary for realizing the functions executed by each server or each PC.

  The RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). The video controller 206 controls display on a display device such as a CRT display (CRT) 210. The display device may be a liquid crystal display as well as a CRT. These are used by the administrator as needed. The present invention is not directly related.

  The memory controller 207 has an adapter in a hard disk (HD), floppy disk (registered trademark FD) or PCMCIA card slot for storing a boot program, browser software, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a compact flash memory connected via the network.

  The communication I / F controller 208 is connected to and communicates with an external device via a network, and executes communication control processing on the network. For example, Internet communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Programs for realizing the present invention are recorded in the external memory 211, and are executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, the definition file and various information tables used by the program according to the present invention are stored in the external memory 211, and a detailed description thereof will be described later.

  Next, with reference to FIG. 3, a description will be given of the work flow until the RDB update history is inquired according to the present invention.

  As shown in FIG. 3, the work is performed in the order of update content recording preparation, application processing and update content recording, and update content record inquiry.

  However, the update content recording preparation is performed only for the first time, and thereafter, it is necessary to perform it when each table structure of the application table group 004 is changed.

  If there is no change, the application process, the update content record, and the update content record inquiry are repeated, and the update content associated with the application update process is grasped.

  First, in preparation for recording update contents, the management terminal 400 shown in FIG. 1 uses the recording base generation device 002 to generate the recording device 006 and the recording table 007.

  Next, in application processing and update content recording, the application 001 is operated on the business terminal 200 shown in FIG. 1 to perform update processing on the application table group 004 on the database server 300.

  On the database server 300, the recording device 006 is activated when each application table 004 is updated, and the updated contents are recorded in the recording table 007.

  In the next update content record inquiry, the inquiry terminal 500 shown in FIG. 1 uses the inquiry device 003 to refer to the record table 007 on the database server 300 to inquire the update contents.

  Next, the flow of work and the flow of processing will be described, and each function will be described in detail.

  FIG. 4 is a diagram showing an outline processing flow until the RDB update history is inquired in the information processing system 100 according to the embodiment of the present invention.

  In the update content recording preparation 010 shown in FIG. 4, the management terminal 400 generates the recording table 007 using the recording base generation device 002 (011). The generation work will be described using the flowchart of FIG. 4 and the generation screen example shown in FIG.

  In the management terminal 400, the recording base generation device 002 is activated (with the activation, connection to the RDB is performed). The setting screen (see FIG. 6) of the recording infrastructure generation device 002 is displayed, and after selecting 030, the number of items (Column Count) and the number of bytes of the item (Column Byte) are set at 031.

  For the number of items, the maximum number of items in the application table group 004 on the database server 300 is set. As for the number of bytes of the item, the maximum number of bytes among the items of the application table group 004 on the database server 300 is set.

  In addition, the item of the self-supporting transaction 031 is set. By setting ON, recording is performed in the recording table 007 in a transaction independent of the monitoring target table update transaction.

  That is, even when the monitoring target table update process is rolled back, the record remains in the recording table 007. Also, by setting OFF, the process is recorded in the recording table 007 as a process within the transaction for updating the monitored table.

  That is, when the table update process to be monitored is rolled back, the contents recorded in the recording table 007 are also rolled back.

  Continuing, since the recording table generation script 033 is generated after selecting the recording table generation instruction at the location 032 using the recording base generation device 002, the database server is then pressed by pressing the compile button 034. Register on 300.

  Therefore, when the configuration of the application table group 004 (maximum number of items, maximum number of items) is changed, it is necessary to execute again after the configuration change.

  Next, the recording table 007 in FIG. 4 will be described. Only one recording table 007 generated in the above-described operation is generated in the RDB to be monitored. The layout of the recording table 007 is shown in FIG. Each item of the recording table 007 can be classified into a management item and a table item.

  The management item 020 includes when (date and time), who (user), where (host name), which program (program name, session ID), which table (table name), and what operation (update type), Data such as (serial number) is recorded in any order, and the record image of the table to be monitored (application table group 004) is recorded in the table item 021.

  Since a plurality of RDB record images are recorded in the recording table 007, general-purpose item names are used, and the number of items is within the range of item 1 to the maximum number of items (n) in the table group to be monitored. It becomes possible to take an aspect.

  Further, in the table item 021, for which record, the value registered in what data item and what value is updated are recorded.

  Next, in the update preparation record 010 shown in FIG. 4, the management terminal 400 generates the recording device 006 using the recording base generation device 002. The generation work will be described using the flow of FIG. 4 and the generation screen example shown in FIG.

  As shown in FIG. 4, first, the recording base generation device 002 is activated on the management terminal 400 (connection to the RDB is performed at the same time as activation). The monitoring target table list screen of the recording base generation device 002 shown in FIG. 7 is displayed, and after selecting 040, the monitoring target candidate table list 041 is displayed. The monitoring target candidate table list 041 corresponds to the application table group 004 shown in FIG.

  Next, the monitoring target table is selected from the monitoring target candidate table list 041 by inputting a check mark in the check box 402.

  After that, since the trigger generation instruction 043 is selected, the recording device generation script 044 is generated. Then, the recording device generation script 044 is registered on the database server 300 by pressing the compile button 045.

  If the configuration of the application table group 004 (item addition / deletion, type change, table deletion / addition) is changed, it is necessary to perform this operation again after the configuration change.

  The display process for the monitoring target candidate table list 041 shown in FIG. 7 is performed in the processing flow shown in FIG. The processing of each step in this flowchart is executed under the control of the CPU 201 of the database server 300.

  First, in step S001, after connecting to the monitored RDB, in step S002, a set of table definition information in the RDB definition information 005 existing on the database server 300 is read.

  Step S003 indicates the start of the loop, and the end of this loop is set as step S006, and the process is repeated for each table.

  In the processing in the loop, in step S004, a table name is acquired and additionally stored in the RAM 203 as a target to be displayed in the monitoring target candidate table list 041.

  If all the processes are completed for the table defined in the table definition information acquired in step S002, the loop is terminated in step S006, and then, in step S007, as shown in FIG. 7 displayed on the CRT 210 of the management terminal 400. A list of table names is displayed in the monitoring target candidate table list 041.

  Thereafter, the administrator manually selects the monitoring target table from the table 041 of monitoring target candidates.

  Next, processing for generating the recording device 006 will be described with reference to the flowchart shown in FIG.

  First, in step S011, a connection is made to the monitoring target RDB, and then in step S012, a table group selected from the monitoring target candidate table list 041 is acquired, and a loop is started for each table acquired in step S013.

  Next, in step S014, a list of table items is acquired for the item definition information in the RDB definition information 005 existing on the database server 300, using the table specified in step S011 as a condition, and stored in the RAM 203.

  Based on the list of items stored in the RAM 203 in the next step S015, a loop is started for each item.

  Next, in step S016, the type information of the item specified in the loop is acquired. In the next step S017, a character type conversion logic is generated for each item and type information. In step S018, the conversion logic generated in step S017 is additionally stored in the RAM 203.

  Step S019 indicates that the item loop is terminated when there are no more processing target items. If there is an item to be processed, the process proceeds to step S015.

  In step S020, a program (SQL) is generated from the conversion logic additionally stored in RAM 203 in step S018.

  Processing is performed in units of tables from step S013 to step S020, and when there is no processing target table, the table loop is terminated (step S021). Programs (SQL) for all tables are displayed in the recording device generation script 044 shown in FIG.

  As a result, preparations for recording update contents are completed. Next, application processing and log recording 013 in FIG. 4 will be described.

  First, the business terminal 200 uses the application 001 to update the application table group 004 on the database server 300.

  By operating the application 001 on the business terminal 200, the standard function of the RDB detects an update event by the trigger mechanism, and the recording device 006 is activated. That is, the recording device 006 is activated in the session in which the application 001 is connected to the RDB, and the update contents for the application table 004 are recorded in the recording table 007. After recording, control returns to the application 001.

  Next, a process for recording the update contents in the recording table 007 after the recording apparatus 006 is activated will be described with reference to the flowchart shown in FIG.

  First, in step S031, connection information (session information) to the RDB is acquired. That is, as described above, it is session information regarding update processing in the application 001. This information is acquired in advance for recording in the session ID of the table layout shown in the recording table 007 shown in FIG.

  Next, in step S032, a sequence number is acquired, a unique number is assigned to the update process, and stored in the RAM 203. Then, in step S033, whether Insert, Update, or Delete is executed for the update process. Is determined.

  In the case of Update or Delete, the process proceeds to step S034, and the data before update is recorded in the recording table 007.

  Next, in step S035, the type of update is determined again. If it is Delete, the process ends. If it is Update, the process proceeds to step S036.

  In step S036, the updated data is recorded in the recording table 007. That is, in the case of Insert, Update, it records in the recording table 007.

  Details of the update from the application operation to the application table and the recording contents of the recording table will be described in detail with reference to FIGS.

  11 to 13 illustrate the application 001 shown in FIG. 4 as an employee master maintenance screen.

  The application 001 is a program for adding, updating, and deleting the “employee master” in the application table group 004 shown in FIG. The operation of the application, the update to the application table, and the recording contents of the recording table when each operation is performed will be specifically described.

  Further, FIG. 14 shows an example when a plurality of users perform update processing on a plurality of applications and application tables.

  FIG. 11 shows an example in which a new employee is added to the employee master.

  First, the employee master maintenance screen 031 is activated. At this time, since there is no change to the table of the application table group 004 (032), recording to the recording table 007 does not occur (033).

  Next, there is no change to the table of the application table group 004 at the timing when the input is made to the input area 034 for inputting information of the employee to be added on the employee master maintenance screen 031 (036), so the recording table 007. No recording is generated (037).

  Next, when the registration button 035 is pressed and the registration process is executed, the result of the registration process is displayed on the employee master maintenance screen 031 (038). After the registration process, information input on the employee master maintenance screen 031 is added to the application table group 004 (039). At this time, in the recording table 007, the management items 020 such as the host name, the program name, the table name, and the type (in the figure, only main items are shown for the sake of illustration) and the data contents of the employee master are stored in the recording table 007. To be recorded.

  FIG. 12 shows an example in which the attribute of an employee already registered in the employee master is changed.

  The employee master maintenance screen 041 is activated and the employee to be changed is displayed on the screen. At this time, since there is no change with respect to the table of the application table group 004, the record table 007 only holds the updated content when the previous employee was added (042).

  Next, an input is made in the input area 044 for inputting the attribute of the employee to be changed on the employee master maintenance screen 041. At this time, since there is no change to the table of the application table group 004 (046), there is no recording in the recording table 007 (047).

  Next, when the registration button 045 is pressed, the registration change process is executed, and the result of the registration change process is displayed on the employee master maintenance screen 041 (048). After the registration change process, the table of the application table group 004 is changed to the information input on the employee master maintenance screen 041 (049). At this time, in the recording table 007, the management items 020 such as the host name, the program name, the table name, the type, etc. (in the figure, only the main items are listed) and the contents of the employee master data are recorded ( 050). In the case of this update process, two records of data, the content of data before update and the content of data after update, are recorded.

  FIG. 13 shows an example of deleting an employee already registered in the employee master.

  The employee master maintenance screen 051 is activated, and the employee to be deleted is displayed on the employee master maintenance screen 051. At this time, there is no change to the RDB of the application table group 004 (052). The record table 007 holds the update contents at the time of the previous employee addition and update (053).

  Next, the information of the employee to be deleted is confirmed (054) on the employee master maintenance screen 051. At this time, since there is no change in the table of the application table group 004 (056), no recording to the recording table 007 occurs (057).

  Next, the registration button 055 is pressed, the deletion process is executed, and the result of the deletion process is displayed on the employee master maintenance screen 051 (058). After the deletion process, the information displayed on the employee master maintenance screen 051 is deleted from the table of the application table group. (059)

  At this time, in the recording table 007, the management items 020 such as the host name, program name, table name, type, etc. (only the main items are shown for illustration in the figure) and the contents of the deleted data of the employee master are recorded. (060).

  Next, FIG. 14 shows an example when a plurality of users perform update processing on a plurality of applications and application tables. The following scenario is set to perform processing in order.

  First, user A updates employee information on the employee master maintenance screen. The employee number is changed to 0001, the employee name is changed to Shigeru Kato, the employment classification is changed from employment to retirement, and the terminal number is updated to 001. When this update is made, the program name of the employee master maintenance screen used is P.exe. As a result of this update, data as indicated by 061 is registered in the recording table 007.

  Next, when user B registers an order on the order registration screen, the customer code is TOK001, the quotation number is M001, the order department code is B001, and the person in charge of the order as order header information for order number J0001. The code is recorded as 0001, the order date is 09/01/05, the delivery date is 09/02/05, and the order amount is 20,000.

  For the order number J0001, as order detail information, the order item is HIN-001, the quantity is 3, the unit price is 6,000, the standard price is 4,000, and the order item is HIN-099. One record of 1 quantity, unit price of 2,000, standard cost of 1,800, 2 records in total.

  When this update is performed, the program name of the order registration screen used is Q.exe. As a result of the update, data as shown in 062 is registered in the recording table 007.

  Next, when user A deletes a department on the department master maintenance screen, a record with a department number of B001, a department name of department A, a use start date of 09/01/05, and a use end date of 99/12/31 Is deleted.

  When this deletion is performed, the program name of the department master maintenance screen used is R.exe. As a result of the update, data as indicated by 063 is registered in the recording table 007.

  Thus, application processing and log recording processing are performed in the information processing system according to the embodiment of the present invention.

  Next, means for referring to the contents of the recording table 007 by the inquiry device 003 and grasping the updated contents will be described with reference to the flow of FIG. 4 and the screens shown in FIGS.

  In the log inquiry 014 in FIG. 4, the data recorded in the recording table 007 is inquired using the inquiry device 003 provided in the inquiry terminal 500. The inquiry work performed by the user or administrator will be described with reference to the flow of FIG. 4 and examples of the screens of FIGS.

  In 015 shown in FIG. 4, the inquiry device 003 is activated in the inquiry terminal 500 (070). Then, in order to specify the RDB of the connection destination where the recording table 007 exists, connection destination information regarding the area where the table exists is input in the connection destination field 071.

  Next, when a search button 072 is pressed, a search condition designation screen 076 is displayed. The search conditions that can be specified here include labels (details will be described later), table names, log search start date and time, end date and time, operations (Insert, Update, Delete), users, host names, programs, etc. 076 can be entered.

  When a search condition is input in the search condition input area 076 and the search start button 077 is pressed, the record table 007 on the RDB is searched, and the search result is displayed on the search result screen shown in FIG.

  On the search result screen, the contents of the recording table 007 corresponding to the search condition are displayed. A management item 080 and a table item 081 are displayed. These display items correspond to the management item 020 and the table item 021 of the recording table 007 shown in FIG.

  As shown in FIG. 5, the recording table 007 is defined as a general-purpose item name. However, when grasping the update contents, the item name of each table is essential as information. Therefore, the sequence numbers are displayed in ascending order (recording table 007 serial number), and each time the table is changed, the item name is acquired from the item list information in the RDB definition information, and the actual table item name is displayed. (082).

  The search result screen display process will be described later. Also, at the time of update, the update contents are compared in the records before and after the update, and identification display such as colored display is performed for items whose values do not match (= updated items).

  Next, search processing for data recorded in the recording table 007 in the inquiry device 003 according to the embodiment of the present invention will be described with reference to the flowcharts shown in FIGS. 17 and 18.

  First, in step S040, it is detected that connection destination information has been input in the connection destination field 071, and the input connection destination information is acquired and stored in the RAM 203. In the next step S041, a connection is made to an area where a table provided in the database server 300 exists based on the connection destination information stored in the RAM 203 in step S040.

  Similarly, the search condition input in the search condition input area 076 of the search condition designation screen 076 is acquired and stored in the RAM 203. Based on the search condition stored in the RAM 203 in step S042 in step S043, a search for the recording table 007 is performed. SQL is generated and stored in the RAM 203.

  In step S044, the SQL stored in the RAM 203 in step S043 is transmitted to the database server 300 and executed.

  In step S045, an SQL for acquiring item information is generated and stored in the RAM 203. Here, the table list and the item list for each table are acquired from the RDB definition information 005 based on the search conditions stored in the RAM 203 in step S042, and the necessary table list and items for each table are stored in the recording table 007. SQL for acquisition is generated and stored in the RAM 203.

  In step S046, the SQL stored in RAM 203 in step S045 is transmitted to database server 300 and executed.

  In step S047, the search result of the recording table 007 executed in step S044 is expanded on the search result screen.

  Next, in step S048, the retrieval result of the item information executed in step S046 is acquired and stored in the RAM 203. In step S049, processing of the retrieval result of the recording table 007 developed in step S047 is started for each line.

  In step S050, a table name is acquired from the table list included in the item information stored in RAM 203 in step S048, and compared with the previous table name stored. The previous table name is stored in step S056.

  As a result of the comparison, if it is determined that the table name does not match the previous table name, the process proceeds to step S052, and if it is not determined that they do not match, the process proceeds to step S055.

  Next, in step S052, the table specified in step S050 is specified from the item information acquired in step S047, and the item list of the specified table is acquired based on the item information stored in the RAM 203 in step S048.

  In step S053, one line of the search result screen is added, and in step s054, the item list stored in the RAM 203 in step S052 is expanded. That is, in the processing from S051 to S054, a line describing the actual table item name is added to the data item indicated by 082 in FIG. As for the addition timing, every time the table name is changed, a line describing the item name is added.

  Next, in step S055, an update process marking process is performed. Details of this processing will be described with reference to the flowchart shown in FIG. Next, in step S056, the table name is stored. This process is saved for comparison / determination in step S051. In other words, the item information as shown in 082 is displayed in table units on the search result screen, that is, to make it easier for the user to visually recognize.

  If there is no search content in the recording table 007 executed in step S044, the loop is terminated (step S057).

  Next, the update location marking process will be described using the flowchart shown in FIG.

  First, in step S058, the record obtained by executing SQL in step S044.

It is determined whether or not the update type (Insert, Update, Delete) of the search result of the record table 007 is Update. If it is determined that it is Update, the process proceeds to Step S059, and it can be determined that it is Update. If not, the process ends.

  In the case of Update, since there are two consecutive records before and after the update, the values of the two rows are compared and this value is colored when the values do not match. It is carried out.

  In step S059 and subsequent steps, a process of marking an update location (item value) at the time of Update is performed.

  Step S059 indicates the start of loop processing for each item in the table item list stored in the RAM 203 in step S052.

  In step S060, the value of the item is acquired from the item list stored in the RAM 203 in step S052, and stored in the RAM 203. In step S061, the value of the item in the next line is also acquired and stored in the RAM 203. In step S062, the values stored in the RAM 203 in steps S060 and S061 are compared and determined. If it is determined that the values do not match, these values are displayed so that they can be identified such as coloring.

  If there are no more items for the item list stored in RAM 203 in step S052, the loop is terminated (step S064), and in step S065, the search target line is advanced by two lines.

  Next, the markup label 73, start button 74, end button 075, and label 078 shown in FIG. 15 will be described.

  These are functions for performing labeling (bookmarking) on the recording table 007 when it is desired to record the updated contents when a specific work or the like occurs.

  This function is effective when a test is executed. When executing a test of an application, first, a test case number “Case-1” is input to the markup label 073.

  Then, before the operation of the application 001 is performed, a start button 074 which is a test start declaration is pressed. As a result of this operation, the start record of the label “Case-1” is added to the recording table 007 (091 in FIG. 19).

  Next, by performing the test target operation of the application 001, the update processing content by the application is recorded in the recording table (092 in FIG. 19). After the application operation 001 is executed, the end button 092 is pressed to declare the end of the test.

  In this operation, the end record of the label “Case-1” is added to the recording table (093 in FIG. 19). The update contents by the application 001 are sandwiched between the start label line and the end label line, and the update target at the time of performing the test can be specified in a range.

  By inputting a test case number in the label 078 of the search condition input area 076 of the search condition designation screen 076 and performing a search, the search result for the line between the start label and the end label is displayed on the search result screen. Can do.

  Next, mark mark label registration processing will be described with reference to a flowchart with reference to FIG.

  In step S066, it is determined whether or not the start button 074 or the end button 075 has been pressed. If it is determined that the button has been pressed, a button for identifying that either the start button 074 or the end button 075 has been pressed. The identification information is stored in the RAM 203, and the process proceeds to step S067.

  In step S067, the inquiry device 003 is activated on the inquiry terminal 500. Then, it detects that connection destination information has been input in the connection destination field 071 in order to specify the RDB of the connection destination in which the recording table 007 exists, acquires the input connection destination information, and stores it in the RAM 203. In the next step S068, connection is made to an area where the table provided in the database server 300 exists based on the connection destination information stored in the RAM 203 in step S067.

  Next, in step S069, the markup label input to the markup label 073 is acquired. In step S070, the button identification information stored in the RAM 203 in step S066 is acquired. In step S071, the markup label acquired in S069 is acquired. A label character string is generated from the label and the button identification information acquired in S070.

  Next, an SQL statement (Insert statement) for registration with respect to the recording table 007 filled with the character string created in step S071 is generated (S063) and stored in the RAM 203.

  In step S072, the SQL stored in the RAM 203 in step S071 is transmitted to the database server 300 and executed.

  As described above, according to the present invention, it is possible to efficiently investigate the cause of the failure without imposing a load on the operator by comprehensively recording information related to the update history for the database.

  As mentioned above, although each embodiment example was explained in full detail, this invention can take the embodiment as a system, an apparatus, a method, a program, or a storage medium etc., for example, from a several apparatus specifically ,. You may apply to the system comprised, and may apply to the apparatus which consists of one apparatus.

  The program according to the present invention is a program that allows a computer to execute (read) each processing method, and the storage medium according to the present invention stores a program that allows the computer to execute each processing method.

  The program in the present invention may be a program for each processing method of each device.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by performing reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network by a communication program, the system or apparatus can enjoy the effects of the present invention. In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

100 information processing system 200 business terminal 300 database server 400 management terminal 500 inquiry terminal 201 CPU
202 ROM
203 RAM
204 System bus 205 Input controller 206 Video controller 207 Memory controller 208 Communication I / F controller 209 Keyboard 210 CRT
211 External memory

Claims (10)

Display selection means for displaying and selecting at least one or more application tables;
Recording means for recording the update contents for the application table selected by the display selection means at the update timing to the application table;
Display means for displaying the update content recorded by the recording means;
An information processing system comprising: The display selecting means further selects the application table and items constituting the application table,
The recording means records the update contents for the items constituting the application table and the application table selected by the display selection means at the update timing to the application table;
The information processing system according to claim 1, further comprising: The display selection means can select a self-contained transaction indicating that recording is performed by the recording means in a transaction independent of the transaction for updating the application table,
3. The recording unit according to claim 1, wherein when the self-supporting transaction is selected by the display selection unit, the recording unit records the update content by a transaction independent of the update transaction of the application table. The information processing system described. It further comprises an input means for inputting specific work information indicating that the updated contents at the time of a specific work are recorded,
4. The information processing system according to claim 1, wherein the recording unit records the update contents in correspondence with the specific work information input by the input unit. 5.   The information processing system according to any one of claims 1 to 4, wherein the update content includes an update type for identifying registration, deletion, and update. Update determination means for determining whether or not the update type is update;
6. The information processing system according to claim 5, wherein when the update type indicates update by the update determination unit, the recording unit records data relating to the application table before update and the application table after update. Comparing means for determining whether or not the data relating to the application table before the update and the application table after the update match,
The information processing apparatus according to claim 6, wherein the display unit displays the data before and after the update so as to be identifiable when the comparison unit determines that they do not match.   The update content includes an update timing to the application table, an update user, an information processing apparatus that has updated the application table, and session information to the application table. The information processing system according to item 1. A display selection step for displaying and selecting at least one or more application tables;
A recording step of recording update contents for the application table selected by the display selection step at an update timing to the application table;
A display step for displaying the updated content recorded by the recording step;
An information processing system control method comprising: A computer readable program that can be executed together, the program comprising:
Display selection means for displaying and selecting at least one or more application tables;
Recording means for recording the update contents for the application table selected by the display selection means at the update timing to the application table;
Display means for displaying the update content recorded by the recording means;
A program characterized by functioning as

Images