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 126.96.36.199, “Troubleshooting
InnoDB Data Dictionary Operations”.
InnoDB has run out of free space in the
tablespace. Reconfigure the tablespace to add a new data
Lock wait timeout expired. The statement that waited too
long was rolled back
(not the entire
can increase the value of the
configuration option if SQL statements should wait longer
for other transactions to complete, or decrease it if too
many long-running transactions are causing
locking problems and
on a busy system.
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
encountered a deadlock
and was automatically rolled
back so that your application could take corrective
action. To recover from this error, run all the operations
in this transaction again. A deadlock occurs when requests
for locks arrive in inconsistent order between transactions.
The transaction that was rolled back released all its locks,
and the other transaction can now get all the locks it
requested. Thus when you re-run the transaction that was
rolled back, it might have to wait for other transactions to
complete, but typically the deadlock does not recur. If you
encounter frequent deadlocks, make the sequence of locking
... FOR UPDATE, and so on) consistent between the
different transactions or applications that experience the
issue. See Section 188.8.131.52, “How to Cope with Deadlocks” for details.
You are trying to add a row but there is no parent row, and a foreign key constraint fails. Add the parent row first.
You are trying to delete a parent row that has children, and a foreign key constraint fails. Delete the children first.