Oracle Database Administration II case studies
Oracle Database Administration II · Put your knowledge to work in context.
Oracle Database Administration II is the second-tier administration exam in Oracle's certification path for database professionals. It is aimed at DBAs who already manage a single instance comfortably and now need to operate backup and recovery, multitenant environments, and performance diagnostics at production scale. The exam is delivered in English as multiple-choice and multiple-response questions, and it tests applied judgment rather than trivia: you are expected to read a scenario, identify the failure mode, and pick the RMAN, Flashback, or CDB/PDB action that actually resolves it. Coverage clusters around RMAN configuration and backup strategy, restore and recovery operations, Flashback and the Data Recovery Advisor, multitenant architecture and PDB lifecycle, provisioning and cloning, transportable tablespaces and data movement, SQL tuning and performance monitoring, plus Resource Manager and Scheduler. The Oracle Database Administration II case studies are 5 cases and about 3,092 words.
1RMAN Retention and FRA Pressure on a 2 TB OLTP Database
Your 19c single-instance OLTP database is 2 TB and generates about 200 GB of redo per day. The backup window is 22:00–02:00.
669 words, about 3 min2Single Datafile Recovery in a Multitenant CDB
A 19c CDB named CDB1 hosts PDBs SALES and HR. The database is in ARCHIVELOG mode, uses a 1 TB FRA, and has a recovery catalog.
622 words, about 3 min3PDB Flashback vs CDB Flashback After a Failed Upgrade
CDB1 runs 19c with PDBs APP and REPORTING. FLASHBACK DATABASE is enabled for the CDB, the FRA is 800 GB, and the retention target is two hours.
610 words, about 3 min4Hot Clone and CDB Resource Plan for a 40-PDB RAC CDB
CDB1 (19c) hosts 40 PDBs on a four-node RAC cluster with 32 CPU cores. Local undo is enabled.
613 words, about 3 min5SQL Plan Baseline Regression After an Upgrade
After an upgrade from 12.2 to 19c, a financial reporting query (SQL ID 8k3x7y2z1) that ran in 2 seconds now runs 90 seconds. AWR shows the query's plan hash value changed and DB CPU is the top foreground wait.
578 words, about 3 min