Provides reference-based operational guidance for Oracle Data Guard and SQLcl DG diagnostics.
- What it does
- This skill routes Oracle Data Guard questions to bundled reference documents covering SQLcl DG commands, Broker fixed views, FSFO and observer state, transport and apply lag, ASYNC/SYNC/FASTSYNC performance, redo apply tuning, SIRA/MIRA, and runnable diagnostic SQL. It identifies the topology and concern, selects the smallest relevant reference, and returns safe diagnostic steps that separate facts from hypotheses. It also flags commands that change database settings or recovery configuration and notes rollback steps where available.
- When to use it
- Use it when a user asks about SQLcl DG commands, Data Guard Broker configuration or fixed views, FSFO or observer state, transport or apply lag, ASYNC/SYNC/FASTSYNC performance, redo apply tuning, SIRA/MIRA, or Data Guard diagnostic SQL. It is intended for triage and health-check guidance rather than direct database changes.
- Requirements
- No scripts are shipped; it is instructions and reference documents only. It assumes the agent can read the bundled reference files. It does not require a live database connection, but it will not claim to have inspected a live database, Broker configuration, or observer unless the user provides output or a connected tool returns it.
Oracle Data Guard
Use the bundled references as the source of truth for SQLcl MCP Data Guard guidance. Read only the smallest relevant reference. Do not claim to have inspected a live database, Broker configuration, or observer unless the user provides output or a connected tool returns it.
Route the request
Response workflow
- Identify the topology and concern: Broker versus SQLcl, transport versus apply, and ASYNC versus SYNC/FASTSYNC where relevant.
- Read the selected reference. Read
09_SQL_QUERY_COOKBOOK.md only when executable SQL directly helps.
- State the evidence needed, provide safe diagnostic steps, and distinguish facts from hypotheses.
- Treat example timestamps as placeholders; ask for the actual incident window when it affects a query.
- When both transport and apply lag are zero, frame guidance as a health check, baseline, configuration review, or commit-latency investigation rather than a lag incident.
Safety
Prefer observation before change. Clearly label commands that change database settings, enable tracing, or alter recovery configuration, and include the corresponding rollback/disable step when the reference provides one.
