JP2012155634A - Information processing program, information processing device and information processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently reduce a data amount of an update log.SOLUTION: A storage means 1a stores initial setting of a record 2 including data items 2a, 2b and 2c, and a first update data group 3 showing contents updated from the initial setting for the data items 2a, 2b and 2c. A specification means 1b specifies an updated update data 3d and 3e for the data items 2a and 2c whose setting by the updated update data is not same as the initial setting, among the data items 2a, 2b and 2c, by referring to the storage means 1a. A processing means 1c generates a piece of second update data 4 for the data items 2a, 2b and 2c using the update data 3d and 3e specified by the specification means 1b to store it in the storage means 1a, and deletes the first update data group 3 from the storage means 1a.

Description

  The present invention relates to an information processing program, an information processing apparatus, and an information processing method for processing an update log.

  Conventionally, in order to improve availability and reliability as a system, an information processing system that operates with redundant components has been used. One of them is to make a database redundant, for example. Specifically, one database is used as an operational system for business processing, and the other database is used as a standby system. The information processing system reflects the update contents in the active system in the standby system and synchronizes both databases. Then, in the event of a failure in the active system, business processing in the active system is handed over to the standby system.

  Here, when making a database redundant, it is desirable from the viewpoint of reliability that data synchronization can be performed at high speed in both databases. Therefore, a difference log in which the difference in one database is recorded is acquired, the difference log is distributed to a plurality of parallel processing targets, and the process of applying the parallel processing target difference log to the other database is performed in parallel. Thus, a method of processing the differential log at high speed has been proposed (see, for example, Patent Document 1).

  In addition, a method has been proposed to increase the transaction speed by combining transactions that may access the same data in the database into the same connection, and committing multiple transactions for each connection together. (For example, refer to Patent Document 2).

International Publication No. 2004/090726 JP 2009-26029 A

  By the way, when a database in which a failure has occurred is restored, it is conceivable to reflect the updated contents so far in the restored database. For this reason, an update log in which update contents are recorded may be acquired in the other database in operation.

  In this case, the longer the operation time using only one database, the greater the amount of data stored in the update log. For this reason, when one side recovers from a failure and tries to synchronize the difference, there is a problem that the processing time becomes longer by the amount of data in the update log. In addition, the maximum data amount of the update log may be limited to a predetermined amount, and there is a problem that it is difficult to acquire an update log exceeding the predetermined amount.

  SUMMARY An advantage of some aspects of the invention is that it provides an information processing program, an information processing apparatus, and an information processing method capable of efficiently reducing the data amount of an update log.

  An information processing program for causing a computer to function as a storage unit, a specifying unit, and a processing unit is provided. The storage means stores an initial setting of a record including a plurality of data items and a plurality of first update data indicating update contents from the initial setting for the plurality of data items. The specifying unit refers to the storage unit and specifies the latest update data for each of the plurality of data items for each data item whose setting by the latest update data is not the same as the initial setting. The processing means generates the second update data for a plurality of data items using the latest update data of all the data items specified by the specifying means, stores the second update data in the storage means, The first update data is deleted.

Further, an information processing apparatus having the same function as a computer that executes an information processing program is provided.
A computer information processing method is also provided. In this information processing method, the computer refers to storage means for storing an initial setting of a record including a plurality of data items and a plurality of first update data indicating update contents from the initial setting for the plurality of data items. Thus, among the plurality of data items, the latest update data is specified for a data item whose setting by the latest update data is not the same as the initial setting. Then, using the latest update data of all the specified data items, one second update data for the plurality of data items is generated and stored in the storage means, and the plurality of first update data is stored from the storage means. delete.

  According to the information processing program, the information processing apparatus, and the information processing method, the data amount of the update log can be efficiently reduced.

It is a figure which shows the information processing apparatus of 1st Embodiment. It is a figure which shows the financial counter system of 2nd Embodiment. It is a figure which shows the relationship of each apparatus. It is a figure which illustrates a transfer workflow. It is a figure which shows the hardware constitutions of DB server. It is a figure which shows the function structure of DB server. It is a figure which shows the example of a data structure of a slip management table. It is a figure which shows the data structure example of an update log file. It is a 1st figure which shows the example of a data structure of the newest record table. It is a 2nd figure which shows the example of a data structure of the newest record table. It is a flowchart which shows an update log compression process. It is the 1st figure which illustrates the update log file after compression processing. It is the 2nd figure which illustrates the update log file after compression processing. It is the 3rd figure which illustrates the update log file after compression processing.

