Migrate databases across platforms using RMAN

1. Data File byte sorting
The Oracle platform generally uses two different byte sorting schemes (the ending number format ).
If multiple platforms use different byte sorting schemes, you need to use the convert command in RMAN to convert the tablespace to the format required on the target platform. You can use the following query to determine the ending number format:
Select endian_format
From v $ transportable_platform tp, v $ database d
Where tp. platform_name = d. platform_name;
2. Use RMAN to convert the tablespace ending number format
First, create a directory for saving the copy of the conversion file, set the tablespace to read-only mode, Start RMAN, and use the new convert tablespace command.
Rman target/
Convert tablespace users to platform = 'Aix-Based Systems (64-bit) 'db_file_name_convert = 'C: \ oracle \ oradata \ betatwo', 'c: \ oracle \ admin \ transport_aix ';
You can also convert the data files on the target site.
Rman target/
Convert datafile = 'C: \ oracle \ oradata \ betatwo \ * 'from platform = 'Aix-Based Systems (64-bit)' db_file_name_convert = 'C: \ oracle \ oradata \ betatwo ', 'c: \ oracle \ admin \ transport_aix ';
The Platform name used is from the platform_name column in the v $ transportable_platform view.
3. cross-platform Mobile Database
RMAN in Oracle Database 10 Gb provides new functions to help move databases between platforms with the same ending number bytes format. The convert database Command combined with the DBMS_TDP package can reduce the overall workload of moving databases between platforms. The procedure is as follows:
(1) Open the database in read-only mode
Startup mount;
Alter database open read only;
(2) Use the dbms_tdb.check_db process to check the database status. This program should run when the serveroutput command is opened:
Set serveroutput on;
Declare
Db_ready boolean;
Begin
Db_ready: = dbms_tdb.check_db ('Microsoft Windows IA (32-bit) ', dbms_tdb.skip_readonly );
End;
/
(3) Use the dbms_tdb.check_external process to identify external objects:
Set serveroutput on;
Declare
External boolean;
Begin
External: = dbms_tdb.check_external;
End;
/
(4) When the database can be transferred, the RMAN convert database command can be used. RMAN creates scripts required for database movement, but does not actually perform the movement operation. Instead, it creates the files required for database movement:
Convert database new database 'copydb' transport script 'C: \ oracle \ copydb \ copyscripts 'to platform 'Microsoft Windows IA (32-bit )';
The optional parameter db_file_name_convert allows you to define a directory for the data file to be converted:
Convert database new database 'copydb' transport script 'C: \ oracle \ copydb \ copyscripts 'to platform 'Microsoft Windows IA (32-bit) 'db_file_name_convert 'C: \ oracle \ product \ 10.2.0 \ oradata \ rob10r2 ', 'c: \ oracle \ newdbdest ';

Recommended reading:

RMAN: Configure an archive log deletion policy

Basic Oracle tutorial-copying a database through RMAN

Reference for RMAN backup policy formulation

RMAN backup learning notes

Oracle Database Backup encryption RMAN Encryption