JP2001022627A - System and method for synchronizing data bases between plural devices - Google Patents

Abstract

PROBLEM TO BE SOLVED: To update a data base by easily extracting non-updated information at high speed in the order of time sequence through utilizing a log file in a FIFO form. SOLUTION: This system has a log file 14 for storing a syntax described in a data base language, an updating processing part 111 for replacing received update data with an SQL language when there is the updating request of a data base 13 from anywhere except for a network 4 to a device 1, updating the data base 13 of the present device by executing that syntax described in the SQL language and preserving that syntax in the log file 14 in the order of updating as updated information and a synchronous processing part 112 for periodically retrieving whether the updated information is preserved in the log file 14 or not and sending the updated information stored in the log file 14 to a device 2 so as to update a data base 23 of the device 2 when the updated information is preserved.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and a method for synchronizing a plurality of databases, and more particularly to a method and a method for synchronizing a database between a plurality of apparatuses that perform updates using log files.

[0002]

2. Description of the Related Art Conventionally, there is a method for realizing a prepaid card service using an SCP (service control node) in an intelligent network. In this service,
In order to keep the balance of the prepaid card in the database on the SCP, after the subscriber uses this service,
A function of updating the balance of the database on the CP is required. FIG. 8 shows a conventional method in this case. Referring to FIG. 8, the device 6 includes an update processing unit 6 for updating the database.
And a communication link 8 connecting them between the devices.
Having. The update processing unit 61 of the device 1 that has received the database update request updates the database 62 and the database 71 of the device 7 via the network 8.

Japanese Patent Application Laid-Open No. 10-07157 discloses a method of matching between a plurality of database sites that are distributed and arranged, creating and managing change histories (assigning sequential numbers) at each site, It is described that the difference data is extracted by referring to and storing the change history between the bases.

Japanese Patent Laid-Open Publication No. Hei 10-111825 discloses a method of managing a difference between databases on a plurality of SCPs by providing a difference management database and assigning time information to each record in the difference management database. It describes that difference management between a plurality of databases is performed.

[0005]

In a conventional general system of this type, as shown in FIG. 8, when a failure of the network 8 or a failure of the device 7 occurs, the database 62 is updated. Reference numeral 71 indicates that updating is prohibited. Thereafter, when the failure is recovered, it is not known to what extent the device 8 has been updated, so that a problem arises in that the database must be manually copied. Furthermore,
Database 6 that is the copy source during manual copying
2 is updated, the synchronization between the database 62 and the database 71 cannot be guaranteed. Therefore, it is necessary to prohibit the update to the database 62 during this time, and the service cannot be provided during manual synchronization. Operational problems occur.

[0006] In this case, Japanese Patent Laid-Open No. 10-07157 discloses that, in this case, a sequential number is assigned to each data of the change history so that the data has the same meaning as the time information. Since it is necessary to add the data to all the data, and it is necessary to extract the difference data based on the data, it is difficult to increase the processing speed.

In this case, Japanese Patent Application Laid-Open No. Hei 10-111825 has a problem that it is difficult to increase the processing speed because a database is used for storing the difference management information.

An object of the present invention is to solve the above-mentioned problems, and
An object of the present invention is to update a database by using a log file in the IFO format so that unupdated information can be extracted in a simple and high-speed chronological order.

[0009]

In order to achieve the above object, a database synchronization method between a plurality of devices according to the present invention connects a plurality of devices having a database via a network, and each device has its own device. In a database synchronization method between a plurality of devices that update a database and a database of another device, a log file in a FIFO format that stores a syntax described in a database language is provided, and a request to update the database to the own device from outside the network is provided. Update processing means for replacing the received update data with a database language, executing a syntax described in the database language, updating the database of the own device, and storing the syntax in the log file in the update order as update information, The update information is periodically stored in the log file Synchronization processing means for sending the update information stored in the log file to the devices other than the own device so as to update the database of the devices other than the own device among the plurality of devices when the device is searched and stored. And characterized in that:

Further, the apparatus receiving the update information by the synchronization processing means updates its own database by executing a syntax described in the database language, which is the update information.

