Error when Binary Logging is Enabled in MySQL

Error when Binary Logging is Enabled in MySQL

Several error messages may display during migration to a MySQL server when binary logging is enabled.


The first message displays during index creation.

ConvertFile Error1


A second message displays during data copy.

ConvertFile Error2


Cause

MySQL 5.0.16 introduced requirements that when binary logging is enabled, you must have the SUPER privilege and a function must be declared DETERMINISTIC if you are using statement-based (the default) binary-logging.


Solution

Binary logging is enabled in MySQL by adding these lines to the my.ini file:

#*** Binlog Settings
# Binary Log Options and Variables (Replication)
log-bin=mysql-bin
#Binary Log Options and Variables
sync_binlog=1

 


To resolve this problem, add these two lines to the [mysqld] section of the my.ini file:

log_bin_trust_routine_creators=1
binlog_format=row

 

This changes how MySQL enforces restrictions on stored function and trigger creation and changes the log format to use row-based logging.



Data Security with Flex2SQL and BTR2SQL Connectivity Products

Data Security with Flex2SQL and BTR2SQL Connectivity Products

The most common reason for Enterprises looking to migrate from legacy Btrieve or DataFlex databases is the urgent need to address security and...

Read More
Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Introduction Many independent software vendors (ISV) and corporate users still rely on applications that use a category of database collective called...

Read More
Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

COBOL applications are the foundation of numerous essential business functions, especially within the banking, insurance, and government sectors....

Read More