oracle-dba-commonlisted

MANDATORY shared foundation for EVERY oracle-dba skill. Import this BEFORE writing or running any DBA task. It is the single source of truth for: the SQLcl MCP connection contract (saved named connection "dba_ai_conn" only — never SYS/SYSTEM, never hardcoded creds), secret resolution from the Oracle Wallet / external password store (NO plaintext in argv/env/files EVER), the structured logging contract and canonical log paths, the exit-code convention (0=ok, documented non-zero codes), and the risk-tier banner + autonomy policy (T1 observe / T2 reversible-with-dry-run / T3 destructive-runbook-only). Do NOT reinvent connection, logging, dry-run, or approval-token logic in any other skill — source _common/scripts/lib.sh or lib.ps1 and follow this contract verbatim.
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · Data & Documents · score 62

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

# Oracle DBA - Common Foundation This skill defines the contracts that every `oracle-dba-<domain>` skill MUST obey. It ships no end-user task of its own; it is imported by all others. Target environment (ground truth): - OS: Linux (`.sh`) AND Windows (`.ps1`) — both produced for every OS-level task. - Oracle: 19c and 23ai (Enterprise Edition). Topology: single_instance and Data Guard. On-prem. - In-DB work: SQLcl MCP server, saved named connection `dba_ai_conn`. - Secrets: Oracle Wallet / external password store. Never plaintext. --- ## 1. Connection contract All in-database actions go through the **SQLcl MCP server** using the saved named connection **`dba_ai_conn`**. Rules: 1. Connect ONLY by name: `sql -name dba_ai_conn` (CLI) or the MCP `connect`/`run-sql` tools targeting the saved connection `dba_ai_conn`. The connection's credentials live in the SQLcl/Oracle Wallet store — they are resolved at connect time. 2. **Never** connect as `SYS` or `SYSTEM` unless a specific runbook explicitly requires `SYSDBA` (e.g. media recovery, `STARTUP MOUNT`). When a runbook needs SYSDBA it must say so and the operator supplies that privileged connection interactively — it is never the default and never auto-executed. 3. **Never** hardcode usernames, passwords, connect strings, or wallet paths in SQL, scripts, argv, environment variables, or files. 4. The helper `connect_db` (in `scripts/lib.sh` / `scripts/lib.ps1`) is the only sanctioned way to open a session.