JPH08194638A - Database backup method and database backup device at specified time - Google Patents

Abstract

PURPOSE: To generate a saving data base at designated time without stopping an on-line job by generating the backup at the designated time corresponding to data before updating and updating time for each prescribed part stored after the designated time. CONSTITUTION: An on-line program 200 updates a ledger data base(DB) 100 based on the updating requests of the ledger DB 100 inputted from a window terminal 600 and an automatic teller machine 700 and writes ledger data before updating into a temporary saving DB 110 together with saving date and time when updating is requested from the respective terminals 600 and 700 after the lapse of reference time while referring to a reference time table 130. Then, a saving DB generation program 300 stores the ledger data of the ledger DB 100, which is not updated after the reference time, and ledger data stored in the temporary saving DB 110 and updated after the lapse of reference time in a saving DB 120 and prepares the backup of data base at the designated time by performing batch processing.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database backup method and a database backup device at a designated time, and more particularly, to stopping update processing of a ledger database by an online program in a system operating online business such as a financial system. Without, that is,
The present invention relates to a database backup method and a database backup device at a designated time for batch processing without interrupting the update operation of a ledger database being used in an online system.

The operation hours of online business of financial institutions tend to be extended, and it is expected that 24-hour continuous operation will be performed in the near future, whereas it is necessary to save the ledger database at a designated time during the online business. Therefore, a system applied to such a system that travels without interruption is desired.

[0003]

2. Description of the Related Art FIG. 26 shows an operating form of a banking online system in a conventional financial institution. In the figure, a indicates a calendar day, b indicates the time of the calendar day, c indicates the business status for each time, and d indicates the date when the data processing is performed. Most conventional system operation forms in financial institutions start online business before 9:00 am and finish online business after 7:00 pm. Online business will start at 8:45 am on the first day of the calendar day and will end at 19:30 on the same day. 1
At the end of the day online, save the ledger database. The save processing creates a save database of the ledger database at 7:30 pm, which is the end time of online. When the creation of the evacuation database is completed, the date of the ledger database for data processing on the next day 2 is changed at 23:00 on the first day of the calendar day. Next, after 23:00 on the first day of the calendar day when the above processing is completed, batch processing incidental to online work is performed. Examples of the processing incidental to the online business include, for example, processing of totaling the deposit holding amount, the total amount of cash withdrawal, etc. of all banks (head offices) at the end of the online day on a calendar day.

When a series of processes such as online work within a predetermined time, a ledger database save process, and an online incidental batch process are completed, the system is in a dormant state until a predetermined time. Thus, like a conventional system,
Online business, separated by a predetermined processing time
Performs batch processing tasks.

[0005]

However, when it becomes necessary for the online system of a financial institution to carry out continuous operation for 24 hours, the conventional operation mode of online business and batch business can be performed in processing time zones. It becomes impossible to divide, and it becomes necessary to process online programs and batch programs in parallel.

As a result, for example, the ledger database cannot be specified on the application at the end of the online business on the last day of the month, and the totaling work by batch processing on the last day of the month becomes impossible while the online system is being executed. That is, there is a problem that it is not possible to secure a time zone for saving the ledger database.

The present invention has been made in view of the above points, and a database backup method and a database for a specified time that can create a save database at a specified time without requiring the suspension of online business. The purpose is to provide a backup device.

[0008]

FIG. 1 is a flow chart for explaining the first principle of the present invention. In order to solve the above problems, a database backup method of the present invention is a method of creating a backup of a database at a specified time in a system having a database, in which a backup time for obtaining a backup of the database is set after the specified time. Specify (Step 1
-1) For an update request for a predetermined location of the database that occurs after the designated time, the data before the update is stored for each predetermined location (step 1-2), and is stored after the designated designated time. A backup of the database at the specified time is created based on the data and the update time before the update for each predetermined location (step 1-3).

FIG. 2 is a flow chart for explaining the second principle of the present invention. The present invention provides a method for backing up a database at a specified specified time in a system having a database, wherein a backup acquisition time for acquiring backup data of the database is specified before the specified time (step 2 -1) The backup data is acquired before the specified time, and the data indicating the backup acquisition time is stored for each predetermined location of the database from which the backup was acquired (step 2-2). The update request is updated at each predetermined location, the updated value and the update time are stored (step 2-3), and the specified time and the acquisition time when the stored backup data is acquired are stored. Data shown,
The backup data acquired before the specified time is corrected based on the updated value at each predetermined location and the data indicating the update time (step 2-4).

FIG. 3 is a flow chart for explaining the third principle of the present invention. The present invention is a method of creating a backup of a database at a specified time in a system having a database, by specifying a backup acquisition time for acquiring backup data of the database after the specified time (step 3-1) and at a predetermined location of the database. When the update request is issued, the backup data before the update for each predetermined location and the acquisition time are stored (step 3-2), and the update request for the predetermined location of the database is updated for each predetermined location and updated. The subsequent data and the update time are stored (step 3-3), and the backup data and the acquisition time thereof are stored, based on the stored value after update for each predetermined portion of the database and the update time. , Correct the backup data (Step 3-
4).

