JPH06187217A - System for synchronization between data base and normal file - Google Patents

Abstract

PURPOSE:To prevent a data base and a normal file from becoming asynchronous by returning even the pointer of the normal file to a last stationary point when program fault occurs and the data base is returned to a nearest stationary point. CONSTITUTION:A program supervising means 2 holds the number of inputs in an input quantity counting table 42 at every input transaction process; when the data base is updated and established by every input quantity, a processing quantity is set in a program control table 41 and the postprocessing process number is set in a transaction number control table 43. If the fault occurs and a program is started while the data base is returned to the nearest stationary point, the program supervising means 2 considers that normal processing is carried out up to the process quantity value in the control table 41 and instructs an operating system 1 so that an input corresponding to the process quantity and the transaction number of an output paired with it are read out of the number control table 43 and the pointers are set to those number values through a pointer returning means 3.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a synchronization processing method for a database and a normal file, and more particularly to a synchronization processing method for a database and a normal file in transaction processing for updating the database and recording input / output data in the normal file. .

[0002]

2. Description of the Related Art Conventionally, in a program that updates a database by an input transaction and generates an output transaction, when a database deadlock or a software failure occurs, the database uses a pre-update journal to execute the database immediately before the failure. When the contents are updated and the contents are established, it is possible to return to the contents generally called the quiesce point immediately before, but the input transaction and the output transaction often use a normal file, and immediately before the normal file. The pointer at the quiescent point is manually restored by examining the data in the program. In addition, in order to avoid such asynchronization, a method of establishing a quiesce point for each transaction may be adopted.

[0003]

The above-mentioned conventional method of manually synchronizing the database and the normal file requires complicated work and time, and also depends on the method of establishing a quiesce point for each transaction. For example, it is possible to synchronize the database with regular files, but each time,
There is a problem that the actual update is performed and the performance is significantly reduced.

[0004]

According to the method of synchronizing a database and a normal file of the present invention, the database is updated by an input transaction to generate an output transaction, and a quiesce point is established by actual updating of the database. When a program failure occurs after processing the input transaction of, the database that was restored to the previous quiesce point by the pre-update journal and the pointer of the I / O transaction that uses the normal file In the synchronous processing method, the status of the program is monitored through the operating system, and the input count of the input transactions in the input count count table is updated and held for each input transaction process, and this input count is maintained for each quiesce point establishment process. Program update is held as a pretreatment number of management tables, a note of the input transaction number pairs from the input transaction process after the establishment process of the still point in the transaction number management table,
Program monitoring means for reading the value of the number of pre-processing cases from the program management table by detecting the start of the program after detecting that the database has returned to the previous quiesce point by the update journal, and before reading by this program monitoring means. Upon receiving the number of processed transactions, the output transaction number corresponding to this number of preprocessed transactions is read from the transaction number management table, and the pointer values of the input and output transaction files to be restored from the number of preprocessed transactions and the read output transaction numbers are operated. And a pointer returning means for instructing the system.

[0005]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the present invention.
The embodiment shown in FIG. 1 monitors a known operating system 1 and operating system 1 for managing jobs, programs, and files, and starts up the program.
The operating system 1 is controlled by the program monitoring means 2 and the program monitoring means 2 for terminating, establishing a quiesce point for the database, executing a restoration process to the immediately preceding quiesce point, and detecting the occurrence of a software failure.
A pointer restoring means 3 for issuing a file pointer reset instruction and a storage section 4 for storing various information necessary for controlling these. The storage unit 4 has a program management table 41, an input number count table 42, and a transaction number management table 43.

FIG. 2 is a diagram showing the contents of each table in the storage unit 4. FIG. 2A is a diagram showing the contents of the program management table 41, with the job name and program name as keys,
The initial value is 0, and the number of pre-processing cases, which is the number of input transactions processed up to that point, is set. FIG. 2B is a view showing the contents of the input case count table 42, in which the number of input cases of the input transaction is set. FIG. 2C is a diagram showing the contents of the transaction number management table 43. With the file name of the output transaction as a key, the record number of the input / output transaction (hereinafter referred to as the input / output transaction number) can be set. .

