Cloning a pluggable database in read-write mode

Patent metadata

Field	Value
Publication number	US-10922331-B2
Application number	US-201615215435-A
Country	US
Kind code	B2
Filing date	Jul 20, 2016
Priority date	Sep 28, 2012
Publication date	Feb 16, 2021
Grant date	Feb 16, 2021

Abstract

Embodiments create a clone of a PDB while the PDB accepts write operations. While the PDB remains in read-write mode, the DBMS copies the data of the PDB and sends the data to a destination location. The DBMS performs data recovery on the PDB clone based on redo entries that record changes made to the source PDB while the DBMS copied the source PDB files. This data recovery makes all changes, to the PDB clone, that occurred to the source PDB during the copy operation. The redo information, on which the data recovery is based, is foreign to the PDB clone since the redo entries were recorded for a different PDB. In order to apply foreign redo information to perform recovery on the PDB clone, a DBMS managing the PDB clone maintains mapping information that maps PDB source reference information to corresponding information for the PDB clone.

First claim

What is claimed is:

1. A computer-executed method comprising:
receiving an instruction to clone, to a destination location, a particular pluggable database that resides within a source container database;
wherein a container database management system, that manages the source container database, maintains a database session for the particular pluggable database; and
in response to receiving the instruction, creating a copy of the particular pluggable database comprising:
determining an initial time stamp that marks a time occurring before any files, of a plurality of files in the particular pluggable database, are copied in connection with the received instruction to clone;
at least partly while one or more changes are made to the plurality of files in the particular pluggable database via the database session, copying files, of the plurality of files in the particular pluggable database, to the destination location to produce the copy of the particular pluggable database at the destination location;
wherein the one or more changes includes a particular change made to a particular file of the plurality of files to produce a changed particular file;
wherein copying the files to the destination location comprises copying the changed particular file to the destination location;
recording the particular change in a particular redo entry in one or more redo logs maintained by the container database management system;
determining a final time stamp that marks a time occurring after said copying the files, of the plurality of files in the particular pluggable database, is complete;
performing recovery on the copy of the particular pluggable database based, at least in part, on a set of redo entries, from the one or more redo logs, that comprise information for a set of changes made to the plurality of files in the particular pluggable database between times marked by the initial time stamp and the final time stamp;
wherein the set of redo entries includes the particular redo entry;

wherein the method is performed by one or more computing devices.

2. The method of claim 1 , wherein:
the files, of the plurality of files in the particular pluggable database, include undo information for the particular pluggable database;
copying the files comprises copying the undo information to produce a copy of the undo information; and
the copy of the particular pluggable database comprises the copy of the undo information.

3. The method of claim 2 , wherein performing recovery on the copy of the particular pluggable database comprises performing recovery on the copy of the undo information.

4. The method of claim 1 , further comprising:
maintaining mapping data that maps each file identifier in the particular pluggable database to a corresponding file identifier in the copy of the particular pluggable database;
wherein performing recovery on the copy of the particular pluggable database comprises performing recovery based, at least in part, on the mapping data.

5. The method of claim 1 , wherein the destination location is within the source container database that contains the particular pluggable database.

6. The method of claim 1 , wherein the destination location is within a destination container database other than the source container database that contains the particular pluggable database.

7. The method of claim 6 , further comprising:
prior to performing recovery on the copy of the particular pluggable database, collecting the set of redo entries, from the one or more redo logs, that record changes made to the plurality of files in the particular pluggable database between times marked by the initial time stamp and the final time stamp;
wherein said collecting the set of redo entries, from the one or more redo logs, comprises:
a first database server instance, that is associated with the source container database, sending redo entries, collected from the one or more redo logs, to a second database server instance that is associated with the destination container database.

8. The method of claim 1 , further comprising, after said performing recovery on the copy of the particular pluggable database, creating one or more connections, to the copy of the particular pluggable database at the destination location, based on one or more connection initiation requests for connections to the copy of the particular pluggable database.

9. The method of claim 1 , wherein the step of performing recovery is performed, at least partially, while the particular pluggable database is in read-write mode.

10. The method of claim 1 , further comprising:
performing a second round of recovery on the copy of the particular pluggable database based, at least in part, on a second set of redo entries, from the one or more redo logs, that record changes made to the plurality of files in the particular pluggable database after the final time stamp;
wherein the step of performing the second round of recovery is performed while the particular pluggable database is closed to write operations.

11. The method of claim 1 , wherein said performing recovery on the copy of the particular pluggable database results in the copy of the particular pluggable database being current as of the final time stamp.

12. One or more non-transitory computer-readable media storing one or more sequences of instructions that, when executed by one or more processors, cause:
receiving an instruction to clone, to a destination location, a particular pluggable database that resides within a source container database;
wherein a container database management system, that manages the source container database, maintains a database session for the particular pluggable database; and
in response to receiving the instruction, creating a copy of the particular pluggable database comprising:
determining an initial time stamp that marks a time occurring before any files, of a plurality of files in the particular pluggable database, are copied in connection with the received instruction to clone;
at least partly while one or more changes are made to the plurality of files in the particular pluggable database via the database session, copying files, of the plurality of files in the particular pluggable database, to the destination location to produce the copy of the particular pluggable database at the destination location;
wherein the one or more changes includes a particular change made to a particular file of the plurality of files to produce a changed particular file;
wherein copying the files to the destination location comprises copying the changed particular file to the destination location;
recording the particular change in a particular redo entry in one or more redo logs maintained by the container database management system;
determining a final time stamp that marks a time occurring after said copying the files, of the plurality of files in the particular pluggable database, is complete;
performing recovery on the copy of the particular pluggable database based, at least in part, on a set of redo entries, from the one or more redo logs, that comprise information for a set of changes made to the plurality of files in the particular pluggable database between times marked by the initial time stamp and the final time stamp;
wherein the set of redo entries includes the particular redo entry.

13. The one or more non-transitory computer-readable media of claim 12 , wherein:
the files, of the plurality of files in the particular pluggable database, include undo information for the particular pluggable database;
copying the files comprises copying the undo information to produce a copy of the un

Assignees

• Oracle Int Corp

Inventors

• Ravipati Giridhar
• Rajamani Kumar
• Li Yunrui
• Lee Jaebock
• Jain Sanket

Classifications

• G06F16/27 Primary

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/273 Primary

  Asynchronous replication or reconciliation · CPC title

• G06F16/119

  Details of migration of file systems (migration mechanisms in storage systems G06F3/0647) · CPC title

• G06F11/1471

  involving logging of persistent data for recovery · CPC title

• G06F16/214

  Database migration support · CPC title