Known issues related to GoldenGate processes
Explore known issues related to GoldenGate processes and how to work around them.
GoldenGate capture for MySQL InnoDB Cluster
There is an known issue that can stop Oracle GoldenGate capture when capturing from a MySQL InnoDB Cluster.
GoldenGate currently supports standard GTIDs, but not tagged GTIDs. MySQL Shell 9.5 and later automatically adds a mysqlsh tag to certain administrative transactions when used with MySQL Server 8.3 or later. If GoldenGate encounters these tagged transactions, the GTID-based Extract can fail.
This affects GTID-based capture for MySQL InnoDB Cluster. Standalone MySQL capture using log number and offset is not affected.
How to prevent this issue
Take action before upgrading the cluster: use MySQL Shell 9.4 or earlier for the cluster upgrade. Do not use MySQL Shell 9.5 or later for cluster operations while using a GoldenGate GTID-based Extract.
Choosing the Shell version after starting the upgrade is too late. If MySQL Shell 9.5 or later adds tagged GTIDs, the Extract can fail; recovery requires a complete resynchronization.
Workaround
You can upgrade the MySQL Server to version 8.3 or later, but use MySQL Shell 9.4 or earlier to install, configure, or upgrade the InnoDB Cluster. Do this before configuring the GoldenGate Extract.
Revoking the TRANSACTION_GTID_TAG privilege is not a valid workaround and can cause MySQL Shell operations, such as adding or removing an instance, to fail.
Security note: MySQL Shell 9.4 contains vulnerabilities addressed in later releases. Review the security implications with your security team before using this temporary workaround.
Apache Iceberg replication using AWS Glue Data Catalog and Amazon S3 buckets
In Apache Iceberg replications using AWS Glue Data Catalog and AWS S3 buckets, you may encounter the following error:
Cannot find constructor for interface org.apache.iceberg.catalog.Catalog
Missing org.apache.iceberg.aws.glue.GlueCatalog [java.lang.NoClassDefFoundError: software/amazon/awssdk/services/glue/model/AlreadyExistsException]
Workaround: Update the gg.classpath as follows:
gg.classpath=$THIRD_PARTY_DIR/iceberg/*:$THIRD_PARTY_DIR/s3/*:$THIRD_PARTY_DIR/hadoop/*::$THIRD_PARTY_DIR/s3/*:$THIRD_PARTY_DIR/glue/*
TLS Security Protocol issue
MongoDB, DocumentDB, and Oracle JSON Collection TLS Security Protocol
If the MongoDB Replicat, DocumentDB Replicat, or Oracle JSON Collection connection fails with the following error in the Report file:
Error: Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Workaround: Add the following property to your Properties file, update <connection_ocid> with your connection OCID and keep the rest as is.
jvm.bootoptions=-Djavax.net.ssl.trustStore=/u02/connections/<connection_ocid>/truststore.pkcs12 -Djavax.net.ssl.trustStorePassword=Welcome123
Bug 37518857: OGGDAA GGS Snowflake Streaming Replicat error
Snowflake Streaming Handler fails with: Exception: java.lang.StackOverflowError thrown from the UncaughtExceptionHandler in thread "process reaper"
Workaround: Add the following to your Replicat Properties file:
jvm.bootoptions= -Djdk.lang.processReaperUseDefaultStackSize=true
OCI GoldenGate deployment console cannot display custom/non-default named Discard file
Discard files, by default, follow the naming convention <process-name>.dsc. You can see all discard files in the OCI GoldenGate deployment console, unless you renamed them. The deployment console doesn’t display custom named discard files.
Workaround: Use the Collect diagnostics tool on the deployment details page to access your discard files.
Replicats fail when using Trail file from MongoDB Extract with BINARY_JSON_FORMAT
When a Replicat uses a Trail file generated from a MongoDB Extract with BINARY_JSON_FORMAT in the Extract parameter file, the Replicat fails with the following error:
ERROR 2023-08-04 17:13:13.000421 [main] - Unable to decode column 0 : Input length = 1
java.nio.charset.MalformedInputException: Input length = 1 at
java.nio.charset.CoderResult.throwException(CoderResult.java:281) ~[?:1.8.0_311]at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:816) ~[?:1.8.0_311] at
oracle.goldengate.datasource.UserExitDataSource.createColumnValue(UserExitDataSource.java:1106)
[ggdbutil-21.9.0.0.3.001.jar:21.9.0.0.3.001] Exception in thread "main"
oracle.goldengate.util.GGException: Unable to decode column 0 : Input length = 1 at
oracle.goldengate.datasource.UserExitDataSource.createColumnValue(UserExitDataSource.java:1203)
Workaround: When BINARY_JSON_FORMAT is removed from the Extract parameters, the Replicat runs successfully and documents are represented in Extended JSON format.
Remote change data capture Extracts fail for GTID enabled databases
When you create a Change Data Capture Extract process with the Remote option enabled for a MySQL database that uses global transaction identifiers (GTIDs), the Extract process fails and the following error is reported:
ERROR OGG-25192 Trail file '<trail name>' is remote. Only local trail allowed for this extract.
Workaround: On the Parameter file screen of the Change Data Capture Extract, remove the line, TRANLOGOPTIONS ALTLOGDEST REMOTE.
For more information, see Using Oracle GoldenGate for MySQL.
Distribution Paths: Add the root certificate to Certificate Management or your client wallet
To send data to or pull data from OCI GoldenGate, you must create a Distribution Server Path or a target initiated path on the Receiver Server in your on-premises or Marketplace Oracle GoldenGate, respectively. You must also add the OCI GoldenGate root certificate or self-signed certificate to your Oracle GoldenGate Certificate Management (Oracle GoldenGate 21c or higher) or client wallet (Oracle GoldenGate 19c). This creates a trusted connection between your Oracle GoldenGate and OCI GoldenGate deployments. Only WebSocket Secure (WSS) protocol is supported for Distribution and Receiver Server Paths between Oracle GoldenGate and OCI GoldenGate.
A change in the OCI GoldenGate root certificate will cause the Distribution Server Path or a target initiated path on the Receiver Server in your on-premises or Marketplace Oracle GoldenGate to fail and produce the following error:
ERROR OGG-10390 Oracle GoldenGate Receiver Service: Generic error -1 noticed for endpoint
wss://<deployment URL>:443/services/v2/sources?trail=<trail name>. Error description - SSL
connection unexpectedly closed.
Workaround: To fix this issue, update the certificate in the client wallet or Service Manager’s Certificate Management screen to use the OCI GoldenGate Deployment Console root certificate. In some cases, when the OCI GoldenGate deployment’s certificate is not signed directly by the root certificate but by intermediate one(s) for example, it might be necessary to also add the intermediate CA certificate(s).
Learn more:
-
For Oracle GoldenGate 19c users, see Creating a Distribution Server Path User Certificate.
-
For users of Oracle GoldenGate 21c or higher, see Create a Trusted Connection Between Oracle GoldenGate and OCI GoldenGate.
Only Digest Authentication is currently supported
Oracle Cloud Infrastructure GoldenGate doesn’t currently support certificate-based authentication when you use Oracle Cloud Infrastructure GoldenGate as the Distribution Path target.
Workaround: None.