Migrate Oracle databases across OS platforms
Port existing Oracle databases (non-binary executable program files/) from one operating system platform to another operating system platform (for example, from Windows to Solaris)
This requirement may occur during Oracle version upgrade (Oracle 8i till Oracle 11G), or in the same Oracle version (Oracle 10.2 to Oracle 10.2 ).
Changes within the operating system (such as Linux, Windows, or Solaris from 32-bit to 64-bit) are not considered during platform migration. These changes are processed as normal upgrade/wordsize conversion.
The following solutions
Solution
We do not have a migration utility (script or DBUA) to perform cross-platform migration of Oracle databases.
To change the platform, you need to rebuild the database and/or move data using one of the following methods:
- Execute the "export/import" operation, including Datapump. All versions support "export/import" operations, but for Datapump, 10.1.0.2 or a later version is required.
- You can use Transportable Tablespaces for version 10G or later.
- The RMAN Convert Database function can be used for version 10G or later.
- Streams stream replication.
- Create Table As Select (CTAS)
- Dataguard is a physical Master/Slave Database Based on heterogeneous platforms.
- Oracle Golden Gate.
Each available option has its advantages and limitations, including the data type, time required, and potential costs.
The advantages and disadvantages of available options depend on the source and target operating systems and the Oracle version.
For example:
Platform limitations exist when using physical Master/Slave databases based on Heterogeneous Platforms
RMAN Convert Database works only when both the source and target belong to the same ENDIAN format.
The RMAN's convert function for Transportable Tablespaces will convert from one ENDIAN format to another.
These two CommandsIs different.
PLATFORM_NAME |
ENDIAN_FORMAT |
Oracle Solaris on iSCSI (32-bit & 64-bit) |
Big |
AIX-Based Systems (64-bit) |
Big |
HP-UX (64-bits) |
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 basic steps for using Transportable Tablespaces are as follows:
- Create an empty database in the new environment
- Insert all data table spaces from the source database to the target database
- SYSTEM + SYSAUX tablespace cannot be transmitted
- Other steps required for moving views and synonyms
- The upgrade may be fast.
- Complexity may be a constraint
- Support for cross-platform and cross-Endian operations since Oracle Database 10 GB
The following is the basic information for using Oracle Streams during the upgrade:
- Build a copy of the database and upgrade the database
- Synchronize it with the source database
- Minimum downtime: Only reconnect to the client
- Cross-platform work
- Cross-version supported since Oracle 9iR2
- Some work required to set it
- Possible rollback since the source database has not been operated
- Possible problems include:
- Data Type restrictions
- Sex
Install Oracle 11gR2 (x64) in CentOS 6.4)
Steps for installing Oracle 11gR2 in vmwarevm
Install Oracle 11g XE R2 In Debian