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

FALSE COMMUNICATION ERROR DETECTED BETWEEN DB2FMP PROCESS AND DB2 EDU
LEADING TO INCORRECT SQL1646N ERROR RETURNED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.5 Fix Pack 3 or higher.   * 
****************************************************************
Local Fix:
alter the value of ASLHEAPSZ
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
This problem was first fixed in V10.5 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList