Oracle Database 19c: RAC Administration Workshop — Lesson 4: Performance, Availability, Diagnostics, and Failure Drills

Technical Scope

• AWR, ASH, ADDM, global cache metrics, interconnect latency, and wait analysis
• services, FAN, Fast Connection Failover, Application Continuity, and load balancing
• Cluster Health Monitor, TFA, CRS logs, network diagnostics, and hang analysis
• node eviction, service outage, storage fault, recovery exercise, and support runbook

Instructor Demonstration

The instructor configures and validates AWR, ASH, ADDM, global cache metrics, interconnect latency, and wait analysis, then connects it to services, FAN, Fast Connection Failover, Application Continuity, and load balancing. 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 execute a guided lab focused on services, FAN, Fast Connection Failover, Application Continuity, and load balancing and Cluster Health Monitor, TFA, CRS logs, network diagnostics, and hang analysis. The exercise introduces a realistic exception related to node eviction, service outage, storage fault, recovery exercise, and support runbook 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 Cluster Health Monitor, TFA, CRS logs, network diagnostics, and hang analysis, traceable proof for AWR, ASH, ADDM, global cache metrics, interconnect latency, and wait analysis, and a repeatable recovery path for node eviction, service outage, storage fault, recovery exercise, and support runbook. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when node eviction, service outage, storage fault, recovery exercise, and support runbook occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested performance, availability, diagnostics, and failure drills implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.