Moving your application to Oracle Autonomous Database
summary
Moving to Oracle Autonomous Database usually gives a Moore’s-law uplift but failures trace to two concrete variables: optimizer metadata and network latency. Bring schema statistics (including histograms and extended stats) plus SQL plan management baselines and SQL profiles rather than relying on fresh stats; use AWR and SQL Monitor to compare plans. Measure latency with the OCIPING tool (tnsping is insufficient); examples show 0.7 ms extra latency × 900 roundtrips/s doubling a 40 → 85 minute batch. Watch defaults like parallel DML enabled by default and bring statistics and SQL plan baselines when migrating.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:41Real-World Performance Team
- 2:28Main Differences ADW vs ATP
- 3:54Multitenant Architecture and RAC
- 6:14Pre-defined Set of TNS Services
- 10:08What's Special About Moving to ADB?
- 21:14Determining Impact of Change in Latency
- 26:28Your Application Will Run on RAC
related talks
28mBest practices for migrations to Autonomous Database
01mAutonomous Database
27mAutomating Data Management for All
16mOracle MAA for Data Resiliency Across Hyperscalers
31mAutonomous Database: Simplify your database management
51mOracle to PostgreSQL Migration with Near Zero Downtime
24mAutomate Data Management with Autonomous Database
06mMigration Consideration Oracle to PostgreSQL