Oracle DBA-Apps DBA-Cloud Expert : Migrate oracle 11.2.0.1.0(Windows 32-bit) TO linux (64-bit);

Migrate oracle 11.2.0.1.0(Windows 32-bit) TO linux (64-bit);

Source: Windows 32-bit

Target Linux 64-bit

Small guide what I am going to do:

Steps:
1. Check platform compatibility between Source and target OS
2. Start the database in read only mode
3. Check database readiness for transport from Windows to Linux using DBMS_TDB.CHECK_DB
4. Check if there are any external objects
5. Execute the RMAN Convert database command
6. Copy Converted datafiles, Generated Script and Pfile to Linux
7. Edit the Pfile for the new database (Linux)
8. Edit the Transport Script and Pfile changing the windows paths to Linux Paths.
9. Execute the Transport Script on Linux
10. Change the DBID

11. Run utlirp.sql and utlrp.sql for recompile all Pl/SQL modules.
12. Verify & Compare the database on Linux

Source:

Step 1:

====

SQL> Select * from v$transportable_platform order by platform_id;

Here both will (Windows and Linux endian format is little only)
Check the Version of database:
SQL> select * from v$version;
SQL> Select * from v$transportable_platform order by platform_id;
Check the Version of database:
SQL> Select * from v$transportable_platform order by platform_id;
Check the Version of database:
SQL> select * from v$version;

BANNER

--------------------------------------------------------------------------------

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

PL/SQL Release 11.2.0.1.0 - Production

CORE 11.2.0.1.0 Production

TNS for 32-bit Windows: Version 11.2.0.1.0 - Production

NLSRTL Version 11.2.0.1.0 – Production

Note: Kindly check it Target server pre-requesite install software only

Step 2:

2. Start the database in read only mode

> shut immediate;

>startup mount;

> alter database open read only;

Step 3:

3. Check database readiness for transport from Windows to Linux using DBMS_TDB.CHECK_DB

Note:

Before converting the database, we have to be make sure that whether a database can be transported to a desired destination platform, and whether the current state of the database permits transport. We check this using "DBMS_TDB.CHECK_DB" procedure.
If this procedure returns "FALSE" then the output includes the reason why the database cannot be transported like target platform has a different endian format, database is not open read-only, there are active transactions in the database, database compatibility version is below 10 etc.

set serveroutput on

declare

db_ready boolean;

begin

db_ready := dbms_tdb.check_db('Linux x86 64-bit');

end;

PL/SQL procedure successfully completed.

Note: If database is not open in read-only mode, then the above procedure may return error like Database is not open READ ONLY. Please open database READ ONLY and retry.

Step 4:

Check if there are any external objects:

Note:

If there is any external objects take note of them, they will need to be taken care manually because RMAN cannot automate the transport of such objects. "DBMS_TDB.CHECK_EXTERNAL" must be used to identify any external tables, directories or BFILEs.

set serveroutput on

declare

external boolean;

begin

external := dbms_tdb.check_external;

end;

The following directories exist in the database:

SYS.ORACLE_OCM_CONFIG_DIR, SYS.DATA_PUMP_DIR, SYS.XMLDIR

Note:

No need to worry its automatically taking when we start using pfile in Target

Step 5

5. Using the RMAN CONVERT DATABASE:
After all the pre-requisites have been performed successfully, we can use the RMAN CONVERT DATABASE command to generate the output files for the target database. While executing the CONVERT DATABASE command, we need to specify the new database name, the destination platform, path to save the transport script and optionally a path, where to save the output files.

Note: If you omit the "DB_FILE_NAME_CONVERT" clause, the output files are created in

"C:\ORACLE_HOME\database" folder.

C:\>rman target /

CONVERT DATABASE NEW DATABASE 'migra'

transport script 'd:\app\mig\script.sql'

to platform 'Linux x86 64-bit'

db_file_name_convert 'D:\app\kumar\oradata\prod500\' 'D:\app\mig\';

output:

Starting conversion at source at 23-JUL-14

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=135 device type=DISK

Directory SYS.ORACLE_OCM_CONFIG_DIR found in the database

Directory SYS.DATA_PUMP_DIR found in the database

Directory SYS.XMLDIR found in the database

User SYS with SYSDBA and SYSOPER privilege found in password file