In place point-in-time recovery of pluggable databases

Patent metadata

Field	Value
Publication number	US-9298564-B2
Application number	US-201313830349-A
Country	US
Kind code	B2
Filing date	Mar 14, 2013
Priority date	Sep 28, 2012
Publication date	Mar 29, 2016
Grant date	Mar 29, 2016

Abstract

In an approach, a database server maintains a container database which comprises: one or more pluggable databases, a root database that stores an undo log for rolling back transactions on the consolidated database, and a redo log for replaying modifications to the container database. The database server restores a particular pluggable with a backup version that corresponds to a first point in time. The database server generates a clone database loaded with a backup version of the root database that corresponds to the first point in time. The database server applies the redo log to recover the particular pluggable database and the clone database to a second point in time that is later than the first point in time. The database server identifies, based on the clone database, one or more active transactions on the particular pluggable database. The database server rolls back the one or more active transactions.

First claim

What is claimed is:

1. A method comprising:
a database server maintaining a container database, wherein the container database comprises:
one or more pluggable databases,
a root database that stores an undo log for rolling back transactions on the one or more pluggable databases, and
a redo log for replaying modifications to the container database;

the database server restoring a particular pluggable database with a backup version of the particular pluggable database that corresponds to a first point in time;
the database server generating a clone database loaded with a backup version of the root database that corresponds to the first point in time, the clone database including a backup version of the undo log of the root database;
the database server applying one or more redo records of the redo log to recover the particular pluggable database and the clone database, including the backup version of the undo log, to a second point in time that is later than the first point in time;
the database server identifying, based on the backup version of the undo log in the clone database, one or more active transactions on the particular pluggable database that have not committed by the second point in time;
the database server rolling back the one or more active transactions, wherein modifications to the particular pluggable database performed during roll back of the one or more active transactions are recorded in the redo log;
wherein the method is performed by one or more computing devices.

2. The method of claim 1 , further comprising receiving one or more user instructions that specify to recover the particular pluggable database to the second point in time.

3. The method of claim 1 , wherein the first point in time corresponds to a state of the container database after a first number of transactions has committed and the second point in time corresponds to a second state of the container database after a second number of transactions has committed, wherein the first number is less than the second number.

4. The method of claim 1 , further comprising storing data that is shared between the one or more pluggable databases in the root database.

5. The method of claim 1 , wherein the database server does not record modifications to the clone database performed during rollback of the one or more active transactions in the redo log of the container database.

6. The method of claim 1 , wherein each pluggable database of the one or more pluggable databases contains a separate data dictionary.

7. The method of claim 1 , wherein the root database contains a data dictionary that defines one or more database objects that are shared between the one or more pluggable databases.

8. The method of claim 1 , further comprising the database server dropping the clone database.

9. The method of claim 1 , wherein at least one pluggable database of the one or more pluggable databases remains available for user transactions while the particular pluggable database is being restored by the database server.

10. The method of claim 1 , further comprising:
the database server restoring the particular pluggable database with a backup version of the particular pluggable database that corresponds to a third point in time that is earlier than the second point in time;
the database server applying one or more redo records of the redo log to recover the particular pluggable database to a fourth point in time that is later than the second point in time.

11. A non-transitory computer-readable storage medium storing one or more instructions which, when executed by one or more processors, cause the one or more processors to:
maintain, via a database server, a container database, wherein the container database comprises:
one or more pluggable databases,
a root database that stores an undo log for rolling back transactions on the one or more pluggable databases, and
a redo log for replaying modifications to the container database;

restore, via the database server, a particular pluggable database with a backup version of the particular pluggable database that corresponds to a first point in time;
generate, via the database server, a clone database loaded with a backup version of the root database that corresponds to the first point in time, the clone database including a backup version of the undo log of the root database;
apply, via the database server, one or more redo records of the redo log to recover the particular pluggable database and the clone database, including the backup version of the undo log, to a second point in time that is later than the first point in time;
identify, via the database server, based on the backup version of the undo log in the clone database, one or more active transactions on the particular pluggable database that have not committed by the second point in time;
roll back, via the database server, the one or more active transactions, wherein modifications to the particular pluggable database performed during roll back of the one or more active transactions are recorded in the redo log.

12. The non-transitory computer-readable storage medium of claim 11 , wherein the one of more instructions further cause the one or more processors to receive one or more user instructions that specify to recover the particular pluggable database to the second point in time.

13. The non-transitory computer-readable storage medium of claim 11 , wherein the first point in time corresponds to a state of the container database after a first number of transactions has committed and the second point in time corresponds to a second state of the container database after a second number of transactions has committed, wherein the first number is less than the second number.

14. The non-transitory computer-readable storage medium of claim 11 , wherein the one or more instructions further cause the one or more processors to store data that is shared between the one or more pluggable databases in the root database.

15. The non-transitory computer-readable storage medium of claim 11 , wherein the database server does not record modifications to the clone database performed during rollback of the one or more active transactions in the redo log of the container database.

16. The non-transitory computer-readable storage medium of claim 11 , wherein each pluggable database of the one or more pluggable databases contains a separate data dictionary.

17. The non-transitory computer-readable storage medium of claim 11 , wherein the root database contains a data dictionary that defines one or more database objects that are shared between the one or more pluggable databases.

18. The non-transitory computer-readable storage medium of claim 11 , wherein the one or more instructions further cause the one or more processors to drop, via the database server, the clone database.

19. The non-transitory computer-readable storage medium of claim 11 , wherein at least one pluggable database of the one or more pluggable databases remains available for user transactions while the particular pluggable database is being restored by the database server.

20. The non-transitory computer-readable storage medium of claim 11 , wherein the one or more instructions further cause the one or more processors to:
restore, via the database server, the particular pluggable database with a backup version of the particular pluggable database that corresponds to a third point in time that is earlier than the second point in time;
apply, via the database server, one or more redo

Assignees

• Oracle Int Corp

Inventors

• Lee J William
• Gokhale Vipin
• Olagappan Muthu
• Hase Sanket
• Raja Vivekanandhan
• Skarpelos Michael John
• Stewart Michael

Classifications

• G06F12/084

  with a shared cache · CPC title

• G06F11/1448

  Management of the data involved in backup or backup restore · CPC title

• G06F11/1471 Primary

  involving logging of persistent data for recovery · CPC title

• G06F16/211

  Schema design and management · CPC title

• G06F16/256

  in federated or virtual databases · CPC title