Further, the synchronous processing means transmits the update information to a device other than the own device, and then detects that there is a failure in the destination device.
The update information is stored in an O-type failure log file.

Further, the synchronous processing means periodically monitors and manages the operation status of the plurality of devices.

[0013] Further, the synchronization processing means may be configured to update the database of the failed device when the notification of failure recovery is received from the failed device. Is transmitted to the failed device.

A method of synchronizing a database between a plurality of apparatuses according to the present invention is a method for synchronizing a plurality of apparatuses having a database by a network, wherein each apparatus updates a database of its own apparatus and a database of another apparatus. Wherein the plurality of devices comprises: a first timer, a second timer, a log file in FIFO format,
Using a status word indicating an operating state for each device, the first timer and the second timer that interrupt at regular intervals are started, and when the own device receives a database update request,
By updating the update data into a syntax described in a database language and executing the syntax, the database of the own device is updated, the syntax is stored as update information in the update file in the log file, and the first timer Include
Determine the target device, confirm by sending an operation status confirmation message to the target device, and when the failure of the target device is detected after sending the operation status confirmation message, the status word indicates that the failure has occurred in the target device. When there is an interruption of the second timer, the content of the log file is searched, and when the presence of the content is detected in the log file, the update device of the transmission destination is determined, and the update device of the update device is determined from the status word. The operation status is searched, and if normal, the update information read from the log file is sent to the update device as an update message.

Further, in the above-mentioned method of synchronizing a database between a plurality of devices, when the plurality of devices receive the update message, the plurality of devices execute a syntax described in the database language as update information from the update message. It is characterized by updating its own database.

Further, in the above-mentioned method for synchronizing a database between a plurality of devices, the plurality of devices may be connected to the
When a failure log file having an O-format history file is used and the update device is detected to have a failure after sending the update message, the update information is stored in a history file of the failed device. .

Further, in the above-mentioned method of synchronizing a database between a plurality of devices, the plurality of devices update the database of the failed device when receiving a recovery message indicating failure recovery from the failed device. In this case, the update information stored in the history file of the failed device is transmitted to the failed device as an update message.

Further, the plurality of devices are service control nodes (SCPs) connected to an intelligent network of a switching network.

[0019]

Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a system block diagram illustrating an embodiment of the present invention, in which an apparatus 1 and a plurality of apparatuses 2 (for example, apparatuses 2A, 2B, 2C,
2D) and a network 4 for communication connection between the device 1 and the plurality of devices 2. The device 1 and the plurality of devices 2 correspond to a service control node (SCP), and each of the device 1 and each device 2 is connected to an intelligent network compatible switch (not shown). The network 3 is configured by a LAN or a WAN. In the description of the present invention, the devices 1 and 2 have the same function but are merely separated for the description. That is, in the embodiment of the present invention, for the sake of explanation, the SCP that first receives as a request for updating the database update data coming from an intelligent network compatible exchange connected to its own device (not shown) is set as the device 1, and the device 1 Will update the database of the other SCP, but the other SCP at that time will be the device 2.

The apparatus 1 is stored in a control unit 11 that operates under program control by a processor, a transmitting and receiving unit 12 that performs transmission and reception with a plurality of apparatuses 2 via a network 4, and a storage medium (for example, a disk). It comprises a database 13, a log file 14 stored in a non-volatile memory, and a fault log file 15 also stored in a non-volatile memory. Although the log file 14 and the failure log file 15 are volatile memories, they may be recording media such as disks.

The control section 11 comprises an update processing section 111 and a synchronization processing section 112.

