Bug 38829679: SQL Server - Unable to edit heartbeat due to stale object error

When you try to alter an existing Heartbeat from the Oracle GoldenGate for SQL Server web interface, the console displays a notification message and the Heartbeat values do not change. As a result, you may not be able to alter the Heartbeat directly.

Workaround

Alternatively, you can alter the heartbeat using the ALTER HEARTBEATTABLE command from the Admin Client.

Bug 38829042: Teradata - Autofill for new DB connection uses port 5432 instead of Teradata Default (1025)

On DB Connections page, when you click on the Add button, the Port number field is auto-populated with 5432 by default, instead of 1025.

Workaround

If user wants to use the default port for Teradata in the new DB Connection, then you must manually delete 5432 and enter 1025 in the port number.

Bug 38829062: Teradata - Connection creation fails when port is left empty but UI says default (1025) will be used

On the DB Connections page, when you clear the port number and click Submit after adding values for other mandatory fields, the web interface throws an error and does not allow adding the new DB Connection.

Workaround

You must specify the correct port number for the DB Connection. If you want to use the default port number in the DB Connection, then you need to manually specify 1025 as the port number.

Bug 38829010: Teradata - Copy/Edit DB connection doesn’t populate DB Name (DSN-Based Connections)

For an existing DSN-based connection, if you click on the Edit button, you will observe that the Database Name field remains blank.

Workaround

The Database Name field must be left blank. The DB Connection will utilize the Database Name from the settings in the DSN file.

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.

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.

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:

1. Install a version of Oracle GoldenGate prior to 23.10.x.

2. Create the Service Manager as a service/daemon using that earlier version of Oracle GoldenGate.

3. Apply the Oracle GoldenGate 23.10.x patch build using OPatch.

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.

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 GETMETADATAFROMVAM

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.

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.

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