DB2 - Problembeschreibung
| Problem IC95362 | Status: Geschlossen |
FALSE COMMUNICATION ERROR DETECTED BETWEEN DB2FMP PROCESS AND DB2 EDU LEADING TO INCORRECT SQL1646N ERROR RETURNED | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
| verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Lösung | |
This problem was first fixed in V10.5 Fix Pack 3 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.08.2013 27.02.2014 27.02.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.5.0.3 |
|
| 10.5.0.3 |
|