Hereinafter, the present embodiment will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a diagram illustrating the information processing apparatus according to the first embodiment. The information processing apparatus 1 manages an update log related to the table “table-A” on the database. The update log is used to synchronize both of the redundant databases. The information processing apparatus 1 includes a storage unit 1a, a specifying unit 1b, and a processing unit 1c.

  The storage unit 1 a stores the initial setting of the record 2. The initial setting indicates the setting contents of the record 2 at the time when acquisition of the update log is started. If there are multiple records, the initial settings are stored for each record. If there are a plurality of data items in the record, the initial setting is further stored for each data item.

  Record 2 includes a plurality of data items. For example, it is assumed that data items 2a, 2b, and 2c are included. Here, the item name “data1” is assigned to the data item 2a, the item name “data2” is assigned to the data item 2b, and the item name “data3” is assigned to the data item 2c. Assume that the initial setting is “10” for all of the data items 2a, 2b, and 2c.

  The storage unit 1a stores the first update data group 3 as an update log from the initial setting for the data items 2a, 2b, and 2c. The first update data group 3 includes, for example, update data 3a, 3b, 3c, 3d, 3e, 3f, and 3g in chronological order.

  The specifying unit 1b refers to the storage unit 1a, and specifies the latest update data for each data item 2a, 2b, 2c in which the setting by the latest update data is not the same as the initial setting.

  For example, the latest update data 3e regarding the data item 2a indicates an update to “12”. Therefore, since it is not the same as the initial setting “10”, the specifying unit 1b specifies the latest update data 3e. The latest update data 3g related to the data item 2b indicates an update to “10”. Therefore, since it is the same as the initial setting “10”, it is not a specific target. The latest update data 3d related to the data item 2c indicates an update to “20”. Therefore, since it is not the same as the initial setting “10”, the specifying unit 1b specifies the latest update data 3d.

  The processing unit 1c generates one second update data 4 for a plurality of data items using the latest update data of all the data items specified by the specifying unit 1b, and stores the second update data 4 in the storage unit 1a. Then, the processing unit 1c deletes the first update data group 3 from the storage unit 1a. The second update data 4 can be used in place of the first update data group 3 in order to synchronize both redundant databases.

  For example, in the example described above, the specifying unit 1b specifies the update data 3e for the data item 2a and the update data 3d for the data item 2c. The processing unit 1c generates the second update data 4 using the update data 3d and 3e. The second update data 4 is data for updating the data item 2a to “12” and the data item 2c to “20”, respectively. Then, the processing unit 1c deletes the first update data group 3 from the storage unit 1a.

  According to the information processing apparatus 1, the storage unit 1a is referred to by the specifying unit 1b, and among the data items 2a, 2b, and 2c, for each of the data items 2a and 2c, the setting by the latest update data is not the same as the initial setting. The latest update data 3d and 3e are specified. The processing means 1c uses the update data 3d, 3e specified by the specifying means 1b to create one second update data 4 for the data items 2a, 2b, 2c and store it in the storage means 1a. The storage means 1a The first update data group 3 is deleted.

  Thereby, the data amount of an update log can be reduced efficiently. Specifically, since the second update data 4 reflecting the latest update data of each of the data items 2a, 2b, 2c is generated and the other update data is deleted, the data amount of the update log Can be reduced. Here, the second update data 4 can be generated only from the latest update data of each of the data items 2a, 2b, and 2c because the update data other than the latest update data is finally set differently depending on the new update data. It is because it is updated. Therefore, by referring to only the latest update data, it is possible to obtain information necessary to synchronize the data item.

  In particular, since one new update data (second update data 4) is generated for the record 2, it is possible to efficiently reduce the data amount of update data that existed for the record 2.

  Further, by generating the second update data 4 for the data items 2a and 2c in which the setting based on the latest update data is different from the initial setting, the second update data 4 includes the data item 2b having the same setting as the initial setting. There is no need to include useless update commands.

  For this reason, if synchronization of the redundant database is performed using the second update data 4, the time required for the synchronization process can be shortened. Even if the maximum data amount of the update log is limited to a predetermined amount, the amount of increase in the update log can be reduced by periodically generating the second update data 4 and deleting the first update data group 3. Can be relaxed.

