Database upgrade best practices: Upgrade now
summary
Recommendation: upgrade to 19c until April 2027 as the long‑term supported target, apply the latest RU (example 19.13) plus the 555.1 MOS one‑offs, and use AutoUpgrade (get the newest build from My Oracle Support, e.g. 21.2) to analyze and deploy with one config file. Remove unused components (benchmark cut upgrade from 52 to 30 minutes), take dictionary stats seven days before, set compatible only after 7–10 days of validation, and rely on guaranteed restore points/Flashback for fast fallback.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:59Release
- 1:54Lifetime Support Policy
- 2:52Patches
- 4:27Familiarize
- 7:04Practice
- 8:48Performance Stability Prescription
- 13:06AutoUpgrade
- 14:17Duration
- 16:27Compatible
- 18:26Multitenant
- 19:19Statistics
- 21:36Parameters
- 26:23Successful Database Upgrades
related talks
23mUpgrade to Oracle Database 19c
26mAutoUpgrade 2.0: internals and new features
14mUpgrade to Oracle Database 23ai
32mOracle Database application development: what's new, what's next?
32mOracle Essbase update and roadmap
06mMigration Consideration Oracle to PostgreSQL
30mMoving your application to Oracle Autonomous Database
46mAn ultimate guide to upgrading your PostgreSQL installation