We have a table with a primary index which is INT NOT NULL AUTO_INCREMENT.

After inserting ~87,000,000 entries, we started seeing error 1062, ER_DUP_ENTRY.

We can get going again after doing an ALTER TABLE to reset the auto_increment starting point, but this takes about an hour...

I've seen a couple of places where how to get around this problem was discussed, but nobody seems to discuss *why* this occurs in the first place.

Does anyone know why MySQL would start failing to increment an auto_increment index properly when it's nowhere near the upper limit? Does anyone know a way to get things functioning again without a couple of hours downtime?

Hoping there's an answer out there somewhere...

Kevin Brock
[EMAIL PROTECTED]





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to