Shi The database stopes after the last connection is terminated and releases all resources. The database starts again when there is a connection comes into database. The database need to allocate all the resources when the request comes after the database is stopped.
This can be avoided by issuing the following commnad db2 activate db dbname This will keep the database active all the time and the message to be noted is it hold the resources all the time. But this will avoid the first connection overhead time. Kish >From: "Shi, Zhong" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: DB2EUG: interpret db2diag.log >Date: Wed, 31 Oct 2001 10:51:21 -0500 > >Hi, list, > >I get a message in db2diag.log on one instance every day. The database >works >fine. I don't know what is the real problem. Can anyone interpret this >message? This is UDB 5.2 on AIX 4.3. >Thank you. > >Zhong > >Here is the message in db2diag.log: > >Starting the database. > >2001-10-31-05.30.10.336835 Instance:inst01d Node:000 >PID:82060(db2agent (GPMEDDB)) Appid:*LOCAL.inst01d.011031103009 >buffer_pool_services sqlbStopPools Probe:0 Database:GPMEDDB > >Stopping the database. > > > > > >===== >To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] >For other info (and scripts), see >http://people.mn.mediaone.net/scottrmcleod > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
