Bug #27943 binlog entry missing INSERT_ID= value.

• Submitted: 19 Apr 2007 0:09
• Modified: 28 Sep 2007 9:09
• Reporter: Matthew Montgomery
• Status: No Feedback
• Category: MySQL Server: Replication
• Severity: S2 (Serious)
• Version: 5.0.30
• OS: Windows
• Assigned to: Assigned Account
• CPU Architecture: Any
• Tags: auto_increment, replication

[19 Apr 2007 0:09] Matthew Montgomery

Description:
Replication was found broken due to Duplicate Key errors.  It was discovered by looking at the binary log on the master that there were some INSERT...SELECT statements that return several rows.

The first at position 37819027 does not include an INSERT_ID= entry.  The second at 37825111 does.  This second query is the one that was found to conflict.

How to repeat:
The table definitions, sample data and query logs involved are attached to the associated support issue.

[19 Apr 2007 0:09] MySQL Verification Team

The complete original binlog is located at shell:/supportftp/pub/mysql/upload/aissql.000269

[25 Apr 2007 11:53] Sveta Smirnova

Thank you for the report.

Please describe your replication chain.

I mean is it simple master->slave or something more difficult?

Also provide configuration files for all the chain.

[28 Sep 2007 23: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".