限制:
   1,redo and control file不是直接cp,會有一個轉變,但在目標庫會有open resetlogs操作
   2,bfile不能傳送,可以手工cp
   3,本地管理臨時表空間不能傳送,當傳送指令碼執行會自動在目標庫重建
   4,外部表和目錄同上
   5,密碼檔案同上,但convert database會包含一系列使用者及相應的許可權資訊,根據這些構建密碼檔案在目標庫

現摘錄oracle官方文件如下：

Using DBMS_TDB.CHECK_DB to Check Database State

DBMS_TDB.CHECK_DB checks whether a database can be transported to a desired destination platform, and whether the current state of the database permits transport. It can be called without arguments to see if any condition at the source database prevents transport. It can also be called with one or both of the following arguments:

Table 15-1 CHECK_DB Procedure Parameters

Parameter

Description

target_platform_name

The name of the destination platform, as it appears in .

This parameter is optional, but is required when the skip_option parameter is used. If omitted, it is assumed that the destination platform. is compatible with the source platform, and only the condtions in not related to platform. compatibility are tested.

skip_option

Specifies which, if any, parts of the database to skip when checking whether the database can be transported. Supported values (of type NUMBER) are:

SKIP_NONE (or 0), which checks all tablespaces
SKIP_OFFLINE (or 2), which skips checking datafiles in offline tablespaces
SKIP_READONLY (or 3), which skips checking datafiles in read-only tablespaces

DBMS_TDB.CHECK_DB returns TRUE if the source database can be transported using CONVERT DATABASE, and FALSE otherwise.

Make sure your database is open in read-only mode, then call DBMS_TDB.CHECK_DB with appropriate parameters.

If SERVEROUTPUT is ON, and DBMS_TDB.CHECK_DB returns FALSE, then the output includes the reason why the database cannot be transported. Possible conditions preventing the use of CONVERT DATABASE and their resolution are listed in the following table:

Table 15-2 Condtitions Tested by CHECK_DB Preventing Use of CONVERT DATABASE

Condition	Action
Unrecognized target platform. name.	Check for recognized platform. names.
Target platform. has a different endian format.	Conversion is not supported.
Database is not open read-only.	Open database read-only and retry.
There are active or in-doubt transactions in the database.	Open the database read-write. After the active transactions are rolled back and the in-doubt transactions are resolved, open the database read-only and retry. This can happen if users flashback the database and open it read only. The active transactions will be rolled back when the database is opened read-write.
Deferred transaction rollback needs to be done.	Open the database read-write and bring online the necessary tablespaces. Once the deferred transaction rollback is complete, open the database read-only and retry.
Database compatibility version is below 10.	Change the init.ora COMPATIBLE parameter to 10 or higher, open the database read-only and retry.
Some tablespaces have not been open read-write with compatibility version is 10 or higher.	Change the init.ora COMPATIBLE parameter to 10 or higher. Then open the affected tablespaces read-write. Then shut down the database, open it read-only, and retry.

This example illustrates the use of CHECK_DB on a 32-bit Linux platform. for transporting a database to 32-bit Windows, skipping read-only tablespaces, with a database that is currently open read-write.

SQL> set serveroutput on
SQL> declare
       db_ready boolean;
     begin
       db_ready := dbms_tdb.check_db('Microsoft Windows IA (32-bit)',dbms_tdb.skip_readonly);
     end;
     /
  
Database is not open READ ONLY. Please open database READ ONLY and retry.

PL/SQL procedure successfully completed.

If you call DBMS_TDB.CHECK_DB and no messages are displayed indicating conditions preventing transport before the PL/SQL procedure successfully completed message, then your database is ready for transport.

Using DBMS_TDB .CHECK_EXTERNAL to Identify External Objects

DBMS_TDB.CHECK_EXTERNAL must be used to identify any external tables, directories or BFILEs. RMAN cannot automate the transport of such files.

DBMS_TDB.CHECK_EXTERNAL takes no parameters. With SERVEROUTPUT set to ON, the output of DBMS_TDB.CHECK_EXTERNAL lists the external tables, directories and BFILEs of your database.

The following example shows how to call DBMS_TDB.CHECK_EXTERNAL:

SQL> set serveroutput on
SQL> declare
     external boolean;
  begin
    /* value of external is ignored, but with SERVEROUTPUT set to ON
     * dbms_tdb.check_external displays report of external objects
     * on console */
    external := dbms_tdb.check_external;
  end;

If there are no external objects, then this procedure completes with no output. If there are external objects, however, the output will be similar to the following example:

The following external tables exist in the database:
SH.SALES_TRANSACTIONS_EXT
The following directories exist in the database:
SYS.DATA_PUMP_DIR, SYS.MEDIA_DIR, SYS.DATA_FILE_DIR, SYS.LOG_FILE_DIR
The following BFILEs exist in the database:
PM.PRINT_MEDIA
 
PL/SQL procedure successfully completed.

Using the RMAN CONVERT DATABASE Command

The process for using CONVERT DATABASE is different depending upon whether the conversion is performed on the source platform. or the destination platform. This section includes the following topics:

CONVERT DATABASE, Converting Datafiles on the Source Platform

When the RMAN CONVERT DATABASE step is to be performed on the source platform, the process for transporting databases across platforms works as follows:

