oracle-dba-exadata-engineered-systemslisted
Install: claude install-skill Shreyas70773/oracle-dba-agentic-skills
# Oracle DBA - Exadata / Engineered Systems
Health, storage-cell visibility, IORM/Smart-Scan/flash diagnostics, patch readiness, and
the plan-only Tier-3 runbooks for Oracle Exadata Database Machine (19c and 23ai; EE;
single-instance and Data Guard; on-prem). Two mechanisms by design:
- **In-DB** work (offload stats, ASM headroom, DBRM plans, CELL_FLASH_CACHE attributes)
runs through the **SQLcl MCP** saved connection `dba_ai_conn` → `sql/*.sql` ("sqlcl-mcp").
- **Host** work (exachk/AHF, `cellcli`/`dcli`, `patchmgr`) **cannot** go through SQLcl MCP
(restrict level 4) → `.sh`/`.ps1` ("script", to later front a guarded oracle-dba-ops MCP).
Everything self-executing is **T1 (observe)** or **T2 (reversible, dry-run-default)**. Every
cell/switch/compute **patch apply**, **storage-cell mutation**, **cell IORMPLAN config**,
**cell flash-cache tuning**, and **rack expansion** is **T3** and lives only in
`references/runbooks.md` — it prints commands for a human and never self-executes.
## Scope & risk map
| Task | Level | Tier | Mechanism (script / sql / runbook path) | Idempotent? |
|------|-------|------|------------------------------------------|-------------|
| Exachk / health check execution (exachk/AHF + in-DB summary) | L2 | T1 | `scripts/run_exachk.sh` / `.ps1` ("script") + `sql/exadata_health_summary.sql` ("sqlcl-mcp") | yes — read-only; run-in-progress lock no-ops; failing best practice = finding |
| In-DB Exadata health & cell-visibility summary | L2 | T1 | `sql/e