The database backup apparatus of the present invention is, in the database system, a time designating means for setting a designated time which is a time corresponding to the acquisition state of the database backup, and a backup time for obtaining the database backup after the designated time. The evacuation time setting means for designating, the temporary evacuation means for storing the data indicating before the update for each predetermined location with respect to the update request for the predetermined location of the database generated after the designated time, the data stored by the temporary evacuation means and the Backup generating means for creating a backup of the database based on the database.

Further, the database backup apparatus of the present invention is, in the database system, a time designating means for setting a designated time which is a time corresponding to the acquisition state of the backup of the database, and the backup data is obtained before the designated time. The temporary saving means for storing the acquired time together, the update information storage means for storing the updated data and the update time for each predetermined location in response to the update request for the predetermined location in the database, and the temporary saving means for storing the updated time. Existing data and backup generation means for creating a backup of the database with the data stored in the temporary saving means according to the information stored in the update information storage means.

Further, the database backup device of the present invention is, in the database system, a time designating means for setting a designated time which is a time corresponding to a backup acquisition state of the database, and an issuance request for an update request at a predetermined portion of the database. Temporary saving means for storing backup data and update time before update for each predetermined location, update information storage for updating each predetermined location based on an update request for a predetermined location in the database, and storing the updated value and update time And a backup generation unit that creates a backup of the database using the data stored in the temporary saving unit and the data stored in the update information storage unit.

[0014]

According to the first method of the present invention, while updating the data in the database in response to the update request, the time at which the database is backed up is after a predetermined specified time, and the online update request is issued after the specified time. In this case, first, the data before update is temporarily saved, and when the save database at the specified time is created, regarding the data updated by the update request,
Data that has been temporarily saved is read, and data that has not been updated is created by reading the data in the database itself. FIG. 4 is a diagram for explaining the first method of the present invention. As shown in the figure, when the update request is first issued after the designated time (a), the ledger data before the update is written (b) and the temporary save data is created (c). In the database save process (d), if the update occurs after the reference time, the temporary save data is written as the save database (e). If the update has not occurred after the reference time, the ledger data is written (f).

The second method of the present invention temporarily saves the database before the specified time, stores the save time at that time, and updates the data in the database in response to the update request. The updated data and the update time are stored. Compare the specified time with the update time and the temporarily saved time.If the updated time is before the specified time and closest to the specified time, the updated data is read and the temporarily saved time becomes the specified time. If it is close, the temporarily saved data is read and the saved database is created. Therefore, by comparing the temporary save data with the updated data and writing the data that has the time before the specified time and closest to the specified time to the save database, the data updated before the specified time and after the temporary save is also saved. Processing becomes possible. FIG. 5 shows the second aspect of the present invention.
FIG. 6 is a diagram for explaining the method of FIG. As shown in the figure,
If the update request is issued before the specified time, the ledger data is updated (a), the update history data is acquired,
Remember (b). Further, the ledger data is temporarily saved, and the temporary save time and the saved data are held (c). Also,
When the update request is issued again before the designated time, the ledger data is updated (d) and the update history data is created (e). When the save database is created after the specified time, the data closest to the specified time before the specified time is created by referring to the creation date and time of the update history data and the temporary save data (f).

Further, according to the third method of the present invention, when the update request is issued after the designated time, the data before the update is held, and the updated data and the update date and time are held. Further, the data is temporarily saved after the designated time, and the temporary save time is held together with the data. Here, when creating the save database, the data closest to the specified time after the specified time is selected by referring to the update date and time and the temporary save time, and written to the save database. FIG. 6 is a diagram for explaining the third method of the present invention. When an update request is issued after the designated time (a), first, the ledger data before the update is written as update history data and the written time is also recorded (b). Here, the database is temporarily saved (c)
At the same time, the time of temporary evacuation is also recorded. Further, when the update request is issued (d), the ledger data before the update is written out as the update history data as well as the above, and the written time is also recorded (e). When creating the save database, refer to the time information (save date and time, write date and time) of the temporary save data and update history data, and create the data closest to the specified time after the specified time as save data (f) .

As described above, according to the present invention, even when the online system is operated for 24 hours, the update date and time before or after the update and the data before the update or the data after the update are recorded, so that there is no contradiction. Processing is realized.

[0018]

Embodiments of the present invention will now be described in detail with reference to the drawings. In the following embodiments, banking online, which is processed online at a financial institution, will be described as an example.

<< First Embodiment >> FIG. 7 shows a system configuration of a first embodiment of the present invention. The system shown in the figure is
Counter terminal 600 used at a bank counter, automated teller machine 700 used by depositors, etc., control program 500 for controlling terminals and databases (hereinafter DB), various online programs such as deposit programs, loan programs, exchange programs, etc. 200, a batch program 300 that performs batch processing such as a save DB creation program, a reference time table 130, a ledger DB 100 that is updated every moment based on an update request by the online program 200, and the contents of the ledger DB 100 before the reference time are temporarily saved. Temporary evacuation DB 110 for storing, ledger DB 1 at the time of the reference time
00 is saved in the save DB 120.

