DB2 - Problembeschreibung
Problem IC72595 | Status: Geschlossen |
DB2 may trap during database connection when user interrupt occurred | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
When multiple connections have issued at the same time, there existed a timing hole that if one connection hit user interrupt during catalog scan on audit catalog , it could cause a trap on another agent with following callstack: <StackTrace> sqleLookupAuditSettings sqlexGetConnectAuditSettings sqlexEngAuthenticate AppLocalStart sqlelostWrp sqleUCengnInit sqleUCagentConnect sqljsConnectAttach sqljs_ddm_accsec sqljsParseConnect .sqljsParse.fdpr.clone.29 @64@sqljsSqlam @64@sqljsDriveRequests @64@sqljsDrdaAsInnerDriver sqljsDrdaAsDriver RunEDU EDUDriver sqloEDUEntry </StackTrace> And similar db2diag.log entries could be found like the following: 2010-10-19-13.21.35.021278+480 I69375448A533 LEVEL: Error PID : 6631638 TID : 70644 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DB1 APPHDL : 0-44613 APPID: 10.42.1.58.4211.101019052103 AUTHID : adm EDUID : 70644 EDUNAME: db2agent (DB1) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_init, probe:222 RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT DETECTED" DIA8003C The interrupt has been received. 2010-10-19-13.21.35.021404+480 I69375982A825 LEVEL: Error PID : 6631638 TID : 70644 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DB1 APPHDL : 0-44613 APPID: 10.42.1.58.4211.101019052103 AUTHID : adm EDUID : 70644 EDUNAME: db2agent (DB1) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_init, probe:222 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0 sqlerrmc: sqlerrp : SQL09072 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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * When multiple connections have issued at the same time, * * there existed a timing hole that if one connection hit user * * interrupt during catalog scan on audit catalog , it could * * cause a trap on another agent with following callstack: * * * * <StackTrace> * * * * sqleLookupAuditSettings * * sqlexGetConnectAuditSettings * * sqlexEngAuthenticate * * AppLocalStart * * sqlelostWrp * * sqleUCengnInit * * sqleUCagentConnect * * sqljsConnectAttach * * sqljs_ddm_accsec * * sqljsParseConnect * * .sqljsParse.fdpr.clone.29 * * @64@sqljsSqlam * * @64@sqljsDriveRequests * * @64@sqljsDrdaAsInnerDriver * * sqljsDrdaAsDriver * * RunEDU * * EDUDriver * * sqloEDUEntry * * </StackTrace> * * * * And similar db2diag.log entries could be found like the * * following: * * * * * * 2010-10-19-13.21.35.021278+480 I69375448A533 LEVEL: * * Error * * PID : 6631638 TID : 70644 PROC : * * db2sysc * * 0 * * INSTANCE: db2inst1 NODE : 000 DB : DB1 * * APPHDL : 0-44613 APPID: * * 10.42.1.58.4211.101019052103 * * AUTHID : adm * * EDUID : 70644 EDUNAME: db2agent (DB1) 0 * * FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_init, * * probe:222 * * RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER * * INTERRUPT * * DETECTED" * * DIA8003C The interrupt has been received. * * * * 2010-10-19-13.21.35.021404+480 I69375982A825 LEVEL: * * Error * * PID : 6631638 TID : 70644 PROC : * * db2sysc * * 0 * * INSTANCE: db2inst1 NODE : 000 DB : DB1 * * APPHDL : 0-44613 APPID: * * 10.42.1.58.4211.101019052103 * * AUTHID : adm * * EDUID : 70644 EDUNAME: db2agent (DB1) 0 * * FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_init, * * probe:222 * * DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes * * sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0 * * sqlerrmc: * * sqlerrp : SQL09072 * * 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: * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 version 9.7 fix pack 4. * **************************************************************** | |
Local-Fix: | |
Activate the database at catalog node before starting any database connection. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
This fix will be included in db2 version 9.7 fix pack 4. | |
Workaround | |
Activate the database at catalog node before starting any database connection. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.11.2010 03.05.2011 03.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |