This section describes the known issues, with any available workarounds, identified in each release . The Bug number
is the number of the BugDB ticket. For questions on specific tickets or issues, consult Oracle Support.
Bug 26856080 — Oracle: Admin Client AUTORESTART help commands are not working
Bug 22826452 — Extract does not capture records if WILDCARDRESOLVE IMMEDIATE is used
Bug 26104564 — Oracle: Deleting AUTORESTART task is killing ER, which was brought up by an AUTORESTART task
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 — 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 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.