Joined: 23 May 2008 Posts: 35 Location: beijing China
WHEN I RUN a bacth program with a plan bound with RELEASE(COMMIT),
a lot of time consumed in DB2 PARENT L-LOCKS ,PM reprot as below:
GLOBAL CONTENTION L-LOCKS AVERAGE TIME AV.EVENT
------------------------------------- ------------ --------
L-LOCKS 3:23.599428 268.4K
PARENT (DB,TS,TAB,PART) 2:47.167313 211.7K
CHILD (PAGE,ROW) 12.726702 19375.00
OTHER 23.705414 37292.00
WHEN I run it with plan bound with RELEASE(deallocate),the
PARENT lock almost disappear,but child lock increased about 50%:
GLOBAL CONTENTION L-LOCKS AVERAGE TIME AV.EVENT
------------------------------------- ------------ --------
L-LOCKS 27.246866 30499.00
PARENT (DB,TS,TAB,PART) 0.037746 49.00
CHILD (PAGE,ROW) 27.172850 30403.00
OTHER 0.036270 47.00
I am very confusing about that,why page level lock amount can be different in
that two mode. there is no X,S lock applid at tablespace or table level,
so the page level lock amout should be equal in that mode. correct me if
I was wrong,thanks in advance!![/quote]
Joined: 23 May 2008 Posts: 35 Location: beijing China
my PLAN BOUND WITH ACQUIRE(USE).
I think ACQUIRE and RELEASE only apply to parent lock,and child lock will always be released when commit is issued. SO,the child lock amout should be equal, becase the DML amount is equal .