Next, the operation of the embodiment shown in FIG. 1 will be described. When the program is started or restarted and this start is detected by the program monitoring means 2 via the operating system 1, the program monitoring means 2
Refers to the program management table 41 using the job name / program name as a key. As a result of the reference, if the job name / program name does not exist, the program monitoring means 2 does nothing until it is judged that this program is not the target of normal file synchronization processing and the next program is started. If the job name / program name exists, that is, it is determined as the target of the normal file synchronization processing, and the number of pre-processing cases in the table is referred to. Then, if the number of pre-processes is 0, it is determined that the execution of the previous program is normally completed, and thereafter, the execution state of the program is continuously monitored via the operating system 1. The program monitoring means 2 continues to monitor the execution state of the program, further counts the number of input transactions, sets the number of input transactions in the input transaction count table 42, and sets the input transaction number and the corresponding output transaction number. Set in the transaction number management table 43. Next, when the program monitoring means 2 detects that the quiesce point establishment process, which is performed by a certain number of input transactions, is normally performed, it sets the value of the input number count table 72 in the program management table 41, and the transaction The contents of the number management table 43 are erased.

If a value other than 0 is set for the number of pre-processing cases, it is judged that there was an abnormality in the previous program execution, and then the program was restarted. When it detects that the process of returning to the previous stationary point has been performed,
Assuming that the input transaction has been normally executed up to the value of the number of preprocesses, the value of the number of preprocesses is passed to the pointer restoring means 3. The pointer restoring means 3 instructs the operating system 1 to set the pointer for the input transaction to the value of the number of preprocessing cases + 1. In addition, the transaction management table 43 is referred to, the input transaction number is compared with the value of the number of pre-processing cases, the output transaction number for the input transaction number larger than the value of the number of pre-processing cases is searched, and the output transaction of this number and thereafter. In order to invalidate the output transaction of, the operating system 1 is instructed to set the pointer to the value of the found transaction number for the output transaction. The operating system 1 sets the instructed value in the pointer. Even when there are a plurality of output transactions, the transaction number management table 43 is provided so as to correspond to each output transaction using the file name as a key, and therefore each file is processed. When the program monitoring means 2 detects that the pointer has been reset after passing control to the pointer restoring means 3, it instructs the program to continue execution via the operating system. When it is detected that the program cannot be continuously executed due to a software error or the like, the operating system 1 is instructed to terminate the program, but when the operator removes the cause of the software error or the like and re-executes the program. Since the above-mentioned processing is performed according to the number of pre-processing cases of the program management table 41, smooth recovery is performed. Furthermore, when the program monitoring means 2 detects that the program has ended normally, it erases the number of preprocessing cases in the program management table 41 to zero.

[0010]

As described above, the present invention manages the number of processings up to the regular establishment processing of the quiesce point for the database in the transaction processing, thereby returning to the immediately preceding quiesce point for the database. Along with the processing, the pointer of the normal file can be restored, and the database and the regular file can be synchronized, so that the pointer of the regular file is manually restored and a quiesce point is established for each input transaction processing. Since it is not necessary, there is an effect that the system performance can be improved.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a diagram showing the contents of each table in the storage unit of the embodiment of FIG.

[Explanation of symbols]

 1 Operating System 2 Program Monitoring Means 3 Pointer Returning Means 4 Storage Unit 41 Program Management Table 42 Input Count Count Table 43 Transaction Number Management Table

Claims (1)

[Claims] 1. A database is updated by an input transaction to generate an output transaction,
Establishing a quiesce point by actually updating the database is a program failure that occurs after the processing of multiple input transactions, and the database that was restored to the last quiesce point by the pre-update journal and the pointer of the I / O transaction that uses a normal file In the synchronization processing method of the database and regular files for synchronization, the status of the program is monitored through the operating system, and the input count of the input transaction in the input count count table is updated and held for each input transaction processing. , This input count is updated and held as the preprocessing count of the program management table for each quiesce point establishment process, and the input / output transaction number pair by the input transaction process after the quiesce point establishment process is stored in the transaction number management table. A program monitoring means for reading the value of the number of pre-processing cases from the program management table by detecting the start of the program after detecting that the database has returned to the previous quiesce point by the update journal, and this program monitoring Upon receiving the number of preprocesses read by the means, the output transaction number corresponding to the number of preprocesses is read from the transaction number management table, and the file of the input and output transactions to be restored from the number of preprocesses and the read output transaction number is read. A synchronization processing method for a database and a normal file, comprising a pointer restoring means for instructing a pointer value to an operating system.