|
Problem IC76906
|
Status: Geschlossen |
DB2AGENT HANGS IN SQLILIDX() FOR LATCH AFTER IT HITS LOG FULL SITUATION |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
After DB2 hits a log full situation, in rare case some db2agent
EDUs performing insert/update/delete may hang, and there is at
least one hung EDU with these functions on the stack:
sqlilidx
sqliundo
ixmUndo
waiting for latch. For example,
0x09000000000EDED8 thread_wait + 0x98
0x09000000092ABC6C getConflictComplex__17SQLO_SLATCH_CAS64FCUl
+ 0x414
0x09000000092AC220 getConflict__17SQLO_SLATCH_CAS64FCUl + 0xEC
0x09000000092AC2E8 getConflict__17SQLO_SLATCH_CAS64FCUl@glueFB
+ 0x74
0x09000000092AC43C
get__20@88@59712@sqlo_latchFCUlCPCcT1P16SQLO_LATCH_TABLECbC14SQL
O_LT_VALUES
+ 0x90
0x09000000092AC544
get__10sqlo_latchFCUlCPCcT1P16SQLO_LATCH_TABLECbC14SQLO_LT_VALUE
S@glue9F0
+ 0x80
0x0900000009146C24 sqlilidx__FP7SQLI_CBUiT2 + 0x8C
0x09000000092BC884 sqlilidx__FP7SQLI_CBUiT2@glueD3B + 0xA8
0x0900000006C5F84C
sqliundo__FP8sqeAgentP8SQLD_TCBPcP9SQLP_LSN8 + 0x32C
0x09000000093C6064
@102@ixmUndo__FP8sqeAgentP8SQLI_LRHP9SQLP_LSN8s + 0x120
0x09000000093C59EC
sqldmund__FP8sqeAgentP9SQLP_LSN8PcUisT4P8SQLP_TIDP15SQLD_RECOV_I
NFO
+ 0x2A8
0x09000000093C4E00
sqlptudo__FP8sqeAgentPUlP15SQLD_RECOV_INFOP11SQLP_TENTRY + 0x1E0
0x09000000093C51B0 sqlptud1__FP8sqeAgentUl + 0x40
0x0900000006802950 sqlpSpRb__FP8sqeAgentiUl + 0x108
0x0900000006804D60 sqlpSpRb__FP8sqeAgentiUl@glue1C0 + 0x78 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2AGENT HANGS IN SQLILIDX() FOR LATCH AFTER IT HITS LOG *
* FULL *
* SITUATION *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 9.7 Fix Pack 5 *
**************************************************************** |
| Local-Fix: |
Avoid log full situation. Adjusting max_log and num_log_span can
help to reduce risk of hitting log full situation |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version 9.7 Fix Pack 5 |
| Workaround |
See LOCAL fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 10.06.2011
16.12.2011
16.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
