Migration Of An Oracle Database Across OS Platforms (Generic Platform)

Migration Of An Oracle Database Across OS Platforms (Generic Platform) (Doc ID 733205.1)

To Bottom

---

In this Document Goal Solution References APPLIES TO: Oracle Database - Enterprise Edition - Version 8.1.7.4 and later Information in this document applies to any platform. 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 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'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. PLATFORM_NAME ENDIAN_FORMAT Oracle Solaris on SPARC (32-bit & 64-bit) Big AIX-Based Systems (64-bit) Big HP-UX (64-bit) Big HP-UX IA (64-bit) Big IBM zSeries Based Linux Big Apple Mac OS Big IBM Power Based Linux Big HP Tru64 UNIX Little Linux IA (32-bit & 64-bit) Little HP Open VMS Little Microsoft Windows IA (32-bit & 64-bit) Little Oracle Solaris on x86 & x86-64 Little Linux 64-bit for AMD Little Microsoft Windows 64-bit for AMD Little The following is the basic information for using Transportable Tablespaces: Create an "empty" database in the new environment Plug in all data tablespaces from source to target database SYSTEM+SYSAUX tablespaces can't be transported Additional steps necessary to move views, synonyms etc. Possibly very fast upgrade Complexity could be constraining Works cross-platform and cross-Endianness since Oracle Database 10g The following is the basic information for using Oracle Streams in an upgrade: Build up a copy of your database and upgrade it Synchronize it with the source database Minimal downtime:  Just reconnecting the clients Works Across platforms Cross version since Oracle 9iR2 Some effort necessary to set it up Fallback possible since source untouched Potential Issues include: Datatype Restrictions Performance