You may have to run 'db2 Activate db <dbname>' command. Otherwise, Db2
releases all allocated storage and archives active logs when there no
database connections. On the next connect, it allocate memory storage,
logs etc. and there will be some initial delay.

Activate db command ensures that DB2 agents are available and waiting to
service connection requests.

Rao V Chinnam




"McClendon Rick
"
<db2udbdba-ezmlms To
hield-x77583242.x "LazyDBA Discussion"
[Email Address Removed] <[Email address protected]
a.com> cc

04/25/2005 08:29 Subject
AM Logging question










I have a problem with the 'db2logmgr' rapidly cutting small (12k) log
records triggering frequent log archive files.

Any suggestions on what may cause this and a standard fix?

Maybe there is an application executing ATTACH/DETACH frequently or
something and I should keep the database in an ATTACHed state?

Can't remember the fix here... [Email Address Removed] you for your considerations -
Rick


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


DB2 & UDB email list listserv db2-l LazyDBA home page