Oracle GoldenGate 12c: Fundamentals for Oracle Ed 2 — Lesson 2: Capture, Trail Files, and Data Pump Configuration

Technical Scope

• integrated and classic capture concepts, registration, and start position
• local trails, rollover, sequence numbers, retention, and disk monitoring
• Data Pump routing, compression concepts, remote trails, and network interruption
• process creation, parameter validation, controlled start, and captured-change proof

Instructor Demonstration

The instructor will configure and verify integrated and classic capture concepts, registration, and start position in the context of a unidirectional Oracle replication solution established with verifiable checkpoints, consistency, and recoverability. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering local trails, rollover, sequence numbers, retention, and disk monitoring and Data Pump routing, compression concepts, remote trails, and network interruption, then introduce a realistic exception involving process creation, parameter validation, controlled start, and captured-change proof. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for Capture, Trail Files, and Data Pump Configuration requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across integrated and classic capture concepts, registration, and start position, local trails, rollover, sequence numbers, retention, and disk monitoring, Data Pump routing, compression concepts, remote trails, and network interruption; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for Capture, Trail Files, and Data Pump Configuration with a reusable implementation record or runbook.