FIG. 8 shows the data flow of the first embodiment of the present invention. The same components as those in FIG. 7 are designated by the same reference numerals.
Upon receiving the update request from the teller terminal 600 or the automatic teller machine 700, the online program 200 refers to the reference time table 130 and obtains the reference time. In this embodiment, the reference time is the ledger D at that time.
It is a time designated in advance to acquire the state of B100. For example, 0:00 is set in the case of date / time processing, and the last day of the month is set in the case of monthly processing.

The online program 200 is a ledger DB input from the teller terminal 600 and the automated teller machine 700.
While updating the ledger DB 100 based on the update request of 100, the reference time table 130 is referred to, and when the update request is issued from each of the terminals 600 and 700 when the reference time has elapsed, the ledger before update The data is written to the temporary save DB 110. At this time, the evacuation date and time (year, month, day,
(Hour, minute, second) are also written to the temporary save DB 110.

The save DB creation program 300, which is a batch program, saves the data that remains in the state before the elapse of the reference time even after the elapse of the reference time, that is, the ledger data of the ledger DB 100 that has not been updated after the reference time, as it is.
Store in B120. Further, the ledger data updated after the elapse of the reference time and stored in the temporary save DB 110 is stored in the save DB 120.

FIG. 9 shows the structure of a record of ledger data according to the first embodiment of the present invention. The ledger data is head office code 1011, account number 1012, name 1013, address 1
014, the customer identification information 1010 including the deposit type 1015 and the update date / time 1020 when the ledger data was updated by the update request, the temporary save date / time 1030 saved in the temporary save DB 110, the ledger data 1040, etc. Composed.

The detailed operation of this embodiment will be described below. FIG. 10 is a flowchart showing the operation of the online program according to the first embodiment of this invention. Step 1001) The online program 200 receives a processing request message (update request) from the teller terminal 600 or the automated teller machine 700.

Step 1002) Reference time table 1
The reference time is read from 30, and the current time is acquired from the system clock. Step 1003) It is determined whether the present is after the reference time based on the acquired reference time and the current time.

Step 1004) As a result of the determination, if the current time is before the reference time, the process proceeds to step 1006.
If the current time (at the time of receiving the processing request message) is after the reference time, it is determined whether the ledger data is written in the temporary save DB 110 as the temporary save data after the reference time.
If it has already been written, the process proceeds to step 1006. When writing to the temporary save DB 110 for the first time,
The process moves to step 1005.

Step 1005) The ledger DB 100 is read, the ledger data before updating is written to the temporary save DB 110, and the temporarily saved date of temporary save is recorded at the temporary save date 1030 of the ledger data. Step 1006) Next, the online program 20
0 updates the ledger data in the ledger DB 100 based on an update request from the terminal 600 or 700.

Step 1007) When the update of the ledger DB 100 is completed, a processing result notification is transmitted to the terminal 600 or 700 which issued the update request. Here, in step 1004, as for the determination as to whether or not the temporary saving DB 110 has already been written, if the temporary saving date 1030 shown in FIG. This means that the data has not been saved.

FIG. 11 is a flow chart showing the operation of the save database creating program of the first embodiment of the present invention. Step 1009) The save DB creation program 300 for creating the save DB 120 is the reference time table 1
The reference time is read from 30.

Step 1010) Furthermore, the ledger DB1
The ledger data is read from 00. Step 1011) When the ledger DB 100 has been read to the end, the processing ends. (Step 1012) It is determined whether the read ledger data has already been temporarily saved. Here, it is determined whether or not the ledger data is temporarily saved by the ledger DB 100.
When the time after the reference time is set in the column of temporary save date 1030 of, the ledger data has already been saved in the temporary save DB 110.

Step 1013) If the ledger data has been saved, the customer identification information 10 in the ledger DB 100
Temporary evacuation DB1 with 10 account numbers 1012 as keys
10 is searched and the retrieved temporary save data of the temporary save DB 110 is written to the save DB 120. The above process is repeated until all the processes of the evacuation target ledger DB 100 are completed.

When the time is not set in the temporary saving date 1030 of the read ledger data, or
If the time before the reference time is set, it means that the ledger data is not saved in the temporary save DB 110, and therefore the save DB creation program 300 writes the ledger data in the save DB 120.

Next, this embodiment will be described by showing a concrete example. FIG. 12 shows a specific example of the first embodiment of the present invention. (1) The save DB creation program 300 acquires the reference time from the reference time table 130. In this example, it is assumed that “12:00” is acquired as the reference time. (2) In the ledger DB 100, account numbers “001” and “0”
The ledger data of “02” exists. Account number “00
The initial balance for both 1 "and" 002 "is 10,000 yen. (3) For the ledger data of account number" 001 "," 1 "
Since the processing request was issued from the terminal 600 at “2:00”, the online program 200 updated the 3,000 yen withdrawal.

