Oracle Database 19c: RAC Administration Workshop — Lesson 3: Backup, Recovery, Patching, Upgrade, and Multitenant RAC

Technical Scope

• RMAN configuration, cluster-aware backup, restore, recovery, and service continuity
• node failure, instance recovery, media failure, control-file/redo scenarios, and drills
• rolling/nonrolling patching, opatchauto, datapatch, upgrade planning, and rollback
• CDB/PDB services in RAC, relocation, open states, and multitenant recovery considerations

Instructor Demonstration

The instructor traces RMAN configuration, cluster-aware backup, restore, recovery, and service continuity, then connects it to node failure, instance recovery, media failure, control-file/redo scenarios, and drills. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners complete a controlled exercise that applies node failure, instance recovery, media failure, control-file/redo scenarios, and drills and rolling/nonrolling patching, opatchauto, datapatch, upgrade planning, and rollback. The exercise introduces a realistic exception related to CDB/PDB services in RAC, relocation, open states, and multitenant recovery considerations and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of rolling/nonrolling patching, opatchauto, datapatch, upgrade planning, and rollback, traceable proof for RMAN configuration, cluster-aware backup, restore, recovery, and service continuity, and a repeatable recovery path for CDB/PDB services in RAC, relocation, open states, and multitenant recovery considerations. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when CDB/PDB services in RAC, relocation, open states, and multitenant recovery considerations occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested backup, recovery, patching, upgrade, and multitenant rac implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.