In the second embodiment described below, a case where the information processing apparatus 1 is applied to a financial window system will be described as an example.
[Second Embodiment]
FIG. 2 is a diagram illustrating a financial window system according to the second embodiment. This financial window system supports the exchange business in the center 10 and the sales office 20 of the financial institution. Here, the transfer business will be described as an example below. However, the same applies to other businesses. In the center 10 and the branch office 20, information processing devices such as a server device (hereinafter also simply referred to as a server) and a terminal device that constitute a financial window system are installed.

  This financial window system includes DB (DataBase) servers 100 and 100a, an AP (Application) server 200, a Web server 300, a procedure terminal apparatus 400, a window terminal apparatus 500, and an approval terminal apparatus 600.

  The DB servers 100 and 100a, the AP server 200, and the Web server 300 are connected to the network 11 in the center 10. The procedure terminal device 400 is connected to the network 12 in the center 10. The network 12 is connected to the network 11. Further, the window terminal device 500 and the approval terminal device 600 are connected to the network 21 in the sales office 20. The networks 11 and 21 are connected via the network 30. The network 30 is a dedicated communication network for the Internet, an intranet, or the financial window system.

  The DB servers 100 and 100a are server devices for storing data used for processing of the financial window system. The DB servers 100 and 100a are made redundant (mirrored). That is, the DB servers 100 and 100a have a function of synchronizing the update contents of one (active system) to the other (standby system). In particular, the DB servers 100 and 100a take over the business processing to the standby system when the operation system cannot be continued due to a failure. For example, when the DB server 100a is an active system, if a failure occurs in the DB server 100a and the operation cannot be continued, business processing is taken over by the DB server 100 that is a standby system. At that time, the DB server 100 generates an update log in which the contents updated in the DB server 100 are recorded. The update log is used to synchronize the update contents in the DB server 100 with the DB server 100a when the DB server 100a is restored.

  The AP server 200 is a server device that executes an application for realizing business processing of the financial window system. The AP server 200 refers to the DB servers 100 and 100a in response to a request received from the Web server 300, and executes business processing.

  The Web server 300 is a server device that provides a GUI (Graphical User Interface) for receiving a business process request from the procedure terminal device 400, the window terminal device 500, and the approval terminal device 600. Each operator of the procedure terminal device 400, the window terminal device 500, and the approval terminal device 600 can use the GUI by a browser provided in each device.

The procedure terminal device 400 is an information processing device for performing a transfer procedure. The procedure terminal device 400 is operated by a procedure operator stationed at the center 10.
The window terminal device 500 is an information processing device that accepts a transfer slip entered by a customer. The window terminal device 500 is operated by a window operator stationed at the sales office 20.

The approval terminal device 600 is an information processing device for approving the continuation of the transfer procedure. The approval terminal device 600 is operated by an approver stationed at the sales office 20.
FIG. 3 is a diagram illustrating the relationship between the devices. Each operator of the window terminal device 500, the approval terminal device 600, and the procedure terminal device 400 can access the Web server 300 and input a business process request. The window terminal device 500, the approval terminal device 600, and the procedure terminal device 400 acquire and display the GUI of the Web server 300 using a browser.

The GUI displayed on the window terminal device 500 is for accepting an input of acceptance completion of a transfer slip.
The GUI displayed by the approval terminal device 600 is a GUI for approving that the transfer procedure may be performed based on the input transfer slip information.

The GUI displayed by the procedure terminal device 400 is a GUI for inputting the confirmation of the transfer procedure.
The Web server 300 generates a request (referred to as an AP request) to the AP server 200 in response to each business process request acquired from the window terminal device 500, the approval terminal device 600, and the procedure terminal device 400, and transmits the request to the AP server 200. . When the Web server 300 receives a processing response (referred to as an AP response) corresponding to the AP request from the AP server 200, the Web server 300 generates a business processing response based on the AP response, and generates a window terminal device 500, an approval terminal device 600, and a procedure terminal. To device 400.

  The AP server 200 generates a request (referred to as a DB request) to the DB servers 100 and 100a in response to the AP request received from the Web server 300, and transmits the request to the DB servers 100 and 100a. Here, the AP server 200 transmits a DB request to the currently active DB server. For example, if the DB server 100a is an active system, a DB request is transmitted to the DB server 100a. Then, the AP server 200 receives a processing response (referred to as a DB response) corresponding to the DB request from the DB server 100a, generates an AP response based on the DB response, and transmits the AP response to the Web server 300. The DB request includes information corresponding to the SQL sentence.

  The DB servers 100 and 100a perform data processing according to the DB request received from the AP server 200. The DB servers 100 and 100a generate a response to the AP server 200 based on the result of the data processing, and transmit the response to the AP server 200. Here, of the DB servers 100 and 100a, one of the active systems performs the process. The result of the data processing executed in the active system is synchronized with the other standby system.

  In the following description, it is assumed that the DB server 100a is stopped due to a failure. In other words, it is assumed that the financial window system is operated in a reduced manner using only the DB server 100. However, the case where the DB server 100 stops due to a failure and the degenerate operation is performed only by the DB server 100a is the same as the following description.

  FIG. 4 is a diagram illustrating a transfer workflow. The transfer workflow 50 indicates the order of the transfer process of the financial window system. The transfer workflow 50 shows a device of a business process request generation source (request source), a process associated with the request, and a slip state after the process at each site (sales office 20 and center 10). Here, the slip state indicates the state of the transfer slip managed by the DB servers 100 and 100a. The processing order by the transfer workflow 50 is as follows.

  First, a transfer slip for a customer to make a transfer request to a financial institution is created. In the transfer workflow 50, the request source is enclosed in parentheses “(customer)”, the process “(transfer request)”, and the slip state “(creation)”. This is because the procedure is performed by the customer and is not performed by the financial window system. However, since the input data that is the starting point of the processing by the financial window system is generated based on the slip, it is shown for easy understanding. The following procedure will be described below. Note that the processing of the DB server 100 is executed based on the DB request via the Web server 300 and the AP server 200 as described above.

  (1) The window terminal device 500 transmits a transfer slip information registration request to the Web server 300. Then, the DB server 100 registers information on the slip. The DB server 100 sets the slip state to “accepted”.

  (2) The window terminal device 500 transmits a transfer approval request request using a transfer slip to the Web server 300. Then, the DB server 100 sets the slip state to “waiting for approval”. Thereby, the approval by the approval terminal device 600 becomes possible.

