Solved

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

Posted on 2013-12-30
2
1,256 Views
Last Modified: 2013-12-30
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
0
Comment
Question by:data_bits
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 45

Accepted Solution

by:
Kent Olsen earned 500 total points
ID: 39746077
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
 

Author Comment

by:data_bits
ID: 39746105
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

Featured Post

Guide to Performance: Optimization & Monitoring

Nowadays, monitoring is a mixture of tools, systems, and codes—making it a very complex process. And with this complexity, comes variables for failure. Get DZone’s new Guide to Performance to learn how to proactively find these variables and solve them before a disruption occurs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recursive SQL in UDB/LUW (you can use 'recursive' and 'SQL' in the same sentence) A growing number of database queries lend themselves to recursive solutions.  It's not always easy to spot when recursion is called for, especially for people una…
Recursive SQL in UDB/LUW (it really isn't that hard to do) Recursive SQL is most often used to convert columns to rows or rows to columns.  A previous article described the process of converting rows to columns.  This article will build off of th…
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question