RMAN CONVERT DATABASE 的限制

普通的RMAN DUPLICATE/RESTORE/RECOVER(非convert database 方式)  对平台有一定的要求:

具体见上一篇博客:

http://space.itpub.net/15747463/viewspace-758172

对于不满足以上要求的需要使用CONVERT DATABASE 进行跨平台迁移

但是也有一定的限制具体如下:

---必须有相同的endian format

   可以通过以下视图查询

   SQL> COLUMN PLATFORM_NAME FORMAT A32

SQL> SELECT * FROM V$TRANSPORTABLE_PLATFORM;
 
PLATFORM_ID PLATFORM_NAME                    ENDIAN_FORMAT
----------- -------------------------------- --------------
          1 Solaris[tm] OE (32-bit)          Big
          2 Solaris[tm] OE (64-bit)          Big
          7 Microsoft Windows IA (32-bit)    Little
         10 Linux IA (32-bit)                Little
          6 AIX-Based Systems (64-bit)       Big
          3 HP-UX (64-bit)                   Big
          5 HP Tru64 UNIX                    Little
          4 HP-UX IA (64-bit)                Big
         11 Linux IA (64-bit)                Little
         15 HP Open VMS                      Little
          8 Microsoft Windows IA (64-bit)    Little
          9 IBM zSeries Based Linux          Big
         13 Linux 64-bit for AMD             Little
         16 Apple Mac OS                     Big
         12 Microsoft Windows 64-bit for AMD Little
         17 Solaris Operating System (x86)   Little
         18 IBM Power Based Linux            Big
 
17 rows selected

----以下部分不能被传输

    1 redo file

    2 controlfile 

    3 外部表和目录

    4 密码文件

官方文档说明:

The principal restriction on cross-platform. transportable database is that the source and destination platform. must share the same endian format. For example, while you can transport a database from Microsoft Windows to Linux for x86 (both little-endian), or from HP-UX to AIX (both big-endian), you cannot transport a whole database from HP_UX to Linux for x86 using this feature. You can, however, create a new database on a destination platform. manually, and transport needed tablespaces from the source database using cross-platform. transportable tablespace as described in "Cross-Platform. Tranportable Tablespace: CONVERT DATAFILE or TABLESPACE".

Also note that some parts of the database cannot be transported directly:

Redo log files and control files from the source database are not transported. New control files and redo log files are created for the new database during the transport process, and an OPEN RESETLOGS is performed once the new database is created.

Note:

The control file for the converted database does not contain a copy of the RMAN repository information from the source database. Backups from the source database cannot be used with the converted database.

BFILEs are not transported. RMAN provides a list of objects using the BFILE datatype in the output for the CONVERT DATABASE command, but users must copy the BFILEs themselves and fix their locations on the destination database.

Tempfiles belonging to locally managed temporary tablespaces are not transported. The temporary tablespace will be re-created on the target platform. when the transport script. is run.

External tables and directories are not transported. RMAN provides a list of affected objects as part of the output of the CONVERT DATABASE command, but users must redefine these on the destination platform. See Oracle Database Administrator's Guide for more information on managing external tables and directories.

Password files are not transported. If a password file was used with the source database, the output of CONVERT DATABASE includes a list of all usernames and their associated privileges. Create a new password file on the destination database using this information. See Oracle Database Security Guide for more information on managing password files.