Re: DB2 Connect - DB2DIAG.LOG file

Philip Nelson

Re: DB2 Connect - DB2DIAG.LOG file
(in response to Denzil Coulter)
On Fri, 8 Oct 1999 07:32:26 -0500, Steck, Dave wrote:

>There is a file DB2DIAG.LOG on our NT machines running DB2 Connect PE that
>is about 20m in size and growing. Is there a way to configure DB2 Connect
>so less information is logged to slow down the growth rate?

You can set the environment variable DIAGLEVEL - by default this is 3, but can be reduced. However its good to have this level of statistics in case of problems.
>
>How can I reduce its size now that it's that big? Can you just delete it?
>
Simply delete it - next time it is needed it will be recreated.



Philip Nelson
Senior DBA
Scottish Widows
([login to unmask email])

Denzil Coulter

Réf. : DB2 Connect - DB2DIAG.LOG file
try modifying the 'client settings...' in the client config assistant. The
Diagnostic tab
contains the 'Diagnostic error capture level' parameter.

Philip Gunning

Re: DB2 Connect - DB2DIAG.LOG file
(in response to Philip Nelson)
you can just delete it. Db2 Connect will recreate it if it needs it. Phil

Phil Gunning
DB2 DBA
IBM Certified Solutions Expert -- DB2 UDB
IBM Certified Solutions Expert -- CICS TS

-----Original Message-----
From: Steck, Dave [SMTP:[login to unmask email]
Sent: Friday, October 08, 1999 8:32 AM
To: [login to unmask email]
Subject: DB2 Connect - DB2DIAG.LOG file

There is a file DB2DIAG.LOG on our NT machines running DB2 Connect PE that
is about 20m in size and growing. Is there a way to configure DB2 Connect
so less information is logged to slow down the growth rate?

How can I reduce its size now that it's that big? Can you just delete it?

Michael McCarthy

Re: DB2 Connect - DB2DIAG.LOG file
(in response to Philip Gunning)
Dave,

There is a Database Manager Configuration parameter called DIAGLEVEL.
Level 1 is for severe errors only, Level 2 is for normal and severe errors,
Level 3 is for warnings, normal, and severe errors, and Level 4 is for
informational, warning, normal, and severe error messages. You probably have
this set to 3(default) or 4. If you delete the db2diag.log, no harm is done.
The next time DB2 needs to write to it, it will be recreated. Use the update
dbm cfg command to change the DIAGLEVEL to the desired level.

-Mike.





"Steck, Dave" <[login to unmask email]> on 10/08/99 08:32:26 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Michael McCarthy/DTC)
Subject: [DB2-L] DB2 Connect - DB2DIAG.LOG file




There is a file DB2DIAG.LOG on our NT machines running DB2 Connect PE that
is about 20m in size and growing. Is there a way to configure DB2 Connect
so less information is logged to slow down the growth rate?

How can I reduce its size now that it's that big? Can you just delete it?