Oracle GoldenGate is the enterprise-grade heterogeneous data replication and change data capture (CDC) platform used by financial institutions for real-time data distribution, by retailers for point-of-sale to central data warehouse synchronisation, by manufacturers for ERP-to-data-lake integration, and by telecoms operators for mediation and BSS/OSS data replication across geographically distributed nodes. GoldenGate's architecture — log-based change data capture using Extract processes, Pump processes for network transmission, and Replicat processes for target apply — operates at a level of performance and latency that software-based ETL tools cannot match for high-transaction-rate Oracle Database environments. The investment in GoldenGate configuration — trail file management, conflict resolution rules, column mapping transforms, filtering logic, and DDL replication governance — represents years of operational tuning that is specific to the source-target topology and cannot be migrated to a new replication platform without a full re-architecture exercise.
Oracle's account teams are systematically repositioning Oracle GoldenGate Classic Architecture (11g through 19c) as legacy and pushing two migration vectors: Oracle GoldenGate Microservices Architecture (21c) — Oracle's container-based, REST-administered redesign — and Oracle GoldenGate on OCI (GoldenGate Cloud Service). The migration narrative is familiar: features investment claims, cloud-native capability arguments, and renewal pricing that makes the gap between Classic and Microservices look smaller than the architecture migration actually is. Third-party support on Oracle GoldenGate 11g through 19c cuts annual support costs by 50–65%, removes Oracle's migration leverage, and preserves your proven replication architecture while you evaluate any evolution on your own timeline.
Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle GoldenGate 11g (11.2.1) entered Sustaining Support in January 2021. Oracle GoldenGate 12c (12.1 and 12.2) entered Sustaining Support in January 2022 and October 2022 respectively. Oracle GoldenGate 12.3 and 18c are also in Sustaining Support as of 2022–2023. Oracle GoldenGate 19c (19.1) remains in Premier Support through January 2025 and Extended Support through January 2028. For any organisation on GoldenGate 11g through 12.3, TPS is immediately relevant. See our Oracle GoldenGate overview and Oracle TPS complete guide for full lifecycle context.
GoldenGate Microservices Architecture — The Re-Architecture Tax Oracle Isn't Disclosing
Oracle GoldenGate Microservices Architecture (MA) — introduced as the strategic replacement for GoldenGate Classic Architecture from version 12.3 onwards and now the only development path from Oracle — is not an upgrade of GoldenGate Classic. It is a fundamentally redesigned product with a different administrative model (REST API and browser-based Service Manager replacing GGSCI command-line), a different process deployment model (deployments and services replacing Classic instance directories), different trail file management, and different configuration file structures. Migrating from Classic Architecture to Microservices Architecture requires: redesigning all Extract, Pump, and Replicat process configurations for the MA deployment model; migrating all parameter files to the new syntax and directory structure; rebuilding all monitoring and alerting integrations (Oracle Management Cloud, custom GGSCI monitoring scripts, custom trail file monitoring); re-testing conflict resolution and filtering logic under the MA apply model; and re-validating all DDL replication configurations — particularly for heterogeneous targets (SQL Server, PostgreSQL, MySQL, Kafka, BigQuery) where the MA replicat behaviour differs from Classic in several edge cases.
For a large financial services institution with 30–80 GoldenGate replication groups, 150–400 Extract/Replicat process pairs, and heterogeneous target topology, system integrator estimates for a Classic-to-Microservices migration range from £450K–£2.1M with a 9–18 month delivery timeline. Oracle GoldenGate on OCI (GoldenGate Cloud Service) adds cloud network egress costs, OCI compute costs (GoldenGate Cloud Service runs on OCI VM.Standard3 or higher), and a fundamental shift in network topology for on-premise source databases — the OCI Extract process must reach on-premise Oracle Database redo logs, which for air-gapped or private network environments requires Direct Connect/FastConnect or complex tunnel configurations. GoVendorFree TPS on the existing Classic Architecture environment eliminates all of this.
Oracle GoldenGate Version Matrix — TPS Eligibility
| Version | Architecture | Oracle Support Status | TPS Available |
|---|---|---|---|
| GoldenGate 11g (11.2.1) | Classic — GGSCI, trail files, Extract/Replicat | Sustaining Support only | ✓ Yes — large TPS cohort |
| GoldenGate 12c R1 (12.1.2) | Classic — GUI Monitor introduced | Sustaining Support only | ✓ Yes — ideal TPS candidate |
| GoldenGate 12c R2 (12.2.0) | Classic — Conflict Detection & Resolution (CDR) enhanced | Sustaining Support only | ✓ Yes — TPS recommended |
| GoldenGate 12.3 | Classic + early Microservices — dual-mode release | Sustaining Support only | ✓ Yes |
| GoldenGate 18c (18.1) | Classic — last pure Classic release | Sustaining Support only | ✓ Yes — common TPS candidate |
| GoldenGate 19c (19.1) | Classic + Microservices — Extended Support phase | Extended Support (ends Jan 2028) | ✓ Yes — proactive TPS candidate |
| GoldenGate 21c (21.x) | Microservices Architecture — REST-managed, MA only | Premier Support | ✓ Yes |
GoVendorFree TPS Coverage for Oracle GoldenGate
GoVendorFree's Oracle TPS covers the complete GoldenGate Classic Architecture stack — Extract, Pump, Replicat, Manager, and the underlying Oracle Database and OS integration. Coverage includes:
- Core GoldenGate Processes: Manager process stability (port management, trail file purging, process monitoring); Extract process stability (integrated vs. classic capture mode; LogMiner dependency advisory; supplemental logging configuration); Pump process stability (data pump trail file transmission, encryption, compression); Replicat process stability (integrated Replicat for Oracle targets; parallel Replicat for high-throughput apply; coordinated Replicat for ordered apply)
- Change Data Capture: Oracle LogMiner supplemental logging configuration and advisory (minimal, primary key, ALL columns logging); supplemental log data management for DDL capture; Archive Log retention advisory for Extract lag management; Online Redo Log switch capture advisory; Integrated Extract capture mode (GoldenGate 11gR2+ with Oracle DB 11.2.0.3+); TRANLOGOPTIONS MINVALIDRECORDS advisory
- Heterogeneous Replication: Oracle-to-SQL Server Replicat stability (Attunity/OGG SQL Server plugin advisory); Oracle-to-MySQL and Oracle-to-PostgreSQL Replicat advisory; Oracle-to-Kafka trail file-based Replicat advisory; Oracle-to-BigQuery via trail file export advisory; Oracle-to-Hadoop HDFS/Hive advisory; column mapping and transformation (COLMAP, SQLEXEC, user exit functions) stability
- Conflict Detection and Resolution (CDR): CDR rule configuration stability (INSERTROWEXISTS, UPDATEROWEXISTS, DELETEROWNOTFOUND); custom conflict resolution via REPERROR and HANDLECOLLISIONS advisory; timestamp-based CDR (USEMAX, USEMIN) advisory; CDR reporting and exception table management
- DDL Replication: DDL capture configuration (DDL INCLUDE/EXCLUDE MAPPED/UNMAPPED); Oracle DDL trigger management; DDL history table advisory; DDL filtering for heterogeneous targets; DDL replication for multi-tenant (CDB/PDB) Oracle environments
- Security and Encryption: AES trail file encryption configuration; Oracle Wallet integration for GoldenGate credential store; SSL/TLS for Collector process encryption; GoldenGate user and privilege management advisory; Secure Enclave advisory for GoldenGate 19c+
Financial Services and Retail — GoldenGate TPS Cohort Analysis
Oracle GoldenGate's two dominant TPS cohorts — financial services and retail — each have sector-specific constraints that make migration to GoldenGate Microservices or OCI GoldenGate a multi-year programme rather than an upgrade.
In financial services, Oracle GoldenGate underpins real-time data distribution for core banking (FLEXCUBE-to-reporting-platform, T24-to-regulatory-data-mart, core-to-ODS synchronisation for Basel IV COREP and IFRS 9 ECL reporting), intraday trade data replication for market risk calculation engines, and reference data distribution for securities and instrument master. The regulatory reporting constraint is decisive: Basel IV CRR3 COREP quarterly and daily reporting requires complete, auditable, time-consistent data lineage from core database to regulatory submission. Migrating the GoldenGate replication layer that feeds regulatory reporting marts during an active reporting cycle — while simultaneously re-testing all CDR rules, column mappings, and latency SLAs — is a risk that regulatory reporting function heads consistently refuse to accept. Our financial services practice covers the FCA/PRA data integrity framework for GoldenGate TPS decisions.
In retail, Oracle GoldenGate provides real-time synchronisation between point-of-sale transaction systems, central inventory and stock management databases, and data warehouse/analytics platforms. Peak trading period constraints (Black Friday, Christmas, summer sale) create a firm change freeze that makes any replication architecture migration a Q1/Q2-only window with 6–12 months of pre-migration testing — a timeline that Oracle's renewal pressure rarely accommodates. See our retail industry practice for the GoldenGate TPS framework in peak-trading environments.