By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,756 Members | 1,749 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,756 IT Pros & Developers. It's quick & easy.

Lock-waits don't get logged ... but

P: n/a
what commands can I use to find out what connection is causing a lock?

where can i change the verbosity level of db2 logfiles?
where are those logfiles?

Greetings & Thanks
Victor
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Snapshot for locks will show you what applications are in lock wait, and
the app holding the lock they need.

diag level is adjusted by the dbm cfg parm diaglevel, and the log file
goes in sqllib\db2dump by default (or DIAGPATH in the dbm cfg if that is
set).

news_account wrote:
what commands can I use to find out what connection is causing a lock?

where can i change the verbosity level of db2 logfiles?
where are those logfiles?

Greetings & Thanks
Victor

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.