LOCKWAIT and configuration Parms

[kozlow]

DB2 Ver 7.2
If we change the LOCKWAIT, we receive msg;

DB21026I For most configuration parameters, all applications must disconnect from this database before the changes become effective.

Is it a dynamic change or does the database need to be restarted?

How can you tell if any changes made are in effect for the configs of the Database or its manager?

 

[fmshire]

Yes, after all connections to database are gone. You can simply connect to it again (db2 connect to <db_name>) or activate the database (db2 activate db <db_name>)

Thank you

 

[kozlow]

The only way I know of making sure all connections to the database are gone is to run a db2stop or db2 force application all..... Since we are tring to be 7X24, I was hoping that I could change a parm and it would take effect sometime in the middle of the night when all the batch jobs have completed. I am not sure if there is anyway of telling that.... I was hoping there was a way to display the parms that are currently in affect compared to what I get from &quot;get db config for&quot; or &quot;get dbm config&quot;.... Thnks anyway.....

 

[sathyarams]

I'm afraid, there is no command to list the parms currently in effect in V7 ..

FYI, SHOW DETAIL keyword following the get command in V8, will show this ..

Some more thoughts:
Be careful when using 'force applications' and connecting to the database and assuming your parameter has been used by db2 ... If you have used 'activate database' then the you may need to issue deactivate database command ...

In your scenario, if you want to know if all apps were terminated and connected, you can check the database snapshot for the 'database activation timestamp'(??) in the database snapshot ..

HTH

sathyaram

More DB2 questions answered at

http://www.dbforums.com/f8

 

[kozlow]

One more reason to migrate to 8!!!!!!!!