Monday, December 4, 2006

LOCKSIZE Parameter

Problem:

Our System has a segmented tablespace against which is accessed by multiple plans running at the same time. The concurrent plans try to insert and update the database at the same time...This causes lot of contention and occassionally our plans go down with -911 (deadlock condition)

Possible Solutions:

1) We could have the tablespace change to a Partitioned one to increase the parallelism.
2) Introduce -911 retry logic to have the plan wait for specified seconds and then try to access the tablespace.
3) Check the LOCKSIZE parameter of the tablespace definition...This parameter decides the degree of locks to be taken on tablespace be it page/row/table/Any...For better concurrency for random processing use LOCKSIZE = ROW...

We applied option 2 and 3 and all our concurrent plans are running better than before the change...

- Suresh Gangadharan

No comments: