Best Practices for Using Transportable Tablespaces (TTS)
(Doc ID 1457876.1)
Last updated on FEBRUARY 21, 2024
Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 9.2 to 12.1] Oracle Database Cloud Schema Service - Version N/A and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Backup Service - Version N/A and later Information in this document applies to any platform.
The purpose of this document is to discuss best practices when using transportable tablespaces (TTS), especially when migrating databases to a different RDBMS version and/or OS.
The suggestions in this note generally apply to all databases. E-Business Suite (EBS) databases, however, have specific instructions for using TTS. For information regarding TTS and EBS databases, please see one of these two notes:
Using Transportable Database to migrate Oracle E-Business Suite 11i Using Oracle Database 10.2.0 or 11.1.0 Document 729309.1
Using Transportable Database to migrate E-Business Suite R12 Using Oracle Database 10gR2 or 11gR1 Document 734763.1.
Note: With 12c, you can now use full transportable export/import to move complete databases for sources that are 184.108.40.206 and up to 12c targets. If this is your scenario, you may want to consider whether or not TTS is still the best way to move your entire database. See <Document 1457743.1> Upgrading a Database Using Transportable Tablespaces (TTS) regarding the Full Transportable option.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!