(3) The approval terminal device 600 transmits a transfer slip approval setting request to the Web server 300. Then, the DB server 100 sets the slip state to “approval”.
(4) The approval terminal device 600 transmits a transfer procedure delegation request to the Web server 300 for the transfer slip. Then, the DB server 100 sets the slip state to “delegation”.

  (5) The procedure terminal device 400 transmits a transfer procedure execution request based on the transfer slip to the Web server 300. Then, the DB server 100 sets the slip state to “in process”. Then, the AP server 200 executes a transfer process with another branch or another financial institution.

(6) When the transfer process is completed, the AP server 200 notifies the DB server 100 to that effect. Then, the DB server 100 sets the slip state to “completed”.
The transfer process is performed in the above order, and the state of the electronic slip on the DB server 100 is updated. The DB server 100 records the update history of the electronic slips sequentially changed in this way as an update log. This is because when the DB server 100a is restored, data synchronization is performed using the update log. At that time, the DB server 100 efficiently reduces the data amount of the update log. Below, the structure of such DB server 100 is demonstrated in detail. First, a configuration of a device (hardware) included in the DB server 100 will be described.

  FIG. 5 is a diagram illustrating a hardware configuration of the DB server. The DB server 100 includes a central processing unit (CPU) 101, a read only memory (ROM) 102, a random access memory (RAM) 103, a hard disk drive (HDD) 104, a graphic processing device 105, an input interface 106, and a recording medium reading device. 107 and a communication interface 108.

The CPU 101 controls the entire DB server 100 by executing an OS (Operating System) program and an application program.
The ROM 102 stores a predetermined program such as a BIOS (Basic Input / Output System) program executed when the DB server 100 is activated. The ROM 102 may be a rewritable nonvolatile memory.

  The RAM 103 temporarily stores at least part of an OS program and application programs executed by the CPU 101. The RAM 103 temporarily stores at least a part of data used for the processing of the CPU 101.

  The HDD 104 stores an OS program and application programs. The HDD 104 stores data used for the processing of the CPU 101. Instead of the HDD 104 (or in combination with the HDD 104), other types of nonvolatile storage devices such as an SSD (Solid State Drive) may be used.

The graphic processing device 105 is connected to the monitor 13. The graphic processing device 105 displays an image on the monitor 13 in accordance with a command from the CPU 101.
The input interface 106 is connected to input devices such as the keyboard 14 and the mouse 15. The input interface 106 outputs an input signal sent from the input device to the CPU 101.

  The recording medium reading device 107 is a reading device that reads data stored in the recording medium 16. For example, a program to be executed by the DB server 100 is recorded in the recording medium 16. For example, the DB server 100 can realize an update log compression function as described later by executing an information processing program recorded in the recording medium 16. That is, the information processing program can be recorded on the computer-readable recording medium 16 and distributed.

  As the recording medium 16, for example, a magnetic recording device, an optical disk, a magneto-optical recording medium, or a semiconductor memory can be used. Examples of the magnetic recording device include an HDD, a flexible disk (FD), and a magnetic tape. Optical disks include CD (Compact Disc), CD-R (Recordable) / RW (ReWritable), DVD (Digital Versatile Disc), DVD-R / RW / RAM, and the like. Magneto-optical recording media include MO (Magneto-Optical disk). Semiconductor memory includes flash memory such as USB (Universal Serial Bus) memory.

  The communication interface 108 is connected to the network 11. The communication interface 108 can perform data communication with the DB server 100 a, AP server 200, Web server 300, procedure terminal device 400, window terminal device 500, and approval terminal device 600 via the network 11.

  Note that the information processing program may be stored in another server device (not shown) connected to the network 11, the network 30, or the like. In that case, the DB server 100 can also download and execute an information processing program from the server device.

  Further, the DB server 100 a, the AP server 200, the Web server 300, the procedure terminal device 400, the window terminal device 500, and the approval terminal device 600 can also be realized with the same hardware configuration as the DB server 100.

  FIG. 6 is a diagram illustrating a functional configuration of the DB server. The DB server 100 includes a slip database 110, a transaction log storage unit 120, an update log storage unit 130, a latest record storage unit 140, a communication unit 150, a database management unit 160, an analysis processing unit 170, a compression processing unit 180, and a synchronization processing unit 190. Have The functions of these units are realized on the DB server 100 by the CPU 101 executing the information processing program. However, all or part of the functions of these units may be realized by dedicated hardware.

  The slip database 110 is a storage area for storing and managing electronic slips. The slip database 110 manages one electronic slip as one record including a plurality of setting items.

  The transaction log storage unit 120 stores a transaction log. The transaction log is a record of all transactions for the slip database 110. The transaction log is used to roll back or roll forward individual transactions with respect to the slip database 110.

  The update log storage unit 130 stores an update log. The update log is acquired by the database management unit 160 when the DB server 100a is in a stopped state due to a failure. The update log is used to synchronize with the DB servers 100 and 100a when the DB server 100a recovers from a failure.

  The latest record storage unit 140 stores the latest record management data. The latest record management data is information used to specify the latest state for each setting item included in the record recorded in the slip database 110.

  The communication unit 150 communicates with the AP server 200. The communication unit 150 outputs the DB request received from the AP server 200 to the database management unit 160. The communication unit 150 transmits the DB response acquired from the database management unit 160 to the AP server 200.

  The database management unit 160 analyzes the DB request acquired from the communication unit 150 and acquires (or generates) an SQL sentence. The database management unit 160 operates the slip database 110 by executing the SQL statement. The operation content is, for example, update (UPDATE), deletion (DELETE), and insertion (INSERT).

