Scalable methods to patch and upgrade your hybrid fleet of Oracle databases
summary
Enterprise Manager Fleet Maintenance automates patching and upgrades by building gold image homes, subscribing targets, deploying homes, then switching databases to the new home; Nationwide runs this across ~1,500 databases (just under 1,000 CDBs), using APIs/EMCLI and custom APEX orchestration to run 25–60 concurrent patching processes and hit an average 12–15 minutes average patch time per database, enabling 3–4 cycles a year, trimming staff effort dramatically while handling intermittent failures like corrupt inventories or data patch space issues.
AI-written summary · about
chapters (19)
- 0:00Scalable Oracle patching intro
- 1:13Database lifecycle pack overview
- 2:17Security and patching challenges
- 4:32Fleet maintenance benefits
- 7:00Nationwide’s patching journey
- 10:18Oracle patching options
- 13:09Fleet maintenance results
- 15:38Patching cycle explained
- 17:23Nationwide’s patching workflow
- 20:15Gold images in patching
- 23:20Fleet maintenance console
- 24:02Monitoring deployments
- 26:11Common errors and fixes
- 27:57Patching best practices
- 29:00Automated patching with EM
- 30:23Diverse DB environments
- 31:51EM CLI automation
- 32:12Getting started hints
- 32:32Summary of fleet maintenance
related talks
15mKeeping a Hypervisor Fleet Up to Date with Minimal Customer Disruption
27mAutomating Data Management for All
24mAutomate Data Management with Autonomous Database
17mPIMS: Fleet-Wide Datacenter Maintenance with Minimal Capacity Buffer and Predictable Lat…
36mHow to make your daily routine, code and database more efficient
27mModernizing On-Premise Infrastructure for Database Scalability
24mHigh Availability and Disaster Recovery Smart Features
28mBest practices for migrations to Autonomous Database