6 Known Issues and Workarounds
This chapter describes the known issues at the time of release.
Release 26ai (23.26.1.0.6) - March 2026
Bug 38924691: Db2 z/OS - Extract abends with ERROR OGG-01741 unexpected log sequence number encountered
Although the bug has fixed some of the Log Sequence Number out of order issue when Extract reads the log records from Db2 z/OS, there are still some edge cases that will trigger this problem.
Workaround
While we are working on a more comprehensive fix, the workaround is to just restart the Extract, it will sort out the issue and continue to run.
Release 26ai (23.26.1.0.5) - March 2026
Bug 31531059: MySQL - Windows - Deployment creation fails when the Service Manager is installed from a non-MySQL Deployment
When creating a MySQL deployment in Windows, if the Service Manager was created under a non-MySQL deployment, subsequent MySQL deployments for that Service Manager will fail to complete.
Workaround
If creating multiple deployments of Oracle GoldenGate for different databases vendors on a server, and not just MySQL deployments, then create the Service Manager deployment from the MySQL oggca program.
Release 26ai (23.26.1.0.3) - February 2026
Bug 38973035: Generic - Replicat abends with error "Invalid TARGET Wildcard Table Name" when '?' wildcard is used
Replicat abends with an error when using a question mark '?' as a wildcard on Windows.
Workaround
List the full table name in the Replicat parameter file instead of using the question mark (?) wildcard specification.
Bug 38869812: Generic - Register Service Manager has unsupported commands for Windows
When registering Service Manager as a Windows service, the
registerServiceManager.bat script may
return a non-critical message that a command is not recognized as an
internal or external command.
Workaround
You can ignore the non-critical message and on completion of the deployment verify that the Service Manager exists and is running in the Windows service applet. Also, verify that you can log in to Service Manager and deployment.
Bug 38942442: Generic - Extract abends when trail is configured with subfolder using the WebUI
Extract and Replicat abend on Windows when using a subdirectory with the trail file. The auto-generated parameter file gets created with an incorrect forward slash (/) instead of backslash (\) for the path separator.
Workaround
Manually edit the parameter file after its creation, changing
the path separator from forward slash (/) to a backslash (\) such
as, subdir\ex, and then restart the process.
Bug 38270083: Generic - Oracle GoldenGate OUI Installer does not launch on Windows without Visual C++ Redistributable v14
The Oracle GoldenGate OUI installer will not launch if the Microsoft Visual C++ Redistributable v14 package is not installed on the Windows server.
Workaround
To install Oracle GoldenGate on Windows, install the latest Microsoft Visual C++ Redistributable v14 package available at https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-supported-redistributable-version
Release 26ai (23.26.1.0.1) - February 2026
Bug 38910133: Generic - Heartbeat Table Target-only setting cannot be modified after the table is created
When you try to modify a Heartbeat table with Target-only setting, the setting cannot be updated once it is configured. The issue exists on the non-Oracle databases that support the Target Only Heartbeat tables.
Workaround
To configure the Target Only setting with the required values, delete the existing heartbeat tables and add a new table with the required values.
Bug 38828193: Generic - Left navigation menu on the Admin Service page does not automatically display the first Extract or Replicat added
When you add the first Extract or Replicat using the web interface, the left navigation menu of the Admin Service page does not display them automatically, however the subsequently added Extract or Replicat will display automatically on the menu.
Workaround
You must refresh the page once after adding the first Extract or Replicat.
Bug 38963914: MySQL - Unable to alter the Extract to specified LOGNUM and LOGPOS via the web interface
Altering an Extract from the web interface to a specified
LOGNUM and LOGPOS results
in a Begin Now.
Workaround
Use the Admin Client command line utility to alter the
Extract to position the LOGNUM and
LOGPOS.
Bug 38964868: MySQL - Duplicate 'Position in Log' fields when creating Extract via the web interface
When using the the web interface to create an Extract and
selecting LSN in the Begin field, both the
Log Number and Log Bin
fields are labeled incorrectly as ‘Position in Log’.
Workaround
From left to right, the first field represents the
LOGNUM value, and the second field
represents the LOGPOS value and will be honored
that way despite their label. Alternatively, you can create the
Extract via the Admin Client using ADD EXTRACT.
Bug 37098868: Teradata/Timesten - Heartbeat functionality not working correctly on web interface
When you try to manage Heartbeat from the Oracle GoldenGate for Teradata and Timesten web interface, the Heartbeat functionality does not work correctly.
Workaround
To manage the heartbeat use the ADD
HEARTBEATTABLE or DELETE
HEARTBEATTABLE command from the Admin Client.
Release 26ai (23.26.1.0.0) - March 2026
Bug 38974142: Generic - Position in Trail field not editable when altering a Replicat
The Position in Trail field is not editable when altering a Replicat on the web interface.
Workaround
Use the Admin Client command line utility to run the
ALTER REPLICAT command.
Release 23.10.3.25.11- December 2025
Bug 38526643: SQL Server - Extract abends with Error in COLMAP clause
The SQL Server Extract displays error when using the
COLMAP clause in the Extract to perform
target column mappings.
Workaround
Use the COLMAP clause in the Replicat rather than an
Extract to remap from source columns to different target
columns.
Release 23.10.1.25.10- October 2025
Bug 37859560: PostgreSQL - Initial Load extract ExtFile name required 3 characters instead of two
While creating an initial load Extract, Oracle GoldenGate requires 3 characters to be used for filename instead of standard two characters.
Workaround
Provide 3 characters to by-pass the step and then change it manually in the parameter file in the next step.
Release 23.10.0.25.10- October 2025
Bug 38544821: Generic - Register Service Manager as a service/daemon in interactive mode (OUI) throws error- 'cannot stop deployment'
When running OGGCA for the first time to create the first deployment and setup the Service Manager to run as a service or system daemon, the deployment creation may return several errors.
Workaround
To avoid this issue while still being able to apply the Oracle GoldenGate 23.10.x patch:
-
Install a version of Oracle GoldenGate prior to 23.10.x.
-
Create the Service Manager as a service/daemon using that earlier version of Oracle GoldenGate.
-
Apply the Oracle GoldenGate 23.10.x patch build using OPatch.
Release 23.9- July 2025
Bug 37873099: Db2 z/OS - Failure to add or delete checkpoint table
If a checkpoint transaction table is improperly cleaned up, the checkpoint table may be removed but the transaction table remains. When this checkpoint table is added again, the transaction table will fail to be added because it already exists.
Workaround
Delete the checkpoint table again. If this doesn't work,
then try to manually delete the transaction table, which will be in
the same schema as the checkpoint table and will have the same name
with _lox appended.
Bug 37710172: Db2 z/OS - Version returned as 0 if the libraries are not authorized
If the WLM steplibs libraries are not authorized then
Extract will abend because the version number is 0.
Workaround
Ensure that the libraries are authorized.
Release 23.8- April 2025
Bug 37834526: SQL Server - Extract abends on CDC and base table mismatch
Extract compares the table structure of the base table with the CDC capture instance table, causing an abend in case of mismatch.
Workaround
Add the following to the Extract parameter file and restart it:
TRANLOGOPTIONS GETMETADATAFROMVAMRelease 23.6- October 2024
Bug 37152943: Db2 for i - Extract fails with core dump issue for heartbeat table
For Oracle GoldenGate Extract for Db2 for i, abends with the core dump error for heartbeat table. This results in heartbeat functionality not working .
Workaround
None.
Bug 37468391: Oracle - XAGTask is killing all GoldenGate processes running on a node when one Service Manager is stopped
When running Oracle GoldenGate using multiple OGG_HOME directories, and a Service Manager registered with XAG fails, or is stopped by XAG/CRS, all GoldenGate processes running on the server will be stopped, no matter what OGG_HOME they are running out of. This will cause a server wide GoldenGate outage.
Workaround
Only use XAG integration with Oracle GoldenGate on servers with:
-
A single Service Manager.
-
No other Oracle GoldenGate processes running out of a different
OGG_HOME.
Release 23.5- August 2024
Parallel Replicat is not supported for Sybase
Oracle GoldenGate for Sybase does not support parallel Replicat.
Workaround
Use coordinated or classic Replicat.
Bug 36926498: Sybase - Bi-directional Extract crashes without any error
An issue with Extract configured for bi-directional replication causes the Extract to abend.
Workaround:
None
Bug 36927786: Generic - OGGCA deployment creation is not picking up SYBASE system variable/value
When creating a Sybase deployment, the SYBASE system
variable is not getting set automatically for the deployment.
Workaround
Add the SYBASE variable to the deployment’s environment
variable configuration manually, and set the path to the Sybase home
directory, such as /opt/sap, then restart the
deployment.
Release 23.4- May 2024
Explicitly exclude Inverted File (IVF) and Hierarchical Navigable Small Worlds (HNSW) index tables
If you are using wildcard parameters, then IVF and HSNW vector index tables must be explicitly excluded from the Extract.
Workaround
None
Extract LSN positioning does not work with 0x:8:8:4 format for the Admin Client
For SQL Server, starting an Extract with ATCSN or
AFTERCSN with the Admin Client and using a
LSN value with a 0x8:8:4 format is not working as
intended.
Workaround
Provide the LSN value in the following format:
0x8:8:4-ffffffff-8:8:4.
For example:
START EXTRACT EXTPROD AFTERCSN
0x000000b3:00002240:0003-ffffffff-000000b3:00002240:0003