Pluggable database archive

A method comprising:

• creating a target pluggable database within a target container database and based on an archive file that contains:
• a plurality of data files that contain a plurality of records, and a manifest file that lists the plurality of data files;
• receiving a request to access a particular data block of a particular data file of the plurality of data files;
• detecting, based on the manifest file, a position of the particular data block within the archive file;
• retrieving, based on the position, the particular data block from within the archive file.

A system comprising:

• a first computer configured to:
• insert into an archive file:
• a plurality of data files that contain a plurality of records from a source pluggable database, a listing of the plurality of data files, one or more rollback scripts, and a list of patches that were applied to the source pluggable database;
• and
• create, based on the archive file, a target pluggable database within a target container database;
• a second computer configured to:
• retrieve the list of patches from the archive file, and
• execute, if a patch that is on the list of patches was not applied in the target container database, at least one of the one or more rollback scripts to adjust the target pluggable database.

A device comprising:

• one or more durable storages configured to store a target pluggable database within a target container database and an archive file that contains:
• a plurality of data files that contain a plurality of records, and a listing of the plurality of data files;
• a processor connected to the durable storage and configured to:
• create the target pluggable database based on the archive file;
• receive a request to access a particular data block of a particular data file of the plurality of data files;
• detect, based on the listing of the plurality of data files, a position of the particular data block within the archive file;
• retrieve, based on the position, the particular data block from within the archive file.

One or more non-transitory computer-readable media that store instructions that comprise:

• first instructions that, when executed by one or more processors, cause inserting into an archive file:
• a plurality of data files that contain a plurality of records from the source pluggable database, a listing of the plurality of data files, one or more rollback scripts, and a list of patches that were applied to the source pluggable database;
• second instructions that, when executed by the one or more processors, cause creating, based on the archive file, a target pluggable database within a target container database;
• third instructions that, when executed by the one or more processors, cause retrieving, the list of patches from the archive file;
• fourth instructions that, when executed by the one or more processors, cause executing, if a patch that is not on the list of patches was applied to the target pluggable database, at least one of the one or more rollback scripts to adjust the target pluggable database.

One or more non-transitory computer-readable media that store instructions that comprise:

• first instructions that, when executed by one or more processors, cause creating a target pluggable database within a target container database and based on an archive file that contains:
• a plurality of data files that contain a plurality of records, and a listing of the plurality of data files;
• second instructions that, when executed by the one or more processors, cause receiving a request to access a particular data block of a particular data file of the plurality of data files;
• third instructions that, when executed by the one or more processors, cause detecting, based on the manifest file, a position of the particular data block within the archive file;
• fourth instructions that, when executed by the one or more processors, cause retrieving, based on the position, the particular data block from within the archive file.