Bug #65468 A couple of rows in tbl had write locks that couldn't be cleared
Submitted: 30 May 2012 20:48 Modified: 28 Feb 2013 19:00
Reporter: Greg Kemnitz Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.5.14-enterprise-commercial-advanced-lo OS:Solaris (innodb)
Assigned to: CPU Architecture:Any
Tags: foreign key, innodb, write lock

File: Maximum allowed size is 3MB.
Description:
Privacy:

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-65468.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

  1. Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
  2. Log in with your newly created Oracle Web account (email address) and password.
  3. Upload the archive to /support/incoming.
  4. Once you have uploaded the file, add a comment to this bug to notify us about it.
Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

[31 May 2012 18:52] Greg Kemnitz
SHOW ENGINE INNODB STATUS output

Attachment: innodb_out.txt (text/plain), 27.08 KiB.

[31 May 2012 18:53] Greg Kemnitz
SHOW FULL PROCESSLIST output

Attachment: show_full_processlist.txt (text/plain), 10.91 KiB.