TTS eligibility checklist

Questions to answer before investing in detailed transportable-tablespace assessment.

Give each answer an owner, a date and a link to the supporting evidence. Record anything unconfirmed as an open question with a decision deadline.

  • Is the source release, platform, character set and feature usage compatible with the physical transport workflow?
  • Has self-containment been assessed, including dependent objects and metadata handling?
  • Does the existing physical model substantially carry forward, with agreed handling for the parts that do not — and is that what the target design actually wants?
  • Is the exact target deployment, service generation and provisioning workflow documented as supported?
  • Has the new-target provisioning constraint been confirmed against this design and any workloads already attached to the target?
  • Can level-0, ordered incrementals and a final read-only cutover fit within source impact, transfer and target capacity limits?
  • Are encryption, key management, credentials, sovereignty and temporary-storage controls approved?
  • Have validation, restoration, the rollback boundary and source-retention conditions been rehearsed?

A material “no” or unresolved item either rules TTS out or defines your next piece of investigation.

Reviewed 25 August 2026

These are my own views, written from years of building and moving large Oracle data platforms. They are not Oracle’s official guidance and this is not Oracle documentation. Volatile product claims are quarantined in Product facts that will date.