Oracle Database 19c: RAC Administration Workshop — Lesson 1: Grid Infrastructure, Clusterware, and RAC Architecture

Technical Scope

• RAC architecture, cache fusion, global resources, interconnect, and instance coordination
• Clusterware stack, OHAS, CRS resources, voting files, OCR, and startup dependencies
• SCAN, VIPs, listeners, public/private networks, and name-resolution requirements
• cluster verification, resource status, log locations, and architecture fault isolation

Instructor Demonstration

The instructor models RAC architecture, cache fusion, global resources, interconnect, and instance coordination, then connects it to Clusterware stack, OHAS, CRS resources, voting files, OCR, and startup dependencies. 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 work through a role-based scenario involving Clusterware stack, OHAS, CRS resources, voting files, OCR, and startup dependencies and SCAN, VIPs, listeners, public/private networks, and name-resolution requirements. The exercise introduces a realistic exception related to cluster verification, resource status, log locations, and architecture fault isolation 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 SCAN, VIPs, listeners, public/private networks, and name-resolution requirements, traceable proof for RAC architecture, cache fusion, global resources, interconnect, and instance coordination, and a repeatable recovery path for cluster verification, resource status, log locations, and architecture fault isolation. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when cluster verification, resource status, log locations, and architecture fault isolation occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested grid infrastructure, clusterware, and rac architecture implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.