How to Migrate to different Endian Platform Using Transportable Tablespaces With RMAN
Last updated on FEBRUARY 13, 2018
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 126.96.36.199 [Release 10.1 to 12.1]
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 12.1]
Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 9.2]
Information in this document applies to any platform.
******************* WARNING *************
Starting with Oracle Database 10g, you can transport tablespaces across platforms. In this note there is a step by step guide about how to do it with ASM datafiles and with OS filesystem datafiles.
If your goal is to migrate a database to different endian platform, the following high-level steps describe how to migrate a database to a new platform using transportable tablespace:
1.- Create a new, empty database on the destination platform.
2.- Import objects required for transport operations from the source database into the destination database.
3.- Export transportable metadata for all user tablespaces from the source database.
4.- Transfer data files for user tablespaces to the destination system.
5.- Use RMAN to convert the data files to the endian format of the destination system.
6.- Import transportable metadata for all user tablespaces into the destination database.
You could also convert the datafiles at source platform and once converted transfer them to destination platform.
The MAA white paper "Platform Migration Using Transportable Tablespace" is available at
From 22.214.171.124, 12C and further, if converting to Linux x86-64 consider to follow this doc:
Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup [1389592.1]
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms