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