Oracle O & M-RMAN heterogeneous platform migration (modifying)

Example:
Recently, the company has a project that involves data migration:
The source database environment is: RedHat as 4 Oracle 10.2.0.1 (64-bit) Single Instance (bare device), hardware platform (IBM x3650)
Target Database: AIX 5.3. Oracle 10.2.0.4 (64-bit) RAC (bare device), hardware platform (IBM p595)
The data volume is about 700 GB.

We want to migrate data from the source database to the target database using RMAN.
Do you have any good tips:

| | |

You cannot use cross-platform RMAN for migration in your environment. Because the source and target endian formats are different, you can only use the tablespace transfer method.

SQL> select platform_name, endian_format from V $ transportable_platform;

Platform_name endian_format
------------------------------------------------------
Solaris [Tm] OE (32-bit) Big
Solaris [Tm] OE (64-bit) Big
Microsoft Windows Ia (32-bit) Little
Linux Ia (32-bit) Little
Aix-based systems (64-bit) Big
HP-UX (64-bit) Big
HP Tru64 UNIX little
HP-UX Ia (64-bits) Big
Linux Ia (64-bit) Little
HP Open VMS little
Microsoft Windows Ia (64-bit) Little
IBM zseries based Linux big
Linux 64-bit for AMD little
Apple Mac OS big
Microsoft Windows 64-bit for AMD little
Solaris operating system (x86) Little
IBM power based Linux big

As the database files are all on bare devices, you can first import the database file RMAN to the DBF file, and then use the DBF file by recreating the control file to migrate it to Aix, copy the DBF File RMAN to the AIX bare device, and re-create the control file to use the bare device.

|

Originally, exp/imp or DataPump was considered for data migration,
However, the data volume is large. The original application is not our own system, and the production database can be stopped for up to 10 hours.

I checked that the cross-version RMAN migration is supported after 10 Gb. You can use the tablespace transmission method.
However, cross-platform database RMAN migration has never been done, and the data files in the target database of the source database are stored on bare devices!

 

|

Metalink Doc 243304.1

10g: transportable tablespaces into SS different platforms

Refer

|

Paste it here. I will try again.
If the two platforms are not on the same endian format, you will need to use transportable tablespace instead of convert Database
See note 243304.1 10g: transportable tablespaces internal SS different platforms

Purpose
-------

This bulletin explains how tablespaces can now be transported from any platform
To any platform in 10g, provided the platforms belong to the list below:

SQL> select * from V $ transportable_platform;

Platform_id platform_name endian_format
-------------------------------------------------------
1 Solaris [Tm] OE (32-bit) Big
2 Solaris [Tm] OE (64-bit) Big
7 Microsoft Windows NT little
10 Linux Ia (32-bit) Little
6 Aix-based systems (64-bit) Big
3 HP-UX (64-bit) Big
5 HP Tru64 UNIX little
4 HP-UX Ia (64-bit) Big
11 Linux Ia (64-bit) Little
15 HP Open VMS little
8 Microsoft Windows Ia (64-bit) Little
9 IBM zseries based Linux big
13 Linux 64-bit for AMD little
16 Apple Mac OS big
12 Microsoft Windows 64-bit for AMD little

The output of the query can change. So please use the query above to find
Current support platforms.
In previous releases, the transportable tablespace feature allowed the transfer
Between platforms of the same architecture only.

Scope & Application
-------------------
-Publish structured data and distribute for integration on other platforms
-Distribute data from a DW environment to data marts (typically different platforms)
-Share read only tablespaces internal SS heterogeneous Clusters
-Migrate a database from one platform to another by only rebuilding the catalog
And transporting the datafiles

Steps
-----
1. Check for restrictions
----------------------
Review the "limitations on transportable tablespace use" section in note 371556.1.
Among other things, objects that reside in the system tablespace and objects owned
By sys will not be transported. This has des but is not limited to users, privileges,
PL/SQL stored procedures, and views.

If you use spatial indexes, apply the solution in note 579136.1 "impdp transportable
Tablespace fails for spatial index) "before continuing.

2. Prepare the database
--------------------
Check that the tablespace will be self-contained
------------------------------------------------
SQL> execute SYS. dbms_tts.transport_set_check ('tbs1, tbs2 ', true );
SQL> select * From SYS. transport_set_violations;
==> These violations must be resolved before the tablespaces
Can be transported

Set the tablespace to read only
-------------------------------
SQL> alter tablespace reposit read only;
Tablespace altered.