In this case, since the update process for this ledger data is after the reference time "12:00",
The online program 200 has been updated before
Minute) ledger data in the state of a balance of 10,000 yen is saved in the temporary save DB 110. At this time, the ledger data before the update is set to "12:01
"Minute" is added and written to the temporary save DB 110. At the same time, the ledger data temporary save time setting field 1030
“12:01” is set as the temporary save time.
After this, the ledger data in the ledger DB 100 is updated,
The balance after updating "12:01" will be 7,000 yen.

(4) From the online program at “12:15” for the ledger data of the account number “001”
2,000 yen withdrawal renewal process was performed. In this case, when the ledger data is sequentially read, the temporary saving is performed at “12:01”, and therefore the saving process to the temporary saving DB 110 is not performed, but only the updating process of the ledger DB 100 is performed. Therefore, the balance of the account number "001" is updated to 5,000 yen. At this time, the update date and time "12:15" is the ledger 1
00 in the update date / time column 1020.

(5) Saving DB1 at "12:00"
The save DB creation program 300 that executes the batch process of creating 20 was executed at “12:30”. The ledger data of the account number “001” is in the state of “12:00” and the temporary saving date and time 1030 of the ledger data of the ledger DB 100 is set.
Referring to, it can be seen that the temporary save data exists because the update process was performed at “12:01”. In this case, the ledger data “10,000 yen” before the update is read from the temporary save DB 110 and written to the save DB 120.

If the temporary save date / time column 1030 of the ledger data of the account number "002" is blank or a time earlier than the reference time is set and no temporary save data exists, A balance of 10,000 yen is written as data stored in the save DB 120 by the batch process (save DB creation program 300). After the temporary save data is saved in the save DB 120, the temporary save D
B110 is cleared.

FIG. 13 shows an operating mode of the first embodiment of the present invention. As shown in the figure, in this embodiment, when the reference date and time is 24:00 (0:00), the calendar date 1
It is possible to create the evacuation DB 120 at 24:00 on the day on the second day of the next day, and to create the evacuation DB 100 at 24:00 on the second day of the calendar day on the third day. Therefore, while performing the online update process,
The evacuation DB creation program 300 temporarily saves the ledger data that has been updated after the reference time as temporary evacuation data, writes it to the evacuation DB 120, and saves the ledger data that has not been updated even after the elapse of the reference time to the evacuation DB 12
It is saved to 0 as it is. As a result, the save DB 120
It is possible to perform batch processing such as tabulation at any time using. In addition, the ledger DB used online
It is assumed that the date and time change of 100 at 24:00 is automatically changed based on the system timer.

As described above, according to this embodiment, the ledger DB
When the content of 100 is not updated even after the reference time has elapsed, the content of the ledger DB 100 itself is saved in the DB 120.
If it is saved in and updated after the reference time has passed,
Save the contents stored in the temporary save DB 110 to the save DB 1
It is possible to evacuate to 20. As a result, the save DB creation program 300 can perform a time-consistent save process in any time zone.

<< Second Embodiment >> FIG. 14 shows a second embodiment of the present invention.
2 shows a system configuration of the embodiment. The system shown in the figure includes a teller terminal 600 used at a bank teller, an automatic teller machine 700 used by depositors, a control program 500 for controlling a terminal and each database (DB), a deposit program, a loan program, Various online programs 200 such as exchange programs, temporary save DB creation program 310, batch program 300 for performing batch processing of save DB creation program 320, reference time table 1
30, ledger DB100, ledger DB100 that is updated momentarily by the online program 200 based on the update request
Temporary save DB 11 for temporarily saving the contents of
0, a save DB 120 for saving the contents of the ledger DB 100 at the time of the reference time, a reference time table 130 that stores the reference time for changing the date to be aggregated in the batch process, and an update of the ledger DB 100. The update history file 140 holds data and time.

In this embodiment, every time the online program 200 updates the ledger DB 100 using the temporary save DB creation program 310 and the save DB creation program 320, which are batch programs, the ledger data is stored in the update history file 140. Incidentally, the contents of the ledger DB 100 that is closest to the reference time before the reference time are stored in the save DB 120.

FIG. 15 shows the data flow of the second embodiment of the present invention. The same components as those in FIG. 14 are designated by the same reference numerals. First, the online program 200 is the window terminal 60
0 or an update processing request input from the automatic teller machine 700 at any time is received, and the ledger data in the ledger DB 100 is given an update date and time to update the ledger data. Further, the update date and time is added to the ledger data as history time and recorded in the update history file 140. The ledger data has the same structure as that shown in FIG. 9 in the first embodiment.

The temporary save DB creation program 310, which is a batch program, saves the entire ledger DB 100 at an arbitrary time before the reference time in the temporary save DB 110.
Next, the save DB creation program 320 sequentially reads the temporary save data of the temporary save DB 110 and the data of the update history file 140 from the beginning after the reference time, and performs the matching process of each data.

In the save DB creation program 320,
When the data in the temporary save DB 110 and the data in the update history file 140 are matched, the last update date and time of the ledger data recorded in the temporary save data in the temporary save DB 110 and the update history data in the update history file 140 are recorded. Compare history times. As a result of the comparison, the data closest to the reference time before the reference time is selected, and the save DB1
Write to 20.

