DB2 - Problembeschreibung
| Problem IC96553 | Status: Geschlossen |
SQL0901N ERROR TRIGGERED IN SQLKTSND:AT SANITY CHECK IN CODE | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problembeschreibung: | |
DB2 can trigger an SQL0901N error in sqlktsnd at a sanity check
in the code resulting
in the corresponding query failing. db2diag.log messages like
the following will be seen:
2013-09-05-08.25.52.151404-300 I492603840E590 LEVEL:
Error
PID : 23393 TID : 46955535263488 PROC :
db2sysc 80
INSTANCE: db2admn NODE : 080 DB :
SAMPLE
APPHDL : XXX-34385 APPID: *NXXX.db2admn.130905131925
AUTHID : DB2INST1 HOSTNAME: db2inst1
EDUID : 433525 EDUNAME: db2agntp (SAMPLE) 80
FUNCTION: DB2 UDB, buffer Q services, sqlkq_error, probe:50
MESSAGE : DIA0001E An internal error occurred. Report the
following error code
: "Not enough pro-active resets. numResets = 51, count
= 64".
2013-09-05-08.26.09.059594-300 I492604431E611 LEVEL:
Error
PID : 23393 TID : 46955535263488 PROC :
db2sysc 80
INSTANCE: db2admn NODE : 080 DB :
SAMPLE
APPHDL : XXX-34385 APPID: *NXXX.db2admn.130905131925
AUTHID : DB2INST1 HOSTNAME: db2inst1
EDUID : 433525 EDUNAME: db2agntp (SAMPLE) 80
FUNCTION: DB2 UDB, table Q services, sqlktsnd, probe:100
MESSAGE : DIA0001E An internal error occurred. Report the
following error code
: "Line=00878, rc1=0x82180001, rc2=0x00000000,
rc3=(nil),
msg=sqlkqsnd()". | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Any users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to V10.1 Fixpack 4 or later * **************************************************************** | |
| Local-Fix: | |
N/A | |
| verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
| Lösung | |
Problem first fixed in V10.1 Fixpack 4 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC96946 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.10.2013 18.06.2014 18.06.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.1.0.4 |
|