28 Simplified Data Transport Using RMAN Backups
Starting with Oracle Database 23ai, RMAN provides a simplified approach for transporting data across platforms.
28.1 Simplified Data Transport Concepts
You can use regular RMAN backups stored on tape to transport tablespaces and pluggable databases (PDB) from a source platform to a destination platform.
In the simplified data transport method, you can leverage preexisting backups available as part of your regular production backup schedules. On a destination platform, RMAN restores the data files from the RMAN backups and plugs in a tablespace or a PDB on the destination database to complete the data transport process in a simplified and efficient manner.
For example, to quickly transport a PDB, you can restore the data files from a preexisting backup of a PDB, and then plug in the PDB to the destination CDB.
RMAN obtains the backup information either from a recovery catalog or from a transport file. In the NOCATALOG
mode, the transport file provides RMAN with the backup information in XML
format.
- You can offload all the complexities associated with transferring and restoring data from a source platform to a destination platform.
- You can leverage regular RMAN backups to transport data. This eliminates any additional steps required to prepare tablespaces or PDBs for transport.
- You can avoid extensive application downtime for transporting data. The source database can remain operational for the entire period when you create backups on a source platform and restore the data files from backups on a destination platform. The process requires minimal application downtime only when RMAN needs to perform a final restore operation on a destination platform.
28.1.1 Methods of Transporting Data Using RMAN Backups
Starting with Oracle Database 23ai, use one of these methods to transport PDBs and tablespaces using their corresponding RMAN backups:
- Transport PDBs and tablespaces across platforms with a recovery catalog connection
In this method, RMAN must be connected to the same recover catalog when you create backups and perform restores.
On a destination database, you must first run the
RESTORE PREVIEW
command along with theTO TRANSPORT LIST
option to generate an in-memory transport list. You can then run theRESTORE
command using the transport list. RMAN restores the data files from backups ,rolls forward the restored data files by applying incremental backups, and then plugs in a tablespace or PDB on the destination database. - Transport PDBs and tablespaces across platforms in
NOCATALOG
modeIn this method, you must create a transport file on the source database. Run the
RESTORE PREVIEW
command along with theTO TRANSPORT FILE
option to store information about the source database backups in a transport file.On the destination database, run the
RESTORE
command using the transport file. RMAN restores the data files from backups ,rolls forward the restored data files by applying incremental backups, and then plugs in a tablespace or PDB on the destination database. - Transport pluggable databases and tablespaces over the network
In this method, RMAN uses the source database files to optimally transfer data over the network. RMAN can connect to the source platform, create the required backups, transfer the backups over the network to the destination platform, and perform the restore operation.
28.1.2 Prerequisites for Transporting Data Using RMAN Backups
- Before you transport a PDB to a different platform, ensure that:
- The destination platform follows the same endian format as the source platform
- The PDB uses local undo
- Before you transport a tablespace, ensure that the tablespace is self-contained. To determine whether a set of tablespaces is self-contained, run the
TRANSPORT_SET_CHECK
procedure in the Oracle supplied packageDBMS_TTS
.You can transport tablespaces to a destination platform that uses a different endian format from the source platform.
- In the recovery catalog based method, ensure that:
- The
COMPATIBLE
initialization parameter of the source and destination databases must be set to 23.0. - The source database and the destination database are both registered in the same recovery catalog.
- The
- In the
NOCATALOG
mode based method, RMAN requires a transport file that contains backup information stored inXML
format. Before you restore the data files from backups on a destination database, ensure to store the transport file in a shared location or a network file location (NFS) path that is accessible to the destination host. - In the network-based method:
- You must create a database link on the destination database before you perform the final transport of a PDB or a tablespace to a destination platform.
Use the
SQL*PLUS
CREATE DATABASE LINK
statement to create aPUBLIC
dblink
.For example, in the following statement, userrco
on the destination database defines a database link callednetworklink
that refers to the pluggable databasepdb1
on the CDBcdb1
.CREATE PUBLIC DATABASE LINK pluginlink CONNECT TO rco IDENTIFIED BY password USING 'cdb1_pdb1'
The
dblink
is used to transport the export dump file or the PDB unplug XML file from the source database to the destination database. - Before you perform a final transport of a tablespace over the network, grant the
EXP_FULL_DATABASE
privilege to theSYSBACKUP
user on the source database.
- You must create a database link on the destination database before you perform the final transport of a PDB or a tablespace to a destination platform.
28.2 Transporting PDBs Across Platforms with a Recovery Catalog
Learn the different ways in which you can transport a PDB by using a backup of the PDB when RMAN is connected to a recovery catalog.
28.2.1 About Transporting PDBs with a Recovery Catalog Connection
In this method, RMAN queries the metadata stored in the recovery catalog to determine the exact backups required for the restore operation and to plug in a PDB on a destination CDB.
These are the essential steps you need to perform to transport a PDB by using a PDB backup when RMAN is connected to a recovery catalog:
On a source CDB:
- Connect RMAN to a recovery catalog
- Use a preexisting backup of a PDB or create a new backup using the
BACKUP PLUGGABLE DATABASE
command - Create a final incremental level 1 backup of the source PDB when the PDB is in a read-only mode.
- Use the
BACKUP PLUGGABLE DATABASE
command to create a final incremental level 1 backup. - Use the
DATAPUMP
clause to create an export dump file along with the incremental backup.
- Use the
On a destination CDB:
- Connect RMAN to the same recovery catalog as the source CDB.
- Use the
SET
command along with theFOREIGN DBID
clause to set theDBID
of the source PDB - Use the
RESTORE
command along with thePREVIEW
clause and theTO TRANSPORT LIST
clause to generate a transport list. The transport list remains in-memory and indicates the PDB backups that RMAN needs to perform a restore operation on the destination CDB. - Use the
RESTORE
command with theFROM TRANSPORT LIST
clause to perform a restore operation using the transport list. RMAN restores the data files from backups, rolls forward, and plugs in the PDB on the destination CDB.
Note:
If the Oracle Active Data Guard logical database rolling upgrade process is running on a destination database, RMAN cannot successfully complete the final step involved in transporting data using backups. This is because the rolling upgrade process restricts RMAN from importing the backup metadata required to restore a final backup and plug in a PDB on the destination database.28.2.2 Quickly Transport a PDB with a Recovery Catalog Connection
Oracle recommends this method for transporting small-sized PDBs that take less time to backup.
In this quick transport method, you must create an incremental level 0 backup of the source PDB, and an export dump file along with the backup. On the destination platform, generate a transport list and perform a single restore operation using the transport list. RMAN restores the data files from the level 0 backup, and then plugs in the PDB on the destination CDB.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.2.2.1 Source CDB: Preparing to Quickly Transport a PDB with a Recovery Catalog Connection
When the source PDB is in read-only mode, create an incremental level 0 backup and an export dump file along with the backup.
28.2.2.2 Destination CDB: Quickly Restore and Plug In a PDB with Recovery Catalog Connection
Perform the final steps required to quickly transport a PDB to a destination CDB when RMAN is connected to a recovery catalog.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
Restore data files from backups and plug in the PDB using the transport list.
28.2.3 Transport a PDB by Using a Preexisting Backup and Recovery Catalog Connection
RMAN enables you to transport a PDB by leveraging a preexisting PDB backup (level 0) that is available as part of your regular backup schedule.
When the source PDB is in read-only mode, you must create a final incremental level 1 backup of the source PDB and an export dump file along with the incremental backup.
On the destination CDB, generate a transport file and then perform a single restore operation using the transport file. RMAN restores the data files using the most recent preexisting level 0 backup of the PDB, rolls-forward the restored data files by applying the final incremental level 1 backup, and then plugs in the PDB on the destination CDB.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.2.3.1 Source CDB: Preparing to Transport a PDB Using a Preexsiting Backup and Recovery Catalog Connection
You can use a most recent preexsiting backup of a PDB to transport the PDB to a destination platform.
28.2.3.2 Destination CDB: Restore Data Files from a Preexisting Backup and Plug In a PDB with Recovery Catalog Connection
Restore the data files from a preexisting PDB backup and plug in the PDB on the destination CDB.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.2.4 Transport a PDB Using Multiple Incremental Backups and Recovery Catalog Connection
Oracle recommends this method for transporting large-size PDBs across platforms with minimum application downtime on the source PDB.
On the destination CDB, you must first restore the data files from a preexisting backup or new backup of the PDB. You can then roll forward the restored data files by applying multiple incremental level 1 backups periodically. While the source PDB remains open and operational, you can continue to apply any number of incremental level 1 backups on the destination CDB until you want to perform the final transport.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.2.4.1 Source CDB: Preparing to Transport a PDB Using Multiple Incremental Backups and Recovery Catalog Connection
You can leverage a preexisting PDB backup. Optionally, use this procedure to create an incremental level 0 backup of the source PDB.
28.2.4.2 Destination CDB: Restore Data Files from a Level 0 Backup of a PDB with Recovery Catalog Connection
The level 0 backup serves as a basis for RMAN to apply subsequent increment level 1 backups of the PDB.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.2.4.3 Restore Incremental Backups of a PDB with Recovery Catalog Connection
On the destination CDB, roll forward the restored data files by applying incremental level 1 backups periodically.
While the source PDB remains open, you can create incremental level 1 backups of the source PDB and then perform a restore operation on the destination CDB. This method minimizes the application downtime and helps to reduce the amount of changed data that needs to be applied to the destination database when you perform the final transport of the PDB.
There is no restriction on the number of times you can repeat this procedure. When you are ready to perform the final transport of the PDB, proceed to step 4.
On the source CDB, create an incremental level 1 backup of the PDB
On the destination CDB, restore data files from the PDB backup
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.2.4.4 Source CDB: Create a Final Incremental Backup of a PDB with Recovery Catalog Connection
Prepare a PDB for the final transport to the destination CDB when RMAN is connected to a recovery catalog.
28.2.4.5 Destination CDB: Perform the Final Transport of a PDB with Recovery Catalog Connection
As a final step, restore data files from the PDB backup and plug in the PDB to the destination CDB when RMAN is connected to a recovery catalog.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.3 Transporting PDBs Across Platforms in NOCATALOG Mode
In the NOCATALOG
mode, you must create a transport file to store information about the source PDB backups. Learn the different ways to transport a PDB by using PDB backups and a transport file.
28.3.1 About Transporting PDBs in NOCATALOG MODE
To transport a PDB using PDB backups, RMAN needs to identify the exact backups from the source PDB and then perform a restore operation on the destination CDB.
In the NOCATALOG
mode, you must create a transport file on the source CDB. The transport file is an XML
format file to store the backup metadata of the PDB you want to transport to a destination CDB. RMAN requires the transport file to restore the data files from backups and plug in a PDB on the destination CDB.
These are the essential steps required to transport a PDB in NOCATALOG
mode:
- Use a preexisting level 0 backup or create a new backup using the
BACKUP PLUGGABLE DATABASE
command. - Create a final incremental level 1 backup of the source PDB when the PDB is set to read-only.
- Use the
BACKUP PLUGGABLE DATABASE
command to create a final incremental level 1 backup. - Use the
DATAPUMP
clause to create an export dump file along with the incremental backup.
- Use the
- On the source CDB, use the
RESTORE PREVIEW
command along with theTO TRANSPORT FILE
clause to create a transportXML
file. - Use operating system specific utilities to manually copy the transport
XML
file from the source host to the destination host. Alternatively, store theXML
file in a network file system (NFS) path or any shared location accessible to the destination host.
On the destination CDB, perform a single restore operation.
Use the RESTORE
command with the FROM TRANSPORT FILE
clause and the PLUGGABLE DATABASE
clause. RMAN uses the specified transport file to restore the data files from backups, and plug in the PDB on the destination CDB.
Note:
If the Oracle Active Data Guard logical database rolling upgrade process is running on a destination database, then RMAN cannot successfully complete the final step involved in transporting data using backups. This is because the rolling upgrade process restricts RMAN from importing the backup metadata required to restore a final backup and plug in a PDB on to a destination CDB.28.3.2 Quickly Transport a PDB in NOCATALOG MODE
Oracle recommends this method for transporting small-sized PDBs that take less time to backup.
In this quick transport method, you must create an incremental level 0 backup of the source PDB and an export dump file along with the backup. On the destination platform, perform a single restore operation to restore the data files from the level 0 backup, and plug in the PDB on the destination CDB to complete the PDB transport.
In the NOCATALOG
mode, you must generate a transport file to store information about the PDB backups in XML
format.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.3.3 Transport a PDB Using a Preexisting PDB Backup and NOCATALOG Mode
Use this procedure to transport a PDB by using a preexisting PDB backup (level 0) and a transport file.
When the source PDB is in read-only mode, you can use RMAN to restore the data files from the most recent preexisting level 0 backup of a PDB, and then plug in the PDB on a destination CDB.
In the NOCATALOG
mode, you must perform an additional step to generate a transport file to store information about the source PDB backups in XML
format.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.3.4 Transport a PDB Using Multiple Incremental Backups In NOCATALOG Mode
Oracle recommends this method for transporting large size PDBs across platforms with minimum application downtime on the source PDB.
On the destination CDB, you must first restore the data files from a preexisting backup or new backup of the PDB. You can then roll forward the restored data files by applying multiple incremental level 1 backups periodically. While the source PDB remains open and operational, you can continue to apply any number of incremental level 1 backups on the destination CDB until you want to perform the final transport of the PDB.
In the NOCATALOG
mode, you must create a transport file to store the information about the source PDB backups in XML
format.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.3.4.1 Source CDB: Creating a Base Incremental Backup of a PDB
Use a preexisting level 0 backup or create a new backup of the source PDB.
28.3.4.2 Step 2: (Destination CDB) Restore Data Files From a Base Incremental Backup of a PDB in NOCATALOG Mode
On the destination CDB, the level 0 backup serves as a basis for RMAN to restore the data files from subsequent increment level 1 backups of the PDB.
28.3.4.3 Step 3: Restore Data Files Using Incremental Backups of a PDB in NOCATALOG Mode
On the destination CDB, you can periodically apply incremental level 1 backups to roll forward the base backup until you want to perform the final transport of the PDB.
While the source PDB remains open, you can create incremental level 1 backups of the source PDB and then perform a restore operation on the destination CDB. This method minimizes the application downtime and helps to reduce the amount of changed data that needs to be applied to the destination database when you perform the final transport of the PDB.
There is no restriction on the number of times you can repeat this procedure. When you are ready to perform the final transport of the PDB, proceed to Step 4: (Source CDB) Create a Final Incremental Backup of a PDB in NOCATALOG Mode.
In the NOCATALOG
mode, you must create a transport file on the source host, and then use the transport file to perform a restore operation on the destination host.
On the source CDB, create an incremental level 1 backup of the PDB
On the destination CDB, restore the data files from the PDB backup
28.3.4.4 Step 4: (Source CDB) Create a Final Incremental Backup of a PDB in NOCATALOG Mode
Use this procedure to create a final incremental level 1 backup and an export dump file along with the backup to prepare a source PDB for the final transport.
28.3.4.5 Step 5: (Destination CDB) Perform the Final Transport of a PDB in NOCATALOG Mode
As a final step, use the transport file to restore the data files from PDB backups, and plug in the PDB to the destination CDB.
XML
file to a network file system (NFS), or shared location that is accessible to the destination CDB.
28.4 Transporting Pluggable Databases Over the Network
RMAN enables you to transport pluggable databases from one platform to another platform using the network.
28.4.1 About Transporting PDBs Over the Network
RMAN can use the network to connect to a source PDB, create a backup of a PDB, transfer the source data files optimally over the network, and then restore the data files from backups on the destination CDB. RMAN also plugs in the a PDB on the destination CDB.
To transport a PDB through the network, RMAN uses the RESTORE
command along with the FROM SERVICE
clause, the FOREIGN PLUGGABLE DATABASE
clause, and the PLUGIN DBLINK
clause.
You use the RECOVER
command to periodically roll forward the incremental backups of the PDB on the destination CDB. The source PDB can remain open and operational until you want to perform a final step to roll forward the final incremental backup and plug in the PDB on the destination CDB.
These are the essential steps required to transport a PDB from a source platform to a destination platform over the network:
- Run the
RESTORE
command along with theFOREIGN PLUGGABLE DATABASE
clause and theFROM SERVICE
clause. RMAN transfers an incremental level 0 backup of the source PDB and restores the data files on the destination CDB. - You can optionally run the
RECOVER
command along with theFOREIGN PLUGGABLE DATABASE
clause and theFROM SERVICE
clause. RMAN applies incremental level 1 backups of the source PDB and rolls forward the PDB backup on the destination CDB. - Before you perform a final restore of the PDB on a destination CDB, you must use
SQL*PLUS
to create a database link ordblink
on the destination CDB. Thedblink
is required for RMAN to transport the export dump file or the PDB unplug file from the source host to the destination host. - When the source PDB is in read-only mode, use the
RECOVER
command with theFOREIGN PLUGGABLE DATABASE
clause, theFROM SERVICE
clause, and thePLUGIN DBLINK
clause to recover the data files using the final incremental backup of the PDB, and then plug in the PDB on the destination CDB.
Note:
If the Oracle Active Data Guard logical database rolling upgrade process is running on a destination database, then RMAN cannot successfully complete the final step involved in transporting data using backups. This is because the rolling upgrade process restricts RMAN from importing the backup metadata required to restore a final backup and plug in a PDB on to a destination CDB.28.4.2 Quickly Transport a Pluggable Database Over the Network
Transport a PDB by restoring the data files from a level 0 backup of a PDB over the network. Oracle recommends this method for transporting small-sized PDBs that take less time to backup.
- Perform these steps on a source CDB:
- Perform these steps on the destination database.
28.4.3 Transport a Pluggable Database by Restoring Backups Incrementally Over the Network
Use the network to restore data files from a level 0 backup of a PDB, and then recover the restored data files on the destination CDB.
While the source PDB remains open, you can periodically perform recover operations on the destination CDB. The RECOVER
command enables RMAN to roll forward the previously restored data files by applying incremental level 1 backups of the source PDB. There is no restriction on the number of times you can perform the recover operation until you want to perform the final transport of the PDB.
28.5 Transporting Tablespaces with Recovery Catalog Connection
Learn the different ways in which you can transport a tablespace by using a backup of the tablespace when RMAN is connected to a recovery catalog.
28.5.1 About Transporting Tablespaces with a Recovery Catalog
RMAN can transport a tablespace by restoring the data files from a tablespace backup when RMAN is connected to a recovery catalog.
RMAN queries the metadata stored in the recovery catalog to determine the exact backups required for the restore operation on a destination database.
These are the essential steps you need to perform to transport a tablespace when RMAN is connected to the recovery catalog:
- Connect RMAN to a recovery catalog
- Use a preexisting backup of the tablespace or create a new backup using the
BACKUP TABLESPACE
command - Create a final incremental level 1 backup of the tablespace when the tablespace is in read-only mode.
- Use the
BACKUP TABLESPACE
command to create a final incremental level 1 backup - Use the
DATAPUMP
clause to create an export dump file along with the incremental backup
- Use the
On the destination database:
- Connect RMAN to the same recovery catalog as the source database
- Use the
SET
command along with theFOREIGN DBID
clause to set theDBID
of the source PDB - Use the
RESTORE
command along with thePREVIEW
clause and theTO TRANSPORT LIST
clause to generate a transport list. The transport list remains in-memory and indicates the tablespace backups required by RMAN to perform the restore operation on the destination database - Use the
RESTORE
command with theFROM TRANSPORT LIST
clause to perform a restore operation using the transport list. RMAN restores the data files from the tablespace backups, and plugs in the tablespace on the destination database.
Note:
If the Oracle Active Data Guard logical database rolling upgrade process is running on a destination database, then RMAN cannot successfully complete the final step involved in transporting data using backups. This is because the rolling upgrade process restricts RMAN from importing the backup metadata required to restore a final backup and plug in a tablespace or a PDB on to a destination database.28.5.2 Quickly Transport a Tablespace with Recovery Catalog Connection
Oracle recommends this method for transporting small sized tablespaces that take less time to backup.
In this quick transport method, you create an incremental level 0 backup of the source tablespace and an export dump file along with the backup. You must then restore the data files from the tablespace backup, and plug in the tablespace on the destination database.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.5.2.1 Source Database: Preparing to Quickly Transport a Tablespace with Recovery Catalog Connection
When the source tablespace is in read-only mode, create an incremental level 0 backup and an export dump file along with the backup.
28.5.2.2 Destination Database: Restore and Plug In a Tablespace with Recovery Catalog Connection
Perform the final steps required to quickly transport a tablespace to a destination database when RMAN is connected to a recovery catalog.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.5.3 Transport a Tablespace Using a Preexisting Tablespace Backup and Recovery Catalog
RMAN enables you to easily transport a tablespace by leveraging a preexisting tablespace backup that is available as part of your regular backup schedule.
When a source tablespace is in read-only mode, you can create a final incremental level 1 backup of the tablespace and an export dump file along with the incremental backup.
On the destination database, you can perform a single restore operation to transport the tablespace. RMAN first restores the data files from a preexisting level 0 backup of the tablespace. During the same restore operation, RMAN rolls forward the restored data files by applying the final incremental level 1 backup, and then plugs in the tablespace on the destination database.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.5.3.1 Source Database: Preparing to Transport a Tablespace by Using a Preexisting Backup and Recovery Catalog
Use a most recent backup of a tablespace to transport the tablespace to a destination database.
28.5.3.2 Destination Database: Restore Backup and Plug In a Tablespace Using Recovery Catalog
Perform a single restore operation to restore the data files from a preexisting backup and to plug in the tablespace to the destination database.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.5.4 Transport a Tablespace Using Multiple Incremental Backups and Recovery Catalog
Oracle recommends this method for transporting large tablespaces across platforms.
On the destination database, you must first restore the data files from a preexisting backup or a new backup of the tablespace. You can then roll forward the restored data files by applying multiple incremental level 1 backups periodically. The source tablespace can remain open for writes while you apply any number of incremental level 1 backups on the destination database. The application downtime begins only when you create the final incremental backup.
This method helps to improve database availability while transporting large tablespaces.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.5.4.1 Source Database: Preparing to Transport a Tablespace by Creating a Base Incremental Backup
RMAN needs to first restore a level 0 backup of the tablespace on the destination database. The level 0 backup serves as a basis for subsequent incremental level 1 backups.
28.5.4.2 Destination Database: Restore Data Files From a Base Incremental Level 0 Backup of a Tablespace with Recovery Catalog
On the destination database, restore data files from the level 0 incremental backup of the tablespace created on the source database. The level 0 backup serves as a basis for RMAN to roll forward the data files with subsequent increment level 1 backups of the tablespace.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.5.4.3 Create and Restore Incremental Backups of a Tablespace with Recovery Catalog
On the destination database, you can periodically roll-forward the previously restored data files to keep the data in-sync with the source tablespace.
Performing frequent incremental backups when the tablespaces are in read/write mode is advantageous because this reduces the amount of changed data that needs to be applied to the destination database using the final incremental backup that is taken when the tablespace is read-only. There is no restriction on the number of incremental level 1 backups you can apply on the destination database.
On the source database, create an incremental level 1 backup of the tablespace
On the destination database, restore data files using the incremental level 1 backup of the tablespace
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.5.4.4 Source Database: Create a Final Incremental Backup of a Tablespace with Recovery Catalog
Prepare a tablespace for the final transport to the destination database when RMAN is connected to a recovery catalog.
28.5.4.5 Destination Database: Perform the Final Transport of a Tablespace with Recovery Catalog
Restore the data files from the final incremental backup of the tablespace and then plug in the restored tablespace to the destination database when RMAN is connected to a recovery catalog.
Perform these steps in a single RMAN session to ensure that the in-memory transport list is available for RMAN during the restore operation.
28.6 Transporting Tablespaces in NOCATALOG Mode
In the NOCATALOG
mode, you must create a transport file to store information about the source tablespace backups. Learn the different ways to transport a tablespace by using a backup of the tablespace backup and a transport file.
28.6.1 About Transporting Tablespaces Across Platforms in NOCATALOG Mode
To transport a tablespace using tablespace backups, RMAN needs to identify the exact backups from the source database and then perform a restore operation on the destination database. In the NOCATALOG
mode, you must create a transport file on the source database. The transport file is an XML
format file to store the backup metadata. RMAN requires the transport file to restore the data files from backups and plug in a tablespace on the destination database.
These are the essential steps required to transport a tablespace in NOCATALOG
mode:
- Use a preexisting level 0 backup of the tablespace or create a new backup using the
BACKUP TABLESPACE
command. - Create a final incremental level 1 backup of the tablespace when the tablespace is in read-only mode:
- Use the
BACKUP TABLESPACE
command to create the final incremental level 1 backup. - Use the
DATAPUMP
clause to create an export dump file along with the incremental backup.
- Use the
- Use the
RESTORE PREVIEW
command along with theTO TRANSPORT FILE
clause to create a transportXML
file. - Use operating system utilities to manually copy the transport
XML
file from the source host to the destination host. Alternatively, store theXML
file in a network file system (NFS) path or any shared location accessible to the destination host.
On the destination database, perform a single restore operation using the transport file created on the source database.
Use the RESTORE
command with the FROM TRANSPORT FILE
clause and the FOREIGN TABLESPACE
clause. RMAN restores the data files from the level 0 backup, rolls forward the data files by applying the incremental level 1 backup, and then plugs in the tablespace on the destination database.
Note:
If the Oracle Active Data Guard logical database rolling upgrade process is running on a destination database, then RMAN cannot successfully complete the final step involved in transporting data using backups. This is because the rolling upgrade process restricts RMAN from importing the backup metadata required to restore a final incremental backup and plug in a tablespace on the destination database.28.6.2 Quickly Transport a Tablespace in NOCATALOG Mode
You can quickly transport a tablespace by restoring the data files from a level 0 backup of the tablespace on the destination database.
Oracle recommends this method for transporting small sized tablespaces that take less time to backup.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.6.3 Transport a Tablespace Using a Preexisting Tablespace Backup and without Recovery Catalog
RMAN enables you to transport a tablespace by leveraging a preexisting tablespace backup (level 0) that is available as part of your regular backup schedule.
In the NOCATALOG
mode, you must generate a transport file on the source database. The transport file stores tablespace backup information in XML
format. On the destination database, RMAN uses the transport file to restore the data files from tablespace backups created on the source database.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.6.4 Transport a Tablespace Using Multiple Incremental Backups in NOCATALOG Mode
Use this method for transporting large tablespaces in NOCATALOG
mode.
On the destination database, you must first restore the data files from a preexisting backup or a new backup of the tablespace. You can then roll forward the restored data files by applying multiple incremental level 1 backups periodically. The source tablespace can remain open for writes while you apply any number of incremental level 1 backups on the destination database. The application downtime begins only when you create the final incremental backup.
This method helps to improve database availability while transporting large tablespaces.
Ensure that you meet the prerequisites described in Prerequisites for Transporting Data Using RMAN Backups.
28.6.4.1 Source Database: Creating a Base Incremental Backup of a Tablespace
Use a preexisting tablespace backup or create a level 0 backup of the tablespace on the source database.
28.6.4.2 Destination Database: Restore the Base Incremental Backup of a Tablespace in NOCATALOG Mode
On the destination database, use a transport file to restore the base incremental level 0 backup of the tablespace being transported. The level 0 backup serves as a basis for RMAN to restore subsequent increment level 1 backups of the tablespace.
28.6.4.3 Restore Data Files Using Incremental Backups of a Tablespace in NOCATALOG Mode
On the destination database, you can periodically apply incremental level 1 backups to roll forward the previously restored data files. The source tablespace can remain open for writes during the backup and restore operation.
On the source database, create an incremental level 1 backup of the tablespace
On the destination database, roll-forward the previously restored data files by applying the incremental level 1 backups of the tablespace.
28.7 Transporting Tablespaces Over the Network
RMAN enables you to transport tablespaces over the network.
28.7.1 About Transporting Tablespaces Over the Network
Starting with Oracle Database 23ai, you can use RMAN to transport tablespaces over the network from a source database to a destination database.
RMAN can connect to a source database, create the required backups of a tablespace, transfer the data files optimally over the network, and then restore the data files on the destination database. RMAN also plugs in the tablespace on the destination database.
To transport a tablespace through the network, RMAN uses the RESTORE
command along with the FROM SERVICE
clause, the FOREIGN TABLESPACE
clause, and the PLUGIN DBLINK
clause.
Additionally, you can use the RECOVER
command to periodically roll forward the restored tablespace backup on the destination database.
These are the major steps required to transport a tablespace from a source database to a destination database over the network:
- Run the
RESTORE
command along with theFOREIGN TABLESPACE
clause and theFROM SERVICE
clause. RMAN restores the data files from a level 0 backup of the source tablespace. - You can optionally run the
RECOVER
command along with theFOREIGN TABLESPACE
clause and theFROM SERVICE
clause. RMAN rolls forward the previously restored data files using the incremental level 1 backups of the source tablespace. - When the source tablespace is in read-only mode, use the
RECOVER
command with theFOREIGN TABLESPACE
clause, theFROM SERVICE
clause, and thePLUGIN DBLINK
clause to recover the data files from a final incremental backup, and plug in the tablespace on the destination database.
Note:
If the Oracle Active Data Guard logical database rolling upgrade process is running on a destination database, then RMAN cannot successfully complete the final step involved in transporting data using backups. This is because the rolling upgrade process restricts RMAN from importing the backup metadata required to restore a final backup and plug in a tablespace on to a destination database.28.7.2 Quickly Transport a Tablespace Over the Network
Use RMAN to quickly transport a tablespace by restoring the data files from a tablespace backup over the network. Oracle recommends this method for transporting small-sized PDBs that take less time to backup.
28.7.3 Transport a Tablespace by Restoring Data Files Using Incremental Backups Over the Network
Use the network to restore data files from a level 0 backup of a tablespace, and then recover the restored data files until you want to perform the final transport of the tablespace over the network.
While the source tablespace remains open for writes, you can periodically perform recover operations on the destination database. The RECOVER
command enables RMAN to roll forward the data files by applying incremental level 1 backups of the source tablespace. There is no restriction on the number of times you can perform the recover operation until you want to transport the tablespace with a final incremental backup.
28.8 Transporting Data Using Backups from a Physical Standby Database
You can use the backups created on a source physical standby database to transport a pluggable database (PDB) or a tablespace to another primary or standby database on a destination host.
28.8.1 About Transporting Data Using Backups from a Physical Standby Database
In this method, you can use the source physical standby database to create the incremental backups and to extract the structural metadata of the PDB or tablespace that needs to be transported to another primary or standby database on a destination host.
- Enable block change tracking on the source physical standby database. Ensure that the managed recovery process is running.
- Connect RMAN to the source standby database to create an incremental level 0 backup of the database or tablespace that you want to transport to a destination primary database. You can also leverage a preexisting level 0 backup, if available.
- On the destination primary database, restore the data files from the level 0 backup created on the source standby database. You can also restore the data files on an existing physical standby database on the destination host.
Roll forward the restored data files by applying multiple incremental level 1 backups periodically. You can continue to apply any number of incremental level 1 backups on the destination primary database until you want to perform the final transport.
- Complete these prerequisite tasks on the source standby database before you perform the final transport:
- Create a guaranteed restore point. In case of any unexpected failures during the transport process, you can recover the source standby database to the guaranteed restore point.
- Stop the managed recovery process and then convert the physical standby database into a snapshot standby database. This ensures that the final incremental level 1 backup is in a consistent state for recoverablity on the destination database.
Note:
You can optionally connect RMAN to the source primary database to create the final incremental backup and the export dump file. In this case, you can skip the preparation tasks on the physical standby database and directly proceed to create the final incremental backup on the primary database. However, this may result in a minimal downtime on the primary database. To avoid downtime and ensure business continuity, Oracle recommends that you use the source standby database to perform the steps required for the final transport.
- On the source standby database, create a final incremental level 1 backup of the database or tablespace. If you are transporting a PDB, create an unplug XML file containing the structural metadata of the source PDB. For a tablespace, you must create the data pump export dump file containing the tablespace metadata.
- On the destination primary database, use the
RESTORE
command to create a transport list. Use the transport list to restore the data files on the destination primary database.
- Stop the managed recovery process.
- Set the
DB_CREATE_FILE_DEST
initialization parameter to specify the location of the data files for the standby database. - On the destination host, connect RMAN to the physical standby database as
TARGET
. Restore the data files from the incremental level 0 backup from the source standby database. Roll forward the restored data files by applying multiple incremental level 1 backups and the final incremental backup. - Set the
STANDBY_FILE_MANAGEMENT
database initialization parameter toMANUAL
so that the newly added data files can be renamed manually. - Start the managed recovery process.
When the standby database applies redo, the recovery process creates a control file entry with a name containing the phrase
UNNAMED
, and stops recovery. Use theALTER DATABASE RENAME FILE
statement to manually rename the individual data files until the media recovery on physical standby database is aware of all the plugged in files.
28.8.2 Performing Data Transport by Using Backups from Physical Standby Database
Use the source physical standby database to transport a PDB or a tablespace to another primary database or physical standby database on a destination host.
Next, transport the PDB or tablespace to an existing physical standby database on the destination host. You can use the same backups from the source standby database to create the data files required for the destination standby database.