DB2 FOR LUW / DB2FORLUW / A10 - DB2

A call statement may fail with  error SQL1646 when the procedure 
has large parameters. 
 
e.g. 
 
call out_language('aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa', 
'aaaaaaaaaaaaaa', 'aaaaaaaaaaaaaa', 'aaaaaaaaaaaaaa', ... 
<multiple lines> 
'aaaaaaaaaaaaaa') 
 
SQL1646N  A routine failed because the fenced user ID cannot 
access required 
files in the sqllib directory or other instance or database 
directories. 
 
The db2diag.log will show : 
 
2013-04-25-22.30.13.668443-240 I519396E550           LEVEL: 
Severe 
PID     : 26504                TID : 46913126656320  KTID : 
26519 
PROC    : db2sysc 
INSTANCE: db2inst1             NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.130426022958 
AUTHID  : DB2INST1             HOSTNAME: server1 
EDUID   : 18                   EDUNAME: db2agent (SAMPLE) 
FUNCTION: DB2 UDB, routine_infrastructure, sqlerSendFmpStart, 
probe:30 
RETCODE : ZRC=0xFFFFFBEE=-1042 
          SQL1042C  An unexpected system error occurred. 
 
This is a condition that should only happen when the size of the 
parameter list is sufficiently large relative to the ASLHEAPSZ 
dbm cfg setting. 
If the problem is hit, using a different setting of ASLHEAPSZ 
would prevent the problem. 
Additionally, the condition is very timing dependent and should 
be rare to hit.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.1 Fix Pack 3              * 
****************************************************************

alter the value of ASLHEAPSZ

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
 

This problem was first fixed in DB2 V10.1 Fix Pack 3

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95362 IT01381 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

30.04.2013
21.10.2013
21.10.2013