10.07.2015 Views

Expert Oracle Exadata - Parent Directory

Expert Oracle Exadata - Parent Directory

Expert Oracle Exadata - Parent Directory

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CHAPTER 13 MIGRATING TO EXADATARestrictions:• Tablespaces must be put in read-only mode during the process.• Character sets will, ideally, be the same for the source and target databases. Thereare exceptions to this rule. See the <strong>Oracle</strong> documentation if you plan to changecharacter sets during migration.• Objects with underlying dependencies like materialized views and table partitionsare not transportable unless they are contained in the same set. A tablespace set isa way of moving a group of related tablespaces together in one operation.• Before transporting encrypted tablespaces you must first copy the <strong>Oracle</strong> wallet tothe target system and enable it for the target database. A Database can only haveone <strong>Oracle</strong> wallet. If the database you are migrating to already has a wallet you willneed to use Data Pump to export and import table data.• Tablespaces that do not use block level encryption but have tables that usecolumn encryption cannot be transported with TTS. In this case Data Pump isprobably the best alternative.• Tablespaces that contain XML data types are supported by TTS as of 11gR1, butyou will have to use Data Pump to export the metadata. There are otherrestrictions and caveats to transporting XML data. Refer to the <strong>Oracle</strong> XML DBDeveloper’s Guide for a complete listing. To list tablespaces with XML data types,run the following query:SQL> select distinct p.tablespace_namefrom dba_tablespaces p,dba_xml_tables x,dba_users u,all_all_tables twhere t.table_name=x.table_nameand t.tablespace_name=p.tablespace_nameand x.owner=u.username;• Opaque types such as RAW and BFILE are supported by TTS but are not convertedcross-platform. The structure of these types is only known to the application andany differences in endian format must be handled by the application. Types andobjects are subject to this limitation whether their use of opaque types is direct orindirect.• Database version differences are supported as long as the target database is of thesame or higher version than the source database.Cross Platform Transportable Tablespaces (XTTS) supports conversion between most but not allplatforms. To determine whether your platform is supported, run the following query:456

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!