Oracle GoldenGate 12c: Fundamentals for Oracle Ed 2 — Lesson 3: Replicat, Mapping, Instantiation, and Data Validation

Technical Scope

• integrated and coordinated apply concepts, checkpoints, and target prerequisites
• TABLE and MAP statements, schema mapping, filters, and column mapping
• initial load and instantiation coordination with change synchronization
• row-count, checksum, transaction, key, and application-level reconciliation

Instructor Demonstration

The instructor will analyze and reconcile integrated and coordinated apply concepts, checkpoints, and target prerequisites 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 TABLE and MAP statements, schema mapping, filters, and column mapping and initial load and instantiation coordination with change synchronization, then introduce a realistic exception involving row-count, checksum, transaction, key, and application-level reconciliation. 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 Replicat, Mapping, Instantiation, and Data Validation 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 coordinated apply concepts, checkpoints, and target prerequisites, TABLE and MAP statements, schema mapping, filters, and column mapping, initial load and instantiation coordination with change synchronization; 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 Replicat, Mapping, Instantiation, and Data Validation with a reusable implementation record or runbook.