oracle-dba-goldengate-replicationlisted

USE THIS for ANY Oracle GoldenGate / logical-replication / materialized-view replication request - EVEN IF the user does not name a task or tool. Covers Extract / Replicat / Distribution-path / Manager status, START/STOP/RESTART, replication LAG (Integrated apply latency, capture latency, heartbeat lag), the automatic heartbeat table (ADD HEARTBEATTABLE / GG_LAG / GGS_HEARTBEAT), trail-file inventory + purge/retention, initial-load (instantiation SCN, HANDLECOLLISIONS, AFTERCSN, expdp/impdp parfiles), supplemental-logging readiness, Conflict Detection & Resolution (CDR / COMPARECOLS / RESOLVECONFLICT), logical-replication troubleshooting (missing rows, lag, ABENDED process), and materialized-view replication refresh/staleness. Trigger on symptoms too: "replication is behind / lagging", "rows not arriving on target", "Extract abended", "Replicat stopped", "OGG-xxxxx", "ggsci / adminclient", "trail files filling the disk", "heartbeat stale", "MV won't refresh", "ORA-26xxx" (LogMiner / Streams / GoldenGate apply
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · DevOps & Infrastructure · score 62

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

# Oracle DBA - GoldenGate / Replication In-scope replication mechanisms: **Oracle GoldenGate** (Integrated Extract / Integrated Replicat / Distribution path, Classic `ggsci` or Microservices `adminclient`), **logical replication / Logical Standby** signals, and **materialized-view replication** (MVs over DB links, scheduled or on-demand refresh). Oracle DB 19c & 23ai, EE, single_instance / Data Guard, on-prem. Host-side GoldenGate commands (`ggsci` / `adminclient`: INFO ALL, LAG, STATS, START, STOP, PURGEOLDEXTRACTS) CANNOT go through the SQLcl MCP server (restrict level 4 = no host commands). They run from the `scripts/*` host wrappers, which authenticate to GoldenGate via the credential store (USERIDALIAS / wallet) - never a password on the CLI. All in-database work goes through the wallet-backed SQLcl saved connection `dba_ai_conn`. ## Scope & risk map Mechanism legend: `sqlcl-mcp:sql/...` = in-DB query via dba_ai_conn; `script:scripts/...` = host wrapper (ggsci/adminclient + OS files); `runbook:references/runbooks.md#...` = print-only operator runbook (T3). | Task | Level | Tier | Mechanism | Idempotent? | |------|-------|------|-----------|-------------| | Process status (Extract/Replicat/path/Manager) | OBSERVE | T1 | script:scripts/process_monitor.sh\|.ps1 + sqlcl-mcp:sql/process_status.sql | yes (read-only) | | Replication lag (host LAG + in-DB latency) | OBSERVE | T1 | script:scripts/lag_monitor.sh\|.ps1 + sqlcl-mcp:sql/replication_lag.sql | yes (read-only) | |