The analysis processing unit 170 refers to the update log stored in the update log storage unit 130, generates the latest record management data, and stores it in the latest record storage unit 140.
The compression processing unit 180 refers to the latest record management data stored in the latest record storage unit 140 and performs update log compression processing.

  When the DB server 100a recovers from a failure, the synchronization processing unit 190 refers to the update log stored in the update log storage unit 130 and synchronizes the slip database included in the DB server 100a with the slip database 110.

The DB server 100 a has the same functional configuration as the DB server 100.
FIG. 7 is a diagram showing an example of the data structure of the slip management table. The slip management table 111 is stored in the slip database 110 and updated by the database management unit 160. The slip management table 111 is data for managing electronic slips. The slip management table 111 includes items indicating a record number, an entry store number, a slip serial number, a slip state, a fetching flag, and a media file. Information arranged in the horizontal direction of each item is associated with each other to indicate information of one electronic slip.

  In the record number field, a number for identifying the record is set. Identification information for identifying the sales store 20 is set in the entry store number field. The serial number assigned to the electronic slip is set in the slip serial number field. The slip state on the transfer workflow 50 is set in the slip state item. Information indicating whether the flag is ON or OFF is set in the item of the extraction flag. Here, the fetching flag is a flag indicating that it is in a state (exclusive state) that cannot be updated by another process because it is used by any process in the transfer workflow 50. Such a flag is sometimes called an exclusive flag. In the item of media file, a file in which the entry contents of the transfer slip is imaged is set (indicated by the file name in the slip management table 111).

  For example, in the slip management table 111, the record number is “1”, the entry store number is “E001”, the slip serial number is “D0001”, the slip state is “accepted”, the fetching flag is “OFF”, and the media file is “ Information “D0001.dat” is set.

  This is because the record number indicating the electronic voucher is “1”, the voucher registered at the sales office 20, the voucher serial number is “D0001”, and the voucher state is “accepted” in the transfer workflow 50. It shows that it is the state of. Further, since the extraction flag is “OFF”, it indicates that it is not used for any processing. Further, it indicates that the media file corresponding to the electronic slip is stored in the slip management table 111 as “D0001.dat”.

  Further, for example, in the slip management table 111, the record number is “2”, the entry store number is “E001”, the slip serial number is “D0002”, the slip state is “waiting for approval”, the fetching flag is “ON”, the media Information that the file is “D0002.dat” is set.

  This is because the record number indicating the electronic voucher is “2”, the voucher registered at the sales office 20, the voucher serial number is “D0002”, and the voucher status is “waiting for approval” in the transfer workflow 50. "". In addition, since the extraction flag is “ON”, it is used for any process (in this case, either (2) or (3) in the transfer workflow 50). Indicates that updating is prohibited. Further, it indicates that the media file corresponding to the electronic slip is stored in the slip management table 111 as “D0002.dat”.

