System and method for verifying integrity of replicated databases

• US 5,765,172 A
• Filed: 01/23/1996
• Issued: 06/09/1998
• Est. Priority Date: 01/23/1996
• Status: Expired due to Term

• Current Assignee: Sound View Innovations, LLC (Sound View Innovation Holdings, LLC)
• Original Assignee: DSC Communications Corp. (Nokia Corporation)
• Inventors: Fox, David L.
• Primary Examiner(s): Lintz, Paul R.
• Assistant Examiner(s): Mizrahi, Diane D.
• Application Number:
  US08/589,928
• Time in Patent Office: 868 Days
• Field of Search: 395/616, 395/618, 395/619, 395/620, 707/200, 707/202, 707/203, 707/204
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1608 Error detection by comparing the output signals of redundant hardware G06F11/1629, G06F11/1666 take precedence; error detection or correction in information storage based on relative movement between record carrier and transducer G11B20/18; checking static stores for correct operation G11C29/00; for logic circuits H03K19/003, H03K19/007; for pulse counters or frequency dividers H03K21/40
• CPC Class Codes: G06F 11/1629 Error detection by comparing the output of redundant processing systems
• CPC Class Codes: H04M 3/2254 in networks
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method to verify the integrity of replicated databases that includes the steps of determining a checksum for a first database after updating the first database, determining a checksum for each of a number of second databases after updating each of the second databases, and comparing the checksums for the first database to that of each of the second databases to verify the integrity of each of the second databases.

Claims

1. A method to verify the integrity of replicated databases in a telecommunications network, comprising the steps of:

determining a checksum for a first database after performing a series of changes on the first database;

determining a checksum for each of at least one second database after performing the series of changes on each second database;

comparing the checksum for the first database to the checksum for each second database; and

storing the changes made to a specific second database if the checksum for the first database matches the checksum for the specific second database.

2. The method of claim 1, further comprising the step of transmitting the checksum for the first database and the series of changes to each second database after the step of determining a checksum for the first database.

3. The method of claim 1, further comprising the step of restoring the specific second database to its original configuration if the checksum for the first database does not match the checksum for the specific second database.

4. The method of claim 1, further comprising the step of synchronizing a second database if the checksum for the first database does not match the checksum for the second database.

5. The method of claim 1, wherein the step of determining a checksum for a first database further comprises the steps of:

determining a checksum for each of at least one table that comprises the first database;

assigning an index number to each table that comprises the first database;

forming a data block for each table that includes an index number block and a checksum block; and

forming a transaction journal message that includes a data block for each table.

6. The method of claim 1, wherein the step of determining a checksum for each of at least one second database further comprises the steps of:

determining a checksum for each of at least one table that comprises each second database;

assigning an index number to each table that comprises each second database; and

forming a data block for each table that comprises each second database that includes an index number block and a checksum block.

7. The method of claim 1 wherein the step of comparing the checksum for the first database to the checksum for each second database further comprises the steps of:

retrieving the data block for each table that comprises the first database;

retrieving the data block for each table that comprises the second database; and

comparing the checksum for each table that comprise the first database with the checksum for each corresponding table of each second database.

8. The method of claim 1, further comprising the steps of:

testing for the presence of an abort signal;

aborting the step of storing the changes made to each second database if an abort signal is present; and

rolling back the first database to its state before performing the series of changes.

9. The method of claim 1, further comprising the step of synchronizing a specific second database if the checksum for the first database does not match the checksum for the specific second database.

10. A method to verify the integrity of replicated databases in a telecommunications network, comprising the steps of:

determining a beginning checksum for a first database before a series of changes are made to the first database;

determining an ending checksum for the first database after the series of changes are made to the first database;

determining a beginning checksum for each of at least one second database before the series of changes are made to each second database;

determining an ending checksum for each second database after the series of changes are made to the second database; and

comparing the beginning and ending checksums determined for the first database to the corresponding beginning and ending checksums for each of the second databases before storing the changes to each of the second databases.

11. The method of claim 10, further comprising the step of transmitting the beginning and ending checksums determined for the first database and the series of changes to each second database after the step of determining an ending checksum for the first database.

12. The method of claim 10, further comprising the step of restoring a specific second database to its original configuration if the ending checksum for the first database does not match the ending checksum for the specific second database.

13. The method of claim 10, further comprising the step of synchronizing a specific second database if the beginning and ending checksums for the first database do not match the corresponding beginning and ending checksums for the specific second database.

14. The method of claim 10, wherein the step of determining a beginning checksum for a first database further comprises the steps of:

determining a checksum for each of at least one table that comprises the first database;

assigning an index number to each table that comprises the first database;

forming a first data block for each table that includes an index number block and a checksum block; and

forming a transaction journal message that includes a first data block for each table.

15. The method of claim 10, wherein the step of determining an ending checksum for the first database further comprises the steps of:

determining a checksum for each of at least one table that comprises the first database;

assigning an index number to each table that comprises the first database;

forming a second data block for each table that includes an index number block and a checksum block; and

forming a transaction journal message that includes a second data block for each table.

16. The method of claim 10, wherein the step of determining a beginning checksum for each second database further comprises the steps of:

determining a checksum for each of at least one table that comprises each second database;

assigning an index number to each table that comprises each second database; and

forming a first data block for each table that comprises each second database that includes an index number block and a checksum block.

17. The method of claim 10, wherein the step of determining an ending checksum for each second database further comprises the steps of:

determining a checksum for each of at least one table that comprises each second databases;

assigning an index number to each table that comprises each second database; and

forming a second data block for each table that comprises each second database that includes an index number block and a checksum block.

18. The method of claim 10 wherein the step of comparing the beginning and ending checksums determined for the first database to the corresponding beginning and ending checksums determined for each second database further comprises the steps of:

retrieving the first and second data blocks from the transaction journal message for each table that comprises the first database; and

comparing the beginning and ending checksum for each table that comprises the first database with the corresponding beginning and ending checksum for each table that comprises each second database.

19. The method of claim 10, further comprising the steps of:

testing for the presence of an abort signal;

aborting the step of storing the changes made to each second database if an abort signal is present; and

rolling back the first database to its state before performing the series of changes.

20. The method of claim 10, further comprising the steps of:

synchronizing a second database if the beginning checksum for the first database does not match the beginning checksum for the second database; and

synchronizing a second database if the ending checksum for the first database does not match the ending checksum for the second database.

21. A system for verifying the integrity of replicated databases in a telecommunications network, comprising:

a first checksum calculator for a first database, wherein the first checksum calculator is operable to calculate a checksum of the first database;

at least one second database, each having an associated second checksum calculator, wherein the second checksum calculator is operable to calculate a checksum of the associated second database; and

at least one checksum comparator, each associated with a second database, wherein each checksum comparator is operable to compare the checksum of the first database to the checksum of the second database to determine whether they are the same.

22. The system of claim 21, further comprising at least one synchronizer, each synchronizer associated with a second database and operable to analyze the second database to determine when to request retransmission of a missing single update message and when to request transmission of the entire database.

23. The system of claim 21, further comprising a data transceiver operable to transmit the checksum of the first database to each of the second databases.