Oracle 12cR2: Cross-Platform PDB Transport Using XTTS

Transportable Tablespace method can be used for Oracle database Migration and Upgrade when the operating systems of the source database and the target database are different and conversion between 32 bits and 64 bits.

When using Cross Platform Transportable Tablespaces (XTTS) to migrate database between systems that have different endian formats, the amount of downtime required is related directly proportional to the size of the data set being moved. To reduce amount of downtime, Oracle recommend  Cross Platform Incremental Backup with Oracle 12c.

 will explain New Oracle XTTS , Cross Platform Oracle Database Migration Using Transportable Tablespace ( XTTS ) With Zero Downtime in this article.

Let’s see how we can perform this process:

1. Verify the prerequisites: The source PDB must be closed in MOUNTED mode and the COMPATIBLE parameter must be set to 12.2 or higher.

2. Start an RMAN session and connect to the CDB instance of the PDB to be transported.

3. For performing cross-platform PDB transport, you may need the exact name of the destination platform to which you are transporting data and may need to verify that the destination platform is of the same endian format.

   SQL> SELECT PLATFORM_ID, PLATFORM_NAME, ENDIAN_FORMAT FROM V$TRANSPORTABLE_PLATFORM WHERE UPPER(PLATFORM_NAME) LIKE ‘%LINUX%’;

   
   

4. Back up the source PDB by using the BACKUP command with TO PLATFORM or FOR TRANSPORT. The new UNPLUG INTO clause creates the XML file containing the metadata of the PDB—tablespaces list, datafiles list, options, and parameters values. The FORMAT clause indicates the directory where the backup sets containing the data required for cross-platform database transportation are stored on the source host.

5. In the first example in the slide, the conversion will take place on the source host and the files stored in the /bkp_dir directory are converted for the Linux x86 64-bit platform. In the second example, the conversion will take place on the destination host during the restore command and the files stored in /bkp_dir directory on the source host are not converted yet.

   

5. Disconnect from the source CDB.

6. Move the backup sets and the XML file created by the BACKUP command to the

   destination host. You can use operating system utilities to move the backup sets and the XML file from the source host to the destination host.

7. Connect to the destination CDB, to which the PDB must be transported. Ensure that the destination CDB is opened.

8. Use the RESTORE command to restore the files for the newly created PDB to the target location, and plug the files into the new PDB by using the new USING clause.

Oracle 12cR2: Cross-Platform PDB Transport Using XTTS..!! Let's see how we can perform this process: Verify the prerequisites: The source PDB must be closed in MOUNTED mode and the COMPATIBLE parameter must be set to 12.2 or higher. Start an RMAN session and connect to the CDB instance of the PDB to be transported

Oracle 12cR2: Cross-Platform Transportable PDB

Oracle Database 12.1 allows you to transport database or tablespace backup sets with conversion at source or destination for same endian platforms.

Oracle Database 12.2 includes cross-platform PDB backup and restore into a CDB by unplugging at backup step and plugging at restore step as long as the source platform and destination platform have the same endian format. For a cross-endian migration, the tablespaces have to be exported and imported with Data Pump, either using the conventional expdp/impdp or the Full Transportable expdp/impdp.

1. Before backing the PDB, ensure that the prerequisites are satisfied.

2. Determine the location of the endian conversion.

   • –  The FOR TRANSPORT clause creates a cross-platform backup indicating that the backup set can be transported to any destination database.

   • –  The TO PLATFORM clause indicates that the conversion performs on the source database for a specific platform and can be restored on that specific platform.

3. Use the BACKUP FOR TRANSPORT or TO PLATFORM command to create a cross- platform PDB backup set on the source host. The new UNPLUG INTO clause creates the XML file containing the metadata for the PDB.

4. 4. Use any operating system utilities to transfer the created backup set and XML file.

   5. Use the RESTORE FOREIGN command to restore the cross-platform PDB backup set on the destination host. The new USING clause uses the XML file to plug the appropriate files for the new PDB.

   6. Open the PDB.