When the update of the contents of the database 13 occurs, the update processing unit 111 uses the initialization parameters necessary for the update set in advance in the update processing unit 111 to convert the update data from the exchange into an SQL syntax. Replace with Further, the further processing unit 111 updates the database 13 by executing the SQL syntax, and stores the updated information (data written in the SQL syntax) in the log file 1.
4 is stored. The log file 14 contains the database 1
The update information is stored in the order of update (one syntax at a time). The storage method of the log file 14 is FIFO (F
It is in the format of "first in first out", and once read, the read contents do not remain in the log file. The initialization parameter is information necessary for accessing the database (for example, table name, key field name, field name, processing),
This is a parameter for converting to an SQL syntax by applying the update data sent from the exchange to this parameter.

The synchronization processing unit 112 periodically updates the database (determines by looking at the contents of the log file 14).
Furthermore, a communication link established between the device 1 and the plurality of devices 2 via the network 4 and the operation status of the plurality of devices 2 are periodically monitored (health check). Note that the synchronization processing unit 112 operates separately from the operation of checking the update result and the operation of performing a health check.

The failure log file 15 has a history file corresponding to the failure of each device 2, and when a failure of the device 2 is detected, updates are stored until the update information is restored. The storage method of the history file of each device in the failure log file 15 is as follows.
It is in FIFO format and the update information is updated in the order of update (SQL
Syntax execution order). Once read, the read contents do not remain in the history file.

The device 2 includes a control unit 21 which operates under program control by a processor, and a transmission / reception unit 2 which transmits and receives the device 1 and other devices 2 via the network 4.
2 and database 2 stored on a disk medium
3. It is composed of a log file 24 and a failure log file 25. It is assumed that there are four devices 2, that is, device 2A, device 2B, device 2C, and device 2D.

The control section 21 comprises an update processing section 211 and a synchronization processing section 212.

Note that the protocol of the message used for updating the database and confirming the operating state among the devices in FIG. 1 is determined in advance at the time of setting the system.

FIG. 2 shows the format of status words stored in memories (not shown) of the devices 1 and 2, and shows the operating status of the devices 2A, 2B,. If there are four devices 2A to 2D, the status word in FIG. 2 has four areas of devices 2A to 2D. In FIG. 2, if the logical value is “1”, it indicates that a fault has occurred, and if the logical value is “0”, it indicates that normal operation is in progress.

Database 13 and database 23
Is a database created based on the SQL language, which is an international standard relational database language, as an example of the present embodiment. Further, since a plurality of SCPs are provided for load distribution, when the database 13 is updated, the database 23 is similarly updated.

FIG. 3 is a flowchart showing the operation when the update processing unit 111 of the device 1 and the update processing unit 211 of the device 2 receive the update message.

FIG. 4 is a flowchart showing the operation when the synchronization processing unit 112 of the device 1 and the synchronization processing unit 212 of the device 2 perform a health check of another device.

FIG. 5 is a flowchart showing an operation when the synchronization processing unit 112 of the device 1 and the synchronization processing unit 212 of the device 2 monitor update information of another device.

FIG. 6 is a flowchart showing the operation when the synchronization processing unit 112 of the device 1 and the synchronization processing unit 212 of the device 2 receive the recovery message.

Next, the operation of this embodiment will be described with reference to FIGS. Now, when a message containing update data of the database 13 (including update data) from the intelligent network compatible exchange connected to the device 1 (not shown) in FIG. The first transmission / reception unit 12 receives this message and passes the message to the control unit 11. Then, the control unit 11 analyzes the received message, recognizes the message from the exchange as an update message from the content of the update data, and passes control to the update processing unit 11. The update processing unit 111 further analyzes the update message (FIG.
Step S1). At this time, when the update processing unit 111 determines that the update message is a request from the exchange in updating the database, the update processing unit 111 converts the update data contained in the message into an SQL syntax, and executes the SQL syntax to thereby update the contents of the database 13. Is updated (steps S3, S
4, S5). Further, the update processing unit 111 writes the SQL syntax into the log file 14 as update information, and returns an update response message indicating normal termination to the transmission destination (switch side) via the transmission / reception unit 12. The SQL file is stored in the log file 14 as it is (step S
6, S7). When the update processing unit 111 determines that the update message is not an update of the database, another process different from the update of the database (the process instructed by the update message) is performed (step S10).

On the other hand, the apparatus 1 performs processing by timer interruption in order to monitor the update information of each apparatus 2 at regular intervals. The monitoring timer is started when each device starts up. When the timer for monitoring the update information times out and a timer interrupt occurs, the synchronization processing unit 112 of the device 1 goes to look at the contents of the log file 14, and when the update information is stored in the log file 14, The operation proceeds to the operation of updating the contents of the database 23 of each device 2 (steps S21 and S22 in FIG. 5). Then, the synchronization processing unit 1
Reference numeral 12 denotes a device 2 in which devices to be updated are set in a predetermined order (in the example, 2A, 2B, 2C, and 2D).
A is determined (step S23). Subsequently, the synchronization processing unit 11
2 reads all the update information of the database from the log file 14, stores it in the memory (not shown in FIG. 1) of the device 1, and goes to the state word stored in the memory of the device 1 (step S24). ). Since the logical value “0” is set in the area of the device 2A to which the status word is to be transmitted, the synchronization processing unit 112 determines that the operation is normal and the update message read from the memory is included in the update message. Information is transmitted, and an update message is transmitted to the first device 2A via the transmission / reception unit 12 and the network 4 (step S).
25, S26). The transmission / reception unit 22 of the device 2 that has received the update message passes the update message to the control unit 21. The control unit 21 analyzes the received message and, when determining that the message is an update message, passes control to the update processing unit 211. The update processing unit 211 analyzes the update message, and if it determines that the update of the database 23 is a request from the device 1, the update information (SQ
The database 23 is updated by executing the L syntax (steps S1, S2, S3, and S8 in FIG. 3). When the update processing unit 211 finishes the update processing of the database 23, the update processing unit 211 sends an update response message indicating a normal end to the transmission / reception unit 2.
2 is returned to the device 1 (step S9). Apparatus 1
When the control unit 11 receives the update response message via the transmission / reception unit 12, the control unit 11 analyzes the message, and when it determines that the message is the update response message, passes control to the synchronization processing unit 112.
The synchronization processing unit 112 analyzes the update response message to determine that the processing has been completed normally, and proceeds to processing for the next device 2B. Thus, the process is repeated up to the device 2D (steps S27 and S30 in FIG. 5).

In step S27, when the synchronization processing unit 112 of the device 1 detects a failure (when the update processing unit 211 of the device 2 is an update response message indicating abnormal termination, or when there is no response), the status word “1” is set in the area of the device where the failure is detected, and the update information is stored in the history file of the device where the failure is detected in the failure log file 15 (S27, S28, S29). Thereafter, the synchronization processing unit 11
2 repeats the operation from step S23 until the operation of the update processing for all devices is completed (S30).

Next, the synchronization processing unit 112 of the device 1
B updates the database 23, but the synchronization processing unit 11
2 operates in the same manner as the device 2A. As described above, the synchronization processing unit 112 finishes a series of processing by updating the database 23 of the devices 2C and 2D in the same manner as the device 2A, and ends the next monitoring time (by the monitoring timer). (Step S30).

Further, the device 1 performs a process by means of a timer interrupt in order to check the health of each device 2 at regular intervals. A timer for health check (operating state monitoring) can be started when each device is started. When the timer for the health check times out and a timer interrupt occurs, the synchronization processing unit 112 performs a health check on each device 2. First, the synchronization device 112 places the target devices in a predetermined order (2A in the example). , 2B, 2C, and 2D (in the order of step S1 in FIG. 4).
1). The synchronization processing unit 112 first transmits an operation status confirmation message to the device 2A via the network 4 in order to check whether the operation status of the device 2A is normal (Step S12). Then, the transmission / reception unit 22 of the device 2A
Receives the operation status confirmation message, and passes the operation status confirmation message to the control unit 21. The control unit 21 that has received the message determines that the message is an operation status confirmation message by analyzing the message, and transmits an operation status confirmation response message indicating normal operation to the transmission / reception unit 22 and the network 4 because the operation is normal. Return to device 1. When the synchronization processing unit 112 of the device 1 receives the operation status confirmation response message via the transmission / reception unit 12 and determines that it is normal, the health check of the device 2A is completed (steps S13, S14, S15, S16). The synchronization processing unit 112 operates the health check of the next device 2B in the same manner as the device 2A. As described above, the synchronization processing unit 112 ends the series of processing by performing the same processing as the apparatus 2A in the apparatuses 2C and 2D, and waits for the processing until the next monitoring time (interruption of the health check timer) comes. (Step S17).