In preparation for transporting the database, the source database must be opened read-only.
```
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE OPEN READ ONLY;
```
Use the CHECK_DB function in the DBMS_TDB package as described in to ensure that no conditions exist that would prevent the transport of the database, such as incorrect compatibility settings, in-doubt or active transactions, or incompatible endian formats between the source platform. and the desired destination platform.
```
set serveroutput on
declare
    db_ready boolean;
  begin
    /* db_ready is ignored, but with SERVEROUTPUT set to ON any 
     * conditions preventing transport will be output to console */
    db_ready := dbms_tdb.check_db('Microsoft Windows IA (32-bit)',
        dbms_tdb.skip_none);
  end;
```

DBMS_TDB.CHECK_EXTERNAL must be used to identify any external objects:

SQL> set serveroutput on
SQL> declare
     external boolean;
  begin
    /* value of external is ignored, but with SERVEROUTPUT set to ON
     * dbms_tdb.check_external displays report of external objects
     * on console */
    external := dbms_tdb.check_external;
  end;

Typical output of DBMS_TDB.CHECK_EXTERNAL is shown in this example:

The following external tables exist in the database:
SH.SALES_TRANSACTIONS_EXT
The following directories exist in the database:
SYS.DATA_PUMP_DIR, SYS.MEDIA_DIR, SYS.DATA_FILE_DIR, SYS.LOG_FILE_DIR
The following BFILEs exist in the database:
PM.PRINT_MEDIA
 
PL/SQL procedure successfully completed.

When the database is ready for transport, the RMAN CONVERT DATABASE command is run, specifying a destination platform. and how to name the output files. RMAN produces the files needed to move the database to the destination system, including the following:

A complete copy of the datafiles of the database, ready to be transported

A PFILE for use with the new database on the destination platform, containing settings used in the PFILE or SPFILE from the source database. Several entries at the top of the PFILE should be edited when the database is moved to the destination platform.:

# Please change the values of the following parameters:
  control_files            = "/tmp/convertdb/cf_D-NEWDBT_id-1778429277_00gb9u2s"
  db_recovery_file_dest    = "/tmp/convertdb/orcva"
  db_recovery_file_dest_size= 10737418240
  instance_name            = "NEWDBT"
  service_names            = "NEWDBT.regress.rdbms.dev.us.oracle.com"
  plsql_native_library_dir = "/tmp/convertdb/plsqlnld1"
  db_name                  = "NEWDBT"

A transport script, which contains SQL statements used to create the new database on the destination platform

The following example demonstrates the use of CONVERT DATABASE on the source platform, along with its outputs. Output related to the transport script. and the parameter file for the new database is highlighted.

RMAN> CONVERT DATABASE NEW DATABASE 'newdb'
        transport script. '/tmp/convertdb/transportscript'
        to platform. 'Microsoft Windows IA (32-bit)'
        db_file_name_convert '/disk1/oracle/dbs' '/tmp/convertdb'
        ;
 
Starting convert at 25-JAN-05
using channel ORA_DISK_1
 
External table SH.SALES_TRANSACTIONS_EXT found in the database
 
Directory SYS.DATA_PUMP_DIR found in the database
Directory SYS.MEDIA_DIR found in the database
Directory SYS.DATA_FILE_DIR found in the database
Directory SYS.LOG_FILE_DIR found in the database
 
BFILE PM.PRINT_MEDIA found in the database
 
User SYS with SYSDBA and SYSOPER privilege found in password file
User OPER with SYSDBA privilege found in password file
channel ORA_DISK_1: starting datafile conversion
input datafile fno=00001 name=/disk1/oracle/dbs/tbs_01.f
converted datafile=/tmp/convertdb/tbs_01.f
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting datafile conversion
input datafile fno=00002 name=/disk1/oracle/dbs/tbs_ax1.f
converted datafile=/tmp/convertdb/tbs_ax1.f
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:03
.
.
.
channel ORA_DISK_1: starting datafile conversion
input datafile fno=00016 name=/disk1/oracle/dbs/tbs_52.f
converted datafile=/tmp/convertdb/tbs_52.f
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:01
Run SQL script. /tmp/convertdb/transportscript on the target platform. 
  to create database
Edit init.ora file init_00gb3vfv_1_0.ora.This PFILE will be used to 
  create the database on the target platform
To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on 
  the target platform
To change the internal database identifier, use DBNEWID Utility
Finished backup at 25-JAN-05
 
RMAN>

When CONVERT DATABASE completes, the source database may be opened read-write again. Then, all of the files produced must then be copied to the destination host.

Place the datafiles in the desired locations on the destination host. If the path to the datafiles is different on the destination, then edit the transport script. to refer to the new datafile locations. Also edit the PFILE to change any settings for the destination database.
Then execute the transport script. in SQL*Plus to create the new database on the destination host.
```
SQL> @transportscript  --見上
```

When the transport script. finishes, the creation of the new database is complete.

oracle10g_rman_cross os_同位元組序_convert database

Using DBMS_TDB.CHECK_DB to Check Database State

Using DBMS_TDB .CHECK_EXTERNAL to Identify External Objects

Using the RMAN CONVERT DATABASE Command

CONVERT DATABASE, Converting Datafiles on the Source Platform

相關文章