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

UNDER RARE MEMORY CONDITIONS, STMM HASH JOIN SIMULATION MAY FAIL AND CAUSE
FODC TO BE PRODUCED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under rare memory conditions, STMM hash join simulation may fail 
and cause FODC to be produced. 
Message similar to the following one will be logged to db2diag: 
 
2013-07-26-11.48.28.691779+120 I539681A880          LEVEL: 
Severe 
PID     : 30081048             TID : 13367          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : DBC2 
APPHDL  : 0-22952              APPID: 
192.168.1.1.50075.130726094828 
AUTHID  : DB2INST1             HOSTNAME: localhost 
EDUID   : 13367                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 15 
 sqlerrmc: numPartitions=0 
 sqlerrp : SQLRI0F7 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFF517      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
The top of the stack trace in FODC_AppErr_<timestamp> 
subdirectory will show: 
sqlri_hsjnCalculateNumPartitions 
stmmSimulateSingleHJInit 
stmmSimulateHJInits 
stmmStartHJMonitor 
sqlri_hsjnInit 
 
This APAR will change this behavior and FODC will no longer to 
be produced.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95668 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.08.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList