oracle-dba-capacity-planning-reportinglisted

USE THIS SKILL WHENEVER the user asks about capacity planning, capacity/sizing reviews, growth trend analysis or forecasting, "days to full" / "when will this tablespace fill", space-usage trend reports, database/instance status reports (daily/weekly health snapshot), resource-utilization reports (CPU / memory / IO / sessions / AAS), SLA / uptime / availability reporting, chargeback or showback / cost-allocation reporting, or a capacity-planning recommendation — EVEN IF they do not name the specific report. Covers the read-only reporting family (status, space-trend, resource, SLA, growth forecast, capacity recommendation, chargeback) plus the single additive daily space-metrics capture that feeds long-term forecasting. Follows the oracle-dba-common contracts: SQLcl MCP saved connection dba_ai_conn, Oracle Wallet secrets (never plaintext), --dry-run default on the one T2 mechanism, and tier gating (max self-execute = T2; all PROVISIONING and repo/structural DDL is T3 runbook).
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · Data & Documents · score 62

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

# Oracle DBA - Capacity Planning & Reporting Read-only operational + capacity reporting (status, space, resource, SLA, growth forecast, capacity recommendation, chargeback) and the one additive metrics-capture job that gives forecasting long-term history — for Oracle 19c and 23ai (EE; single-instance and Data Guard; on-prem). Everything self-executing is **T1 (observe)** except the daily space-snapshot capture, which is **T2 (reversible, additive, dry-run-default)**. **All ACTING on a recommendation — provisioning storage/CPU/memory/sessions, and creating the optional repository tables (DDL) — is T3** and lives only in `references/runbooks.md`: it prints commands for a human and never self-executes. The reports recommend; humans (with an approval token) provision. "When in doubt, runbook." ## Scope & risk map Covers every task in section 18 ("Capacity Planning & Reporting") of the `oracle_dba_task_level_map.md`, plus the supporting capture job and the T3 repo / provisioning runbooks the L3 reports point at. | Task | Level | Tier | Mechanism (sql / script / runbook path) | Idempotent? | |------|-------|------|------------------------------------------|-------------| | Daily / weekly status report | L1 | T1 | `scripts/checks/run_report.sh --report status` / `.ps1 -Report status` -> `sql/status_report.sql` | yes — read-only (emits KEYVAL metrics + threshold findings, never mutates) | | Space usage trend report | L2 | T1 | `scripts/checks/run_report.sh --report space-trend` /