Goal
To migrate an existing Oracle database (NOT BINARIES) from one Operating System platform to another (i.e. Windows to Solaris)
This can occur as part of an Oracle version upgrade (Oracle 8i .. Oracle 11G) or within the same Oracle version: (Oracle 10.2 to Oracle 10.2).
Changes within an Operating System (ie: Linux,Windows or Solaris from 32 bit to 64 bit) are not considered cross platform migrations and are performed as normal version upgrades/wordsize conversions.
For details please refer to the appropriate migration manual or
<NOTE:62290.1>Changing between 32-bit and 64-bit Word Sizes
Solution
There is no migration utility (Script or DBUA) to perform a cross platform migration of an Oracle Database.
Changing platforms requires the database be re-built and / or the data moved using one of the following methods:
- Export / Import to include the use of Datapump facilities. All versions support Export/Import but for Datapump 10.1.0.2 or higher is required
- Transportable Tablespaces 10G or Later
- RMAN Convert Database functions. 10G or Later
- RMAN Duplicate
- Streams Replication
- Create Table As Select (CTAS)
- Dataguard Heterogeneous Primary and Physical Standbys
- Oracle Golden Gate (For assistance with Oracle Golden Gate, an SR needs opened with the correct team)
Each available choice will have strengths and limitations to include data types, time required and potential costs.
The choices available will depend on BOTH the Operating System and Oracle versions on both the source and destination.
For example:
There are platform limitations when using Dataguard Heterogeneous Primary and Physical Standbys
For more information please refer to Note: 413484.1 Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration
RMAN Convert Database only works if both source and destination belong to the same ENDIAN format.
RMAN Duplicate Database only works if both source and destination belong to the same ENDIAN format.
For more infomaiton on RMAn Duplicate please refer to Note: 1079563.1 RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support 1079563.1
RMAN’s convert function for Transportable Tablespaces will convert from one ENDIAN format to another.
These two commands ARE NOT the same. Please refer to the notes at the end of the document for the correct note needed.
set linesize 500
set pages 50000
col PLATFORM_NAME for a45
select PLATFORM_ID, PLATFORM_NAME, ENDIAN_FORMAT from v$transportable_platform order by 1,2,3;
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
----------- -------------------------------------------------- --------------
1 Solaris[tm] OE (32-bit) Big
2 Solaris[tm] OE (64-bit) Big
3 HP-UX (64-bit) Big
4 HP-UX IA (64-bit) Big
5 HP Tru64 UNIX Little
6 AIX-Based Systems (64-bit) Big
7 Microsoft Windows IA (32-bit) Little
8 Microsoft Windows IA (64-bit) Little
9 IBM zSeries Based Linux Big
10 Linux IA (32-bit) Little
11 Linux IA (64-bit) Little
12 Microsoft Windows x86 64-bit Little
13 Linux x86 64-bit Little
15 HP Open VMS Little
16 Apple Mac OS Big
17 Solaris Operating System (x86) Little
18 IBM Power Based Linux Big
19 HP IA Open VMS Little
20 Solaris Operating System (x86-64) Little
21 Apple Mac OS (x86-64) Little
The following is the basic information for using Transportable Tablespaces:
1.Create an "empty" database in the new environment
2.Plug in all data tablespaces from source to target database
3.SYSTEM+SYSAUX tablespaces can't be transported
4.Additional steps necessary to move views, synonyms etc.
5.Possibly very fast upgrade
6.Complexity could be constraining
7.Works cross-platform and cross-Endianness since Oracle Database 10g
The following is the basic information for using Oracle Streams in an upgrade:
1.Build up a copy of your database and upgrade it
2.Synchronize it with the source database
3.Minimal downtime: Just reconnecting the clients
4.Works Across platforms
5.Cross version since Oracle 9iR2
6.Some effort necessary to set it up
7.Fallback possible since source untouched
8.Potential Issues include:
1.Datatype Restrictions
2.Performance
The following are a list of notes to assist users in deciding which process will work best for them.
Notes:
Note.553337.1 Export/Import DataPump Parameter VERSION - Compatibility of Data Pump Between Different Oracle Versions
Note.556636.1 Oracle Server - Export Data Pump and Import DataPump FAQ
Note.351598.1 Export/Import DataPump The Minimum Requirements to Use Export DataPump and Import DataPump (System Privileges)
Note.243304.1 10g : Transportable Tablespaces Across Different Platforms
Note:371556.1 How move tablespaces across platforms using Transportable Tablespaces with RMAN
Note: 413484.1 Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration
Oracle Streams Concepts and Administration: Appendix D
http://download.oracle.com/docs/cd/E11882_01/server.112/e17069/ap_strmnt.htm#CIHJBIAA
References
NOTE:556636.1 – Oracle Server – Export DataPump and Import DataPump FAQ
NOTE:1377213.1 – R11i / R12: Oracle E-Business Suite Upgrades and Platform Migration
NOTE:1389592.1 – 11G – Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
NOTE:351598.1 – Export/Import DataPump: The Minimum Requirements to Use Export DataPump and Import DataPump (System Privileges)
NOTE:371556.1 – How to Migrate to different Endian Platform Using Transportable Tablespaces With RMAN
NOTE:413484.1 – Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration
NOTE:553337.1 – Export/Import DataPump Parameter VERSION – Compatibility of Data Pump Between Different Oracle Versions
NOTE:243304.1 – 10g+: Transportable Tablespaces Across Different Platforms
NOTE:62290.1 – Changing between 32-bit and 64-bit Word Sizes
NOTE:1401921.1 – Cross-Platform Database Migration (across same endian) using RMAN Transportable Database
NOTE:1133355.1 – Migrating an Oracle E-Business Suite Database to Oracle Exadata Database Machine
NOTE:1079563.1 – RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support