The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

GoldenGate 19c Now Certified with EBS 12.2 and EBS 12.1 Using DB 19c

Elke Phelps, and contributing author: Allison Sparshott

We are pleased to announce the certification of Oracle GoldenGate 19c (19.1) with Oracle E-Business Suite 12.2.3 and later and Oracle E-Business Suite 12.1.3 using Oracle Database 19c (19.7 or later). 

Oracle GoldenGate provides real-time capture, transformation, routing, and delivery of database transactions across heterogeneous systems. The certified configuration of EBS with GoldenGate 19c provides a unidirectional method of replicating the Oracle E-Business Suite (source) database to a remote (target) Oracle database, which can be used for operational reporting. 

The configuration is achieved using Integrated Extract and Integrated Replicat using the Oracle GoldenGate Classic Architecture. See the following document for details:

"How" But Not "What"

The document above describes how to use GoldenGate to replicate data from the E-Business Suite to another system. It doesn't provide any guidance about which database objects to replicate.

The E-Business Suite data model is vast, as you'd expect of something that has supports the integrated functioning of over 200 functional product modules. GoldenGate is a development tool, and like all development tools, requires an expert-level understanding of the E-Business Suite data model for successful use. Here's a good EBS data model resource:

Only Unidirectional Replication for EBS

GoldenGate includes the ability to provide data replication in both directions. In some generic scenarios, you can choose to make alterations to replicated data on the external instance and have those changes updated back in the source database.

Bidirectional replication is not permitted for E-Business Suite environments. You can use GoldenGate to replicate EBS data to an external database, but you cannot move that altered data back into the EBS database. GoldenGate's ability to read data in EBS databases is certified, but it must not be used to write to EBS databases.

Not Certified for EBS Platform Migrations, Database Upgrades, or Disaster Recovery

GoldenGate is not certified with EBS for the following:

  • Upgrading E-Business Suite databases from one version to another
  • Migrating E-Business Suite databases from one operating system platform to another
  • Replicating E-Business Suite databases for disaster recovery purposes

Why not? Tables without a primary key or unique index are fully supported by Oracle GoldenGate, but could add extra volume to redo log generation as all columns must be logged as well. EBS has over 10,000 tables without primary keys. If update or delete operations are performed on these tables it may negatively impact performance. In addition to this, GoldenGate does not support all data types that are used by EBS. 

Oracle does not currently have any plans to produce a certified or automated method of using GoldenGate for EBS database upgrades, platform migrations or the creation of disaster recovery environments. You should use our certified processes for EBS database upgrades, platform migrations and business continuity. 

Replication to a Non-Editioned Target Database

EBS 12.2's Online Patching architecture has significant implications for data replication solutions implemented using Oracle GoldenGate. The referenced MOS note describes how to set up a unidirectional configuration of Oracle GoldenGate replication from an Oracle E-Business Suite Release 12.2 source database to a non-editioned target database.

Using GoldenGate with EBS 12.2 environments is significantly different from previous EBS releases.  If you are upgrading your GoldenGate + EBS 12.1 environment to EBS 12.2, you must plan carefully for the new integration steps detailed in the document.


Related Articles

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.