oracle-dba-enterprise-manager-oem-toolinglisted

USE THIS SKILL WHENEVER the user mentions Oracle Enterprise Manager (OEM), Cloud Control, EM 13.5 / EM 24ai, the OMS (Oracle Management Service), the Management Repository / SYSMAN schema, emcli or emctl, a management agent, OEM targets, blackouts, monitoring templates, metric/threshold templates, OEM repository administration, or an OEM / Cloud Control upgrade — EVEN IF they do not name the specific task. Covers OEM target/agent management (add/sync/relocate/remove), blackout management (create/stop), monitoring template management (export/create/apply/delete), repository administration (status, SYSMAN stats gather, pause/resume repository collection jobs), and the plan-only Tier-3 OEM/Cloud Control upgrade + repository DR + destructive-repo runbooks. Follows the oracle-dba-common contracts: SQLcl MCP saved connection dba_ai_conn, Oracle Wallet secrets (never plaintext), --dry-run defaults on T2, and tier gating (max self-execute = T2; the OEM upgrade and destructive repository ops are T3).
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · DevOps & Infrastructure · score 62

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

# Oracle DBA - Enterprise Manager (OEM) / Tooling OEM (Cloud Control) target/agent/blackout/template management and repository administration via **emcli/emctl** (host-boundary tools), read-only repository reporting via **SQLcl `dba_ai_conn`**, and the plan-only **Tier-3** OEM/Cloud Control upgrade + repository DR runbooks. Targets EM **Cloud Control 13.5** (on a **19c** repository) and **EM 24ai** (on a **23ai** repository), EE, single-instance and Data Guard, on-prem. Everything self-executing is **T1 (observe)** or **T2 (reversible, dry-run-default)**. The **OEM upgrade**, **repository DB upgrade**, **OMS/repository DR**, and **destructive repository administration** are **T3** and live only in `references/runbooks.md` — they print commands for a human and never self-execute. > **Routing.** `emcli`/`emctl` are HOST-boundary tools and are **not** reachable > through the SQLcl MCP server (restrict level 4 = no host commands). They run as > generated `.sh`/`.ps1` scripts (candidates to later front a guarded > `oracle-dba-ops` MCP). In-DB reads/maintenance (repository health, SYSMAN stats, > scheduler-job pause/resume) run through SQLcl MCP `run-sql` on **`dba_ai_conn`** > (`sql/*.sql` + supported SYSMAN package calls). T3 -> runbook + approval token. ## Scope & risk map | Task | Level | Tier | Mechanism (script / sql / runbook path) | Idempotent? | |------|-------|------|------------------------------------------|-------------| | OEM target management — list | L2 | T1 | `