home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC76441 Status: Closed

AN ENTRY IS ADDED TO STATEMENT LIST PRIOR TO RESOLVING PACKAGE PATH
RESULTING INTO A LARGE MONITOR STATEMENT LIST.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
The problem only happen when customer is using the "set current 
package path" and db2 try to use the package that is not the 
default one. 
 
  When db2 work on a new statement, monitor code will try to 
check if the statement is new or not. If it is a new statement, 
it will create a new entry in the statement list. However, 
monitor code create the entry before RDS able to resolve the 
package path. So we got code to update the creator  in the 
statement list to the new creator. That is not correct. Because 
next time when the agent work on the same statement, Monitor 
will think it is a new statement and it will create other entry 
in the statement list again. And monitor end up with a huge 
statement list , as we can see in the customer case. 
 
Operating system and level: 
 
All system 
 
System setup 
 
All setup 
 
Diagnostic information: 
 
list application show lot of statement
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* For customers using set current package path.                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The problem only happen when customer is using the "set      * 
* current package path" and db2 try to use the package that is * 
* not the default one.                                         * 
*                                                              * 
*   When db2 work on a new statement, DB2 will try to check if * 
* the statement is new or not. If it is a new statement, it    * 
* will create a new entry in the statement list. However,  DB2 * 
* will create the entry before RDS is able to resolve the      * 
* package path. So DB2 updates the creator in the statement    * 
* list to the new creator. That is not correct. Because  next  * 
* time when the agent work on the same statement, Monitor will * 
* think it is a new statement and it will create other entry   * 
* in the statement list again. And monitor end up with a large * 
* statement list.                                              * 
* Operating system and level:                                  * 
*                                                              * 
* All system                                                   * 
*                                                              * 
* System setup                                                 * 
*                                                              * 
* All setup                                                    * 
*                                                              * 
* Diagnostic information:                                      * 
*                                                              * 
* list application show lot of statement                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.8 fixpak 4.                                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC77408 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.05.2011
28.09.2011
28.09.2011
Problem solved at the following versions (IBM BugInfos)
9.8.
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList