SQL Locks

[Willard Farwark]

Does this mean that only one of the two offending SQL statements
finished? The other did not?

2006-10-04-22.16.02.828568 Instance:xrprod Node:000
PID:11482(db2ag ent (CLINK_P)) Appid:C0A80AD6. AE97.0610050515 54
data_management sqldEscalateLoc ks Probe:2 Database:LINK_P

-- Lock Count, Target : 6491, 3245
-- Table (ID) Name : (1;14) LINK .VEHICLES_CA
-- Locks, Request Type : 6486, X
-- Result (0 = success): 0

SUCCESS: 0 Means this is not a deadlock, they both made it?

I have been getting one each min for 10 mins while a Java jobs runs
at night.

Thanks again

Ted

[memmerto@yahoo.com]

Re: SQL Locks

Willard Farwark wrote:

Does this mean that only one of the two offending SQL statements
finished? The other did not?
>
2006-10-04-22.16.02.828568 Instance:xrprod Node:000
PID:11482(db2ag ent (CLINK_P)) Appid:C0A80AD6. AE97.0610050515 54
data_management sqldEscalateLoc ks Probe:2 Database:LINK_P
>
-- Lock Count, Target : 6491, 3245
-- Table (ID) Name : (1;14) LINK .VEHICLES_CA
-- Locks, Request Type : 6486, X
-- Result (0 = success): 0
>
SUCCESS: 0 Means this is not a deadlock, they both made it?
>
I have been getting one each min for 10 mins while a Java jobs runs
at night.

All queries completed. (If one didn't, you would have seen an error in
your applciation - either a lock timeout or deadlock error.)

All this message is telling you is that the lock escalation request was
successful.

You can avoid this scenario by increasing LOCKLIST (total space
allocated for locks) or by increasing MAXLOCKS (which increases the
percentage of LOCKLIST that a single query can use for locks before
triggering lock escalation).

--
Matt Emmerton