oracle-dba-routine-maintenancelisted

USE THIS SKILL WHENEVER the user mentions routine / housekeeping DBA maintenance: recompiling INVALID objects (utlrp / UTL_RECOMP), purging old trace / alert / incident files (ADR / adrci), the standard daily/weekly health-check report, sequence cache tuning (row-cache / SQ enqueue / "sequence" waits), index rebuild / coalesce, partition add / drop / split / merge maintenance, materialized-view refresh, PURGE RECYCLEBIN, AWR snapshot / retention management, optimizer stats-history purge, or Unified/standard audit-trail purge (DBMS_AUDIT_MGMT) — EVEN IF they do not name the specific task. Covers Oracle 19c and 23ai, EE, single-instance and Data Guard, on-prem. Follows the oracle-dba-common contracts: in-DB work via the SQLcl MCP saved connection dba_ai_conn, Oracle Wallet secrets (never plaintext, never SYS/SYSTEM), --dry-run default on every T2 script (explicit --execute to act), structured logging, and tier gating (max self-execute = T2; structural DROP/SPLIT/MERGE/EXCHANGE and big segment moves are T3 runbo
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · AI & Automation · score 62

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

# Oracle DBA - Routine Maintenance Housekeeping that keeps a database healthy: recompiling invalid objects, purging diagnostic files and history (trace/alert, recyclebin, AWR, stats history, audit trail), the standard health-check report, sequence-cache tuning, and the reversible side of index / partition / materialized-view maintenance — for Oracle 19c and 23ai (EE; single-instance and Data Guard; on-prem). Everything self-executing here is **T1 (observe, read-only)** or **T2 (reversible, dry-run-default)**. **Structural** changes — partition `SPLIT`/`MERGE`/`DROP`/`EXCHANGE`, index `DROP`/`UNUSABLE`/ partition-level rebuild, and large segment/table moves (online redefinition / shrink) — are **T3** and live only in `references/runbooks.md`; they print commands for a human and never self-execute. In-DB tasks run their SQL through the SQLcl MCP saved connection `dba_ai_conn` ("sqlcl-mcp" routing) via the `connect_db` / `Connect-Db` helper. The single host/OS task (ADR file purge) cannot go through SQLcl MCP (host commands are out of scope for that server, restrict level 4) so it runs as a generated `.sh`/`.ps1` ("script" routing, a candidate to later front the guarded `oracle-dba-ops` MCP). ## Scope & risk map | Task | Level | Tier | Mechanism (script / sql / runbook path) | Idempotent? | |------|-------|------|------------------------------------------|-------------| | Recompile invalid objects (utlrp / UTL_RECOMP) | L1 | T2 | `scripts/recompile_invalid.sh` / `.ps1` -> `s