If i do "db2 disconnect all" after an application finishes, does it
mean that any application that connects after this will find the buffer
pool "cold"? Or the pages accessed by last application will be still in
buffer pool? Apparently when I do "db2 disconnect all" at the end, the
windows task manager shows that all bufferpool memory has been deallocated.

thanks

TMAG wrote:

> If i do "db2 disconnect all" after an application finishes, does it
> mean that any application that connects after this will find the
> buffer pool "cold"? Or the pages accessed by last application will
> be still in buffer pool? Apparently when I do "db2 disconnect all" at
> the end, the windows task manager shows that all bufferpool memory
> has been deallocated.

If your connection was the only one to the database, then when it
disconnects the database will become "inactive" - in other words, the
buffer pools are indeed deallocated.

If you wish to keep the database "active" and the bufferpools hot, use
the "ACTIVATE DATABASE dbname" command which effectively tells DB2 to
maintain a persistent connection to the database itself.

Naturally, the "DEACTIVATE DATABASE dbname" command can be used to shut
down this "extra" connection, which you'll need to do whenever you want
to take the database offline for whatever reason (configuration change,
offline backup, etc. etc.)


Cheers,

Dave.