At the time of matching, if temporary save data exists in the temporary save DB 110 and update history data does not exist in the update history file 140, the temporary save data is written to the save DB 120. Further, although the temporary save data does not exist in the temporary save DB 110, the update history file 14
When the update history data exists in 0, data whose history time recorded in the update history data is before the reference time and closest to the reference time is selected and written to the save DB 120.

FIG. 16 is a flow chart showing the operation of the online program according to the second embodiment of the present invention. The online program 200 updates the ledger DB 100 and generates history data of the update history file 140. Step 2001) The online program 200 receives a processing request message from the teller terminal 600 or the automatic teller machine 700.

Step 2002) The online program 200 updates the ledger DB 100 by adding update date and time to the ledger data in the ledger DB according to the processing request message. (Step 2003) The updated ledger data is used as update history data, and the update date and time is similarly given and written in the update history file 140.

Step 2004) Next, the window terminal 600 or the automated teller machine 700 is notified that these processes have been completed. FIG. 17 is a flowchart showing the operation of the temporary save DB creation program according to the second embodiment of this invention.

Step 2005) The temporary save DB creation program 310, which is a batch program, first reads data in the ledger DB 100 one by one at an arbitrary time within the reference time. Step 2006) When the reading of the ledger DB 100 is completed, the process is ended.

Step 2007) Each time each data is read, the ledger data and the save time are written in the temporary save DB 110. The process is repeated until the reading of all the ledger data is completed. 18 and 19 are flowcharts showing the operation of the save DB creation program according to the second embodiment of this invention.

Step 2100) The save DB creation program 320 first sorts the update history files 140 in descending order by account number and time. (Step 2101) The reference time is read from the reference time table 130. (Step 2102) Temporary save data is sequentially read from the temporary save DB 110 in descending order.

Step 2103) Temporary save DB 110
When the above has been read to the end, the procedure moves to step 2116. (Step 2104) Each time the temporary save data is read, the update history data is sequentially read from the update history file 140.

Step 2105) Update history file 1
When the reading of 40 is completed, the process proceeds to step 2117. Step 2106) Select the data whose update date and time within the same key (account number, time) of the read update history data is earlier than the reference time and closest to the reference time.

Step 2107) Next, a process of matching the temporarily saved data with the update history data is performed. (Step 2108) As a result of the matching process, if the matching is successful, the process proceeds to step 2109, and if only update history data exists, step 211.
If there is only temporarily saved data, the process proceeds to step 2113.

Step 2109) If the data close to the reference time is temporary save data, step 2110
If it is update history data, go to step 2
Move to 111. (Step 2110) Save the temporary save data to the save DB 120
To step 2102.

On the other hand, when the update history data is close to the reference time, the update history data is saved D
Write to B120. (Step 2112) Next, if only the update history data exists as a result of the matching, the update history data is written to the save DB 120, and the process proceeds to step 2104.

Step 2113) If only temporary save data exists as a result of the matching, the temporary save data is written to the save DB 120. (Step 2114) After that, the temporary save data is read from the temporary save DB 110.

Step 2115) When the temporary save data is completed, the process moves to step 2116. (Step 2116) If all the data in the update history file 140 has been read, the process ends, and if there is remaining data, the process moves to step 2104.

[Step 2117] Also, the temporary save DB
If all 110 data has been read, the process ends,
If there is remaining data, save the temporary saved data D
Write to B120 and move to step 2102. Next, this embodiment will be described by showing a concrete example. FIG.
Shows a specific example of the second embodiment of the present invention.

(1) The reference time is set to "12:00". That is, the save DB creation program 320 acquires “12:00” from the reference time table 130. (2) In the ledger DB 100, account numbers “001” and “0”
02 ”ledger data exists. Account number“ 001 ”,
The ledger data of “0:00” of “002” is 10,000 yen.

(3) 3,000 from account number "001" to "10:05" by online program 200
Since there was a withdrawal of yen, the current balance of "10:05" of the account number "001" was set at 7,000 yen, and the time of the update "1"
"05:05" is added to update the contents of the ledger DB 100, and the update history file 140 has update balance data of 7,000 yen as the update history data.
Minutes ”is added and recorded.

(4) At "11:15", the batch program temporary save DB creation program 310 is the ledger DB 10
The account numbers “001” and “002” of the ledger data of 0 are read, and the ledger data of the account number “001” (7,000
Yen) and ledger data for account number “002” (10,000 Yen)
To the temporary save DB 110.

(5) The account number "00" at "11:40"
Since there was a withdrawal processing of 2,000 yen from 1 ", the balance of account number" 001 "was set to 7,
000 yen-2,000 yen = 5,000 yen, while updating the ledger DB100, the balance at "11:40" is 5,000
The ledger data that is a circle and the update time “11:40” are written to the update history file 140.

(6) Account number "00" at "12:15"
Since there was a withdrawal of 1,000 yen from 1 ”, the online program 200 set the account number“ 001 ”to“ 12:15
Minutes ”The current balance is set at 5,000 yen-1,000 yen = 4,000 yen, and the ledger DB 100 is updated, and the update time is“ 12.
15 minutes ”is added. In addition, the updated ledger data 1,
Write 000 yen and the update date and time to the update history file 140.

