If the two platforms are not on the same endian format, you will need to use TRANSPORTABLE TABLESPACEinstead of CONVERT DATABASEsee Note 243304.110g : Transportable Tablespaces Across Different Platforms2) Use DBMS_TDB.CHECK_DB to check whether the database can be transported to a desired destination platform, and whether the current state of the database (such as incorrect compatibility settings, in-doubt or activetransactions) permits transport. Make sure your database is open in READ ONLY mode before you callDBMS_TDB.CHECK_DB. Since we need to transport to Linux we will call the procedure with followingarguments:
SQL> set serveroutput onSQL> declare2 db_ready boolean;3 begin4 db_ready := dbms_tdb.check_db('Linux IA (32-bit)');5 end;6 /PL/SQL procedure successfully completed.
If you call DBMS_TDB.CHECK_DB and no messages are displayed indicating conditions preventing transportBEFORE the "PL/SQL procedure successfully completed message", then your database is ready for transport.3) Use DBMS_TDB.CHECK_EXTERNAL to identify any external tables, directories or BFILEs. RMAN cannotautomate the transport of such files as mentioned above.
SQL> set serveroutput onSQL> declare2 external boolean;3 begin4 external := dbms_tdb.check_external;5 end;6 /The following directories exist in the database:SYS.DATA_PUMP_DIRPL/SQL procedure successfully completed.
If there are no external objects, then this procedure completes with no output. If there are external objects,however, the output will be somewhat similar to above.4) When the database is ready for transport, the RMAN CONVERT DATABASE command is run (when thesource database is READ ONLY), specifying a destination platform and how to name the output files. RMAN produces the following files needed to move the database to the destination system:a) A complete copy of the datafiles of the database, ready to be transported b) A PFILE for use with the new database on the destination platform, containing settings used in thePFILE/SPFILE from the source database.c) A transport script, which contains SQL statements used to create the new database on the destination platform
C:\>rman target / nocatalogRecovery Manager: Release 10.2.0.1.0 - Production on Fri Feb 2 17:05:35 2007Copyright (c) 1982, 2005, Oracle. All rights reserved.connected to target database: ORA10G (DBID=3926158280)using target database control file instead of recovery catalog