The best way is to compress and move the current db2diag.log file to
Log-archive directory. The best time to do this is whenever the engine
is bounced. The following steps CAN be followed.

1. After stopping the database engine, move the db2daig.log
file to db2diag.log.<date_time> .
2. Immediately touch the file db2diag.log. This is because if you
have any of your web-services or any other services try to talk, then
error happened will also get logged into the new db2diag.log file.
3. Compress the file db2diag.log.<date_time>.
4. Move the compressed file db2diag.log.<date_time> to the log-archive
directory. [You should have purging strategy set on this directory].

When you start the engine you will have new db2diag.log file for the
latest start.

Hope this helps.
Partha
-----Original Message-----
From: Brian Sandmann
[mailto:db2udbdba-ezmlmshield-x14875890.[Email address protected]
Sent: Wednesday, March 30, 2005 11:11 AM
To: LazyDBA Discussion
Subject: Pruning db2diag.log

Over time the db2diag.log/log gets extremely large. What is the easiest way
to manage the size log the log? After entries are 3 or 4 months, we really
don't need the entries. Is there a job or parameter that were delete
entries in the log after they are X days old?


---------------------------------------------------------------------
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