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 IC67958 Status: Closed

IN DPF, POSSIBLE TRAP WHEN RUNNING TABLE FUNCTION MON_GET_UNIT_O F_WORK OR
MON_GET_UNIT_OF_WORK_DETAILS IN LOW MEMORY SITUATION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In DPF, possible trap when running table function 
MON_GET_UNIT_OF_WORK or MON_GET_UNIT_OF_WORK_DETAILS in low 
memory situation 
 
In db2diag.log, it would have the following entry: 
2010-04-06-10.53.31.245643-240 I1756350894A577    LEVEL: Error 
PID     : 8622252              TID  : 39730       PROC : db2sysc 
30 
INSTANCE: svtdbm7              NODE : 030         DB   : LNXXML 
APPHDL  : 5-1051               APPID: *N5.svtdbm7.100406145312 
AUTHID  : SVTDBM7 
EDUID   : 39730                EDUNAME: db2agntp (LNXXML) 30 
FUNCTION: DB2 UDB, WLM, sqlrwGetWorkloadOccurrenceMetrics, 
probe:30 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
           DIA8301C No memory available in the application heap. 
 
The stack trace would be similar to the following: 
<StackTrace> 
sqlrwSendGetWLMTableFunctionResult 
sqlrwGetWLMTableFunctionMergedResult 
sqlerTrustedRtnCallbackRouter 
monGetUnitOfWorkMetricsFromEngn 
monGetUnitOfWork 
sqloInvokeFnArgs 
sqlriInvokerTrusted 
sqlriInvokeInvoker 
sqlriutf 
sqlri_tfopn 
sqlriopn 
sqlriopn 
sqlrita 
sqlriSectInvoke 
sqlrr_process_fetch_request 
sqlrr_open 
sqljs_ddm_opnqry 
sqljsParseRdbAccessed 
.sqljsParse.fdpr.clone.477 
@64@sqljsSqlam 
@64@sqljsDriveRequests 
@64@sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
RunEDU 
EDUDriver 
sqloEDUEntry 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems on all Linux, Unix and Windows platforms at  * 
* service levels from Version 9.7 GA through to Version 9.7    * 
* Fix Pack 1.                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 2 or see "Local Fix"     * 
* portion for other suggestions.                               * 
****************************************************************
Local Fix:
Increase application heap
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The complete fix for this problem first appears in DB2 Version 
9.7 Fix Pack 2 and all the subsequent Fix Packs.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67959 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.04.2010
26.04.2010
26.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList