Bug #48622 Binary logging not possible. Transaction level 'READ-UNCOMMITTED' in Innodb

• Submitted: 9 Nov 2009 7:43
• Modified: 13 Dec 2009 10:15
• Reporter: sonika rani
• Status: No Feedback
• Category: MySQL Server: InnoDB storage engine
• Severity: S1 (Critical)
• Version: upgrade from 5.0.45 to 5.1.37
• OS: Linux (Red Hat Enterprise Linux Server release 5.1 (Tikanga))
• CPU Architecture: Any

[9 Nov 2009 7:43] sonika rani

Description:
Hi

I have upgraded mysql  5.0.45 to 5.1.37 on red hat release 5.1 (Tikanga)

after upgrading it starts giving error on every update "Binary logging not possible. Message: Transaction level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'"

& after that we have changed Transaction level to READ-COMMITTED then again the same error is coming & again changed to Transaction level to REPEATABLE-READ then too same error
after that we changed binlog mode to "ROW" then it resolve the error but mysqlbinlog giving error 

"ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 44040192, event_type: -16
ERROR: Could not read entry at offset 97954: Error in log format or read error."

& even after after changing binlog mode to MIXED the same error comes from mysqlbinlog

we aren't able to start replication

please suggest, how can i resolve the problem

Regards

Sonika

How to repeat:
Hi

I have upgraded mysql  5.0.45 to 5.1.37 on red hat release 5.1 (Tikanga)

after upgrading it starts giving error on every update "Binary logging not possible. Message: Transaction level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'"

& after that we have changed Transaction level to READ-COMMITTED then again the same error is coming & again changed to Transaction level to REPEATABLE-READ then too same error
after that we changed binlog mode to "ROW" then it resolve the error but mysqlbinlog giving error 

"ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 44040192, event_type: -16
ERROR: Could not read entry at offset 97954: Error in log format or read error."

& even after after changing binlog mode to MIXED the same error comes from mysqlbinlog

we aren't able to start replication

please suggest, how can i resolve the problem

Regards

Sonika

[13 Nov 2009 10:15] Valeriy Kravchuk

Please, send the results of:

mysqlbinlog --version

[14 Dec 2009 0:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".