home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC63340 Status: Geschlossen

LOADING LOCK DISAPPEARS IN XML WORKLOAD WHICH WILL CAUSE THE SYSTEM TO
CRASH WITH A -901 ERROR.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
This issue is a concurrency issue, and it only occurs in DPF and 
with XML related workloads. The problem arise when one agent is 
driving an authentication of an XML statement on all nodes while 
a commit occurs immediately after. There is a very small timing 
window in which the commit would free the lock when some remote 
nodes returns to the application but before all the remote nodes 
could return, which would cause the system to crash with a -901 
error. 
 
You would see the following in the db2diag.log: 
 
2009-04-26-14.32.20.198198-240 I34032826A457 LEVEL: Severe 
PID : 1589248 TID : 36711 PROC : db2sysc 2 
INSTANCE: svtdbm10 NODE : 002 DB : ABSINTHE 
APPHDL : 0-9077 APPID: 9.26.48.232.44508.090427133552 
AUTHID : SVTDBM10 
EDUID : 36711 EDUNAME: db2agntp (ABSINTHE) 2 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:250 
RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown" 
 
2009-04-26-14.32.20.277133-240 I34034102A850 LEVEL: Severe 
PID : 1589248 TID : 36711 PROC : db2sysc 2 
INSTANCE: svtdbm10 NODE : 002 DB : ABSINTHE 
APPHDL : 0-9077 APPID: 9.26.48.232.44508.090427133552 
AUTHID : SVTDBM10 
EDUID : 36711 EDUNAME: db2agntp (ABSINTHE) 2 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 18 
sqlerrmc: loading lock error 
sqlerrp : SQLRC00B 
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 
(4) 0x00000000 (5) 0xFFFFFFA6 (6) 0x00000002 
sqlwarn : (1) (2) (3) (4) (5) (6) 
(7) (8) (9) (10) (11) 
sqlstate: 
 
2009-04-26-14.32.20.294582-240 I34034953A175 LEVEL: Severe 
PID:1589248 TID:36711 NODE:002 Title: SQLCA 
Dump 
File:/home/svtdbm10/sqllib/db2dump/1589248.36711.002.dump.bin 
 
2009-04-26-14.32.20.326425-240 I34035129A175 LEVEL: Severe 
PID:1589248 TID:36711 NODE:002 Title: DB2RA 
Dump 
File:/home/svtdbm10/sqllib/db2dump/1589248.36711.002.dump.bin 
 
2009-04-26-14.32.20.362263-240 I34035305A531 LEVEL: Severe 
PID : 1589248 TID : 36711 PROC : db2sysc 2 
INSTANCE: svtdbm10 NODE : 002 DB : ABSINTHE 
APPHDL : 0-9077 APPID: 9.26.48.232.44508.090427133552 
AUTHID : SVTDBM10 
EDUID : 36711 EDUNAME: db2agntp (ABSINTHE) 2 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:400 
MESSAGE : CREATOR 
DATA #1 : Hexdump, 8 bytes 
0x0700000017542358 : 4E55 4C4C 4944 2020 
 
 
Call Stack: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000547450 pthread_kill + 0xB0 
0x0900000024CFC48C sqloDumpEDU + 0x4C 
0x0900000024F59958 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0x138 
0x0900000024E2EBE4 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x644 
0x0900000024E27978 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x58 
0x0900000024E28258 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x378 
0x0900000024E23E68 sqlrrSqlCode + 0x2C8 
0x0900000026034FE4 
sqlrlc_auth_update_entries__FP8sqlrr_cbP21sqlrlc_auths_requiredU 
iP14SQLP_LOCK_INFOPbUl 
+ 0xA44 
0x090000002602F95C 
sqlrlc_sda_get_auths__FP8sqlrr_cbP21sqlrlc_auths_requiredUiPUc + 
0xAFC 
0x090000002603099C 
sqlrlc_sda_request_auths__FP8sqlrr_cbP11sqlr_aainfo + 0x5FC 
0x0900000024E20A40 
sqlrr_set_authinfo__FP8sqlrr_cbPcsUcP11sqlo_xlatchPP14sqlrr_auth 
info 
+ 0x940 
0x0900000026AC19A8 
sqlrr_get_authinfo__FP8sqlrr_cbPcscP11sqlo_xlatchPP14sqlrr_authi 
nfo 
+ 0x108 
0x0900000026AC2194 sqlra_set_stmt_authid__FP8sqlrr_cbiPcT2c + 
0x6F4 
0x0900000026A05204 
sqlriReceiveDss__FP8sqlrr_cbP16sqlkdRqstRplyFmtPl + 0x5A4 
0x090000002938FD78 sqlrr_dss_router__FP8sqlrr_cb + 0x418 
0x09000000293943DC 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x15BC 
0x0900000027B2B430 sqleSubRequestRouter__FP8sqeAgentPUiT2 + 
0xAD0 
0x0900000027B35010 sqleProcessSubRequest__FP8sqeAgent + 0x190 
0x0900000024E0D870 RunEDU__8sqeAgentFv + 0x2F0 
0x0900000024DFD55C EDUDriver__9sqzEDUObjFv + 0x19C 
0x0900000024DFD87C sqlzRunEDU__FPcUi + 0x3C 
0x0900000024D0499C sqloEDUEntry + 0x69C 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all DB2 Version 9.7 GA on Linux, Unix and Windows platforms  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This issue is a concurrency issue, and it only occurs in DPF * 
* andwith XML related workloads. The problem arise when one    * 
* agent                                                        * 
* is driving an authentication of an XML statement on all      * 
* nodes                                                        * 
* whilea commit occurs immediately after. There is a very      * 
* small                                                        * 
* timing window in which the commit would free the lock when   * 
* some                                                         * 
* remote nodes returns to the application but before all the   * 
* remote nodescould return, which would cause the system to    * 
* crash                                                        * 
* with a -901 error.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 9.7 fix pack 1 and reissue activate        * 
* database                                                     * 
****************************************************************
Local-Fix:
No workaround
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem is fixed in DB2 Version 9.7 fix pack 1 and all 
subsequent fix packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.09.2009
04.01.2010
04.01.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList