|
Problem IT07453
|
Status: Geschlossen |
RARE TIMING DB2 CRASH IN SMP |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
When customer has SMP machine, in rare cases db2 can crash in
one of the following stacks:
sqlo_xlatch11getIdentityEv + 0x0000
sqlriLatchXP11sqlo_xlatch + 0x0016
sqlri_hsjnCloseP8sqlrr_cbP11sqlri_hsjno + 0x0b59
sqlricjpP8sqlrr_cbP12sqlri_opparmill + 0x0dc0
sqlricjpP8sqlrr_cbP12sqlri_opparmill + 0x0231
sqlricls_complexP8sqlrr_cbilll + 0x13c0
sqlra_close_sectionP8sqlrr_cbP25sqlra_sql_context_siblingiiiiiii
+ 0x01a2
sqlrr_subagent_closeP8sqlrr_cb + 0x0151
sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x07d2
And
getIdentity__12sqloSpinLockCFv + 0x184
getIdentity__11sqlo_xlatchCFv + 0x14
sqlriLatchX__FP11sqlo_xlatch + 0x30
sqlrsdrop__FP8sqlrr_cbP9sqlri_tao + 0x2C4
sqlridrp__FP8sqlrr_cbP9sqlri_tao + 0x2E8
sqlricls_complex__FP8sqlrr_cbilN23 + 0x44AC
sqlricls__FP8sqlrr_cbiN32 + 0x178
sqlra_close_section__FP8sqlrr_cbP25sqlra_sql_context_siblingiN63
+ 0x27C
sqlra_close_sections_on_finalcmt_rollback__FP8sqlrr_cb + 0x8A8
sqlra_close_sections__FP8sqlrr_cbUiT2b + 0xC7C
sqlrr_cleanup_tran_before_DPS__FP8sqlrr_cbiN62PiT9 + 0x1A6C
sqlrr_tran_router__FP8sqlrr_cb + 0x2980
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x1FB0
sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0xEA8
........... |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* NA *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 Fix Pack 5 or higher *
**************************************************************** |
| Local-Fix: |
Turn off intra_parallel or set the query degree to 1 |
| Lösung |
Fixed in DB2 V10.1 Fix Pack 5 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 03.03.2015
16.07.2015
16.07.2015 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.5
|
 |
