Oracle GoldenGate 12c: Troubleshooting and Tuning Ed 1 — Lesson 1: Diagnostic Method, Architecture, Logs, and Checkpoints

Technical Scope

• capture, pump, trail, collector, and delivery
• GGSCI status, lag, reports, and commands
• ggserr.log, reports, and discard files
• checkpoints, positions, and incident timelines

Instructor Demonstration

Demonstrate capture, pump, trail, collector, and delivery inside a replication system deliberately degraded at different data-path stages, then capture the exact configuration, command, transaction, report, or code evidence that proves the result.

Applied Workshop

Implement a controlled workshop covering GGSCI status, lag, reports, and commands and ggserr.log, reports, and discard files, then test a failure or exception involving checkpoints, positions, and incident timelines.

1. Confirm environment, identity, data, dependencies, and expected result.
2. Complete the product-specific implementation or analysis.
3. Capture commands, configuration, output, logs, transactions, or reports.
4. Explain the operational, security, performance, or business trade-off.

Validation Standard

The Diagnostic Method, Architecture, Logs, and Checkpoints result must be reproducible, traceable to approved inputs, and consistent with the expected Oracle product behavior.

• The intended target and ownership are verified.
• The result is supported by reproducible evidence.
• Security, performance, reliability, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance.

Failure Analysis

Diagnose issues in capture, pump, trail, collector, and delivery, GGSCI status, lag, reports, and commands, ggserr.log, reports, and discard files, or checkpoints, positions, and incident timelines without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.