|
Problem IC98722
|
Status: Geschlossen |
DB2 WILL WAIT FOR MORE THAN 8 HOURS FOR TSA TO CHANGE RESOURCE LOCK STATE APPEARING AS A HANG |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
When TSA has a problem locking a resource group, as requested by
DB2, then DB2 will spin for more than 8 hours waiting for TSA to
change the lock state before returning an error. This can be hit
during create/drop DB commands.
Reduce this time so that an error is returned much sooner when
TSA fails to lock the resource group.
Symptoms:
"DROP DATABASE" command lasted 2 hours. Instance was hung. CPU
usage was 80 to 100%. All
new connections hung. 3000+ in run queue as shown in vmstat.
FORCE APPLICATIONS kicks them all out, but within seconds, the
run queue is filled again."
Using db2pd tool to dump stacks, the following two stacks show
the problem codepath:
00000032C660E4EB read + 0x002b
(/lib64/libpthread.so.0)
0x00007FA21578949E sqloReadNamedPipe + 0x00be
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA216EEA637 sqloInvokeVendorFunction + 0x00b7
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215F071E5 _Z26sqlhaDisableResourceGroup2jPvS_i + 0x0205
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215EFC3D6 sqlhaDisableResourceGroup + 0x0066
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215F2E769
_Z31sqlhaSDMountDependencyOperationPKciP19SQLHA_CONTROL_BLOCK +
0x08b9
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215F2D1D8
_Z34sqlhaDeleteConcurrentMountInternalP14mountInfoBlockP19SQLHA_
CONTROL_BLOCK + 0x0618
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215F1B4C3
_Z24sqlhaDeleteClusterObjectP25SQLHA_CLUSTER_OBJECT_INFOP19SQLHA
_CONTROL_BLOCK + 0x0b73
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215F2BE44 _Z16sqlhaDeleteMountPKcS0_s + 0x0394
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA215F56C6B _Z15sqlhaRemoveHADBPc + 0x037b
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA2164F1B80 _Z16sqleDropDatabasePcS_S_bbP5sqlca + 0x1620
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA2164F2976 _Z14sqledrpd_agentP5sqldabP5sqlca + 0x03c6
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA214F1F2BF
_Z19sqlerKnownProcedureiPcPiP5sqldaS2_P13sqlerFmpTableP8sqeAgent
P5sqlca + 0x064f
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA214F2111D _Z11sqlerCallDLP14db2UCinterfaceP9UCstpInfo +
0x05ad
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA217C64AB4
_Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject +
0x08e4
(/home/db2instance/sqllib/lib64/libdb2e.so.1)
0x00007FA217C61E6E
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14
3875.3713763104.000.stack.txt shows
StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00007F91E5630DBA
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm +
0x020a
(/drouter/V101Linux/lib64/libdb2osse.so.1)
0x00007F91E5630B4B ossDumpStackTraceV98 + 0x002b
(/drouter/V101Linux/lib64/libdb2osse.so.1)
0x00007F91E562BA73 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x0103
(/drouter/V101Linux/lib64/libdb2osse.so.1)
0x00007F91E562D9E9 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009
(/drouter/V101Linux/lib64/libdb2osse.so.1)
0x0000000000406771 db2vendCodeTrapHandler + 0x0301
(db2havend (db2ha))
0x0000003A6A632900 address: 0x0000003A6A632900 ; dladdress:
0x0000003A6A600000 ; offset in lib: 0x0000000000032900 ;
(/lib64/libc.so.6)
0x0000003A6A6AAB9D nanosleep + 0x002d
(/lib64/libc.so.6)
0x00007F91DB12EC6C sqlhausleep + 0x003c
(/home/db2instance/sqllib/lib64/libdb2tsa.so)
0x00007F91DB12E16B db2haDisableResourceGroup + 0x048b
(/home/db2instance/sqllib/lib64/libdb2tsa.so)
0x000000000040A173 _Z26_sqlhaDisableResourceGroupjPv + 0x00e3
(db2havend (db2ha))
0x00000000004072A9 _Z25sqlhaInvokeVendorFunctionPv + 0x0269
(db2havend (db2ha))
0x0000000000405F66 main + 0x05a6
(db2havend (db2ha))
0x0000003A6A61ECDD __libc_start_main + 0x00fd
(/lib64/libc.so.6)
0x0000000000405929 pdOSSeLoggingCallback + 0x0261
(db2havend (db2ha))
</StackTrace> |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* DB2 Purescale *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product DB2 V10.1.0.4 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
Fixed in DB2 V10.1.0.4 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 14.01.2014
02.06.2014
02.06.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.4
|
 |
