DBA Hub

📋Steps in this guide1/13

Transportable Tablespaces Migration

Learn how Transportable Tablespaces (TTS) offers the fastest way to migrate Oracle databases with minimal downtime. This guide covers prerequisites, step-by-step migration, metadata export, datafile copy, XTTS for cross-platform moves, and best practices.

oracle configurationintermediate
by OracleDba
42 views
1

What Are Transportable Tablespaces?

Transportable Tablespaces (TTS) is an Oracle feature that allows you to: - Move tablespaces across databases quickly Move tablespaces across databases quickly - Transfer only metadata using export/import Transfer only metadata using export/import - Reuse the same physical datafiles Reuse the same physical datafiles - Avoid full data unload/load Avoid full data unload/load - Reduce downtime from hours to minutes Reduce downtime from hours to minutes It works for both non-CDB and PDB databases, and it’s widely used in migrations, upgrades, and cloud moves.
2

Why TTS Is the Fastest Migration Method

Traditional migration ( ) exports every row and imports it again — slow for large DBs. TTS, on the other hand: - Copies datafiles directly (very fast using cp/rsync) Copies datafiles directly (very fast using cp/rsync) - Exports/imports only metadata Exports/imports only metadata - Avoids row-level export Avoids row-level export - Supports incremental backup-based transfer (XTTS) Supports incremental backup-based transfer (XTTS) - Minimizes application downtime Minimizes application downtime This makes it ideal for databases with huge volumes of static or historical data.
3

When Should You Use TTS?

Use Transportable Tablespaces when: - Migrating large databases between servers Migrating large databases between servers - Moving to Oracle Cloud (OCI) Moving to Oracle Cloud (OCI) - Upgrading hardware or storage Upgrading hardware or storage - Consolidating databases into a new CDB Consolidating databases into a new CDB - Refreshing environments (DEV/TEST from PROD) Refreshing environments (DEV/TEST from PROD) - Performing cross-platform migrations (using XTTS) Performing cross-platform migrations (using XTTS)
4

Prerequisites

Before starting a TTS migration: - Source and target DB must be same or higher version . Source and target DB must be same or higher version . - Endianness must match (or use RMAN conversion). Endianness must match (or use RMAN conversion). - Tablespaces must be self-contained . Tablespaces must be self-contained . - Tablespaces must be in READ ONLY mode during final copy. Tablespaces must be in READ ONLY mode during final copy. - Sufficient space on target system. Sufficient space on target system.
5

Step 1: Identify Self-Contained Tablespaces

Check for violations:
6

Step 3: Export Metadata Using Data Pump

This exports only metadata , not data.
7

Step 4: Copy Datafiles to Target Server

Use cp/scp/rsync: Or use RMAN CONVERT if cross-platform:
8

Step 5: Import Metadata on Target

Oracle will plug the tablespaces into the target database.
9

Step 6: Make Tablespaces READ WRITE

Migration is complete! Cross-Platform Transportable Tablespaces (XTTS) uses incremental RMAN backups to sync changes while the source DB is online. This gives: - Near-zero downtime Near-zero downtime - Faster final cutover Faster final cutover - Platform migration flexibility (Linux → Solaris, AIX → Linux, etc.) Platform migration flexibility (Linux → Solaris, AIX → Linux, etc.) XTTS is the preferred method for enterprise-level migrations. At Learnomate Technologies, we see DBAs using TTS for: ✔ Refreshing massive QA/DEV instances ✔ Migrating on-prem databases to OCI ✔ Platform-to-platform migrations ✔ Splitting large databases into modular TTS chunks ✔ Storage-level migrations (file system → ASM) Because TTS avoids full import/export, migrations become predictable and fast.
10

Speed

Datafiles are directly copied, making the process significantly faster.
11

Low Downtime

Only the READ ONLY phase causes application freeze.
12

Flexibility

Supports non-CDB, CDB, and cross-platform.
13

Efficient

Ideal for multi-terabyte databases. - Tablespaces must be self-contained Tablespaces must be self-contained - Cannot migrate SYSTEM, SYSAUX, UNDO, TEMP Cannot migrate SYSTEM, SYSAUX, UNDO, TEMP - Needs downtime during final sync Needs downtime during final sync - May require endian conversion May require endian conversion Transportable Tablespaces is one of the fastest and most efficient ways to migrate large Oracle databases with minimal downtime. If you’re dealing with multi-terabyte systems, cloud onboarding, or platform refreshes, TTS (and XTTS) will save you hours—sometimes days—during migrations. Learnomate Technologies recommends using TTS whenever speed and efficiency matter the most in database transitions. Explore more with Learnomate Technologies! Want to see how we teach? Head over to our YouTube channel for insights, tutorials, and tech breakdowns: www.youtube.com/@learnomate To know more about our courses, offerings, and team: Visit our official website: www.learnomate.org Interested in mastering Oracle Database Administration? Check out our comprehensive Oracle DBA Training program here: https://learnomate.org/oracle-dba-training/ Want to explore more tech topics? Check out our detailed blog posts here: https://learnomate.org/blogs/ And hey, I’d love to stay connected with you personally! Let’s connect on LinkedIn: Ankush Thavali Happy learning! Ankush😎

Comments (0)

Please to add comments

No comments yet. Be the first to comment!