That parm. (numdb) is only used for one thing.
It controls, at the instance level, how many db's can be acivated
concurrently.
It is default to 8, never reset, and changed only by the Control Center
function or the proper update dbm cfg command that is issued by a sysadmin.
Drop or create of db's does not change it.
HTH, Pierre.
COXJ94 wrote:
Hello, when I setup a db2 environment I initially setup numdb to equal
the amount dbs I had.
Well today, I had people saying that they couldn't get in, that they
were getting the error associated with the numdb. A couple days ago, I
had dropped a db, only to re-create it (it a test server).
When I did a 'db2 get dbm cfg', the numdb was reset to 1.
Does dropping a db reset the numdb?
TIA,
+CB
--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.