|
Problem IC84605
|
Status: Geschlossen |
DB2 PERFORMANCE ISSUE WHEN XML DATA IS BEING USED HEAVILY. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
If XML data is being used heavily, users may experience
performance issues.
From the stack analysis, latch contention can be seen during XML
temp table handling.
Stacks may look similar to the following:
0x0900000011646384 sqloXlatchConflict + 0x284
0x090000001164603C sqloXlatchConflict@glue1A5 + 0x78
0x0900000011798380 captureLatch__12SMemBasePoolFv + 0x54
0x09000000117970BC sqlogmblkEx + 0x2D8
0x0900000011833524
sqldAllocEmptyTCB__FP8sqeAgentPP8SQLD_TCBiN23UlT3UiT8 + 0xB4
0x0900000011833238
sqldAllocEmptyTCB__FP8sqeAgentPP8SQLD_TCBiN23UlT3UiT8@glueA46 +
0x94
0x090000000DD80C5C
@102@sqldCreateDAT__FP8sqeAgentPUsN32UiT6UlT8iN310_P10SQLD_FIELD
P12SQLD_COLINFOP15SQLD_RCTCOLINFOT10_PiPP8SQLD_TCBPcUsN221_T6 +
0x748
0x090000001152FF50
sqldInternalCreateTable__FP8sqeAgentP19SQLD_TABLECREATE_CB +
0x3C4
0x090000001152FAB8
sqldTableCreateTemp__FP8sqeAgentPUsT2UcUlT5iP10SQLD_FIELDP12SQLD
_COLINFOT7 + 0x1AC
0x090000000E4C2290 xmlsCreateTempXDA__FP8sqeAgentPP8SQLD_TCB +
0x1F0
0x090000000D8E95F4
xmls_InsertTempCSLRecord__FP11XMLSTORE_CBUiPPcPUsR8XMLS_XIDb +
0x4F0
0x090000000DD60274
flushRecord__18XmlrnTempRecordMgrFP11XMLSTORE_CBUiPPcPUsR8XMLS_X
ID + 0x1F0
0x090000000D8E9F40 flush__17xmlDataDescriptorFP11XMLSTORE_CBUc
+ 0x340
0x090000000ECCEE50
addItemSubtree__13XmlrnSequenceFP17xmlDataDescriptor + 0x124
0x0900000010224A10 sqlriXAgg__FP8sqlrr_cb + 0x320
or
0x0900000011646384 sqloXlatchConflict + 0x284
0x090000001164603C sqloXlatchConflict@glue1A5 + 0x78
0x0900000011798380 captureLatch__12SMemBasePoolFv + 0x54
0x0900000011797708 sqlofmblkEx + 0x180
0x09000000118412A4 sqldFreeTCB__FP16sqeLocalDatabaseP8SQLD_TCB
+ 0x980
0x090000001184237C
sqldDelTCB__FP8sqeAgentP16sqeLocalDatabaseP8SQLD_TCB + 0xCC
0x0900000011841FFC
sqldDropTable__FP8sqeAgentP12SQLB_GLOBALSP8SQLD_TCBi + 0x174
0x090000000E0C1F28
sqldDropTable__FP8sqeAgentP12SQLB_GLOBALSP8SQLD_TCBi@glue3C4 +
0x78
0x090000000E068028 sqldTableDrop__FP8sqeAgentUsT2UciPcT5T6T5 +
0x1EC
0x090000001156B108
sqldTableDrop__FP8sqeAgentUsT2UciPcT5T6T5@glueC6F + 0xA0
0x090000000E06CD20 sqlricls_complex__FP8sqlrr_cbilN23 + 0x818
0x09000000116B0F1C sqlricls_complex__FP8sqlrr_cbilN23@glue852
+ 0x78
0x09000000116AB6D0 sqlrr_process_execute_request__FP8sqlrr_cbi
+ 0xAA8
0x09000000116ABBD4
sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x21C
0x090000000F9995EC executeSection__10pvmPackageFP5sqlcaUib +
0x674 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 V10 GA *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10 FP1 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
First Fixed in DB2 v10 FP1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 14.06.2012
01.11.2012
01.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.1.0.2
|
|
| 10.5.0.1
|
|
| 10.5.0.2
|
|
