Oracle cross-operating system migration

 

For cross-OS dB migration, MOS has related articles: [id733205.1].

 

To migrate anexisting Oracle Database (not binaries) from one operating systemplatform to another (I. e. windows to Solaris), this can occur as part ofan Oracle version upgrade (Oracle 8i .. oracle 11g) or within the sameoracle version: (Oracle 10.2 to Oracle 10.2 ).

-- Oracle db can be migrated from one operating system to another, for example, from windows to Solaris. Note that the migration only involves data migration and does not contain the installation media of the database. This migration can be performed in different dB versions, for example, from 8i to 11g, or in the same version, for example, from 10.2 to 10.2.

 

Changes withinan Operating System (ie: Linux, Windows or Solaris from 32 bit to 64 bit) arenot considered cross platform migrations and are running med as normal versionupgrades/wordsize conversions.

-- To change the operating system, you do not need to consider the system platform. You can change the operating system according to the normal DB version upgrades and wordsize.

 

I. Solution

There is no migrationutility (script or dbua) to perform a cross platform migration of an oracledatabase.

-- There are no migration tools such as scripts or dbua to perform cross-OS data migration.

 

Changingplatforms requires the database be re-built and/or the data moved using oneof the following methods:

-- For cross-platform migration, You need to recreate the database, and then use the following method to complete data migration.

(1) Export/Import to include theuse of DataPump facilities. All Versions support export/import but for datapump10.1.0.2 or higher is required

(2) Transportable tablespaces 10gor later

(3) RMAN convert databasefunctions. 10g or later

(4) streams Replication

(5) Create Table as select (CTAs)

(6) dataguard heterogeneous primaryand physical standbys

(7) Oracle Golden Gate

 

Each availablechoice will have strengths and limitations to include data types, time requiredand potential costs.

-- Each optional method has its advantages and limitations, such as the data type, time required, and some potential consumption.

 

The choicesavailable will depend on both the operating system and Oracle versions on boththe source and destination.

-- Whether the method is available depends on the operating system and Oracle version at both ends of source and destination.

 

 

Ii. Example

There areplatform limitations when using extends uard heterogeneous primary and physicalstandbys.

-- For example, when the heterogeneous platform of DG is used for migration, the operating system is limited. We have a detailed blog on this part:

Description of heterogeneous platforms supported by Oracle elastic uard

Http://blog.csdn.net/tianlesoftware/article/details/7241488

 

RMAN convertdatabase only works if both source and destination belong to the same endianformat.

-- RMAN convert dB can be used only when the Source and Destination endian formats are the same.

Rman's convertfunction for transportable tablespaces will convert from one endian format toanother.

In the case of different endian formats, you can use RMAN convert function to convert endian from one format to another. For example:

RMAN> convert tablespace tbs1 to platform = "Linux Ia (32-bit)" format '/tmp/% U ';

 

After the two ends are the same, you can perform the transportablespace operation.

 

You can view the system's endian format in the V $ transportable_platform View:

SQL> columnplatform_name format A35

SQL> select * from V $ transportable_platform order by 1;

 

Platform_idplatform_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

Apple Mac OS (x86-64) Little

 

20 rowsselected.

 

1.2.1 The following isthe basic information for using transportable tablespaces:

-- Procedure for using transport tablespace:

(1) create an "empty" database in the new environment

(2) Plug in all data tablespacesfrom source to target database

(3) system + sysaux tablespaces can't be transported

(4) Additional steps necessary tomove views, synonyms etc.

(5) possibly very fast upgrade

(6) Complexity cocould beconstraining

(7) works cross-platform andcross-endianness since Oracle Database 10g

 

1.2.2 The following isthe basic information for using Oracle streams in an upgrade:

-- Steps for using Oracle streams:

(1) Build up a copy of yourdatabase and upgrade it

(2) synchronize it with the sourcedatabase

(3) minimal downtime: justreconnecting the clients

(4) works platform SS platforms

(5) Cross version since Oracle 9ir2

(6) Some effort necessary to set itup

(7) fallback possible since sourceuntouched

(8) potential issues include:

1) datatyperestrictions

2) Performance

1.2.3 The following are a list of notes to assist users in deciding whichprocess will work best for them.

-- Related instructions:

Note.553337.1 export/importdatapump parameter version-compatibility of data pump between differentoracle versions
Note.556636.1 oracleserver-export data pump and import DataPump FAQs
Note.351598.1 export/importdatapump the minimum requirements to use export DataPump and import DataPump (SYSTEM privileges)

Note.243304.1 10g: transportable tablespaces into SS different platforms
Note: 371556.1 how to move tablespaces into SS platforms using transportable tablespaces with RMAN
Note.413586.1 how to use RMAN convert database for cross platform migration

Note: 413484.1 data guard support for heterogeneous primary and physicalstandbys 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

 

 

Summary:

For Oracle cross-OS migration, we don't need to worry too much about the operating system type. This Migration supports cross-DB version and cross-wordsize migration.

 

We can use the following method to achieve cross-OS migration:

(1) Export/Import to include theuse of DataPump facilities. All Versions support export/import but for datapump10.1.0.2 or higher is required

(2) Transportable tablespaces 10gor later

(3) RMAN convert databasefunctions. 10g or later

(4) streams Replication

(5) Create Table as select (CTAs)

(6) dataguard heterogeneous primaryand physical standbys

(7) Oracle Golden Gate

 

During the migration process, we need to pay attention to two types of information:

1. the endian format of the operating system is different from that of the operating system. If the endian format of the two OS to be migrated is different, we can use the rman's convert function for conversion, make them consistent.

2. If the wordsize of the database is inconsistent during the migration process, we also need to modify the wordsize to make the two ends consistent. For details, refer:

Oracleconvert a 32-bit database to 64-bit database (32-bit to 64-bit) Description

Http://blog.csdn.net/tianlesoftware/article/details/7252742

 

Next I will write several blogs about using transportable tablespaces.

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Email: tianlesoftware@gmail.com

Skype: tianlesoftware

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940