Transportable Database

This method works in conjunction with RMAN to migrate whole databases between platforms that share the same endian format. The result is a block-for-block replica of the source database. Consequently, the transportable database method is useful in cases where it is not necessary to physically re-organize the source database.

Though conceptually similar, the transportable database method is substantially different from transportable tablespaces. The transportable database method involves copying an entire database, including the SYSTEM tablespace, from one platform to another. Because the whole database is copied, containment checks are unnecessary and no Data Pump export and import are required. RMAN is used to perform the required backup, conversion and restoration operations, and you can also use backups stored in Oracle Database Backup Cloud Service.

The transportable database method only works across platforms that share the same endian format. Therefore, your source database must reside on a little-endian platform in order to facilitate transport to Exadata Cloud at Customer.

When you use the transportable database method, the result is a block-for-block copy of the source database, and the target database automatically uses the database character set of the source database. You should carefully consider whether the physical organization and character set of your source database are suitable for use in conjunction with Exadata Cloud at Customer before selecting this approach.

To perform a migration using the transportable database method, you perform a different set of tasks depending on:

  • The type of backup used. You can choose between:

    • Image copies, which are file copies generated with the RMAN BACKUP AS COPY command, an operating system command such as the UNIX cp command, or by the Oracle archiver process.

    • An RMAN backup set, which is one or more binary files that contain backup data in a format that can only be created or restored by RMAN. In general, Oracle recommends using backup sets because they are optimized for use with RMAN.

  • The system where conversion is performed. You can choose between:

    • The source system. You might select this option in order to prepare the database as much as possible before using Exadata Cloud at Customer.

    • The target system. You might select this option to minimize any migration impact on the source system.

See Transporting Data Across Platforms in Oracle Database Backup and Recovery User's Guide for Release 18, 12.2, 12.1, or 11.2.