MESSAGE: Warning: db2 MAY BE looping in lookup statement.

Technote (troubleshooting)


Problem(Abstract)

Review of db2diag.log reveals numerous messages indicating 'db2 MAY BE looping in lookup statement'. In addition, the size in megabyte of the db2diag.log may become very large due to these statements and requires cleanup.

Symptom

Large in megabyte size db2diag.log file due to excessive error messages similar to the below:

2013-08-14-01.11.29.973000-240 E523732658F503 LEVEL: Error
PID : 3412 TID : 11560 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TPCDB
APPHDL : 0-4093 APPID: 172.20.220.26.14079.13081405003
AUTHID : DB2ADMIN
EDUID : 11560 EDUNAME: db2agent (TPCDB) 0
FUNCTION: DB2 UDB, database monitor, sqm___special1, probe:516
MESSAGE : Warning: db2 MAY BE looping in lookup statement. Dumping out the statement list

Cause

db2 9.7.04 contains debug code which may lead to excessive and unnecessary error reporting.


Review the following link to obtain additional information:

IC73941


Environment

TPC 5.1.x and db2 9.7 Fix Pack 4

Diagnosing the problem

Review of db2diag.log shows the symptom message is repeated in high repetition.

Resolving the problem

There are two methods to resolve the messages being repeated:


Note: commands should be run when logged in as instance owner or a user
with db2admin authority:

1. Work Around: Disable the statement monitor

>db2 UPDATE MONITOR SWITCHES USING statement OFF

If applicable, read additional details regarding the above command and its arguments via the following link(s):

UPDATE MONITOR SWITCHES COMMAND

System monitor switches control how snapshot monitors and some event monitors collect data, additional details are explained in the following link:

System Monitor Switches

2. Upgrade db2 9.7.0.4 to a more recent and supported Fix Pack as follows:

This fix is included in DB2 9.7 Fix Pack 5+.

To resolve this, you can apply the supported DB2 9.7 Fix Pack 6 or the supported Fix Pack 8 as per the TPC Support Matrix.

3. It may be necessary to archive and create new the current db2diag.log , as the size in megabytes may potentially have grown very large due the erroneous messages.

i.e. Windows:
Open a db2 command window as follows:
Start -> All Programs -> IBM DB2 -> Command Line Tools -> Command Window
Run the following Command:
>db2diag -A

Unix:
>su - db2inst1
>cd /home/db2inst1/sqllib/bin
>db2diag -A

*where db2inst1 = the db2 instance owner user_id relevant to the environment in question..


Related information

IC73941
UPDATE MONITOR SWITCHES COMMAND
System Monitor Switches
TPC Support Matrix - Databases

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Productivity Center

Software version:

5.1, 5.1.1

Operating system(s):

AIX, Solaris, Windows

Reference #:

1647199

Modified date:

2013-08-16

Translate my page

Machine Translation

Content navigation