PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 [#1947914]

I am experiencing a strange problem. On one of my websites I am receiving this warning when trying to create a new node...

PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '0' for key 'vid': INSERT INTO {node} (vid, type, language, title, uid, status, created, changed, comment, promote, sticky) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8, :db_insert_placeholder_9, :db_insert_placeholder_10); Array ( [:db_insert_placeholder_0] => 0 [:db_insert_placeholder_1] => article [:db_insert_placeholder_2] => und [:db_insert_placeholder_3] => test [:db_insert_placeholder_4] => 1 [:db_insert_placeholder_5] => 1 [:db_insert_placeholder_6] => 1363745759 [:db_insert_placeholder_7] => 1363745759 [:db_insert_placeholder_8] => 2 [:db_insert_placeholder_9] => 1 [:db_insert_placeholder_10] => 0 ) in drupal_write_record() (line 6975 of /data/disk/o1/static/thinkingskills.me/includes/common.inc).

I have tested another site which is using the platform and it is receiving no errors.

The strange thing is though that I have not been doing anything on the site for a while and am wondering if being updated to B.O.A-2.0.6-dev could have caused this.

Users on the site could create new nodes until Yesterday. The only thing that has happened since is an MYSQL ERROR email today.

I have searched for a solution to the problem but it seems to occur mostly after installing new modules or upgrading Drupal, or adding new fields, or relating to Rules.. none of which occurred.

One solution requires editing the structure of the database which I am very reluctant to do.

mysqlcheck on the database in question shows no errors. I'm at a loss. Could it relate to the MyIsam change (made by omega8.cc support staff) or the dev version of B.O.A.?

Any advice on this would be great,

Cheers,

Will.

Comments

Comment #1

Musicious CreditAttribution: Musicious commented 20 March 2013 at 15:10

Status:

Active

» Closed (fixed)

It was a database error. Deleted a node and now we are back up again.

thanks.

Comment #2

omega8cc CreditAttribution: omega8cc commented 20 March 2013 at 15:13

Project:	Barracuda	» Octopus
Component:	Aegir Master Instance	» Miscellaneous
Status:	Closed (fixed)	» Active

The error is pretty much self-explanatory: Duplicate entry '0' for key 'vid'. You need to de-duplicate entries in the database. This typically happens when you import database without required DROP TABLE IF EXISTS lines. Also "MYSQL ERROR email today" suggests that there was some table crashed and the self-healing had to repair it. You need to investigate this, but I doubt there is anything BOA related. Using MyISAM does help when you have limited RAM/CPU but it also comes with cost of lost ability to auto-recover, like it is in the InnoDB. It is highly possible that there was some problem before, and converting tables to MyISAM only exposed the issues you need to investigate.