Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC89502 Status: Closed

SQLMTABLEITERATOR::EXECUTE SQLM_RC_MON_BUFFER_FULL ERROR MESSAGE SHOULD NOT
BE RAISED IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This message can be seen in the db2diag.log : 
 
FUNCTION: DB2 UDB, database monitor, sqlmTableIterator::execute, 
probe:453 
CALLED  : DB2 UDB, database monitor, sqlmTableIterator::execute 
RETCODE : ZRC=0x850D008C=-2062745460=SQLM_RC_MON_BUFFER_FULL 
          "The Database System Monitor output buffer is full" 
 
 This message is written to the db2diag.log when a snapshot was 
requested from the server side and the supplied buffer size was 
not 
sufficient to contain the full snapshot. 
This is expected behaviour and translates to a message : 
 
SQL1606W  The Database System Monitor output buffer is full. 
 
sent to the client. 
The client code ( e.g. CLP ) normally then chooses to resubmit 
the snapshot request with a bigger buffer size, hence the issue 
should be transparent to the user. 
 
The error message should hence not be written to the db2diag.log 
as it leads to confusion.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.1 Fix Pack 3              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
This problem was first fixed in DB2 V10.1 Fix Pack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91698 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.01.2013
21.10.2013
21.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList