Oracle GoldenGate for MySQL supports the following objects and operations:

• Oracle GoldenGate supports the following DML operations on source and target database transactional tables:

  • Insert operation

  • Update operation (compressed included)

  • Delete operation (compressed included)

  • Truncate operation

• Oracle GoldenGate supports the extraction and replication of DDL (data definition language) operations.

• Oracle GoldenGate supports transactional tables up to the full row size and maximum number of columns that are supported by MySQL and the database storage engine that is being used. InnoDB supports up to 1017 columns.

• Generated columns are supported and captured.

• Oracle GoldenGate supports the AUTO_INCREMENT column attribute. The increment value is captured from the binary log by Extract and applied to the target table in a Replicat insert operation.

• Oracle GoldenGate can operate concurrently with MySQL native replication.

• Oracle GoldenGate supports the DYNSQL feature for MySQL.

  Note:

  XA transactions are not supported for capture and any XA transactions logged in binlog cause Extract to abend. So, you must not use XA transactions against a database that Extract is configured to capture.

  If XA transactions are being used for databases that are not configured for Oracle GoldenGate capture, then exclude those databases from logging into MySQL binary logs by using the parameter binlog-ignore-db in the MySQL server configuration file.

  Limitations on Automatic Heartbeat Table support are as follows:

  • Ensure that the database in which the heartbeat table is to be created already exists to avoid errors when adding the heartbeat table.

  • In the heartbeat history lag view, the information in fields like heartbeat_received_ts, incoming_heartbeat_age, and outgoing_heartbeat_age are shown with respect to the system time. You should ensure that the operating system time is setup with the correct and current time zone information.

• Position by End of File (EOF) is supported in MySQL. Oracle GoldenGate Extract for MySQL finds the position corresponding to the end of the file and starts reading transactions from there. The EOF position is not exact, if data is continuously written to the binary log.

  The Extract is added and altered using:

  ADD EXTRACT group_name, TRANLOG, EOF

  ALTER EXTRACT group_name, EOF