As described above, since the synchronization processing unit 112 updates data in chronological order, it is not necessary to prohibit the update processing unit 111 from updating the database 13 even during the update processing of the database 23 of the device 2.

If the operating state of the partner device is normal, the update information (not including the management information) contained in the log file in the FIFO format is read at regular intervals, and the database of the partner device is read in accordance with the update information. Since there is a synchronous processing unit for updating, there is an effect that information that has not been updated can be processed simply and at high speed in chronological order.

Next, a case where a failure occurs in the device 2A will be described. The synchronization processing unit 112 of the device 1 starts a health check by transmitting an operation status confirmation message to the failed device 2A (step S in FIG. 4).
11, S12), and the control unit 21 of the device 2A transmits an operation status confirmation response message indicating that the device is not operating normally.
To return. Then, the synchronization processing unit 112 of the device 1 analyzes the received message, recognizes that a failure has occurred in the device 2, and recognizes the status word in the memory of the device 1 in the device 2A.
The logical value "1" indicating that a fault has occurred is written in the area (steps S13, S14, S15). Step S13
In the case where the device 2 cannot receive the data in, the synchronization processing unit 112 of the device 1 monitors the response time,
A failure is detected (detected by timeout), and a logical value "1" indicating that the failure is also occurring is written in the area of the status word device 2A (steps S13 and S16).

