DB2 - Problembeschreibung
Problem IC95233 | Status: Geschlossen |
SQLCODE -1229 RECEIVED ON DB2LUSED CONTINUOSLY EVEN AFTER A LOT OF TIME HAS PASSED AFTER THE LAST NODE RECOVERY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In DPF systems, users may observe that the db2lused continues to get the below error messages continuously even after a node recovery has completed successfully much in the past: ---------------------------------------------------------------- ------------- AUTHID : XXXXX HOSTNAME: XXXXXX EDUID : 11053 EDUNAME: db2lused (DATABASE_NAME) 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 80000004 from node number 0 DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1229 sqlerrml: 49 sqlerrmc: X SRC_CODEPAGE DATABASE_NAME OS_DETAILS DESTINATION_CODEPAGE sqlerrp : SQLRR06A sqlerrd : (1) 0x81580016 (2) 0x00000016 (3) 0x00000000 (4) 0x00000003 (5) 0xFFFFFB50 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: ---------------------------------------------------------------- ----------- After a node failure the sqlca is set with -1229. When the node recovery completes and returns from the corresponding functions, the sqlca is not reset. So this -1229 from a previous node failure gets dumped in sqleMergeSqlca and thus logged continuously as seen above. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description Above * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 3. * **************************************************************** | |
Local-Fix: | |
N/A | |
verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in Version 10.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 |