Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Lock DB

Status
Not open for further replies.

nmorph

IS-IT--Management
Sep 27, 2004
19
DE
Hello

I have this error on DB2DIAG file,

2004-10-14-08.16.35.522166 Instance:ufhdba01 Node:000
PID:78408(db2agent (FH01D)) Appid:0A5108CC.04BA.041014062041
data_management sqldEscalateLocks Probe:3 Database:FH01D

-- Lock Count, Target : 2283, 1141
-- Table (ID) Name : (4;4) UFHDBTBL.FH01T01
-- Locks, Request Type : 2279, X
-- Result (0 = success): FFFF8544
7570 6461 7465 2055 4648 4442 5442 4c2e update UFHDBTBL.
4648 3031 5430 3120 7365 7420 4155 4654 FH01T01 set AUFT
5241 4753 5246 4e52 3d30 2077 6865 7265 RAGSRFNR=0 where
2057 4552 4b7c 7c53 504a 7c7c 4b4e 5220 WERK||SPJ||KNR
494e 2028 7365 6c65 6374 2046 4830 3154 IN (select FH01T
3031 2e57 4552 4b7c 7c46 4830 3154 3031 01.WERK||FH01T01
2e53 504a 7c7c 4648 3031 5430 312e 4b4e .SPJ||FH01T01.KN
5220 6672 6f6d 2055 4648 4442 5442 4c2e R from UFHDBTBL.
6668 3031 7430 3120 4648 3031 5430 3120 fh01t01 FH01T01
7768 6572 6520 4648 3031 5430 312e 5745 where FH01T01.WE
524b 313d 2734 3327 2041 4e44 2046 4830 RK1='43' AND FH0
3154 3031 2e53 5441 5455 5331 3d27 4130 1T01.STATUS1='A0
3030 2720 414e 4420 2828 4648 3031 5430 00' AND ((FH01T0
312e 6d6f 6465 6c6c 206c 696b 6520 2737 1.modell like '7
2527 2929 29 %')))

And about the same time all the application where unable to connect to database. Can anyone help me in order to find an explanation for this?

Thanks
 
Hex code FFFF8544 is the equivalent to a -911 deadlock. I would guess that you have two transactions running against the same table and that you are getting them both locking each other out.
From the error message given it looks to me (and this is a huge guess) I would guess that the table has been set up with row level locking, that the max locks has been reached, and that it is attempting to escalate to table space lock, with an exclusive intent. If you have two transactions attempting to do this at the same time, you'll lock the whole thing up.

Hope this helps.

Marc
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top