On the other hand, the synchronization processing section 112 of the device 1 goes to the contents of the log file 14 at regular intervals, and if the update information is stored in the log file 14, the contents of the database 23 of each device 2 (Steps S21 and S22 in FIG. 5). Then, the synchronization processing unit 112
Reads all the update information of the database from the log file 14 and goes to a status word stored in the memory of the device 1 to check the operation status of the device 2 that transmits the information (steps S23 and S24). Since the logical value “1” is set in the area of the device 2A to which the status word is to be transmitted, the synchronization processing unit 112 recognizes that a failure has occurred, and stores the failure log file 15 in the history file of the device 2A. The update information is stored in SQL syntax (step S2).
5, S29). The other devices 2B, 2C, and 2D have each device 2B because the status word is not set to logical one.
Is updated.

Thereafter, the faulty device 2A is switched to the device 1
When a recovery message is received indicating that the failure has been recovered, the control unit 11 of the device 1 analyzes the received message, and passes control to the synchronization processing unit 112 when recognizing that the message is a recovery message. Then, the synchronization processing unit 112 resets the area of the device A of the status word in the memory of the device 1 to “0”, reads out the update information from the history file of the device A in the failure log file 15, and reads out the update message. The update information is loaded and an update message is transmitted to the device 2A via the transmission / reception unit 12 and the network 4. The transmitting / receiving unit 22 of the device 2 that has received the update message passes the update message to the control unit 21 (Steps S31 and S32 in FIG. 6).
Upon receiving the update message, the control unit 21 analyzes the message and determines that the message is an update message, and passes control to the update processing unit 211. The update processing unit 211
The received update message is analyzed, and when it is determined that the update of the database 23 is a request from the device 1, the database 23 is updated by executing the update information (SQL syntax) in the update message (step in FIG. 3). S
1, S2, S3, S8). Upon completion of the update processing, the update processing unit 211 transmits an update response message indicating a normal end to the transmission destination (step S9).

As described above, the synchronization processing unit 112
Monitors the operating status (health check) and the update status of the remote device (repairs with the error log file), so if a failure occurs, the process is immediately interrupted. Are read in chronological order (oldest first), and the database of the partner device can be updated in the same manner as in normal operation. In other words, it is possible to automatically perform a database synchronization recovery operation when a failure occurs in the partner apparatus, and to avoid operational problems such as prohibiting updating of the database of the own apparatus and interrupting call processing. It becomes possible.

