DATA SYNCHRONIZATION METHOD, COMPUTER READABLE RECORDING MEDIUM HAVING STORED THEREIN DATA SYNCHRONIZATION PROGRAM, AND DATA SYNCHRONIZATION CONTROL DEVICE

• US 20130346363A1
• Filed: 08/08/2013
• Published: 12/26/2013
• Est. Priority Date: 02/09/2011
• Status: Abandoned Application

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Matsuda, Takashi, ARAKAWA, Takahiro
• Application Number:
  US13/961,937
• Publication Number:
  US 20130346363A1
• Time in Patent Office: Days
• US Class Current: 707/610
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

Disclosed is a data synchronization method which includes acquiring first update data for an update process performed on a first database, converting the first update data into second update data according to a format of a second database based on a previously set conversion definition information, deciding a lock range based on the first update data and the pre-update data that has not been subjected to the update process, locking the first and second databases based on the decided lock range, and updating the first and second databases using the first and second update data, respectively.

Claims

1. A data synchronization method, comprising:

acquiring first update data for an update process performed on a first database;

converting the first update data into second update data according to a format of a second database based on previously set conversion definition information;

deciding a lock range based on the first update data and pre-update data that has not been subjected to the update process;

locking the first and second databases based on the decided lock range; and

updating the first and second databases using the first and second update data, respectively.

2. The data synchronization method according to claim 1,

wherein the locking of the first and second databases includes

determining whether or not the lock range in the first and second databases has been locked based on lock management information to which lock statuses of the first and second databases are set based on the lock range, and

when it is determined that the lock range has not been locked, setting lock acquisition information representing that the lock range for the update process has been locked in the lock management information.

3. The data synchronization method according to claim 2,

wherein the locking of the first and second databases includes

when it is determined that the lock range has been locked, setting standby information representing that the lock range for the update process is in a lock standby status in the lock management information.

4. The data synchronization method according to claim 3,

wherein the lock management information includes a lock key which is used to specify a row for the update process and common to the first and second databases,

the converting of the first update data into the second update data includes generating a lock key for the update process, and

the determining of whether or not the lock range has been locked includes determining whether or not the same lock key as the generated lock key for the update process is included in the lock management information, and determining that the lock range has not been locked when it is determined that the lock key for the update process is not included in the lock management information.

5. The data synchronization method according to claim 4,

wherein the determining of whether or not the lock range has been locked includes determining whether or not there is a range common to a lock range corresponding to the lock key included in the lock management information and the lock range for the update process when it is determined that the lock key for the update process is included in the lock management information, determining that the lock range has not been locked when it is determined that there is no common range, and determining that the lock range has been locked when it is determined that there is a common range.

6. The data synchronization method according to claim 4,

wherein the first database and the second database are databases of types different from each other, and

the locking of the first and second databases includes referring to the lock management information based on information representing each of a correspondence relation between a lock key of the first database and a lock key of the second database and a correspondence relation between the lock range of the first update data and the lock range of the second update data.

7. The data synchronization method according to claim 3, further comprising:

releasing the locking of the first and second databases after the first and second databases are updated;

determining whether or not the lock range for the update process to which the standby information is set has been locked after releasing the locking; and

when it is determined that the lock range has not been locked, deleting the standby information for the update process from the lock management information, and setting lock acquisition information for the update process to the lock management information.

8. The data synchronization method according to claim 1,

wherein the deciding of the lock range includes deciding the lock range using a column of a table in the first and second databases as a minimum unit.

9. The data synchronization method according to claim 1,

wherein the deciding of the lock range includes

generating update difference data based on the pre-update data and the update data, and

determining a range to be updated by the update process based on the update difference data and deciding the lock range.

10. The data synchronization method according to claim 1,

wherein the converting of the first update data is performed for each data synchronization target database on which the update process is to be performed other than the first database based on the conversion definition information,

the locking of the database includes locking all data synchronization target databases, and

the updating of the database includes updating each of all data synchronisation target databases using the first update data or the converted update data.

11. The data synchronization method according to claim 1,

wherein the converting of the first update data into the second update data and the deciding of the lock range are performed in parallel, and the locking of the first and second databases is performed after the converting of the first update data into the second update data and the deciding of the lock tease are completed.

12. The data synchronization method according to claim 1,

wherein the first database is disposed in a first operating system (OS),

the second database is disposed in a second OS,

the first and second OSs operate on a single system, and

the updating of the first and second databases includes outputting the second update data to the second OS through a shared memory accessible from the first and second OSs.

13. The data synchronization method according to claim 12,

wherein the first and second OSs are virtual OSs, and

the system is a virtual machine.

14. A computer readable recording medium having stored therein a data synchronization program causing a computer to execute a process for synchronizing data, the process comprising:

acquiring first update data for an update process performed on a first database;

converting the first update data into second update data according to a format of a second database based on previously sat conversion definition information;

deciding a lock range based on the first update data and pre-update data that has not been subjected to the update process;

locking the first and second databases based on the decided lock range; and

updating the first and second databases using the first and second update data, respectively.

15. The computer readable recording medium having stored therein the data synchronisation program according to claim 14,

wherein the locking of the first and second databases includes

determining whether or not the lock range in the first and second databases has been locked based on lock management information to which lock statuses of the first and second databases are set based on the lock range, and

when it is determined that the lock range has not been locked, setting lock acquisition information representing that the lock range for the update process has been locked in the lock management information.

16. The computer readable recording medium having stored therein the data synchronization program according to claim 15,

wherein the locking of the first and second databases includes

when it is determined that the lock range has been locked, setting standby information representing that the lock range for the update process is in a lock standby status in the lock management information.

17. The computer readable recording medium having stored therein the data synchronisation program according to claim 16,

wherein the lock management information includes a lock key which is used to specify a row for the update process and common to the first and second databases,

the converting of the first update data into the second update data includes generating a lock key for the update process, and

the determining of whether or not the lock range has been locked includes determining whether or not the same lock key as the generated lock key for the update process is included in the lock management information, and determining that the lock range has not been locked when it is determined that the lock key for the update process is not included in the lock management information.

18. The computer readable recording medium having stored therein the data synchronization program according to claim 16, the process further comprising:

releasing the locking of the first and second databases after the first and second databases are updated;

determining whether or not the lock range for the update process to which the standby information is set has been locked after releasing the locking; and

when it is determined that the lock range has not been locked, deleting the standby information for the update process from the lock management information, and setting lock acquisition information for the update process in the lock management information.

19. The computer readable recording medium having stored therein the data synchronization program according to claim 14,

wherein the deciding of the lock range includes deciding the lock range using a column of a table in the first and second databases as a minimum unit.

20. A data synchronisation control device, comprising:

to processor,

wherein the processor

acquires first update data for an update process performed on a first database,

converts the first update data into second update data according to a format of a second database based on previously set conversion definition information,

decides a lock range based on the first update data and pre-update data that has not been subjected to the update process,

locks the first and second databases based on the decided lock range, and

updates the first and second databases using the first and second update data, respectively.