Managing Database Resources - OCP: Oracle Database 12c Administrator Certified Professional - page 470

Linux x86 64-bit Little
Microsoft Windows x86 64-bit Little
Solaris Operating System (x86) Little
HP IA Open VMS Little
Solaris Operating System (x86-64) Little
Apple Mac OS (x86-64) Little
12 rows selected.
SQL>
If the source and target have the same endian format, no RMAN conversion is necessary.
If they are different, you will need to use RMAN to convert the tablespace data files in the
transportable set to the correct endian format.
Step 2: Choose the Transportable Tablespace Set
In order for a tablespace set to be transportable, it must be self-contained; that is, objects in
the tablespace set must have no dependencies in tablespaces outside the tablespace set. Here
are some basic rules:
■ The tablespace set must contain all of the partitions of a partitioned table if any of the
table's partitions are included in the tablespace set.
■ If an index is included in a tablespace set, its corresponding table must also be included
in the tablespace set.
■ If you choose to include referential integrity constraints in the tablespace set, then all
tablespaces required to support the constraints must be included in the set.
■ If you have tables with LOB columns in the set, the tablespace that contains the LOBs
must be included.
The easy way to determine if the set of tablespaces is self-contained is to execute
the DBMS_TTS.TRANSPORT_SET_CHECK procedure, supplying the list of tablespaces in the
tablespace set, as in this example:
SQL> create table scott.foo_1 (x number, y varchar2(20)) tablespace users;
Table created.
SQL> create index scott.foo_1_indx on scott.foo_1 (x) tablespace user_data;
Index created.
SQL> SET SERVEROUTPUT ON
SQL> exec dbms_tts.transport_set_check ('USER_DATA');
PL/SQL procedure successfully completed.
SQL> SELECT * FROM TRANSPORT_SET_VIOLATIONS;
VIOLATIONS
ORA-39907: Index SCOTT.FOO_1_INDX in tablespace USER_DATA points to table
SCOTT.FOO_1 in tablespace USERS.
SQL>