Further, since the update information is simply stored in the log file in the order of the update occurrence irrespective of the failure, there is no need to store all the management information in the log file in time series, and the processing is simplified. It has the effect of becoming.

Next, a database used in the prepaid card service will be described as a specific example. It is assumed that the databases 13 and 23 in FIG. 1 have a subscriber registration table in which the balance is registered for each subscriber registration number. That is, the database includes a subscriber information registration table as a table name, a calling number as a key field name, and a balance as a field name. Therefore, in the update processing units 11 and 211, table names (= subscriber information registration table), key field names (= calling number), field names (= balance), processes (= UPDATE, INSERT, Or DELETE) is set. In this state, the pre-made card service, after the subscriber uses the service, identifies the subscriber's record using the calling number as a key,
The balance of the record is to be updated.

Now, it is assumed that the balance of the subscriber having the transmission number 471857234 of the terminal under the exchange corresponding to the intelligent network connected to the apparatus 1 of FIG. 1 is 100. If the balance becomes 80 after this subscriber uses this service, the update request is "update (UPDATE) the balance of the subscriber whose calling number on the subscriber information registration table is 471857234 to 80". . Therefore, the update request message from this exchange includes, as the update information, the value of the transmission number (= 47187234)
And the value of the balance (= 80). Then, device 1
Update processing unit 111 performs processing according to the flowchart of FIG. In this case, the processing in step S4 is converted into an SQL syntax as shown in FIG. This SQ
Steps S6 and S7 are performed with the L syntax as update information. When this processing is completed, the log file 14 contains the update information, and therefore, according to the update information monitoring flowchart of the synchronization processing unit 112 in FIG.
At 26, the update information in the SQL syntax of FIG. Then, the update processing unit 211 of the device 2 performs processing according to the flowchart of FIG. In this case, the processing in step S8 of the update processing unit 212 updates the database 23 by executing the SQL syntax of FIG.

As described in the specific example, in the format in which raw update data (update data sent from the exchange) is held as it is, it is necessary to repeat the process of creating an SQL syntax based on this update data. However, in the present invention, useless processing can be omitted by retaining the update information once created in the SQL syntax in the log file as it is.

Further, as shown in FIG. 7, by holding in the form of SQL syntax, the means for holding is simplified. This is because, in the format in which the raw update data is retained as it is, it is not necessary to retain the information and the information that form a pair (in the present invention, the table name is the subscriber information registration table, the key Field name is calling number and value is 471
857234, the field name is a balance, the value is 80, and the processing does not need to be associated and stored in the form of UPDATE).

In the above description, the SQL language is used as the database language. However, the syntax created in a database language other than the SQL language is exactly the same as that in the case of the SQL syntax, and is included in the present invention. Needless to say,

[0051]

As described above, the present invention has a means for storing the syntax created in the database language as update information in the log file, so that it can be saved simply, and the past database update information can be saved. Can be referenced.

Further, since the present invention has means for monitoring the operation status of other devices and the database update processing status, if a failure occurs in these devices and the database is not updated normally, , And the result of updating the database can be held.

According to the above effects, when the failure of the other device is recovered, the database of the other device can be automatically updated based on the update result of the database.

Further, since there is a means for updating data in chronological order, it is possible to operate the apparatus while updating the database of the own apparatus while synchronizing the database of the other apparatus.

[Brief description of the drawings]

FIG. 1 is a block diagram of a system showing an embodiment of the present invention.

FIG. 2 is a format diagram of a state word indicating an operation state of each device of the device 1 of FIG.

FIG. 3 is a flowchart showing an operation when the update processing unit of FIG. 1 receives an update message.

FIG. 4 is a flowchart illustrating an operation when the synchronization processing unit in FIG. 1 performs a health check of another device.

FIG. 5 is a flowchart showing an operation when the synchronization processing unit of FIG. 1 monitors update information of another device.

FIG. 6 is a flowchart illustrating an operation when the synchronization processing unit in FIG. 1 receives a restoration message.

FIG. 7 shows an SQL syntax described in an SQL language used as a specific example of the embodiment of the present invention.

