diaglog size too big

[chettiar]

Hi,

I have a script whcih creates a new db2diag.log file everyday. My
problem is the moment a new file gets created, there is too much data
being written into the db2diag.log

Is there any way where in we can restrict unnecessary items being
written to the diaglog.

Pls help

Chettiar

[Mark A]

"chettiar" <ch************@yahoo.com> wrote in message
news:11**********************@b68g2000cwa.googlegr oups.com...

Hi,

I have a script whcih creates a new db2diag.log file everyday. My
problem is the moment a new file gets created, there is too much data
being written into the db2diag.log

Is there any way where in we can restrict unnecessary items being
written to the diaglog.

Pls help

Chettiar

You can lower the DIAGLEVEL in the dbm cfg. The default is 3, with 4 giving
you the most messages:

db2 update dbm cfg using DIAGLEVEL 2

If you are not using the HEALTH MONITOR, I would turn that off since it
generates a lot of messages:

db2 update dbm cfg using HEALTH_MON OFF

You may need to do a db2stop and db2start for these changes to take effect.

[Visu]

what is your diaglevel?

db2 get dbm cfg | grep -i diaglevel

Allowed values are 0 - 4

* 0 - No diagnostic data captured
* 1 - Severe errors only
* 2 - All errors
* 3 - All errors and warnings
* 4 - All errors, warnings and informational messages

chettiar wrote:

Hi,

I have a script whcih creates a new db2diag.log file everyday. My
problem is the moment a new file gets created, there is too much data
being written into the db2diag.log

Is there any way where in we can restrict unnecessary items being
written to the diaglog.

Pls help

Chettiar

[chettiar]

thnx guys.. it worked
Visu wrote:

what is your diaglevel?

db2 get dbm cfg | grep -i diaglevel

Allowed values are 0 - 4

* 0 - No diagnostic data captured
* 1 - Severe errors only
* 2 - All errors
* 3 - All errors and warnings
* 4 - All errors, warnings and informational messages

chettiar wrote:

Hi,

I have a script whcih creates a new db2diag.log file everyday. My
problem is the moment a new file gets created, there is too much data
being written into the db2diag.log

Is there any way where in we can restrict unnecessary items being
written to the diaglog.

Pls help

Chettiar