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.mdonly 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.
