The following is a nonexhaustive list of common
InnoDB-specific errors that you may
encounter, with information about why each occurs and how to
resolve the problem.
Cannot create table. If the error message refers to error
150, table creation failed because a foreign key constraint
was not correctly formed. If the error message refers to
error –1, table creation probably failed because the
table includes a column name that matched the name of an
Cannot find the
InnoDB table from the
InnoDB data files, although the
.frm file for the table exists. See
Section 188.8.131.52, “Troubleshooting InnoDB Data Dictionary Operations”.
InnoDB has run out of free space in the
tablespace. You should reconfigure the tablespace to add a
new data file.
Lock wait timeout expired. Transaction was rolled back.
The total number of locks exceeds the lock table size. To
avoid this error, increase the value of
Within an individual application, a workaround may be to
break a large operation into smaller pieces. For example, if
the error occurs for a large
INSERT, perform several
Transaction deadlock. You should rerun the transaction.
You are trying to add a row but there is no parent row, and a foreign key constraint fails. You should add the parent row first.
You are trying to delete a parent row that has children, and a foreign key constraint fails. You should delete the children first.