Arvind Gangal wrote:
I have been using the mysqlbinlog to investigate the 'saturn2-bin.051'
binlog file.. I have come to pinpoint the problem position in the binlog,
but don't know how i can bypass the corrupted segment.
This is a bit tricky. Open the binlog in a hex editor, and go to the last good
[mailto:[EMAIL PROTECTED]
Sent: 24 March 2004 21:17
To: '[EMAIL PROTECTED]'
Subject: Error 1236 corrupt binlog on master
Hello Gurus,
Anyone have any ideas as to how I should handle a case of the following
error?
040324 21:02:05 Slave I/O thread: connected to master
'[EMAIL PROTECTE
Hello Gurus,
Anyone have any ideas as to how I should handle a case of the following
error?
040324 21:02:05 Slave I/O thread: connected to master
'[EMAIL PROTECTED]:3306', replication
started in log 'saturn2-bin.051' at position 442744915
040324 21:02:05 Error in Log_event::read_log_event():
