| Title | Bugzilla integration may fail due to MySQL IntegrityError |
| Status | suspended |
| Priority | optional |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | A user had a problem with a MySQL consistency check. The error message looked like this: (1062, "Duplicate entry '532232' for key 2") This means that the P4DTI was attempting to add a row to a table with an auto-increment column (the 'id' column in the 'p4dti_replications' table). MySQL is then complaining that the auto-increment value which it has generated, and which MySQL is supposed to guarantee is unique, is not unique. |
| Analysis | This is almost certainly a MySQL bug. We have not been able to reproduce it. This may be a symptom of underlying database corruption. It may be possible to fix this up by a suitable sequence of MySQL "alter table" commands, but the exact sequence may depend on the current state of the table. We are awaiting more information from the user. |
| How found | customer |
| Evidence | Support call: <http://info.ravenbrook.com/mail/2001/11/28/12-42-05/0.txt> |
| Observed in | 1.2.1 |
| Created by | Nick Barnes |
| Created on | 2001-11-28 17:05:35 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:27:49 |
| History | 2001-11-28 NB Created. 2002-01-31 GDR Downgraded to "optional" since this hasn't happened to any other customers. Added support information. 2018-07-05 NB Suspended because the P4DTI is obsolete. |
| Support | Advice for all releases. Symptoms: The P4DTI stops with an error message from the MySQL database of the form (1062, "Duplicate entry '532232' for key 2"). Cause: Your MySQL database has been corrupted, either by a bug in MySQL or by an operating system or disk error. Solution: You can check, and possibly repair, the affected tables with the "check table" and "repair table" commands in MySQL. See http://www.mysql.com/doc/R/e/Repair.html. If you can't repair the problems with the "repair table" command,
then if the only affected table is |