1. Oracle GoldenGate Classic Architecture Documentation
  2. Prepare
  3. Prepare Your Database for Oracle GoldenGate Classic Architecture
  4. MySQL
  5. Understanding What's Supported for MySQL
  6. Oracle GoldenGate for MySQL Supported Data Types
  7. Limitations and Clarifications

Limitations and Clarifications

When running Oracle GoldenGate for MySQL, be aware of the following:

  • Functional indexes are not supported for Capture or Delivery.

  • Oracle GoldenGate does not support BLOB or TEXT types when used as a primary key.

  • Oracle GoldenGate supports a TIME type range from 00:00:00 to 23:59:59.

  • Oracle GoldenGate supports timestamp data from 0001/01/03:00:00:00 to 9999/12/31:23:59:59. If a timestamp is converted from GMT to local time, these limits also apply to the resulting timestamp. Depending on the time zone, conversion may add or subtract hours, which can cause the timestamp to exceed the lower or upper supported limit.

  • Oracle GoldenGate does not support negative dates.

  • The support of range and precision for floating-point numbers depends on the host machine. In general, the precision is accurate to 16 significant digits, but you should review the database documentation to determine the expected approximations. Oracle GoldenGate rounds or truncates values that exceed the supported precision.

  • When you use ENUM type in non-strict sql_mode, the non-strict sql_mode does not prevent you from entering an invalid ENUM value and an error will be returned. To avoid this situation, do one of the following:

    • Use sql_mode as STRICT and restart Extract. This prevents users from entering invalid values for any of the data types. An IE user can only enter valid values for those data types.

    • Continue using non-strict sql_mode, but do not use ENUM data types.

    • Continue using non-strict sql_mode and use ENUM data types with valid values in the database. If you specify invalid values, the database will silently accept them and Extract will abend.

  • Table with single column is not supported for JSON datatype. Extract will abend in case it is configured for a table which has a single column of JSON datatype.

  • JSON datatype does not support CDR. The following message gets logged in the report file if GETBEFORECOLS is configured and the table has columns of JSON datatypes:
    INFO OGG-06556 The following columns will not be considered for CDR

    The limtations for CDR applies to cases where the GETBEFORECOLS and COMPARECOLS are used.