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
data_bitsAsked:
Who is Participating?
 
Kent OlsenConnect With a Mentor Data Warehouse Architect / DBACommented:
Hi data_bits,

That's one of the system errors that I find interesting (and amusing).  It's caused by debug code that IBM added in version 9.5.  The warning was triggered more often than expected and became both a problem and a nuisance.  IBM fixed it a couple of fixpacks later.

  http://www-01.ibm.com/support/docview.wss?uid=swg1IC72701

You're probably running DB2 V9.5 with fixpack 5, 6, or 7.  Updating to fixpack 8 will solve this.


Good Luck,
Kent
0
 
data_bitsAuthor Commented:
Thanks for the information, Kent. Looking at the link you posted, looks like a temporary workaround is to turn off the STATEMENT monitor switch.
0
All Courses

From novice to tech pro — start learning today.