Non-Supported Objects and Operations

Oracle GoldenGate for MySQL does not support the following objects and operations:

  • Invisible columns

  • The Oracle GoldenGate BATCHSQL feature.

  • Array fetching during initial load.

  • The following character sets are not supported:

    • ULIB_CS_ARMSCII8, /* American National 166-9 */
    • ULIB_CS_GEOSTD8, /* Geogian Standard */
    • ULIB_CS_KEYBCS2, /* Kemennicky MS-DOS
  • Capturing NLS LOB data using the FETCHMOCOLS and FETCHMODCOLEXCEPT TABLE options is not supported when DDL is enabled.

  • Renaming tables.

  • DDL statements inside stored procedures is not supported.

  • When the time zone of the Oracle GoldenGate installation server does not match the time zone of the source database server, then the TIMESTAMP data sent to the target database will differ from the source database. For Oracle GoldenGate Microservices installations, regardless of the time zones being the same, Extract will resolve the time zone to UTC. Determine the source database time zone by running the following query:

    select @@system_time_zone; 

    This will return a time zone value, such as PDT.

    Create a session variable for Oracle GoldenGate, called TZ, and set it equal to the time zone value of the database.

  • Extraction and replication from and to views is not supported.

  • Transactions applied by the slave are logged into the relay logs and not into the slave's binlog. If you want a slave to write transactions the binlog that it receives from the master , you need to start the replication slave with the log slave-updates option as 1 in my.cnf. This is in addition to the other binary logging parameters. After the master's transactions are in the slave's binlog, you can then setup a regular capture on the slave to capture and process the slave's binlog.