oracle10g_rman_cross os_同位元組序_convert database

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.

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.