DB2 - Problem description
Problem IT25536 | Status: Closed |
SQLKD_SYSERR MAPPED TO -902 BY RUNTIME, CAUSING DATABASE MARKED BAD. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When a closed buffer insert does not complete, Db2 is returning -902 error after an FODC_AppErr which leads to an FODC_Panic causing Db2 to crash and mark the database as bad. The error returned should be -901 which will only give an FODC_AppErr and not an FODC_Panic, thus Db2 carries on running. The following db2diag.log can also be observed. 2018-06-27-11.40.43.160836-240 I792466B392 LEVEL: Severe PID : 90374834 TID : 20234 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-85 APPID: *N0.db2inst1.111222154987 AUTHID : DB2INST1 HOSTNAME: testhost EDUID : 20234 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data management, sqldInvCursorPos, probe:4145 MESSAGE : Scan not allowed to be open during ROLLBACK. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 LUW Users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW 10.5 Fix Pack 11 or later * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : follow-up : IT25578 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.06.2018 25.02.2020 25.02.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |