Bug #56239 InnoDB: Error: unlock row could not find a 4 mode lock on the record
Submitted: 25 Aug 2010 5:13 Modified: 20 May 2011 23:19
Reporter: Anil Alpati Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.1.45 OS:Any
Assigned to: CPU Architecture:Any

[25 Aug 2010 5:13] Anil Alpati
Description:
I'm facing an error in back end log..

Please help out -
InnoDB: Error: unlock row could not find a 4 mode lock on the record

Herewith attaching log is just for your reference.

How to repeat:
SAME AS ABOVE
[25 Aug 2010 5:14] Anil Alpati
mysqlInnoDB ERROR

Attachment: mysqlInnodb.err (application/octet-stream, text), 10.32 KiB.

[25 Aug 2010 5:22] Valeriy Kravchuk
What exact version of MySQL server do you use? Any ideas about exact SQL statements executed when you get these messages in the log?
[25 Aug 2010 5:44] Anil Alpati
Version - 5.1.45

NO,there is no statements executed in back end while getting this message.

Steps -

1. I have taken raw data backup (data directory) from windows machine to linux machine (ubuntu)
2. I have installed binary MySQL 5.1.45 on ubuntu.
3. Every thing installed sucessfully.
4.Copy the data directory to MySQL installed data directory.
5.Restarted the server.
6.Server started sucessfully with any issues.
[25 Aug 2010 8:03] Anil Alpati
Kindly respond for the request!  as mentioned in last chain...
[25 Aug 2010 15:54] Sveta Smirnova
Thank you for the feedback.

> 6.Server started sucessfully with any issues.

Did you mean server started *without* any issues? If so this can be forgotten temporary table which was removed after restart.
[25 Aug 2010 15:55] Sveta Smirnova
If you still have issues please try last suggestion from http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting-datadict.html
[25 Sep 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[20 May 2011 23:19] James Day
This is a duplicate of bug #53674, fixed in 5.1.49 and later.