Pluggable database archive

Patent metadata

Field	Value
Publication number	US-11550667-B2
Application number	US-202016791091-A
Country	US
Kind code	B2
Filing date	Feb 14, 2020
Priority date	Oct 23, 2015
Publication date	Jan 10, 2023
Grant date	Jan 10, 2023

Abstract

Techniques herein make and use a pluggable database archive file (AF). In an embodiment, a source database server of a source container database (SCD) inserts contents into an AF from a source pluggable database (SPD). The contents include data files from the SPD, a listing of the data files, rollback scripts, and a list of patches applied to the SPD. A target database server (TDS) of a target container database (TCD) creates a target pluggable database (TPD) based on the AF. If a patch on the list of patches does not exist in the TCD, the TDS executes the rollback scripts to adjust the TPD. In an embodiment, the TDS receives a request to access a block of a particular data file. The TDS detects, based on the listing of the data files, a position of the block within the AF. The TDS retrieves the block based on the position.

First claim

What is claimed is:

1. A computer-implemented method comprising:
inserting, by a source database server of a source container database, into a single archive file:
a plurality of data files that contain a plurality of records from a source pluggable database of the source container database,
a listing of the plurality of data files, and
a list of release patches that were applied to the source pluggable database;

detecting, by a target database server and based on the list of release patches, that the single archive file specifies a range of release versions that contains a release version of a target container database;
creating, based on the single archive file, a target pluggable database within the target container database;
receiving a database statement that accesses data in the target pluggable database;
retrieving, based on the database statement, a particular data block within the single archive file.

2. The method of claim 1 further comprising detecting at least one selected from the group consisting of:
the target container database contains a particular relational table, and
the target container database contains a relational table that contains a particular column.

3. The method of claim 1 wherein said creating the target pluggable database comprises resolving a version incompatibility of the target container database.

4. The method of claim 1 wherein said retrieving the particular data block within the single archive file comprises including the particular data block in a scan of a relational table that is defined in a database dictionary of the target pluggable database.

5. The method of claim 1 wherein:
the database statement specifies reading and writing the data;
the single archive file is read only;
the method further comprises in response to said receiving the database statement, persisting a specific data block outside of the single archive file.

6. The method of claim 1 wherein said inserting into the single archive file comprises compressing the plurality of data files but not compressing the listing of the plurality of data files.

7. The method of claim 1 further comprising inserting, by the source database server of the source container database, into the single archive file, at least one selected from the group consisting of a data manipulation language (DML) statement and a data definition language (DDL) statement.

8. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause:
inserting, by a source database server of a source container database, into a single archive file:
a plurality of data files that contain a plurality of records from a source pluggable database of the source container database,
a listing of the plurality of data files, and
a list of release patches that were applied to the source pluggable database;

detecting, by a target database server and based on the list of release patches, that the single archive file specifies a range of release versions that contains a release version of a target container database;
creating, based on the single archive file, a target pluggable database within the target container database;
receiving a database statement that accesses data in the target pluggable database;
retrieving, based on the database statement, a particular data block within the single archive file.

9. The one or more non-transitory computer-readable media of claim 8 wherein said instructions further cause detecting at least one selected from the group consisting of:
the target container database contains a particular relational table, and
the target container database contains a relational table that contains a particular column.

10. The one or more non-transitory computer-readable media of claim 8 wherein said creating the target pluggable database comprises resolving a version incompatibility of the target container database.

11. The one or more non-transitory computer-readable media of claim 8 wherein said retrieving the particular data block within the single archive file comprises including the particular data block in a scan of a relational table that is defined in a database dictionary of the target pluggable database.

12. The one or more non-transitory computer-readable media of claim 8 , wherein:
the database statement specifies reading and writing the data;
the single archive file is read only;
the instructions further cause in response to said receiving the database statement, persisting a specific data block outside of the single archive file.

13. The one or more non-transitory computer-readable media of claim 8 wherein said inserting into the single archive file comprises compressing the plurality of data files but not compressing the listing of the plurality of data files.

14. A system comprising:
one or more computers that host a source database server and a target database server, wherein:
the source database server is configured to insert into a single archive file:
a plurality of data files that contain a plurality of records from a source pluggable database of a source container database,
a listing of the plurality of data files, and
a list of release patches that were applied to the source pluggable database;

the target database server is configured to:
detect, based on the list of release patches, that the single archive file specifies a range of release versions that contains a release version of a target container database;
create, based on the single archive file, a target pluggable database within the target container database;
receive a database statement that accesses data in the target pluggable database;
retrieve, based on the database statement, a particular data block within the single archive file.

15. The system of claim 14 wherein said target database server is further configured to detect at least one selected from the group consisting of:
the target container database contains a particular relational table, and
the target container database contains a relational table that contains a particular column.

Assignees

• Oracle Int Corp

Inventors

• Shanthaveerappa Prashanth
• Ravipati Giridhar
• Susairaj Margaret
• Rajamani Kumar

Classifications

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• G06F2201/80

  Database-specific techniques · CPC title

• G06F16/113

  Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446) · CPC title

• G06F16/21 Primary

  Design, administration or maintenance of databases · CPC title

• G06F11/1458

  Management of the backup or restore process · CPC title