oracle-dba-rac-high-availabilitylisted

USE THIS SKILL WHENEVER the user mentions RAC, Real Application Clusters, Grid Infrastructure / GI, Clusterware, CRS, OHASD, crsctl / srvctl / olsnodes / cluvfy, OCR (Oracle Cluster Registry) or voting disk, SCAN / SCAN listener, node VIP, cluster interconnect / private network / Cache Fusion / GCS / GES, node eviction or split-brain or reboot/fence, instance start/stop on a cluster, cluster-managed database SERVICES, TAF / Transparent Application Failover, Application Continuity (AC) / FAN / ONS / FCF, connection or runtime load balancing (CLB / RLB), policy-managed vs admin-managed databases, or ANY of the codes CRS-xxxx, ORA-29740 (eviction/reconfiguration), ORA-481/ORA-29702 (CSS/clusterware), ORA-12545/ORA-12516 (SCAN/listener), or "gc blocks lost" / high "gc cr/current block receive time" — EVEN IF they do not name a specific task or tool. Covers read-only cluster/interconnect/service/eviction diagnostics, OCR manual backup, RAC instance and service start/stop/relocate, VIP & SCAN runtime ops, SCAN port
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · AI & Automation · score 62

Install: claude install-skill Shreyas70773/oracle-dba-agentic-skills

# Oracle DBA - RAC / High Availability In-DB RAC diagnostics (cluster/interconnect/service/eviction reports via SQLcl MCP `dba_ai_conn`) plus host-level Grid Infrastructure operations (`crsctl` / `srvctl` / `ocrconfig` / `olsnodes`) for Oracle 19c and 23ai (EE; single-instance, RAC and Data Guard topologies; on-prem). Everything self-executing is **T1 (observe)** or **T2 (reversible, dry-run-default)**. Every **structural / recovery / fencing** action (OCR or voting-disk restore, node add/remove, SCAN identity change, the full AC architecture rollout, eviction remediation) is **T3** and lives only in `references/runbooks.md` — it prints commands for a human and never self-executes. > The GI stack (`crsctl`, `srvctl`, `ocrconfig`, `ocrcheck`, `olsnodes`, `cluvfy`) > is a **host-level** toolset. SQLcl MCP runs in-DB SQL only (restrict level 4 = no > host commands), so GI operations ship as guarded `.sh` / `.ps1` (mechanism > `script:`); in-DB visibility ships as `sql:` run through `dba_ai_conn`. A future > guarded `oracle-dba-ops` MCP would front exactly these host scripts. ## Scope & risk map | Task | Level | Tier | Mechanism (sqlcl-mcp:sql/… \| script:scripts/… \| runbook:references/runbooks.md#…) | Idempotent? | |------|-------|------|-------------------------------------------------------------------------------------|-------------| | RAC cluster + instance topology report | L1 | T1 | `sqlcl-mcp:sql/rac_topology.sql` | yes — read-only | | In-DB cluster awareness / insta