(7) The account number "00" at "12:20"
Since there was a withdrawal of 3,000 yen from 2 ", the online program 200 is" 12:20 "for the account number" 002 ".
The current balance is set at 10,000 yen-3,000 yen = 7,000 yen and the ledger DB 100 is updated, and the update time is "12:20.
Minutes ”. Update date and balance of "12:20"
The ledger data of 7,000 yen is written in the update history file 140.

(8) Save DB creation program 320 for creating the save DB 120 at the reference time "12:00"
Was executed from "12:30". Since the reference time “12:00” has already passed when the save DB 120 was created, the ledger data of the account number 001 is from the time when the temporary save data is written to the time “12:00”. Since an update has occurred in the meantime, among the update history data written at the time of update, "12: 00" and before "12
The update history data (“11:40”, balance 5,000 yen) at the time closest to “hour 00” is written to the save DB 120.

Since the ledger data of the account number "002" has not been updated from the time ("10:15") when the temporary save data was written to the reference time "12:00", The temporary save data at “11:15” is written to the save DB 120.

That is, the data in the temporary save DB 110 and the data in the update history file 140 after "00:00" are read in descending order, and the matching of these data is performed. Select close data. The update history data before the reference time of the account number "001" and closest to the reference time is "11".
The current data, and the temporary save data is "1 hour 40 minutes".
0:15 ”Since it is the current data, the data at 11:40 is saved in the save DB 120.

Update history file 140 and temporary save DB1
Update history file 1 without reading 10 and matching
If only the data of 40 exists, the data of the update history file 140 that is closest to the reference time before the reference time is saved in the save DB 120. If only data in the temporary save DB 110 exists, save D
The temporarily saved data is saved in B120. Account number "00
In the case of 2 ", the data before the reference time" 12:00 "is temporarily saved at" 10:15 "in the temporary save DB.
Only the temporary saving data of 110 (balance 10,000 yen) is saved in the saving DB 120.

After being saved in the save DB 120, the temporary save DB 110 is cleared. FIG. 21 shows an operating mode of the banking system according to the second embodiment of the present invention. As shown in the figure, when the date for data processing is changed at 24:00 on the calendar day, the ledger data in the ledger DB 100 is read from 21:00 on the first day of the calendar day and temporarily saved.
The creation of B110 is started and finished by 24:00 on the day. Further, every time the ledger DB 100 is updated by the online program 200, the update history file 1
40 stores updated ledger data and update date and time. Therefore, since the ledger data updated on the calendar day date 1 day after being stored in the temporary save DB 110 on the calendar day date 1 day is stored in the update history file 140, the date changes on the calendar day date 2 day. However, the update history file 14
By referring to 0 and the temporary save DB 110, it is possible to create the save DB 120 at 24 o'clock on the calendar day 1st.

As described above, according to the second embodiment, the updated ledger data and the update time are stored in the temporary save DB 110, and the date and time when the ledger data was updated and the updated data are recorded in the update history. Stored in the file 140, and after the reference time, the temporary save DB 110 and the update history file 1
40 data is read in sequence, and temporary save DB110
Alternatively, the data closest to the reference time before the reference time of the update history file is selected and saved in the save DB 120. As a result, the save DB that is a batch processing program
The creation program 320 is capable of performing save processing without contradiction in any time zone.

<< Third Embodiment >> A third embodiment of the present invention will be described below. FIG. 21 is a flow chart showing the operation of the online program according to the third embodiment of the present invention.

Step 3001) The online program 200 receives a processing request message from the window terminal 600 or the cash dispenser 700. Step 3002) The contents of the ledger data before the update and the update date and time are added and written as update history data in the update history file 140.

Step 3003) Next, according to the processing request message, the ledger data in the ledger DB 100 is updated, and the update date and time is given. Step 3004) Send a message to notify the processing result to the terminal. Here, temporary save D which is a batch program
The processing of the B creation program 310 is the same as that of the second embodiment described above, so description thereof will be omitted here.

23 and 24 are flowcharts showing the operation of the save DB creating program according to the third embodiment of the present invention. Step 3100) First, save DB creation program 3
20 is a temporary save DB 110 and an update history file 1 in advance
40 is sorted in ascending order by account number and time.

Step 3101) Reference time table 1
The reference time is read from 30. (Step 3102) The temporary save data is read from the temporary save DB 110. (Step 3103) When the reading of the data in the temporary save DB is completed, the process proceeds to step 3116.

Step 3104) Update history file 1
The update history data is read from 40. (Step 3105) After reading all the data of the update history field 140, the process moves to step 3117.

Step 3106) The update date and time of the update history data (in the same account) for the same key is after the reference time and is closest to the reference time. Step 3107) The temporary save data and the update history data are matched.

Step 3108) As a result of matching,
If the matching is successful, the process proceeds to step 3109, if only the update history data exists, the process proceeds to step 3112, and if only the temporarily saved data exists, the process proceeds to step 3113.

