oracle-dba-multitenant-cdb-pdblisted

USE THIS SKILL WHENEVER the user mentions multitenant, container database / CDB, pluggable database / PDB, CDB$ROOT, PDB$SEED, open/close a PDB, PDB open mode (READ WRITE / READ ONLY / MOUNTED / RESTRICTED), SAVE STATE / DISCARD STATE, PDB clone or snapshot copy, PDB unplug / plug / manifest (.xml/.pdb), PDB relocation, CDB resource plan / inter-PDB shares, lockdown profile / PDB_LOCKDOWN, application container / application root / application PDB, PDB_PLUG_IN_VIOLATIONS, or the related views V$PDBS / CDB_PDBS / DBA_PDB_SAVED_STATES — EVEN IF they do not name the specific task. Covers PDB status monitoring, PDB open/close, save/discard state, local clone & snapshot copy, unplug-to-manifest, CDB-level Resource Manager configuration, lockdown profile rules + assignment, and the plan-only Tier-3 runbooks for PDB relocation, application-container management, plug, drop, and lockdown-profile drop. Follows the oracle-dba-common contracts: SQLcl MCP saved connection dba_ai_conn, Oracle Wallet secrets (never plaintex
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · DevOps & Infrastructure · score 62

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

# Oracle DBA - Multitenant (CDB / PDB) Day-to-day operation of Oracle multitenant containers for **19c and 23ai** (EE; single-instance and Data Guard; on-prem): PDB status monitoring, open/close, save state, local clone / snapshot copy, unplug-to-manifest, CDB-level Resource Manager, and lockdown profiles. Everything self-executing is **T1 (observe)** or **T2 (reversible, dry-run-default)**. The **structural / cross-CDB** operations — **PDB relocation, application-container lifecycle, plug-from-manifest, drop, and lockdown-profile drop — are T3** and live only in `references/runbooks.md`; they print exact commands for a human and never self-execute. In-DB SQL/PL-SQL runs through the **SQLcl MCP** saved connection **`dba_ai_conn`** (wallet-backed). Host-level steps (none are required by the T1/T2 scripts here beyond invoking SQLcl) and all T3 structural DDL are operator-driven. **Never SYS/SYSTEM** except inside a T3 runbook that explicitly states `AS SYSDBA`, supplied interactively. ## Scope & risk map | Task | Level | Tier | Mechanism (script / sql / runbook path) | Idempotent? | |------|-------|------|------------------------------------------|-------------| | PDB status monitoring | L1 | T1 | `scripts/checks/check_pdb_status.sh` / `.ps1` + `sql/pdb_status.sql` | yes — read-only (emits KEYVAL metrics + RESTRICTED / violation findings, never mutates) | | PDB open / close | L2 | T2 | `scripts/pdb_open_close.sh` / `.ps1` + `sql/pdb_open_close.sql` | yes — already in target