DB2 FOR LUW / DB2FORLUW / A10 - DB2

When an access plan that contains Hash Join is executed and the 
statics are not up-to-date or the memory settings are not 
configured properly on the system, then the lack of memory can 
result in SQL0901N error with token "no tuple blocks" and 
FODC_AppErr get generated with the following db2diag.log entry 
and stack traces: 
 
db2diag.log: 
 
2014-08-07-18.53.33.944258+120 I60013290A244      LEVEL: Severe 
PID:9437224 TID:58635 NODE:000 Title: MASTER TIME INFO 
Dump 
File:/testdb/testdb3/sqllib/db2dump/FODC_AppErr_2014-08-07-18.55 
.36.00000_0000000_11111_000/0000000.11111.000.dump.bin 
 
2014-08-05-18.45.31.335024+120 I26498719A887        LEVEL: 
Severe 
PID     : 9437224              TID : 47647          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
testdb 
APPHDL  : 0-33801              APPID: 0.0.0.0.0.0 
AUTHID  : test3                 HOSTNAME: testserver1 
EDUID   : 47647                EDUNAME: db2agent (testdb) 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: no tuple blocks 
 sqlerrp : SQLRI109 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFED1B      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
 Stack trace: 
 
<StackTrace> 
 
  pthread_kill 
  sqloDumpEDU 
  sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 
  sqlrr_dump_ffdc__FP8sqlrr_cbiT2 
  sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai 
  sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc 
  sqlrrSqlCode 
 
sqlri_hsjnLoadTupleCollection__FP8sqlrr_cbP11sqlri_hsjnoP25sqlri 
_hsjnPartitionBucketPb 
  sqlri_hsjnLeftoversReturnMatch__FP8sqlrr_cbP11sqlri_hsjno 
  sqlrihsjn__FP8sqlrr_cb 
  sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm 
 
</StackTrace>

**************************************************************** 
* USERS AFFECTED:                                              * 
* plans with HSJN                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install this APAR                                            * 
****************************************************************

- Update Statistics by running the RUNSTATS. 
 
- Increase the size of the SORTHEAP value. 
 
- Set DATABASE_MEMORY and INSTANCE_MEMORY to AUTOMATIC. 
 
- Enable STMM tuning.

See Error Description

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

08.09.2014
06.10.2015
06.10.2015