Here, in the following description, each record indicating an electronic slip is referred to as a slip management record.
FIG. 8 is a diagram illustrating an example of the data structure of the update log file. The update log file 131 is generated by the database management unit 160 and stored in the update log storage unit 130. The update log file 131 describes a plurality of update data. In the update log file 131, an item number for identifying the update data is described in association with the update data for convenience. The item numbers are assigned in ascending order in time series, and the older the number, the newer the number. It is assumed that the slip management table 111 is designated by the notation “slip management” for each update data.

  In the update data, update contents of the slip database 110 by the database management unit 160 are described. In the update log file 131, starting from the insertion (INSERT) of a new record relating to one electronic voucher, (1) to (6) of the transfer workflow 50 (hereinafter simply referred to as “process (1)”, etc.) The update data corresponding to the series of processes shown in FIG.

  Specifically, registration of a new slip (insertion of a record) corresponds to the update data of item number 1. The process (1) corresponds to the update data items 2 to 4. The process (2) corresponds to the update data of item numbers 5 to 7. The process (3) corresponds to the update data of item numbers 8 to 10. The process (4) corresponds to the update data of item numbers 11-13. The process (5) corresponds to the update data of item numbers 14-16. The process (6) corresponds to the update data of item numbers 17-19.

  Here, the contents indicated by the update data of item numbers 2 to 4 corresponding to the process (1) will be described. The record number of the record to be updated is “1”. In the processing of (1), first, the fetching flag is set to “ON” by the update data of item number 2. As a result, the record becomes exclusive. Next, the slip state is set to “accepted” by the update data of item number 3. Further, the fetching flag is set to “OFF” by the update data of item number 4. As a result, the exclusive state of the record is released.

  Regarding the processes (2) to (6), the slip state is updated in the same manner as the process (1). That is, first, the record is put into an exclusive state, the slip state is updated, and the exclusive state is released.

  Further, in the update log file 131, the update data of item number 1 has the update type “INSERT” (new addition), so the state of the slip management record with the record number “1” at the time when acquisition of the update log file 131 is started. Is shown. That is, the update data of item number 1 is an initial setting of each data item included in the record.

  On the other hand, the update type of the update data of item number 1 may be “UPDATE”. In this case, the update data of item number 1 indicates the initial setting of the data item to be “UPDATE”. The initial settings of other data items are acquired and stored when the other data items are first updated. Therefore, in this case, there are a plurality of update data indicating the initial setting.

  FIG. 9 is a first diagram illustrating a data structure example of the latest record table. The latest record table 141 is generated by the analysis processing unit 170 and stored in the latest record storage unit 140. The latest record tables 141a and 141b indicate changes in the update of the latest record table 141 by the analysis processing unit 170. The latest record table includes items such as a table name, a record number, a deletion flag, and update contents. Information arranged in the horizontal direction of each item is associated with each other to indicate the latest state of one record.

  In the table name item, the name of the table is set. In the record number field, a number for identifying a record in the table is set. In the item of the deletion flag, a deletion flag indicating whether or not the record has been deleted (DELETE) is set. The deletion flag is set to “ON” if the record has been deleted, and “OFF” otherwise. In the item of update contents, the data item name and the update value of the data item are set. An update content item is provided for each data item name. For this reason, when managing update values of a plurality of data items, a plurality of items of update contents are also provided. In the latest record tables 141a and 141b, items of update contents (A) and (B) are provided to distinguish a plurality of update contents.

Hereinafter, the transition of the update of the latest record table 141 will be specifically described.
The latest record table 141 corresponds to the update data of item number 2 in the update log file 131. That is, the latest record table 141 records that the item name “retrieving flag” is set to the update value “ON” for the record with the record number “1” in the slip management table 111.

  The latest record table 141 a corresponds to the update data of item number 3 in the update log file 131. That is, the latest record table 141a records that the item name “slip state” is set to the update value “accepted” for the record with the record number “1” in the slip management table 111.

  The latest record table 141 b corresponds to the update data of item number 4 in the update log file 131. That is, the latest record table 141b records that the item name “retrieving flag” is set to the update value “OFF” for the record with the record number “1” in the slip management table 111.

Thereafter, the latest record table 141b is updated in the same manner for the item numbers 5 to 19 of the update log file 131.
FIG. 10 is a second diagram illustrating a data structure example of the latest record table. The latest record table 141 n corresponds to the update data of item number 19 in the update log file 131. In other words, the latest record table 141n specifies the latest state of the record with the record number “1” in the slip management table 111.

Next, a processing procedure of the DB server 100 having the above configuration will be described. The processing shown below is executed periodically, for example, during degenerate operation.
FIG. 11 is a flowchart showing the update log compression processing. In the following, the process illustrated in FIG. 11 will be described in order of step number.

  [Step S <b> 1] The analysis processing unit 170 determines whether the update log file 131 exists in the update log storage unit 130. If there is an update log file 131, the process proceeds to step S2. If there is no update log file 131, the process ends.

