Oracle Database 19c: Data Guard Administration Workshop — Lesson 3: Switchover, Failover, Reinstate, Fast-Start Failover, and Client Continuity

Technical Scope

• switchover readiness, execution, service movement, and post-role validation
• failover scenarios, data loss assessment, activation, and application checks
• flashback database, reinstate, rebuild, and recovery after role transition
• observer, fast-start failover, thresholds, services, TAF or FAN awareness

Instructor Demonstration

Demonstrate switchover readiness, execution, service movement, and post-role validation within a mission-critical Oracle Database protected by a physical standby across sites, validated for planned switchover, unplanned failover, data protection, and operational recovery, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering failover scenarios, data loss assessment, activation, and application checks and flashback database, reinstate, rebuild, and recovery after role transition, then test a failure, exception, or business-control scenario involving observer, fast-start failover, thresholds, services, TAF or FAN awareness.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The Switchover, Failover, Reinstate, Fast-Start Failover, and Client Continuity result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in switchover readiness, execution, service movement, and post-role validation, failover scenarios, data loss assessment, activation, and application checks, flashback database, reinstate, rebuild, and recovery after role transition, or observer, fast-start failover, thresholds, services, TAF or FAN awareness without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for Switchover, Failover, Reinstate, Fast-Start Failover, and Client Continuity and defend the result with documented evidence.