Hi,

In the db2dump folder files db2diag was increasing every day 1GB.I have checked the db2diag file also it shows no error or severe all are the warning message olny.

How to trouble shoot the problem?

Regards,
Raj

Raj, the first thing I would do is run DB2 GET DBM CFG and see what the DIAGLEVEL is set to. I think 4 is the highest level which records all messages, even the informational ones. If it is 4 you can change it with:

update dbm cfg using DIAGLEVEL 3

If DIAGLEVEL is already at 3, you will need to examine the DB2DIAG.LOG file and see if you can determine what messages are causing such large increases to the size of the file.

Hi,
I have checked the db2diag.log file.This file increasing only night time only.I able to see lot of message regarding to EVENT. Automatic Runstats happening night time how to stop this please help me..

2009-08-05-08.04.13.451564+330 I938376773A368 LEVEL: Event
PID : 29997 TID : 67969 PROC : db2acd 0
INSTANCE: db2irp NODE : 000
APPID : *LOCAL.db2irp.090805023437
FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:500
START : Automatic Runstats: runstats has started on table "SAPIRQ "."ALTSTLOD"

2009-08-05-08.04.13.567547+330 I938377142A379 LEVEL: Event
PID : 29997 TID : 67969 PROC : db2acd 0
INSTANCE: db2irp NODE : 000
APPID : *LOCAL.db2irp.090805023437
FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:900
STOP : Automatic Runstats: runstats completed successfully on table "SAPIRQ "."ALTSTLOD"

2009-08-05-08.04.13.623832+330 I938377522A365 LEVEL: Event
PID : 29997 TID : 67971 PROC : db2acd 0
INSTANCE: db2irp NODE : 000
APPID : *LOCAL.db2irp.090805023439
FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:500
START : Automatic Runstats: runstats has started on table "SAPIRQ "."TUCON"

Regards,
Raj

Please refer:

IBM DB2 9.5 Information Center for Linux, UNIX, and Windows

Set diaglevel to appropriate value as explained below:

# 1 – Severe errors only
# 2 – All errors
# 3 – All errors and warnings

A tip and a warning on this subject:
- Tip: execute "db2diag -A" once a day/week/month. This will start a fresh copy of the db2diag file
- warning: on win2003 I noticed a complete freeze of DB2 when the db2diag file reaches 4Gb! Avoid this using above mentioned tip :-)

About stopping auto runstats, please check the following article:
Automatic table maintenance in DB2, Part 1: Automatic statistics collection in DB2 for Linux, UNIX, and Windows