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 IC95405 Status: Geschlossen

SQL STATEMENT MAY HANG DUE TO A DEADLATCH WHEN PROCESSING SUBSECTIONS OF A
ZIG ZAG JOIN PLAN

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The hang can be observed in db2pd -latches e.g. : 
 
Database Member 1 -- Active -- Up 0 days 05:21:19 -- Date 
2013-03-21-09.49.47.079454 
 
Latches: 
Address            Holder     Waiter     Filename 
LOC        LatchType            HoldCount 
0x07000000200147A8 11117      11374      |B9               8574 
SQLO_LT_SQLD_APP_CB__inDMSlatch 1 
0x0700000030CB55D8 11374      11117      c                   207 
SQLO_LT_SQLP_SAVEPOINTS__spLatch 1 
 
i.e. the holder of both latches wait on each other to release 
their latch. 
 
both EDUs are subagents running the same SQL statement. 
 
The stack for both subagents may look like : 
 
sqloXlatchConflict 
sqlpGetSPLatch 
sqlpSpReq 
sqldRowInsert 
sqlrinsr 
sqlritib2 
sqldEvalDataPred 
sqldReadNorm 
sqldFetchNext 
sqldfrd 
sqldRowFetch 
sqlritaSimplePerm 
sqlriZZOpenDims 
sqlriZZInit 
sqlriZigZagJoin 
sqlriSectInvoke 
sqlrr_dss_router 
sqlrr_subagent_router 
 
Subagent 2 has : 
 
getConflictComplex 
getConflict 
sqldRowInsert 
sqlrinsr 
sqlriisr 
sqlriSectInvoke 
sqlrr_dss_route 
sqlrr_subagent_router 
 
Once the hang occurs, the instance will need to be restarted by 
running db2_kill ( db2stop force will hang )
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to v10.5 Fix Pack 3 or higher.   * 
****************************************************************
Local-Fix:
disable the use of of Zig Zag joins : 
db2set DB2_REDUCED_OPTIMIZATION="ZZJN OFF"
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
This problem was first fixed in v10.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 FixList
10.5.0.3 FixList
10.5.0.4 FixList