Using DG4ODBC ORA-28500: [MySQL] Cannot Execute : Impossible To Write To Binary Log Since BINLOG_FORMAT = STATEMENT
(Doc ID 1478434.1)
Last updated on MAY 11, 2022
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Using 11g of the Oracle Database Gateway for ODBC (DG4ODBC) the following error occurs when inserting or updating a MySQL table -
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[MySQL][ODBC 3.51
Driver][mysqld-5.5.24-enterprise-commercial-advanced-log]Cannot execute
statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT
and at least one table uses a storage engine limited to row-based logging.
DB is limited to row-logging when transaction isolation level is READ
COMMITTED or READ UNCOMMITTED.
ORA-02063: preceding 2 lines from DBLINK
[MySQL][ODBC 3.51
Driver][mysqld-5.5.24-enterprise-commercial-advanced-log]Cannot execute
statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT
and at least one table uses a storage engine limited to row-based logging.
DB is limited to row-logging when transaction isolation level is READ
COMMITTED or READ UNCOMMITTED.
ORA-02063: preceding 2 lines from DBLINK
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |