4 Known Issues and Workarounds

This chapter describes the known issues at the time of release.

4.1 Release 26ai (23.26.3) — August 2026

Bug 39523038 - MongoDB Extract Creation with an LSN Using REST API or Web UI

When creating a MongoDB Extract at a specific LSN, requests submitted through the REST API or Web UI can fail with the following error:
OGG-12111: JSON element '/begin' does not match any schemas
The issue affects the REST API/Web UI request path for MongoDB Extract creation when a starting LSN is specified. The same LSN can be used to create the Extract through Admin Client.

Workaround

Use Admin Client to create the MongoDB Extract at the required LSN. For example:
ADD EXTRACT <extract-name> TRANLOG LSN <lsn>

Bug 39860674 -Test Connection Fails with OGG-08110 Error

When testing the database connection, the Test Connection operation may fail with error code OGG-08110, indicating that database login validation was unsuccessful. The following error is displayed:
Login failed.Database login validation failed.Review DB-Connection log and verify connection settings, 
DOMAIN/USERIDALIAS, and credential store configuration.
Code: OGG-08110
Cause: There was an error while logging into the database.
Action: Check credentials. Refer to the printed message for more details.

Workaround

In the deployment configuration, add the following environment variables if they are not already configured: 
JAVA_HOME=<full path to JDK>
PATH=$PATH:$JAVA_HOME/bin

After updating the deployment configuration, retry the Test Connection.

Parent topic: Known Issues and Workarounds

4.2 Release 26ai (23.26.2) — May 2026

Bug 38943094 - VDOM OGGDAA WEBUI: Extract/Replicat navigation entries not automatically displayed in left pane of Admin Service Page, requires manual reload

In Oracle GoldenGate Microservices Architecture (MA) that contains no existing Extracts and/or Replicats, when the user adds an extract or replicat for the first time, the left navigation menu does not automatically display the newly added extract or replicat, despite the dedicated Extract/Replicat page listing them correctly.

Workaround

After you add the first Extract and/or Replicat, refresh the page once. The left navigation menu then shows Extracts and/or Replicats correctly and continues to update as you add more.

Parent topic: Known Issues and Workarounds

4.3 Release 23ai (23.10) — February 2026

Bug 38797457 - Limitations on Avro-based staging tables for table and column names

In Oracle GoldenGate for Distributed Analytics and Applications (GG for DAA) Stage and Merge, if the incoming source object names contains characters that are not valid according to Avro specification, then the replication will fail.

Parent topic: Known Issues and Workarounds