Method and system for validating remote database updates

• US 7,047,258 B2
• Filed: 11/01/2002
• Issued: 05/16/2006
• Est. Priority Date: 11/01/2001
• Status: Active Grant

• Current Assignee: VeriSign, Inc.
• Original Assignee: VeriSign, Inc.
• Inventors: McMillen, Bradley Thomas, Balogh, Aristotle Nicholas
• Primary Examiner(s): Mofiz, Apu
• Assistant Examiner(s): Wu, Yicun
• Application Number:
  US10/285,547
• Publication Number:
  US 20030084074A1
• Time in Patent Office: 1,292 Days
• Field of Search: 707/1, 707/2, 707/3, 707/4, 707/5, 707/6, 707/7, 707/8, 707/9, 707/10, 707/100, 707/104.1, 707/201, 707/202, 707/203, 707/101, 707/102, 707/200, 395/610
• US Class Current: 707/610
• CPC Class Codes: G06F 16/2315 Optimistic concurrency control
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/966 Distributed
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Embodiments of the present invention provide a method and system for validating remote database updates over a network. A local database record and a remote database record may be compared and exceptions may be generated. Each exception may describe a discrepancy between the remote and local database records. An exception identifier may be associated with each exception, where the exception identifier may be associated with an identifier of the record. An event identifier may be associated with each event in the update, where the event identifier may be associated with an identifier of the record. The events and exceptions that correspond to the record may be compared to determine whether the update is valid.

Claims

1. A computer implemented method for validating an update to a record in a remote database over a network, the update including at least one event, comprising:

comparing the record in the remote database with a corresponding record in a local database;

generating an exception that describes a discrepancy between the remote database record and the local database record, for each discrepancy;

associating an exception identifier with each exception, wherein each exception identifier is associated with an identifier of the record;

associating an event identifier with each event in the update, wherein each event identifier is associated with an identifier of the record; and

determining whether the update is valid by comparing the events and exceptions that correspond to the record;

wherein the types of exceptions include;

a first exception type in which the record is in the remote database and not in the local database;

a second exception type in which the record is in the local database and not in the remote database; and

a third exception type in which the record is in the local database and the remote database and a value of a field of the record in the local database is different than the value of the same field of the record in the remote database.

2. The method of claim 1, wherein the update to the record is valid if every exception corresponding to the record is justified by an event corresponding to the record.

3. The method of claim 1, wherein the event justifies the exception if:

the event is a deletion of the record from the local database and the exception is the first exception type, the event is an addition of the record to the local database and the exception is the second exception type, the event is a modification of the record in the local database and the exception is the third exception type, or the event is a deletion from followed by an addition of the record to the local database and the exception is the third exception type.

4. The method of claim 1, further comprising:

repeating the method for validating the update a given amount of time after the update was determined to be invalid, if the update is determined to be invalid.

5. The method of claim 1, wherein the comparing includes:

comparing the entire local database against the entire remote database.

6. A computer implemented method for validating a remote database, comprising:

sending to the remote database a plurality of periodic updates based on incremental changes to a local database, each of the plurality of periodic updates having at least one transaction;

sending to the remote database an initialization update including a version of the local database as the local database existed at a start time, wherein the initialization update is applied to the remote database;

identifying discrepancies between the local database and the remote database;

determining whether the discrepancies are valid; and

notifying the remote database to apply the periodic updates that have a start time later than the start time of the initialization update;

wherein the discrepancies include;

a first discrepancy type in which a record is in the remote database and not in the local database;

a second discrepancy type in which a record is in the local database and not in the remote database; and

a third discrepancy type in which the record is in the local database and the remote database and a value of a field of the record in the local database is different than the value of the same field of the record in the remote database.

7. The method of claim 6, further comprising:

repeating the method for validating the update a given amount of time after the update was determined to be invalid, if the update is determined to be invalid.

8. A computer system for validating an update to a record in a remote database over a network, wherein the update includes at least one event, the system, comprising:

at least one processor coupled to the network; and

a memory coupled to the processor, the memory including a database and instructions adapted to be executed by the processor to implement a method for validating the update of the record in the remote database over the network, the method including;

comparing the record in the remote database with a corresponding record in a local database, generating an exception that describes a discrepancy between the remote database record and the local database record, for each discrepancy, associating an exception identifier with each exception, wherein each exception identifier is associated with an identifier of the record, associating an event identifier with each event in the update, wherein each event identifier is associated with an identifier of the record, and determining whether the update is valid by comparing the events and exceptions that correspond to the record;

wherein the types of exceptions include;

a first exception type in which the record is in the remote database and not in the local database;

a second exception type in which the record is in the local database and not in the remote database; and

a third exception type in which the record is in the local database and the remote database and a value of a field of the record in the local database is different than the value of the same field of the record in the remote database.

9. The system of claim 8, wherein the update to the record is valid if every exception corresponding to the record is justified by an event corresponding to the record.

10. The system of claim 8, wherein the event justifies the exception if:

the event is a deletion of the record from the local database and the exception is the first exception type,

the event is an addition of the record to the local database and the exception is the second exception type,

the event is a modification of the record in the local database and the exception is the third exception type, or

the event is a deletion from followed by an addition of the record to the local database and the exception is the third exception type.

11. The system of claim 8, wherein, if the update is determined to be invalid, the processor repeats the method for validating the update a given amount of time after the update was determined to be invalid.

12. The system of claim 9, wherein the processor compares the entire local database against the entire remote database.

13. The system of claim 8, further comprising:

at least one remote processor coupled to the network; and

a remote memory coupled to the remote processor, the remote memory storing the remote database and instructions adapted to be executed by the remote processor to;

create a new element based on new information received from the database over the network, and without restricting search access to the remote database, write a pointer to the new element to the remote database using a single uninterruptible operation.

14. The system of claim 13, wherein the instructions are further adapted to:

physically delete an existing element after the pointer is written to the database.

15. The system of claim 13, wherein the single uninterruptible operation is a store instruction.

16. The system of claim 15, wherein the remote processor has a word size of at least n-bytes, the remote memory has a width of at least n-bytes and the store instruction writes n-bytes to a remote memory address located on an n-byte boundary.

17. A machine readable medium including program instructions adapted to be executed by a processor to implement a method for validating an update to a record in a remote database over a network, wherein the update includes at least one event, the method comprising:

comparing the record in the remote database with a corresponding record in a local database;

generating an exception that describes a discrepancy between the remote database record and the local database record, for each discrepancy;

associating an exception identifier with each exception, wherein each exception identifier is associated with an identifier of the record;

associating an event identifier with each event in the update, wherein each event identifier is associated with an identifier of the record; and

determining whether the update is valid by comparing the events and exceptions that correspond to the record;

wherein the types of exceptions include;

a first exception type in which the record is in the remote database and not in the local database;

a second exception type in which the record is in the local database and not in the remote database; and

a third exception type in which the record is in the local database and the remote database and a value of a field of the record in the local database is different than the value of the same field of the record in the remote database.

18. The machine readable medium of claim 17, wherein, if the update is determined to be invalid, the processor repeats the method for validating the update a given amount of time after the update was determined to be invalid.

19. The machine readable medium of claim 17, wherein the update to the record is valid if every exception corresponding to the record is justified by an event corresponding to the record.