MySQL Forums
Forum List  »  General

Re: Unexpected Innodb table lock
Posted by: Scott Krise
Date: February 15, 2019 10:09AM

Well, I'm just starting to become familiar with all the information in the status report and how to use it, but here is one thing that looked interesting..

delete from kathy.wo_weekly_rel
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 321 page no 22 n bits 544 index index3 of table `kathy`.`wo_weekly_rel` trx id 643630 lock_mode X locks rec but not gap waiting
Record lock, heap no 104 PHYSICAL RECORD: n_fields 7; compact format; info bits 0

and a little further down...

MySQL thread id 69544, OS thread handle 2088, query id 54815648 w764-fos2.symmco.local 192.168.16.21 root Sending data
insert into kathy.tt_iorder(workorder,upc,user)select w.workorder, i.upc, 'kathy' from wo_details w join in_master i on i.part_number = w.part_number join kathy.wo_weekly_rel r on r.part_number = i.upc where w.workorder < 200000
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 321 page no 22 n bits 544 index index3 of table `kathy`.`wo_weekly_rel` trx id 643613 lock mode S
Record lock, heap no 1 PHYSICAL RECORD: n_fields 1; compact format; info bits 0

and also...

RECORD LOCKS space id 321 page no 22 n bits 544 index index3 of table `kathy`.`wo_weekly_rel` trx id 643613 lock mode S waiting
Record lock, heap no 322 PHYSICAL RECORD: n_fields 7; compact format; info bits 32

Kathy is the person who was running it at the time it locked.

Options: ReplyQuote


Subject
Written By
Posted
February 15, 2019 09:13AM
Re: Unexpected Innodb table lock
February 15, 2019 10:09AM
February 15, 2019 02:21PM
February 19, 2019 08:28AM
February 22, 2019 08:04AM
February 19, 2019 09:01AM
February 15, 2019 10:20AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.