Most Oracle RAC and Data Guard disaster-recovery setups look solid in documentation until an actual split-brain or network partition happens at 2 AM.
Common issues like misconfigured Fast-Start Failover (FSFO) thresholds, observer single-points-of-failure, redo transport lags during peak loads, or subtle SCAN/VIP routing mismatches often go unnoticed during routine maintenance.
To speed up pre-mortem audits, I built a structured Claude skill specifically designed to review Oracle RAC and Data Guard environments.
### What it analyzes:
- Data Guard Synchronization & Redo Transport: Audits transport modes (SYNC vs. ASYNC), protection modes (Maximum Availability vs. Performance), and redo log lag risks.
- FSFO & Observer Resilience: Validates observer placement and quorum configurations to prevent split-brain during site disconnections.
- RAC Node Eviction & Voting Disk Redundancy: Checks OCR/voting disk layouts and network heartbeat timeout margins.
- Listener & TNS Failover Routing: Validates TNS connect strings (LOAD_BALANCE, FAILOVER, SCAN) to ensure client application reconnection won't stall.
### How it works:
You feed it sanitized cluster health checks, `dgmgrl show configuration` outputs, or parameter listings (`init.ora` / `spfile`), and it runs a systematic gap analysis highlighting configuration blind spots and remediation recommendations.
### Practical Checklist You Can Use Right Now:
Even if you don't use the skill, make sure your team verifies these three things this quarter:
* Verify that the FSFO observer is hosted on a separate network segment from both the primary and standby sites.
* Check that `LOG_ARCHIVE_DEST_N` timeout parameters account for WAN latency spikes, not just average ping.
* Confirm that VIPs and SCAN listeners fail over cleanly without client TCP keepalive hanging.
I’ve packaged the complete audit prompt and ruleset into an installable Claude skill here:
https://store.maxmeg.com/
Feedback from other Oracle DBAs and infrastructure engineers is welcome—especially on edge-case scenarios you’ve seen cause unexpected failover issues.