Method and apparatus for replicated transaction consistency

• US 6,012,059 A
• Filed: 08/21/1997
• Issued: 01/04/2000
• Est. Priority Date: 08/21/1997
• Status: Expired due to Term

• Current Assignee: Dataxel Corporation, Oracle International Corporation (Oracle Corporation)
• Original Assignee: Dataxel Corporation
• Inventors: Neimat, Marie-Anne, Shoens, Kurt, Shmueli, Oded
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/918,686
• Time in Patent Office: 866 Days
• Field of Search: 707/8, 707/200, 707/201, 707/10
• US Class Current: 1/1
• 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: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

Local transactions are run at replication sites while receiving and tracking replication packages from primary sites. If a package coming in from a primary site updates data that a local transaction used, the data is considered stale and the local transaction is restarted. When the replication site wishes to commit (e.g., update data at the primary sites), a special dummy marker is submitted and committed. The marker comprises a dummy transaction that updates a piece of data at the primary site private to the replication site. The local site waits for the dummy transaction in the stream of replication packages sent from the primary site. Once the dummy transaction is received, the replication site is assured that any subsequent replication packages from the primary site will not affect the local transaction. If the replication packages received before the marker do not affect data items referenced during the local transaction, the local transaction commits.

Claims

1. A method for conducting transactions on replica data items replicated from a primary site, comprising:

initiating a local transaction on the replica data items;

referencing the replica data items with the local transaction;

generating updates to the replica data items from the primary site, the updates occurring independently of the local transaction;

identifying which replica data items were updated at the primary site during the local transaction;

committing the local transaction to the primary site when the local transaction references to the replica data items occur independently of identified replica data items updated from the primary site;

establishing a reference point in time when data items are updated at the primary site by;

committing a dummy transaction to the primary site;

identifying one of the updates from the primary site returning the dummy transaction; and

identifying a set of primary site updates occurring from the initiation of the local transaction to reception of the dummy transaction; and

committing the local transaction only when replica data items referenced by the local transaction are not updated from the primary site before the reference point.

2. A method according to claim 1 wherein the step of committing the dummy transaction comprises modifying one of the replica data items with a unique identifier for the local transaction.

5. A method according to claim 1 wherein establishing the reference point comprises the following steps:

assigning numbers in sequence for each update to the replica data items made at the primary site;

requesting the numbers from the primary site; and

committing the local transaction when the requested numbers have previously received by the local transaction.

6. A method according to claim 1 wherein establishing a reference point comprises the following steps:

requesting a marker with the local transaction;

placing the marker in updates to the replica data items from the primary site; and

identifying a set of primary site updates occurring from the initiation of the local transaction to reception of the marker.

7. A method according to claim 1 including the following steps:

storing a set of temporary replica data items updated by the local transaction;

committing the set of temporary updates to the primary site when the local transaction commits; and

aborting the set of temporary updates when the local transaction references coincide with the primary site updates.

8. A methods according to claim 1 including the following steps:

generating the replica data items from multiple primary sites;

tracking local transaction updates according to which one of the primary sites generated the replica data items; and

identifying which replica data items were updated by each one of the tracked primary sites during the local transaction.

9. A method according to claim 1 wherein updated replica data items are identified using triggers for each replica data item updated by the local transaction.

10. A method according to claim 1 including the following steps:

providing a record at the primary site; and

modifying the record before committing the local transaction for serializing transaction validation among the replica sites.

11. A method according to claim 1 including the following steps:

temporarily storing local transaction updates to the replica data items in a transaction scope;

tracking each local transaction reference to the replica data items in a first list;

tracking each primary site update to the replica data items in a second list; and

committing the first transaction scope to the primary site when the first and second lists comprise independent replica data items.

12. A method according to claim 11 including aborting the first transaction scope when the first and second lists include common replica data items.

3. A method for conducting transactions on replica data items replicated from multiple primary sites, comprising:

initiating a local transaction on the replica data items;

referencing the replica data items with the local transaction;

generating updates to the replica data items from the multiple primary sites, the updates occurring independently of the local transaction;

tracking local transaction updates according to which one of the primary sites generated the replica data items;

identifying which replica data items were updated by each one of the tracked primary sites during the local transaction by;

committing a dummy transaction to each one of the primary sites;

waiting for the dummy transaction updates from each one of the primary sites; and

identifying all updates from the primary sites that occur from initiation of the local transaction to reception of all dummy transactions; and

committing the local transaction to the tracked primary sites when the local transaction references to the replica data items occur independently of identified replica data items updated from the multiple primary sites.

4. A method for conducting transactions on replica data items replicated from a primary site, comprising:

initiating a local transaction on the replica data items;

referencing the replica data items with the local transaction;

generating updates to the replica data items from the primary site, the updates occurring independently of the local transaction;

identifying during the local transaction which replica data items were updated at the primary site;

establishing a reference point in time when data items are updated at the primary site; and

committing the local transaction only when replica data items referenced by the local transaction are updated from the primary site after the reference point.

13. A replicated data system, comprising:

at least one primary site for storing a database, the primary site generating replication packages reflecting updates to portions of the database;

at least one local site connected to the primary site, the local site storing a local replica of at least a portion of the database and conducting local transactions with the local replica; and

the local site generating a marker after each local transaction and waiting for receipt of the marker from the primary site before committing each local transaction thereby identifying which of the replication packages affected the local replica during the local transaction.

14. A system according to claim 13 wherein the local site includes a local update transaction scope for temporarily storing local transaction updates to the replica data.

15. A system according to claim 13 wherein the primary site comprises a database file server and the local site comprises an application server coupled to the database file server with a local area network.

16. A system according to claim 13 wherein the local site includes a reference transaction scope for tracking each local transaction reference to the replica data.

17. A system according to claim 13 wherein the local site includes a primary update transaction scope for tracking each primary site update to the replica data.

18. A method for conducting local transactions on replica data copied from a primary database, comprising:

generating replication packages for updating data items in the replica data;

conducting a transaction that references the replica data;

establishing a reference point when data items are updated at the primary database; and

committing the local transaction to the primary database when the replication packages generated prior to the reference point do not update the data items referenced during the transaction.

19. A method according to claim 18 including the following steps:

temporarily storing local transaction updates to the replica data items in a transaction scope;

tracking each local transaction reference to the replica data items in a first list;

tracking each primary site update to the replica data items in a second list;

committing the transaction scope to the primary site when the first and second lists comprise independent replica data items; and

aborting the transaction scope when the first and second lists track common portions of the replica data.

20. The method according to claim 18 wherein establishing a reference point includes the following steps:

committing a marker to the primary database at the end of the transaction;

identifying one of the replication packages containing the marker; and

committing the transaction to the primary database when the replication packages generated prior to the marker do not update the data items referenced during the transaction.

21. A method according to claim 18 wherein the step of committing a marker comprises generating a trigger to the primary database.