This chapter describes the known issues at the time of release.
Bug 28091901 - MySQL: Bidirectional filtering for DDL replication is not supported
Bug 27819094 - Oracle: Replicat error OGG-00665 OCI Error writing LOB for column xxx 24801-ORA-24801: occurred
Bug 27938481 - Non-Integrated Parallel Replicat fails with ORA-01403 error when using ALLOWDUPTARGETMAP
Bug 28091901 - MySQL: Bidirectional filtering for DDL replication is not supported
Bug 27812006 — Oracle: PURGE WALLET doesn’t delete the MASTERKEY
Bug 28001613 - HP-UX: Oracle GoldenGate Collector doesn’t start if FIPS mode is enabled
Bug 28000908 - zLinux: Administration Server fails with SEGV in Task Manager
Bug 27248167 — Oracle: Time zones that are not replicated properly
Bug 26782577 - Oracle: ALTID Missing data for Lob out of line columns.
Bug 26929711 - DB2 z/OS: ERROR OGG-00551 Database operation failed: init sp - execute. ODBC error
When running Oracle GoldenGate Extract against DB2 for z/OS V11, in compatibility mode, the Extract fails to correctly identify the version of the database needed for log reading APIs. Extract identifies DB2 for z/OS V11 as V10, in compatibility mode, which causes the incorrect selection of V10 stored procedures for log reading.
None
Bug 26929711 - Oracle: Extract abends with the OGG-10461 failed to retrieve timestamp error
When using classic Replicat on tables where Automatic Change Detection Resolution is enabled, Extract abends because some of the inserts in the tombstone tables are missed. This occurs because the internal trigger that inserts records into tombstone tables, triggers only on user DMLs and classic Replicat suppresses all the triggers.
None
Bug 27917936 — Oracle: Task-based initial load is not supported in Oracle GoldenGate Microservices Architecture
Bug 26856080 — Oracle: Admin Client AUTORESTART help commands are not working
Bug 26190334 — Documentation update for JAgent exclusive support on 12.3 OGG Core Classic Mode
Bug 25897967 — Oracle: Must remove deployments and stop ServiceManager process before uninstalling Oracle GoldenGate
If there are Oracle GoldenGate 12.3 processes running when OGG_HOME/deinstall/deinstall.sh
is executed, then those processes continue to run after deinstallation. The orphaned services' process IDs become defunct because the associated binaries no longer exist. However, the Service Manager process is kept alive and remains listening on the original port. Subsequent attempts to add deployments (after reinstalling Oracle GoldenGate Microservices Architecture) may be blocked due to the discovery of the active, existing Service Manager port.
When uninstalling Oracle GoldenGate MA, the best practice is to delete all affiliated deployments and/or stop their processes. In addition, identify the process ID of the Service Manager and manually kill the process. If the Service Manager is set up as an operating system service daemon, deinstall.sh
does not clean up the configuration, so this task is also manual.
Bug 26104564 — Oracle: Deleting AUTORESTART task is killing ER, which was brought up by an AUTORESTART task
Bug 25502490 — Oracle: Unable to deploy MA on Solaris Sparc Hosts
The LD_LIBRARY_PATH_64
environment variables must be set correctly before running Oracle GoldenGate on Solaris Sparc or Solaris x86_64.
Before running the configuration wizard or any Oracle GoldenGate executables, you can resolve this issue in one of two ways:
Remove the /usr/sfw/lib/sparcv9
directory, that is installed with Solaris, from the LD_LIBRARY_PATH_64
environment variable . Oracle recommends this workaround.
Update the LD_LIBRARY_PATH_64
environment variable to include $OGG_HOME/lib
as the first entry.
Bug 22826452 — Extract does not capture records if WILDCARDRESOLVE IMMEDIATE is used
Bug 22739872 — Oracle: START MGR can hang for XAGENABLEd setup if the MGR process has abended
Bug 22967088 — Oracle: IR abends with 3117-ORA-03117: two-task save area overflow
Bug 19512704 — Oracle: Wrong results with @BINTOHEX and @STRCAT functions
Bug 22854712 — Oracle: NOUSERID should force downstream mode
Bug 25043127 — Honor MAPINVISIBLECOLUMNS and NOMAPINVISIBLECOLUMNS in user exit
XL C++ runtime environment on AIX
Bug 26564428 — Solaris 10: Replicat doesn't map derived objects when schema name is specified with it
Bug 26564428 — Replicat doesn't map derived objects when schema name is specified with it
When a source schema name is appended to the derived object (indexes and triggers) during DDL (like CREATE TRIGGER tkggu1.mytrigger1
), then the derived object is not mapped correctly by the Replicat. Since mapderived
is default for Replicat, the statement should map per the map statements.
Do not append a source schema name to the derived object name in DDL statement so that the statement is executed on the correct schema.
Bug 26533353 — Deployment creation fails when Integrate with XAG option is used
Bug 26501195 — realpath() resolution fails on Solaris 10 - 404 returned instead of index.html
Bug 26596046 — SQL Server: CDC Extract encountered OGG-14053 and not process data for myheart
Bug 26593572 — The Admin Client does not allow connection to deployment as a non-admin user
Bug 26613655 — SQL Server CDC: GGSCI ADD HEARTBEATTABLE does not create Fetch Processes
Mac OS Browser Support
Bug 25061436 — DB2 for i: On system time change rollback extract stops or loses records
An issue has been raised with IBM about the generation of system sequence numbers where the system sequence numbers roll back during the one hour window in the fall daylight savings time adjustment period at 2 a.m. This can cause a loss of data and/or hung Extract.
Shut down the Extract during the fall Daylight Savings Time change at or before 2 a.m. local time and wait until 2 a.m. standard time has passed to restart Extract.
Bug 26546679 — SQL Server CDC: Doc for the Release Notes needed regarding unsupported Data Types
For tables that contain SPARSE
columns, the sql_variant
data type, or the FILESTREAM
attribute, Extract may fail if processing DML
for these tables. .
You must remove these tables from Extract with either the TABLEEXCLUDE
parameter, or you can remove TRANDATA
for the specific tables with DELETE TRANDATA
Bug 26492075 — SQL Server CDC: Invalid character found in column with different character set than the database
Due to a limitation with SQL Server's Change Data Capture abilities, column level collations that are different from the database collation, may cause incorrect data to be written to the CDC tables for character data, and Extract may capture them as they are written to the CDC tables.
None
Bug 26046195 — SQL Server CDC: versions prior to 2012 have a problem with primary key updates
SQL Server 2008 and 2008R2 Change Data Capture may write a primary key update to the CT staging table as a Delete or Insert that is not part of the same transaction. If this occurs, data written to the trail is as a Delete, followed by an Insert, and this could impact target foreign key constraints.
Disable target table foreign key constraints.
Bug 26768896 — CDC Extract for SQL Server 2016 SP1+ Standard Edition:
Bug 26020817 - Oracle: Extract will have actual LAG + 1 hour during DST transition from DST to Non-DST
Bug 26812463 - Oracle: GRANT ... TO ... IDENTIFIED BY DDL operation
Combination DDL operations that create a user at the same that as granting permissions to that user are not supported in DDL replication for Classic Extract. For example, GRANT DBA TO scott IDENTIFIED BY tiger;
is not a supported DDL operation, and Replicat will abend when it encounters these types of operations.
You can workaround this by splitting the DDL operation into two separate commands. The first DDL to create the user, and a second DDL to grant the permissions to the new user.
Bug 27622553 — SQL Server CDC: Oracle GoldenGate 12c (12.2.0.1) Replicat does not support Oracle GoldenGate 12c (12.3.0.1) SQL Server CDC Extract LSN Formats
Oracle GoldenGate 12c (12.2.0.1) and lower releases do not support the LSN format of the CDC Extract introduced with Oracle GoldenGate 12c (12.3.0.1) and so, ATCSN
and AFTERSCN
are not supported. The LSN
value that is stored in the trail by the Oracle GoldenGate 12c (12.3.0.1) CDC Extract is different than with Classic Extract when positioning an Oracle GoldenGate 12c (12.2.0.1) Replicat using ATCSN
or AFTERCSN
that was generated from an Oracle GoldenGate 12c (12.3.0.1) CDC Extract. This is regardless of using FORMAT RELEASE
Oracle GoldenGate 12c (12.2.0.1) with the Extract.