Best practices for migrations to Autonomous Database
summary
After 3+ years in production Autonomous Database claims to simplify provisioning, automate patching and scale resources up to 3x headroom on demand, but migrations are logical only (no datafile transport). Legacy features like application containers and data masking pack are locked down. Migration tools and limits are concrete: CPAT validates readiness and emits JSON/text, ZDM automates zero‑downtime migrations using GoldenGate (installer ~800 MB), and Data Pump handles Oracle 10g–21 exports for multi‑TB imports. Database Actions, SQL Developer, SQL Loader and Database Migration Service are the operational choices.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:31Autonomous Database Infrastructure Choices
- 5:50Autonomous Database Pre-migration checks
- 8:59Migration Best Practice Cloud Premigration Advisor Tool (CPAT)
- 10:58Autonomous Database Migration Techniques
- 13:33Options Database Actions (Public and C@C)
- 14:29Options SQL Developer (Public and C@C)
- 16:49Options Data Pump (Public and CC)
- 19:04Options Zero Downtime Migration (ZDM) Public and Cloud at Customer
- 20:33Logical Migration with ZDM
- 24:56Database Migration Service in OCI
- 25:58Migration Best Practices Summary
related talks
24mAutomate Data Management with Autonomous Database
34mOracle Autonomous Database: simplify your database management
01mAutonomous Database
30mMoving your application to Oracle Autonomous Database
33mAutonomous Database: taking Oracle's most secure database to the next level
49mOracle Database directions
16mOracle MAA for Data Resiliency Across Hyperscalers
35mBest practices for migrating with databases