For CREATE TABLE statements containing columns that have an fsp (fractional seconds precision) value greater than 0, replication fails due to parser errors.

Statements that use temporal data types with an fsp value of 0 works with statement-based logging but not row-based logging. In the latter case, the data types have binary formats and type codes on the source that differ from those on the replica.

Some expression results differ on source and replica. Examples: On the source, the timestamp system variable returns a value that includes a microseconds fractional part; on the replica, it returns an integer. On the source, functions that return a result that includes the current time (such as CURTIME(), SYSDATE(), or UTC_TIMESTAMP()) interpret an argument as an fsp value and the return value includes a fractional seconds part of that many digits. On the replica, these functions permit an argument but ignore it.