FIG. 8 is a block diagram of a conventional database synchronization method.

[Explanation of symbols]

 1, 2, 6, 7 device 4, 8 network 11, 21, control unit 12, 22, transmission / reception unit 13, 23, 62, 71 database 14, 24 log file 15, 25 failure log file 61, 111, 211 update processing unit 112 , 212 Synchronization processing unit

──────────────────────────────────────────────────の Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 15/16 620 G06F 15/16 620H 15/177 672 15/177 672G 672H 682 682J F term (Reference) 5B042 GA12 GB03 GB09 GC08 HH20 JJ08 JJ15 KK06 LA20 MA08 MC09 MC15 5B045 AA03 BB13 BB28 BB35 BB47 BB49 DD16 DD17 DD18 JJ07 JJ13 JJ48 5B082 DB02 DC06 DC09 DD07 GA14 GB06 HA03

Claims (11)

[Claims] 1. A database synchronization method in which a plurality of devices having a database are connected via a network, and each device updates a database of its own device and a database of another device. A log file in a FIFO format for storing the syntax, and when there is a request for updating the database from a device other than the network, the received update data is replaced with a database language, and the syntax described in the database language is executed to execute the syntax described in the database language. Update processing means for updating the database and storing the syntax in the log file in the order of update as update information, and periodically searching for whether the update information is stored in the log file, and Update database of devices other than own device A synchronization processing means for transmitting the update information stored in the log file to a device other than the own device. 2. The apparatus which receives the update information by the synchronization processing means updates a database of the apparatus itself by executing a syntax described in the database language as the update information. Item 2. A database synchronization method between a plurality of devices according to Item 1. 3. The synchronous processing means transmits the update information to a device other than the own device, and then detects a failure in the destination device, and stores the update information in a FIFO log file which can be stored for each device. 2. The database synchronization method according to claim 1, wherein update information is stored. 4. The system according to claim 1, wherein said synchronization processing means periodically monitors and manages the operation status of said plurality of devices. 5. The update information stored in the failure log file to update a database of the failed device when a notification of failure recovery is received from the failed device. 4. A database synchronization method between a plurality of devices according to claim 3, wherein the database is sent to the failed device. 6. A database synchronization method in which a plurality of devices having a database are connected via a network, and each device updates a database of its own device and a database of another device, wherein the plurality of devices include a first device. A timer, a second timer, a log file in FIFO format,
Using a status word indicating an operating state for each device, the first timer and the second timer that interrupt at regular intervals are started, and when the own device receives a database update request,
By updating the update data into a syntax described in a database language and executing the syntax, the database of the own device is updated, the syntax is stored as update information in the update file in the log file, and the first timer Include
Determine the target device, confirm by sending an operation status confirmation message to the target device, and when the failure of the target device is detected after sending the operation status confirmation message, the status word indicates that the failure has occurred in the target device. When there is an interruption of the second timer, the content of the log file is searched, and when the presence of the content is detected in the log file, the update device of the transmission destination is determined, and the update device of the update device is determined from the status word. A method of synchronizing a database between a plurality of devices, wherein an operation status is searched, and if normal, the update information read from the log file is transmitted to the update device as an update message. 7. The plurality of devices, when receiving the update message, update a database of the own device by executing a syntax described in the database language as update information from the update message. The method for synchronizing a database between a plurality of devices according to claim 6. 8. The apparatus according to claim 1, wherein the plurality of devices use a failure log file having a history file in a FIFO format for each device,
7. The database synchronization method according to claim 6, wherein when the update device detects a failure in the update device after sending the update message, the update information is stored in a history file of the failed device. 9. The history file of the failed device so that the plurality of devices update a database of the failed device when receiving a recovery message indicating failure recovery from the failed device. 7. The database synchronization method according to claim 6, wherein the update information stored in the database is sent to the failed device as an update message. 10. The database synchronization method according to claim 1, wherein the plurality of devices are service control nodes (SCPs) connected to an intelligent network of a switching network. 11. The method according to claim 6, wherein the plurality of devices are service control nodes (SCPs) connected to an intelligent network of a switching network.