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

monitoring questions

P: n/a
I go in through the Control Center Activity Control Center and
eventually select view locks, I get a popup window "The Activity
Monitor is unable to collect the required snapshot
data because the monitor switch "LOCK" is not turned on at the
database manager level."

I had run db2 update monitor switches using BUFFERPOOL on LOCK on SORT
on STATEMENT on TIMESTAMP on TABLE on UOW on Does DB2 need to be
restarted? Does das need a restart?

Another question, I turned on event monitor and wondering where I can
find what data in the fields means for SELECT * FROM
TABLE(SNAPSHOT_LOCK('proddb',-1)) AS SNAPSHOT_LOCK
like "lock_mode", "lock_object_type", "lock_Status" etc..?

Nov 20 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
<bi******@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
>I go in through the Control Center Activity Control Center and
eventually select view locks, I get a popup window "The Activity
Monitor is unable to collect the required snapshot
data because the monitor switch "LOCK" is not turned on at the
database manager level."

I had run db2 update monitor switches using BUFFERPOOL on LOCK on SORT
on STATEMENT on TIMESTAMP on TABLE on UOW on Does DB2 need to be
restarted? Does das need a restart?

Another question, I turned on event monitor and wondering where I can
find what data in the fields means for SELECT * FROM
TABLE(SNAPSHOT_LOCK('proddb',-1)) AS SNAPSHOT_LOCK
like "lock_mode", "lock_object_type", "lock_Status" etc..?
I believe that it takes affect immediately. You can attach to the instance
and run the following:

db2 get dbm cfg show detail

This will show which parm changes are pending vs. already in effect.
Nov 20 '06 #2

P: n/a
I believe you need to ser the monitor switches at the instance level, as in:
db2 update dbm cfg usinf dvt_mon__lock on ... and so on.
The reason is that the:
db2 update monitor switches .. command applies only to the application or
session issuing it. So, when you do that an then call the activity monitor
thru the cc, it is the activity monitor that is in control and it has not
issued an update monitor switches. However, it will acquire their settings
from the dbm cfg.
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Mark A" <no****@nowhere.coma écrit dans le message de news:
GK******************************@comcast.com...
<bi******@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
>>I go in through the Control Center Activity Control Center and
eventually select view locks, I get a popup window "The Activity
Monitor is unable to collect the required snapshot
data because the monitor switch "LOCK" is not turned on at the
database manager level."

I had run db2 update monitor switches using BUFFERPOOL on LOCK on SORT
on STATEMENT on TIMESTAMP on TABLE on UOW on Does DB2 need to be
restarted? Does das need a restart?

Another question, I turned on event monitor and wondering where I can
find what data in the fields means for SELECT * FROM
TABLE(SNAPSHOT_LOCK('proddb',-1)) AS SNAPSHOT_LOCK
like "lock_mode", "lock_object_type", "lock_Status" etc..?

I believe that it takes affect immediately. You can attach to the instance
and run the following:

db2 get dbm cfg show detail

This will show which parm changes are pending vs. already in effect.
Nov 24 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.