Oracle GoldenGate | 2026 migration

GoldenGate 19c and 21c: end of support. What to do next?

Premier Support for Oracle GoldenGate 19c and 21c ends in April 2026. For organizations using these versions for data replication and real-time integration, it is time to assess risk, choose a migration strategy, and move toward a modern architecture.

Support, security, migration, and Microservices Architecture

End of support is not just a date on a calendar

Systems will not stop working immediately after support ends, but security risk, compliance exposure, integration limits, and failure risk in critical data flows grow over time.

Planning

Why start the migration now

GoldenGate migrations in enterprise environments require time for dependency analysis, replication testing, failover validation, and cutover planning. Starting early reduces operational pressure and lets the migration align with a broader cloud or modernization strategy.

01

avoid last-minute project risk

02

test replication consistency and rollback scenarios

03

maintain zero or minimal downtime

Options

GoldenGate migration paths

The strategy depends on the current architecture, SLA requirements, and risk tolerance. In complex environments, side-by-side migration supports testing, preserves rollback options, and reduces risk during cutover to the new environment.

01

Side-by-side migration

Recommended for high-availability and mission-critical environments. It lets teams prepare a new environment in parallel, validate topologies, and reduce cutover risk.

02

OCI or hybrid migration

A strong path when the GoldenGate upgrade is combined with database, cloud, monitoring, or disaster recovery modernization.

Execution

How to prepare a safe upgrade

A successful migration starts with a structured process: environment assessment, strategy selection, testing, and controlled execution. At Goldenore, we combine architecture, administration, and critical-systems operations perspectives.

  1. 01

    Environment assessment

    Analysis of GoldenGate configuration, dependencies, topology, and operational risks.

  2. 02

    Migration strategy

    Selection of an in-place, side-by-side, cloud, or hybrid path.

  3. 03

    Testing and validation

    Validation of data consistency, performance, latency, and failover readiness.

  4. 04

    Migration

    Delivery with minimal disruption to business operations.

Modernization

Moving beyond Classic Architecture

Oracle GoldenGate 19c was the final release supporting the Classic Architecture model. Moving to Microservices Architecture is not only about supportability; it is also an opportunity to improve automation, security, monitoring, and replication scalability.

REST APIs and automation

Documented APIs support Infrastructure as Code, orchestration, and standardized operations.

Modern web interface

A browser-based console simplifies monitoring, diagnostics, configuration, and operational control.

Better observability

Performance Metrics Service provides visibility into lag, throughput, checkpoints, and process health.

Security and cloud readiness

HTTPS, TLS, OAuth 2.0, certificate-based communication, and patterns suitable for hybrid environments.

Classic Architecture

Classic Architecture versus Microservices

Classic Architecture

  • GGSCI-centric management
  • separate Data Pumps and Collectors
  • limited automation
  • basic monitoring
  • traditional deployment model

Microservices Architecture

  • web UI and REST APIs
  • centralized Distribution and Receiver Services
  • API-first automation
  • centralized metrics and operational visibility
  • cloud-ready architecture

FAQ - Oracle GoldenGate end of support

When does Oracle GoldenGate 19c and 21c support end?

Premier Support ends in April 2026.

Can GoldenGate be used after support ends?

Technically yes, but it involves significantly greater security, compliance, and operational stability risk.

How long does a GoldenGate migration take?

Depending on complexity: from a few weeks to several months.

What is the safest strategy?

For most enterprise environments, side-by-side migration is the safest approach.