It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,878
×6,036
×4,715
×82

question asked: Feb 25 '13, 8:46 a.m.
question was seen: 7,170 times
last updated: Feb 25 '13, 11:26 a.m.

Related questions

What is the recommended LOCKTIMEOUT for CCM on DB2 9.7?

0
Scott Crouch (485●3●24●26) | asked Feb 25 '13, 8:46 a.m.
 We're seeing lock timeouts on the DB for CCM only when doing SCM operations on very large codebases. We're wondering if we need to increase the LOCKTIMEOUT from the current setting of 15sec. And if so, what is the recommended setting?

The DB is db2 9.7 and the we're running RTC 4.0.1.

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Kevin Ramer (4.5k●9●186●201) | answered Feb 25 '13, 11:26 a.m.
Scott,

I will answer from general DB2 experience.   Increasing the locktimeout will introduce trade-offs in that longer timeout will increase the likelyhood that more 'applications' will get into lock-wait state.  The more things in lock-wait the less work that gets done and could lead to deadlocks.  The lock timeout only affects those applications that are held in lock-wait status (they are terminated by DB2), not the application holding the lock.

The DB2 Performance rates lock a "medium" in terms of performance impact.  

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.