3. Export metadata
---------------
& Lt; HP-UX & gt; exp userid =/'/As sysdba/' transport_tablespace = y
Tablespaces = reposit
File = TTS. dmp log = exp_tts.log
Statistics = none

Export: Release 10.1.0.1.0-Beta on Mon Nov 24 11:49:49 2003
...

Note: Table data (rows) will not be exported
About to export transportable tablespace metadata...
For tablespace reposit...
. Exporting cluster Definitions
. Exporting table Definitions
.. Exporting table mtg_col_dep_chg
.. Exporting table mtg_databases
....
.. Exporting table sybase11_sysusers
. Exporting referential integrity constraints
. Exporting triggers
. End transportable tablespace metadata export
Export terminated successfully without warnings.

Review the export log for warnings and errors and resolve issues
Before continuing. Failure to do so can result in data loss.

4. Check the endianness of the target database and convert, if necessary
---------------------------------------------------------------------
Case 1
------
The source platform is Sun iSCSI Solaris: endianness big
The target platform is HP-UX (64-bit): endianness big

SQL> select platform_id, platform_name from V $ database;

Platform_id platform_name
-----------------------------------------
3 HP-UX (64-bit)

No conversion is needed for files that (1) do not contain Undo/rollback
Segments and (2) have a source and target OS with the same endianness.
Refer to Note 415884.1 "cross platform database Conversion
With same endian "to determine which files contain Undo/rollback segments.

Case 2
------
The source platform is Microsoft Windows NT: endianness little
The target platform is HP-UX (64-bit): endianness big

If we move the files and import the tablespace:

. Importing sys's objects into sys
Imp-00017: following statement failed with Oracle error 1565:
"Begin SYS. dbms_plugts.beginimptablespace ('tbs _ TTS ', 37, 'sys', 57"
"54175, 1, 2147483645,8, 462754339,1, null, 0, 0, null, null"
"); End ;"
Imp-00003: Oracle error 1565 encountered
ORA-01565: Error in identifying File '/database/db101b2/v101b2/datafile/reposit01.dbf'
ORA-27047: unable to read the header block of File
HP-UX error: 2: no such file or directory
Additional information: 2
ORA-06512: At "SYS. dbms_plugts", line 1540
ORA-06512: At line 1
Imp-00000: Import terminated unsuccessfully

You have to convert the files:
--> Locally before the import step so that the files are endian compatible:

<Solaris> RMAN target =/

Recovery MANAGER: Release 10.1.0.1.0-64bit Beta
Connected to target database: v101b2 (dbid = 3287908659)

RMAN> convert tablespace 'reposit'
2> to platform = "Linux Ia (32-bit )"
3> db_file_name_convert = '/database/db101b2/v101b2/datafile/reposit01.dbf ',
4> '/tmp/reposit01.dbf ';

Starting backup at 24-nov-03
Using target database controlfile instead of recovery catalog
Allocated channel: ora_disk_1
Channel ora_disk_1: SID = 8 devtype = Disk
Channel ora_disk_1: Starting datafile Conversion
Input datafile fno = 00006 name =/database/db101b2/v101b2/datafile/reposit01.dbf
Converted datafile =/tmp/reposit01.dbf
Channel ora_disk_1: datafile Conversion complete, elapsed time: 00:00:01
Finished backup at 24-nov-03

The converted datafile is staged in/tmp directory until it is copied to
Target server.

--> Remotely on the target server after having copied them on the server.

5. Move datafiles and export dump file
-----------------------------------
$ Ftp tts. dmp
+
/Database/db101b2/v101b2/datafile/reposit01.dbf (no conversion)
Or
/Tmp/reposit01.dbf (converted file if conversion had been required)

6. Import metadata
---------------
$ Imp userid =/'/As sysdba/' transport_tablespace = y
Datafiles =/database/db101b2/v101b2/datafile/reposit01.dbf
(Or/tmp/reposit01.dbf)
File = TTS. dmp log = imp_tts.log

Import: Release 10.1.0.1.0-Beta on Mon Nov 24 03:37:20 2003

Export File Created by export: v10.01.00 via conventional path
About to import transportable tablespace (s) Metadata...
...
. Importing sys's objects into sys
. Importing omwb's objects into omwb
... Importing table "mtg_col_dep_chg"
...
.. Importing table "sybase11_sysusers"
Import terminated successfully without warnings.

Review the import log for warnings and errors and resolve issues
Before continuing. Failure to do so can result in data loss.

7. Set the imported tablespace To Read Write
---------------------------------------
SQL> alter tablespace reposit read write;
Tablespace altered.