[Step S2] The analysis processing unit 170 acquires one of the oldest update data among the unprocessed update data from the update log file 131.
[Step S3] The analysis processing unit 170 determines the update type described in the update data. In the case of “UPDATE”, the process proceeds to step S4. In the case of “DELETE”, the process proceeds to step S5. In the case of “INSERT”, the process proceeds to step S6.

[Step S4] The analysis processing unit 170 overwrites and records the updated contents in the latest record table 141 stored in the latest record storage unit 140.
[Step S5] The analysis processing unit 170 sets the deletion flag item of the latest record table 141 stored in the latest record storage unit 140 to “ON”.

  [Step S6] The analysis processing unit 170 determines whether all update data included in the update log file 131 has been processed. If all the update data has been processed, the process proceeds to step S7. It is assumed that the latest record table 141n is stored in the latest record storage unit 140 when the process proceeds to step S7. If there is unprocessed update data, the process proceeds to step S2.

  [Step S7] The compression processing unit 180 refers to the latest record table 141n and generates single update data for each record. The single update data is update data for updating each data item with one processing command (“UPDATE” or “DELETE”) for the record. At this time, the compression processing unit 180 includes only data items in which the update value of the latest record table 141n is different from the initial setting in the update data. When updating the record (when the deletion flag is “OFF”), update data of the update type “UPDATE” is generated. When deleting a record (when the deletion flag is “ON”), update data of the update type “DELETE” is generated. The compression processing unit 180 describes the generated update data in the update log file 131.

[Step S8] The compression processing unit 180 deletes update data other than the update data generated in step S7 stored in the update log storage unit 130 (excluding the default update data).
In this way, the analysis processing unit 170 and the compression processing unit 180 reduce the data amount of the update log file 131.

  FIG. 12 is a first diagram illustrating an update log file after compression processing. The update log file 131a is generated by the compression processing unit 180 based on the update log file 131 and the latest record table 141n, and is an update log after processing by the compression processing unit 180 in step S8 of FIG. As compared with the update log file 131, it can be seen that the update data of item number 20 is added and the data of item numbers 2 to 19 are deleted.

  In particular, the update data of item number 20 describes a process for updating the slip state to “completed” for the target slip management record. This corresponds to the updated content (B) of the latest record table 141n. On the other hand, in the update data of item number 20, the process corresponding to the update content (A) of the latest record table 141n is not described. This is because the fetching flag “OFF” indicated in the update data of item number 1 is the same as the latest setting “OFF” of the fetching flag specified in the update content (A) of the latest record table 141n. is there. That is, since there is no need for updating, it is possible to omit the description of the processing relating to the data item.

