Synchronization of Dissimilar Databases

• US 20080183763A1
• Filed: 01/31/2007
• Published: 07/31/2008
• Est. Priority Date: 01/31/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Javalkar, Shirish S.
• Granted Patent: US 8,332,353 B2
• Time in Patent Office: Days
• US Class Current: 707/200
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• 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/275 Synchronous replication

Abstract

A method, system and computer-readable medium for synchronizing databases between two disparate computer systems are presented. In one embodiment, the method includes updating a first database, which is part of a first computer system, with a database update, wherein updating the first database does not initially commit the database update to the first computer system; calling a remote function to incorporate the database update into a second database that is part of a second computer system; in response to the remote function determining that the second database has been successfully updated with the database update, committing the database update to the first computer system; and in response to the remote function determining that the second database has not been successfully updated with the database update, rolling back the database update such that the first computer system is unaware of the attempted updating of the first database.

Claims

1. A method for synchronizing databases between two disparate computer systems, the method comprising:

loading a buffer, which is part of a first computer system, with a database update, wherein loading the buffer does not commit the database update to a first database in the first computer system;

calling a remote function, in the first computer system, to incorporate the database update into a second database that is part of a second computer system, wherein the first and second computer systems operate in disparate environments;

in response to the remote function determining that the second database has been successfully updated with the database update, committing the database update to the first database in the first computer system; and

in response to the remote function determining that the second database has not been successfully updated with the database update, rolling back the database update in the buffer such that the first computer system is unaware of an attempted updating of the first database.

2. The method of claim 1, wherein the remote function is positioned after a plurality of database updates in a database table update queue in the first computer system, and wherein the remote function is not called until all of the database updates are successfully implemented and loaded in the buffer.

3. The method of claim 1, wherein the disparate environments of the first and second computer systems are caused by different hardware architectures in the first and second computer systems.

4. The method of claim 1, wherein the disparate environments of the first and second computer systems are caused by the first computer system operating under a first software system and the second computer system operating under a second software system.

5. The method of claim 4, wherein the first software system is initially designed by a software manufacturer such that the first software system is unable to confirm that the second software system has updated the second database.

6. The method of claim 4, wherein the first software system is a SAP™

software system, and wherein the second software system is a non-SAP™

software system.

7. A system comprising:

a processor;

a data bus coupled to the processor;

a memory coupled to the data bus; and

a computer-usable medium embodying computer program code, the computer program code comprising instructions executable by the processor and configured for synchronizing databases between two disparate computer systems by performing the steps of;

loading a buffer, which is part of a first computer system, with a database update, wherein loading the buffer does not commit the database update to a first database in the first computer system;

calling a remote function, in the first computer system, to incorporate the database update into a second database that is part of a second computer system, wherein the first and second computer systems operate in disparate environments;

in response to the remote function determining that the second database has been successfully updated with the database update, committing the database update to the first database in the first computer system; and

in response to the remote function determining that the second database has not been successfully updated with the database update, rolling back the database update in the buffer such that the first computer system is unaware of an attempted updating of the first database.

8. The system of claim 7, wherein the remote function is positioned after a plurality of database updates in a database table update queue in the first computer system, and wherein the remote function is not called until all of the database updates are successfully implemented and loaded in the buffer.

9. The system of claim 7, wherein the disparate environments of the first and second computer systems are caused by different hardware architectures in the first and second computer systems.

10. The system of claim 7, wherein the disparate environments of the first and second computer systems are caused by the first computer system operating under a first software system and the second computer system operating under a second software system.

11. The system of claim 10, wherein the first software system is initially designed by a software manufacturer such that the first software system is unable to confirm that the second software system has updated the second database.

12. The system of claim 10, wherein the first software system is a SAP™

software system, and wherein the second software system is a non-SAP™

software system.

13. A computer-readable medium embodying computer program code for synchronizing databases between two disparate computer systems, the computer program code comprising computer executable instructions configured for:

loading a buffer, which is part of a first computer system, with a database update, wherein loading the buffer does not commit the database update to a first database in the first computer system;

calling a remote function, in the first computer system, to incorporate the database update into a second database that is part of a second computer system, wherein the first and second computer systems operate in disparate environments;

in response to the remote function determining that the second database has been successfully updated with the database update, committing the database update to the first computer system; and

in response to the remote function determining that the second database has not been successfully updated with the database update, rolling back the database update in the buffer such that the first computer system is unaware of an attempted updating of the first database.

14. The computer-readable medium of claim 13, wherein the remote function is positioned after a plurality of database updates in a database table update queue in the first computer system, and wherein the remote function is not called until all of the database updates are successfully implemented and loaded in the buffer.

15. The computer-readable medium of claim 13, wherein the disparate environments of the first and second computer systems are caused by different hardware architectures in the first and second computer systems.

16. The computer-readable medium of claim 13, wherein the disparate environments of the first and second computer systems are caused by the first computer system operating under a first software system and the second computer system operating under a second software system.

17. The computer-readable medium of claim 16, wherein the first software system is initially designed by a software manufacturer such that the first software system is unable to confirm that the second software system has updated the second database.

18. The computer-readable medium of claim 16, wherein the first software system is a SAP™

software system, and wherein the second software system is a non-SAP™

software system.

19. The computer-readable medium of claim 13, wherein the computer-usable medium is a component of a remote server, and wherein the computer executable instructions are deployable to a client computer from the remote server.

20. The computer-readable medium of claim 13, wherein the computer executable instructions are capable of being provided by a service provider to a customer on an on-demand basis.