Transportable Tablespaces allow you to move an entire tablespace (datafiles + metadata) across Oracle databases without exporting full table data . Only metadata is exported using Data Pump — datafiles are copied directly.

✔ 10x faster than Full Export/Import ✔ Ideal for multi-terabyte databases ✔ Enables platform migration (Linux → RHEL → AWS EC2) ✔ Supports Oracle versions 11g → 19c ✔ Minimal downtime

TTS is suitable when: - Migrating large Oracle databases to Amazon EC2 (same OS platform) Migrating large Oracle databases to Amazon EC2 (same OS platform) - Moving schemas stored in dedicated tablespaces Moving schemas stored in dedicated tablespaces - Performing lift-and-shift cloud migrations Performing lift-and-shift cloud migrations - Reducing downtime during migration Reducing downtime during migration - Migrating from on-prem Oracle to AWS cloud-managed setups (EC2 based) Migrating from on-prem Oracle to AWS cloud-managed setups (EC2 based) > Note: TTS does not apply to Amazon RDS Oracle, because RDS does not allow direct datafile access. Note: TTS does not apply to Amazon RDS Oracle, because RDS does not allow direct datafile access.

Migration flow using TTS:

1
2
3
4
5

On-Prem Oracle DB → Identify self-contained TS → Make TS READ ONLY
→ Export metadata using Data Pump
→ Copy datafiles to AWS EC2
→ Plug tablespaces into AWS Oracle DB
→ Import metadata → Make TS READ WRITE

- Source and target platforms must be same endian format Check using: Source and target platforms must be same endian format Check using: - Target DB version must be equal or higher than source Target DB version must be equal or higher than source - Tablespaces must be self-contained Tablespaces must be self-contained - Sufficient space on AWS EC2 storage Sufficient space on AWS EC2 storage

- AWS EC2 instance with: Oracle Linux / RHEL Oracle Database installed Enough block storage (EBS) AWS EC2 instance with: - Oracle Linux / RHEL Oracle Linux / RHEL - Oracle Database installed Oracle Database installed - Enough block storage (EBS) Enough block storage (EBS) - Secure Copy (SCP/SFTP) access for transferring datafiles Secure Copy (SCP/SFTP) access for transferring datafiles

Check if they are self-contained : Only metadata is exported, not the datafiles: This generates: - - Datafiles belonging to USERS, HR Datafiles belonging to USERS, HR Use SCP or AWS Transfer Family: Login to AWS Oracle instance. Oracle reads the datafiles and integrates them into the target database. Migration is complete!

- Use separate tablespaces per schema for easier TTS migration Use separate tablespaces per schema for easier TTS migration - Perform TRANSPORT_FULL_CHECK=Y before migration Perform TRANSPORT_FULL_CHECK=Y before migration - Ensure same block size on source and target Ensure same block size on source and target - Run before starting Run before starting - Perform migration during low traffic period Perform migration during low traffic period - Validate objects after import Validate objects after import - Always backup source and target databases Always backup source and target databases

Avoid TTS if: Database contains SYS , SYSTEM objects Cross-tablespace dependencies exist Migrating to Amazon RDS Oracle Tablespaces use Bigfile TS with different block size Platform endian formats do not match