Oracle Autonomous Database Internals: What Is Really Automated
Service: Oracle Autonomous Database on OCI (Shared & Dedicated Exadata Infrastructure)
Workload Types Tested: ADW, ATP, AJD • Oracle DB Version: 19c base + 23ai features on ADB
Workload: 2.8 TB OLTP + 6.1 TB analytics • Scale: 4–32 ECPU auto-scaling • Region: OCI ap-mumbai-1 primary, ap-hyderabad-1 DR
"The self-driving database." Oracle's marketing for Autonomous Database promises that the DBA is no longer needed — the database manages itself. Patches itself. Tunes itself. Scales itself. After running Oracle ADB in production for financial and analytics workloads across multiple OCI regions, I can tell you the reality is more nuanced and more interesting than the marketing suggests.
Oracle Autonomous Database genuinely automates things that used to consume enormous DBA time — patching, backup, storage management, and a meaningful subset of performance tuning. But it does not eliminate the need for database expertise. It changes what that expertise is applied to. The DBA who understands what ADB actually automates and what it does not will be dramatically more effective than one who takes the "self-driving" claim at face value.
This guide opens the hood on Oracle ADB internals: how auto-indexing actually works, what happens inside auto-patching, when auto-scaling kicks in, and which critical responsibilities remain firmly with the DBA and architect.