on 06/18/2004 05:16 PM, Kevin Brock at [EMAIL PROTECTED] wrote: > 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...
While I do not know why, I would suggest you simply drop the PK and recreate it, this should be a whole lot faster than the alter. -- ------------------------------------------------------------- Scott Haneda Tel: 415.898.2602 http://www.newgeo.com Fax: 313.557.5052 [EMAIL PROTECTED] Novato, CA U.S.A. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
