Posted by & filed under reference.

相同的的字节序的平台可以使用transportable database,否则只能使用transportable tablespace。

Note the following restrictions exist with Cross-Platform Transportable Database:

1) The principal restriction on cross-platform transportable database is that the source and destination platform must share the same endian format.
2) 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 Resetogs is performed once the new database is created. Similarly, 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.
3) BFiles, External tables and directories, Password files are not transported.
4) The Source and the target database version must be equal / greater than 10.2.0. version

关于字节序,可以查看以下的语句查询结果。

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

If the source platform and the target platform are of different endianness, then an additional
step must be done on either the source or target platform
to convert the tablespace being transported to the target format.
If the two platforms are not on the same endian format, you will need to use TRANSPORTABLE TABLESPACE
instead of CONVERT DATABASE.
If they are of the same endianness, then no conversion is necessary and tablespaces can be transported
as if they were on the same platform.

Transportable Database

在源库,用rman的convert database命令生成transport script,然后在目标库执行这个脚本既可创建新的数据库。
实际上,不需要把所有的datafile都转换一遍,只转换包含undo信息的表空间即可,一般是指system,undo表空间的所有数据文件,其他数据文件无需转换。
Transportable Tablespace

把表空间置成read only状态,
从源库导出metadata信息,
同样的rman转换数据文件格式,
数据文件传输到目标库,
将metadata信息导入目标库中。

Reference:

http://www.oracle.com/technetwork/database/features/availability/oracle-database-maa-best-practices-155386.html
How to Move Tablespaces Across Platforms Using Transportable Tablespaces With RMAN [ID 371556.1]
How To Use RMAN CONVERT DATABASE on Source Host for Cross Platform Migration [ID 413586.1]
10g : Transportable Tablespaces Across Different Platforms [ID 243304.1]
What Is The Best Practice If You Want To Migrate Oracle Database To 10g Release To A Different Operating System? [ID 433918.1]
Cross-Platform Migration on Destination Host Using Rman Convert Database [ID 414878.1]
Avoid Datafile Conversion during Transportable Database [ID 732053.1]

Related posts:

  1. Move all database objects from one tablespace to another
  2. Oracle Metalink reference – Database