Method and apparatus for data rollback

• US 8,880,480 B2
• Filed: 01/03/2007
• Issued: 11/04/2014
• Est. Priority Date: 01/03/2007
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kundu, Joydip, Brown, Archie W., Voss, Douglas A., Wang, Qinqin
• Primary Examiner(s): GIRMA, ANTENEH B
• Application Number:
  US11/649,180
• Publication Number:
  US 20080162590A1
• Time in Patent Office: 2,862 Days
• Field of Search: None
• US Class Current: 707/682
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• 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 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A database rollback processor allows rollback, or rewind, of the data and metadata to a point at which a failover or other metadata change occurred, therefore “rewinding” the metadata to a previous consistent point. The rollback processor identifies transaction entries in a redo log resulting in changes to the metadata. The changes are identified backward to a target recovery time. Transactions affecting the metadata are stored in a stack. The transactions are then backed out of the metadata according to the stack to restore the metadata to the state at the target recovery time. Data changes from the redo log may then be applied to the corresponding metadata as it existed at the target recovery time. Since the target recovery time is not bound by the timing of the snapshots, but rather may be at an arbitrary point chosen as the target recovery time, a failover, replication or recovery operation need not rely on the snapshot time.

Claims

1. A method comprising:

detecting a failover event for a primary database, where the primary database includes an associated data dictionary;

performing a failover by transferring database responsibilities from the primary database to a secondary database and includes causing a delay for capturing a snapshot of the data dictionary until a subsequent time to the failover;

storing, in a redo log, database operations performed on the secondary database from a time of the failover;

subsequent to the failover, capturing the snapshot of the data dictionary; and

generating a recreated data dictionary representing a state of the data dictionary at the time of the failover, where the generating includes performing redo operations from the redo log from a time of the capture of the snapshot back to the time of the failover.

2. The method of claim 1 where capturing the snapshot of the data dictionary includes capturing data that defines a structure of the primary database and an arrangement of data stored in the primary database.

3. The method of claim 1 where transferring the database responsibilities includes making the secondary database function as the primary database, and making the primary database function as a backup database to the secondary database.

4. The method of claim 1 further comprising obtaining the time of the failover and locking the data dictionary;

and noting a time before the lock on the data dictionary is released.

5. A computer system, comprising:

a primary database and a data dictionary that stores data that defines a structure of the primary database and an arrangement of content stored in the primary database;

a stand-by database configured as a backup to the primary database;

at least one processor configured to execute instructions stored in a memory that when executed cause the computer system to;

in response to a failover event associated with the primary database, perform failover operations including making the stand-by database function as a new primary database;

during the failover operations, delay capturing a snapshot of the data dictionary;

store, in a redo log, database operations performed with the stand-by database from a time of the failover;

subsequent to the failover, capture a current snapshot of the data dictionary; and

recreate the data dictionary in a state at the time of the failover by performing redo operations from the redo log from a time of the current snapshot back to the time of the failover.

6. The computer system of claim 5 further comprising:

one or more replication databases configured to provide a redundant architecture to the primary database.

7. The computer system of claim 5 where the computer system is configured to transmit copies of the recreated data dictionary to one or more replication databases.

8. The computer system of claim 5, wherein the memory further comprises stored instructions that when executed cause the computer system to obtain the time of the failover and lock the data dictionary;

and to note a time before the lock on the data dictionary is released.

9. A non-transitory computer-readable storage medium storing instructions that when executed by a processor cause the computer system to perform a method, the method comprising:

detecting a failover event for a primary database, where the primary database includes an associated data dictionary;

performing a failover by reassigning a secondary database to function as a new primary database where performing the failover includes delaying the capture of the snapshot of the data dictionary until a subsequent time;

storing, in a redo log, database operations performed on the secondary database from a time of the failover;

subsequent to the failover, capturing the snapshot of the data dictionary; and

recreating the data dictionary in a state at the time of the failover by performing redo operations from the redo log from the capture of the snapshot back to the time of the failover.

10. The computer-readable storage medium of claim 9 where the reassigning includes making the secondary database function as the primary database, and making the primary database function as a backup database to the secondary database.

11. The non-transitory computer-readable storage medium of claim 9, further comprising instructions for obtaining the time of the failover and locking the data dictionary, and instructions for noting a time before the lock on the data dictionary is released.