oracle-dba-networking-connectivitylisted
Install: claude install-skill Shreyas70773/oracle-dba-agentic-skills
# Oracle DBA - Networking & Connectivity
Oracle Net stack management for Oracle 19c and 23ai (EE; single_instance and Data
Guard; on-prem): the listener lifecycle, `listener.ora` / `tnsnames.ora`
maintenance, static and dynamic service registration, connectivity testing, and
layered ORA-12xxx connection-error diagnosis. Everything self-executing is
**T1 (observe)** or **T2 (reversible, dry-run-default)**. **Connection Manager
(CMAN) setup** and **deep network / SDU / buffer tuning** are **T3** and live only
in `references/runbooks.md` — they print commands for a human and never self-execute.
In-DB SQL (service registration, connection diagnostics) runs through the SQLcl MCP
saved connection **`dba_ai_conn`** ("sqlcl-mcp"). Host operations (`lsnrctl`,
`srvctl`, `tnsping`, editing `*.ora`) cannot go through SQLcl MCP (restrict level 4 =
no host commands) and ship as behaviour-equivalent `.sh` / `.ps1` **scripts** (to
later front a guarded `oracle-dba-ops` MCP).
## Scope & risk map
| Task | Level | Tier | Mechanism (script / sql / runbook path) | Idempotent? |
|------|-------|------|------------------------------------------|-------------|
| Listener restart / reload / start / stop | L1 | T2 | `scripts/listener_restart.sh` / `.ps1` (`restart\|reload\|start\|stop`) | yes — `start` already-up -> noop; `restart` converges to "up"; `stop` already-down -> noop |
| Listener status | L1 | T1 | `scripts/listener_restart.sh status` / `.ps1 status` | yes — read-only (`lsnrctl`/`srvctl