Next, another example of the latest record table 141n and another example of the update log file 131a generated by the compression processing unit 180 according to the example will be specifically described.
FIG. 13 is a second diagram illustrating an update log file after compression processing. First, the latest record table 141x shows another example of the latest record table 141n. Specifically, an item of update content (C) is added. In the item of the update content (C), the item name “slip serial number” and the update value “D1001” are set. This indicates that the slip serial number is changed to “D1001” for the record number “1”. The update content (C) is specified by update data separate from the update content (B) from the update log file before compression.

  The compression processing unit 180 generates the update log file 131b based on the update log file before the compression process and the latest record table 141x. Here, in the update log file before compression processing, the update type of the update data of the initial setting (item 1) is “INSERT”, the fetching flag is “OFF”, the slip state is not “complete”, and the slip sequence number is “ It is assumed that it is other than D1001 ". In this case, since the update type is “UPDATE”, the update data of item number 1 can also be deleted as described above.

  In the update log file 131b, in addition to the update data of item number 1, update data of item number 31 is described. The update data of the item number 31 describes a process for updating the slip state to “completed” and the slip serial number to “D1001” for the target slip management record. This corresponds to the update contents (B) and (C) of the latest record table 141x. In addition, in the update data of item number 31, a process corresponding to the update content (A) of the latest record table 141x is not described. This is because the initial setting flag “OFF” is the same as the latest setting “OFF” of the extraction flag specified by the update content (A) of the latest record table 141x.

  As described above, the compression processing unit 180 combines a plurality of update contents described in a plurality of update data before the compression process into a single update data, and describes them in the update log file. Then, a plurality of update data describing the update contents of the slip management record is deleted from the update log file before compression. As a result, an update log file 131b is generated.

  Thereby, the data amount of an update log file can be reduced efficiently. In particular, a plurality of update contents are combined into a single update data. Therefore, if the synchronization process is performed using the update log file 131b, the number of update processes can be reduced as compared with the case where synchronization is performed using the update log file before compression. Therefore, the synchronization process can be performed at high speed.

  At this time, the update process is not described in the update data for data items that are not different between the initial setting and the latest setting. Therefore, the data amount of the update log file can be further reduced. Further, it is not necessary to perform update processing for the data item in the synchronization processing. Therefore, the synchronization process can be performed at a higher speed.

  Such control includes a data item in the update log file that is updated only when used for data processing, such as an exclusion flag such as a fetching flag, and returns to the original setting when the data processing is completed. Is particularly effective. This is because such an exclusive flag is finally returned to the original set value, although it is frequently updated in a series of data processing. Therefore, if all these update processes are reproduced during the synchronization process, the process is likely to be wasted.

  FIG. 14 is a third diagram illustrating the update log file after the compression processing. First, the latest record table 141y shows another example of the latest record table 141n. Specifically, the deletion flag is set to “ON” for the slip management record with the record number “2”. This indicates that “DELETE” processing has been performed on the record number “2”. It is assumed that a plurality of “UPDATE” processes are described for the slip management record with the record number “2” in the update log file before the compression process. It is assumed that the initial setting is also acquired by a plurality of update data including the update type “UPDATE”.

  The compression processing unit 180 generates the update log file 131c based on the update log file before the compression process and the latest record table 141y. In the update log file 131c, the update data of item number 41 is described. In the update data of the item number 41, a process for deleting the target slip management record is described.

  In this way, even if a plurality of update contents are described with a plurality of update data before the compression processing, the compression processing unit 180 only displays the update data describing the deletion processing when the deletion processing is performed. Generate and delete other update data. The update data other than the update data describing the deletion process can be deleted because it is considered that the deleted slip management record is not used for a new process thereafter.

  Thereby, the data amount of an update log file can be reduced more efficiently. Specifically, since update data indicating processing other than the deletion processing is deleted, the amount of data corresponding to the deleted update data can be reduced. Further, if the update log file 131c is used, it is not necessary to perform processing other than the deletion processing for the slip management record in the synchronization processing. Therefore, the synchronization process can be performed at a higher speed.

  In particular, when generating update data for record deletion processing, as shown in the update log file 131c, update data described in the update type “UPDATE” may be deleted including the initial setting ( Update data described by the update type “DELETE” remains). This is because it is useless to reproduce the update process at the time of synchronization for the deleted record.

  Further, if the above-described compression processing is periodically performed, the increase amount of the update log file can be reduced. Therefore, even if the maximum data amount of the update log file is limited to a predetermined amount, a time margin is obtained until the data amount of the file reaches the predetermined amount. As a result, it becomes easy to secure the operating time of the degenerate operation, the maintenance time, and the like.

  The information processing program, information processing apparatus, and information processing method of the present invention have been described based on the illustrated embodiments. However, the present invention is not limited to these, and the configuration of each unit is an arbitrary configuration having the same function. Can be substituted. Moreover, other arbitrary structures and processes may be added. Further, any two or more configurations (features) of the above-described embodiments may be combined.

DESCRIPTION OF SYMBOLS 1 Information processing apparatus 1a Memory | storage means 1b Identifying means 1c Processing means 2 Record 2a, 2b, 2c Data item 3 1st update data group 3a, 3b, 3c, 3d, 3e, 3f, 3g 1st update data 4 2nd Update data for

Claims (5)

Computer
Storage means for storing an initial setting of a record including a plurality of data items, and a plurality of first update data indicating update contents from the initial setting for the plurality of data items;
Referring to the storage means, a specifying means for specifying the latest update data for each of the plurality of data items for a data item whose setting by the latest update data is not the same as the initial setting;
Using the latest update data of all the data items specified by the specifying means, one second update data for the plurality of data items is generated and stored in the storage means, and the storage means Processing means for deleting a plurality of first update data;
An information processing program that functions as a computer program. The processing means includes a description of a process for deleting the record when deletion of the record is specified as the latest update data for any of the plurality of data items by the specifying means. Generate update data,
The information processing program according to claim 1. The computer,
Synchronization processing means for synchronizing the setting of the record with the setting of the record stored in another computer using the second update data stored in the storage means;
The information processing program according to claim 1, wherein the information processing program is made to function as: Storage means for storing an initial setting of a record including a plurality of data items, and a plurality of first update data indicating update contents from the initial setting for the plurality of data items;
With reference to the storage means, among each of the plurality of data items, a specifying means for specifying the latest update data for a data item whose setting by the latest update data is not the same as the initial setting;
Using the latest update data of all the data items specified by the specifying means, one second update data for the plurality of data items is generated and stored in the storage means, and the storage means Processing means for deleting a plurality of first update data;
An information processing apparatus comprising: A computer information processing method,
With reference to storage means for storing an initial setting of a record including a plurality of data items and a plurality of first update data indicating update contents from the initial setting for the plurality of data items, the plurality of data items Of each, the latest update data is specified for the data item whose setting by the latest update data is not the same as the initial setting,
Using the latest update data of all the specified data items, one second update data for the plurality of data items is generated and stored in the storage unit, and the plurality of first items are stored in the storage unit. Delete update data,
An information processing method characterized by the above.

Images