Step 3109) It is determined whether the data close to the reference time is temporary save data or update history data. (Step 3110) If the temporary save data is closer to the reference time, the temporary save data is written to the save DB 120, and the process proceeds to step 3102.

Step 3111) If the update history data is close to the reference time, save the update history data in the DB 12
The data is written in 0 and the process proceeds to step 3102. (Step 3112) If only the update history data exists as a result of matching, save the update history data in the save DB.
The data is written in 120 and the process proceeds to step 3104.

Step 3113) As a result of matching,
If only the temporary save data exists, the temporary save data is written to the save DB 120. (Step 3114) Then, the temporary save data is read from the temporary save DB 110.

Step 3115) Temporary save DB 110
When the data reading is completed, the process proceeds to step 3116, and if not completed, the process proceeds to 3107. (Step 3116) When the reading of the data of the update history file 140 is completed, the whole process is completed, and when the data of the update history file 140 still exists, the process proceeds to step 3104.

Step 3117) Temporary save DB 110
If the data in # 1 remains, the temporary save data is written to the save DB 120, and the process proceeds to step 3102. If there is no data in the temporary save DB 110, the entire process ends. FIG. 25 shows a specific example of the third embodiment of the present invention.

(1) The reference time is set to "12:00". That is, the save DB creation program 320
Reference time “12:00” from the reference time table 130
Shall be obtained. (2) Account numbers “001” and “00” in the ledger DB 100
There is 2 "ledger data. The ledger data of the two account numbers both have information of a balance of 10,000 yen.

(3) With respect to the ledger data of the account number 001, the online program 200 updated the withdrawal of 3,000 yen at "11:15" by the update request.
The online program 200 displays the update time (“11:15
Minutes)) is added to the update history file 1
Write to 40. The balance of the ledger data at this time is 7,000 yen, and "11:15" is recorded as the update time.

(4) With respect to the ledger data of the account number "002", the online program 200 updated the 3,000 yen withdrawal at "12:10" by the update request.
The online program 200 writes the update history data in which the update time is added to the content of the ledger data before the update with the balance of 10,000 yen to the update history file 140. As the ledger data at this time, the balance is 7,000 yen and the update time is "12:10".

(5) Temporary save DB1 at "12:30"
The process of the temporary save program 310 for creating 10 is performed, and the ledger data of the account at that time is written to the temporary save DB 110 as temporary save data. That is, the temporary evacuation data for the account numbers "001" and "002" is 7,000 yen, and the evacuation time is "12:30".

(6) For the ledger data of the account number "001", the online program 200 is set at "12:45".
Has processed the renewal of the 2,000 yen withdrawal. The online program 200 adds the time when the update processing was performed to the contents of the ledger data before the update with the balance of 7,000 yen, and writes it to the update history file 140 as update history data.

(7) Online program 200 at "13:15" for the ledger data of account number "002"
Performed a renewal process for a withdrawal of 2,000 yen. The online program 200 adds the time of the update to the contents of the ledger data before the update with the balance of 7,000 yen, and stores it in the update history file 140 as the update history data.

(8) Save DB creation program 320 for creating the save DB 120 at the reference time "12:00"
The batch processing by the company started from "14:30".
The ledger data of the account number "001" is created at "12:45" because the update by the online program 200 has not occurred while the temporary save data was written after the reference time "12:00". The saved temporary save data (balance 7,000 yen, time 12:30) is written to the save DB 120. The ledger data of the account number “002” is “12
While writing the temporary save data after "00: 00",
Since the update by the online program 200 has occurred, of the update history data written at the time of update, “1
Update history data closest to "12:00" after "2:00" (balance (10,000 yen) update time (12:10))
Is written to the save DB 120.

As described above, according to the third embodiment, the ledger data before the update is stored in the update history file 140, and the temporary save DB 110 saved at any time after the reference time or In the update history file 140, the data closest to the reference time after the reference time is saved in the save DB 120. This allows the save DB creation program 300 to perform consistent backup processing in any time zone.

In the above embodiment, the save DB 120
Uses a magnetic disk device, but may be any external storage device capable of filing depending on the amount of data to be written. The present invention is not limited to the above embodiments, and various modifications and applications are possible within the scope of the claims.

[0094]

As described above, according to the present invention, when the banking online system is operated for 24 hours, the ledger data is temporarily saved by the online program or the batch program, and the ledger data is updated. It is possible to batch process the data saved after the reference time without affecting. As a result, the ledger data in the date / time processing etc. is updated at 24:00
It is updated without being aware of 0 minutes, and the update work can be performed consistently in any time zone.

[Brief description of drawings]

FIG. 1 is a flow chart for explaining a first principle of the present invention.

FIG. 2 is a flow chart for explaining the second principle of the present invention.

FIG. 3 is a flow chart for explaining the third principle of the present invention.

FIG. 4 is a diagram for explaining the first method of the present invention.

FIG. 5 is a diagram for explaining the second method of the present invention.

FIG. 6 is a diagram for explaining a third method of the present invention.

