Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

What is the recommended LOCKTIMEOUT for CCM on DB2 9.7?

Questions
Tags
Users
Badges
Scott Crouch
(485●3●24●26) 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.

0 votes

1 answer
7,248 views
0 votes

One answer

Permanent link
Kevin Ramer
(4.5k●9●186●201) 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.  

1 vote

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 82

Question asked: Feb 25 '13, 8:46 a.m.

Question was seen: 7,248 times

Last updated: Feb 25 '13, 11:26 a.m.

Confirmation Cancel Confirm