DB2 - Problem description
| Problem IC73941 | Status: Closed |
EXCESSIVE DB2DIAG.LOG ERROR REPORTING FOLLOWING "WARNING: DB2 MAY BE LOOPING IN LOOKUP STATMENT." MESSAGE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
V9.7 Fixpak 3 contains a fix for apar IC67240
As part of the fix, debug code was added but that may get
triggered in normal circumstances
( e.g. when a connection has more than 100 open cursors ) which
may lead to excessive unnecessary error reporting in the
db2diag.log.
The messages will start with "WARNING: DB2 MAY BE LOOPING IN
LOOKUP STATMENT."
for example the following shell script may trigger the problem
from CLP :
i=200
while [ $i -gt 100 ]
do
db2 +c "declare c$i cursor for values ( $i )"
db2 +c "open c$i"
i=`expr $i - 1`
done
while [ $i -gt 0 ]
do
db2 +c "declare c$i cursor with hold for values ( $i )"
db2 +c "open c$i"
i=`expr $i - 1`
done
db2 commit | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * Excessive db2diag.log messages. * **************************************************************** * RECOMMENDATION: * * upgrade to V9.7 Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
Turn off the statement monitor switch Identify the application/connection with a high number of open cursors and alter the application.( e.g. more frequent commits ) | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
| Solution | |
The problem has first been fixed in v9.7 Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.01.2011 22.12.2011 22.12.2011 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.5 |
|