Databases Reference
In-Depth Information
5. Transfer the datafiles to the target platform (if the DBA decides to perform
the format conversion at the target platform, then the file transference must
be performed first).
6. Import the tablespace metadata at the target database.
7. Make the tablespace read/write.
Some important points to consider when performing an inter-platform tablespace
transportation are:
• The source and target database character sets must be the same
• The source and target platforms must have the same Endianess, if this is not
the case; it is when RMAN must perform the endianess conversion.
• The tablespace name must be unique at the target database and the data must
be self-contained. If the tablespace is not unique, then it must be renamed.
Let's create a regular locally managed tablespace on a windows platform. The goal is
to have this tablespace migrated to a server running under a Linux operating system:
SQL> create tablespace MIGRATE_TO_UNIX_TS
2 datafile 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ALPHA\MIGRATE_TO_UNIX_
TS_01.DBF' size 64m
3 extent management local
4 segment space management auto uniform size 64k;
Tablespace created.
SQL> create table system.where_are_you_from(
2 Question varchar2(40),
3 Answer varchar2(80))
4 tablespace MIGRATE_TO_UNIX_TS;
Table created.
SQL> select * from where_are_you_from;
QUESTION ANSWER
---------------- --------------------------------
Version Oracle Database 10g Enterprise
Edition Release 10.1.0.5.0 - Prod
OS Platform Microsoft Windows IA (32-bit)
Endian Format Little
SQL> exec dbms_tts.transport_set_check('MIGRATE_TO_UNIX_TS', TRUE);
SQL> SELECT *
2 FROM transport_set_violations;
no rows selected
Search WWH ::
Custom Search