FIG. 7 is a system configuration diagram of a first embodiment of the present invention.

FIG. 8 is a diagram showing a data flow in the first embodiment of the present invention.

FIG. 9 is a diagram showing a structure of ledger data according to the first embodiment of this invention.

FIG. 10 is a flowchart showing the operation of the online program according to the first embodiment of the present invention.

FIG. 11 is a flowchart showing an operation of the save database creation program according to the first embodiment of this invention.

FIG. 12 is a diagram showing a specific example of the first exemplary embodiment of the present invention.

FIG. 13 is a diagram showing an operation of the first embodiment of the present invention.

FIG. 14 is a system configuration diagram of a second embodiment of the present invention.

FIG. 15 is a diagram showing a data flow according to the second embodiment of the present invention.

FIG. 16 is a flowchart showing an operation of the online program according to the second embodiment of the present invention.

FIG. 17 is a flowchart showing an operation of a temporary save database creation processing program according to the second embodiment of this invention.

FIG. 18 is a flowchart (part 1) showing the operation of the save database creation program according to the second embodiment of the present invention.

FIG. 19 is a flowchart (part 2) showing the operation of the save database creation program according to the second embodiment of the present invention.

FIG. 20 is a diagram showing a specific example of the second exemplary embodiment of the present invention.

FIG. 21 is a diagram showing an operating mode of the banking system according to the second embodiment of the present invention.

FIG. 22 is a flow chart showing the operation of the online program according to the third embodiment of the present invention.

FIG. 23 is a flowchart (part 1) showing the operation of the save database creation program according to the third embodiment of this invention.

FIG. 24 is a flowchart (part 2) showing the operation of the save database creation program according to the third embodiment of this invention.

FIG. 25 is a diagram showing a specific example of the third exemplary embodiment of the present invention.

FIG. 26 is a diagram showing an operating form of a conventional banking system.

[Explanation of symbols]

 100 Ledger database 101 Ledger data 110 Temporary evacuation database 120 Evacuation database 140 Update history file 200 Online program 300 Batch program 310 Temporary evacuation database creation program 320 Evacuation database creation program 500 Control program 600 Counter terminal 700 Cash machine 1011 Head office / branch name Code 1012 Account number 1013 Name 1014 Address 1015 Deposit type 1020 Update date / time 1030 Temporary evacuation date / time 1040 Ledger data

Claims (6)

[Claims] 1. A method for creating a backup of a database at a specified time in a system having a database, wherein a backup time for obtaining a backup of the database is specified after the specified time, and the backup occurs after the specified time. Regarding an update request for a predetermined location of the database, data before update is stored for each predetermined location, and after the designated time, the stored data before update for each predetermined location and update time are stored. And a database backup method at a specified time, wherein a backup of the database at the specified time is created based on the database. 2. A method of creating a backup of a database at a specified designated time in a system having a database, wherein a backup acquisition time for acquiring backup data of the database is specified before the specified time, and Previously acquired backup data, for each predetermined location of the database from which the backup was acquired, store data indicating the backup acquisition time, and for the update request of the predetermined location of the database, for each predetermined location, The updated value and update time are stored, and the designated time, data indicating the acquisition time when the stored backup data is acquired, and data indicating the updated value and update time for each predetermined location Correction of backup data acquired before the specified time based on Database backup method for the specified time and performing. 3. A method for creating a backup of the database at a specified time in a system having a database, wherein a backup acquisition time for acquiring backup data of the database is specified after the specified time, and When the update request is issued, the backup data before the update for each predetermined location and the acquisition time are stored, and the update request for the predetermined location of the database is updated for each predetermined location, and the updated data and the update time are stored. Is stored, and the backup data is corrected based on the backup data and the acquisition time of the backup data, the value after the update at each predetermined location of the stored database, and the update time. How to back up the database at the specified time. 4. In a database system, time designation means for setting a designated time, which is a time corresponding to a database backup acquisition state, and evacuation time for designating a backup time for acquiring the database backup after the designated time. Setting means, a temporary saving means for storing data indicating before update for each predetermined location of an update request for a predetermined location of the database generated after the specified time, data stored by the temporary saving means and the database A database backup device comprising: a backup generation unit that creates a backup of the database based on the above. 5. In a database system, time designation means for setting a designated time, which is a time corresponding to a backup acquisition state of a database, and backup data acquired before the designated time,
A temporary save means for storing the acquired time together, an update information storage means for storing the updated data and update time for each predetermined location in response to an update request for the predetermined location in the database, and the temporary save means A database backup comprising stored data and backup generation means for creating a backup of the database with the data stored in the temporary storage means according to the information stored in the update information storage means. apparatus. 6. In a database system, time designation means for setting a designated time, which is a time corresponding to a backup acquisition state of the database, and before issuing an update request for the predetermined location of the database, Temporary save means for storing backup data and acquisition time; update information storage means for updating each predetermined location of the database based on an update request for the predetermined location, and storing updated value and update time; A database backup device comprising: a backup generation unit that creates a backup of the database based on the data stored in the saving unit and the data stored in the update information storage unit.