Why are we getting repeated lock wait warnings on the SCM.CONTENT_CLAIMER table?
We started getting multiple lock wait warnings each hour recently against one of our RTC backend databases in DB2. The statement is LOCK TABLE SCM.CONTENT_CLAIMER IN SHARE MODE.
What are the possible reasons that this is occurring? Is this multiple people or applications trying to check-out the same file and one user already has the lock?
I looked at the rows inside that table but couldn't get an idea exactly what it's used for.
What are the possible reasons that this is occurring? Is this multiple people or applications trying to check-out the same file and one user already has the lock?
I looked at the rows inside that table but couldn't get an idea exactly what it's used for.
One answer
This wouldn't be caused by multiple users loading the same content or having a file locked. This looks like a problem at the database level. I suggest taking a look at the tuning guide or contacting IBM support.
Comments
Michael Walker
May 08 '13, 3:16 a.m.bump bump bump