Bug #26616 Setting auto_increment_increment causes "Incorrect information" in .frm file
Submitted: 24 Feb 2007 17:20 Modified: 26 Mar 2007 10:52
Reporter: Patrick Galbraith Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.0.27 OS:
Assigned to: Assigned Account CPU Architecture:Any
Tags: qc

[24 Feb 2007 17:20] Patrick Galbraith
Description:
If you have existing data on a box that you enable this, beware, because if that data isn't offset, you could end up with what I have experienced (this is using innodb)

"Incorrect information in file: './grazr_monitor/scheduled_tests.frm'"

Breaking the table.

I see no information to be able to limit auto_increment_increment to a specific schema.

How to repeat:
Set up a master replication server, set auto_increment_increment and auto_increment_offset values to something that's more than a +1 for each subsequent primary key value, and observer that any access to those tables results in an error like:

Incorrect information in file: './grazr_monitor/scheduled_tests.frm'

Suggested fix:
Is there a way to limit auto_increment_increment/offset to a specific schema as opposed to the whole RDBMS?
[26 Feb 2007 10:52] Sveta Smirnova
Thank you for the report.

I can not repeat it if I issue on master next commands:

create table t1(id int not null auto_increment primary key) engine=innodb;

insert into t1 values(),(),(),(),();

select * from t1;

set @@auto_increment_increment=10;
set @@auto_increment_offset=10;

insert into t1 values(),(),(),(),(),(),(),(),(),();
select * from t1;

Please, confirm or refuse if my test is wrong. And if it is wrong, correct it.
[26 Mar 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".