DB2 - Problem description
Problem IT18850 | Status: Closed |
IF NODE FAILURE RECOVERY OCCURS AFTER END OF TRANSACTION, THE NEXT OPERATION CAN RECEIVE SQL1229 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
In a DPF instance if an application has ended its transaction and then node failure recovery occurs that application can receive SQL1229 on its next operation as the application is interrupted with a NODE FAILURE interrupt like below. 2016-11-05-16.05.43.929695+540 E34581281A980 LEVEL: Severe PID : 5701754 TID : 5656 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DBNAME APPHDL : 0-797 APPID: application1 AUTHID : DB2INST1 HOSTNAME: hostname EDUID : 5656 EDUNAME: db2agent (DBNAME) 0 FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20 DATA #1 : String, 92 bytes Due to node failure at node 0 received sqlcode -1229 for request 80000000 from node number 0 DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1229 sqlerrml: 0 sqlerrmc: sqlerrp : SQLE058 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DPF or pureScale user * **************************************************************** * PROBLEM DESCRIPTION: * * This fix will be in APAR IT21845 on Db2 V11.1 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 11.1 with the fix * **************************************************************** | |
Local Fix: | |
Retry the failed transaction, or re-connect to the database after -1229 error | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : follow-up : IT21845 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.01.2017 21.06.2018 21.06.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |