Link to home
Start Free TrialLog in
Avatar of data_bits
data_bitsFlag for United States of America

asked on

DB2 db2diag.log file filling up with messages about "db2 amy be looping"

What is causing these messages and how can I stop them? It is causing the db2diag.log file to grow and fill up the instance $HOME:

2013-12-30-02.04.51.933373-360 E1045018A501       LEVEL: Error
PID     : 18153686             TID  : 28511       PROC : db2sysc 0
INSTANCE: tcitest              NODE : 000         DB   : HQSNDBOX
APPHDL  : 0-1631               APPID: 192.168.65.205.51640.131230080441
AUTHID  : TCIHQ
EDUID   : 28511                EDUNAME: db2agent (HQSNDBOX) 0
FUNCTION: DB2 UDB, database monitor, sqm___special1, probe:999
MESSAGE : Warning: db2 MAY BE looping in lookup statment. Dumping out the statement list

2013-12-30-02.04.51.948195-360 E1045520A4816      LEVEL: Error
PID     : 18153686             TID  : 28511       PROC : db2sysc 0
INSTANCE: tcitest              NODE : 000         DB   : HQSNDBOX
APPHDL  : 0-1631               APPID: 192.168.65.205.51640.131230080441
AUTHID  : TCIHQ
EDUID   : 28511                EDUNAME: db2agent (HQSNDBOX) 0
FUNCTION: DB2 UDB, database monitor, sqm___special1, probe:0
DATA #1 : Pointer, 8 bytes
0x0780000002bb3be0
DATA #2 : Pointer, 8 bytes
0x0780000002ed9b20
DATA #3 : Hexdump, 840 bytes
ASKER CERTIFIED SOLUTION
Avatar of Kent Olsen
Kent Olsen
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of data_bits

ASKER

Thanks for the information, Kent. Looking at the link you posted, looks like a temporary workaround is to turn off the STATEMENT monitor switch.