6 Known Issues and Workarounds
This chapter describes the known issues at the time of release.
Release 26ai - January 2026
Bug 38829679: SQL Server - Unable to edit heartbeat for SQL Server 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
-
Delete the existing heartbeat.
-
Add a new heartbeat table with the required parameters.
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.