|
Problem IC77237
|
Status: Closed |
DB2 CRASH DUE TO MEMORY CORRUPTION DURING CURSOR INTERRUPT HANDLING. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 may abend with memory corruption errors during user
interrupt handling.
If there are many user interrupts sent to running applications
that use cursors, db2 may abend with memory corruption errors
during the user interrupt handling.
db2diag.log messages may look as follows:
2011-06-14-15.19.20.057511-240 E25588598A1446 LEVEL: Severe
PID : 524842 TID : 1169947 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-44645 APPID:
155.180.252.31.61228.1106141745
AUTHID : db2inst1
EDUID : 1169947 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure,
probe:999
MESSAGE : Memory validation failure, diagnostic file dumped.
DATA #1 : String, 28 bytes
Corrupt pool free tree node.
DATA #2 : File name, 34 bytes
524842.1169947.mem_diagnostics.txt
CALLSTCK:
[0] 0x09000000093586B8 pdLog + 0xD4
[1] 0x09000000085B5910
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc + 0x26C
[2] 0x09000000085B55CC
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glue7CC
+ 0x78
[3] 0x090000000932A2BC
.MemTreePut.fdpr.clone.420__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloC
hunkSubg
roup + 0x24
[4] 0x0900000009325C70 sqlofmblkEx + 0x288
[5] 0x09000000091E99EC
sqlra_sqlC_mem_free_block__FP8sqlrr_cbUlPv +
0x48
[6] 0x09000000091EB498
sqlra_sqlC_mem_free_block__FP8sqlrr_cbUlPv@glue863 + 0x74
[7] 0x09000000058ADF48
sqlra_free_section__FP8sqlrr_cbP25sqlra_sql_context_siblingiN23
+ 0x21C
[8] 0x090000000589308C
sqlra_sqlC_free_section__FP8sqlrr_cbP25sqlra_sql_context_sibling
i
+ 0xA0
[9] 0x0900000005A4B4D0
sqlra_sqlC_free_sibling__FP8sqlrr_cbP25sqlra_sql_context_sibling
ib
+
0xB8
2011-06-14-15.19.20.057832-240 I25591002A1002 LEVEL: Error
PID : 524842 TID : 1129100 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-44495 APPID:
155.180.252.70.35243.1106141742
AUTHID : db2inst1
EDUID : 1129100 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post,
probe:1700
MESSAGE : Severe TERMINATE err at nest lvl 1, in SQL from rtn
db2inst1.sample_routine:
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -431 sqlerrml: 49
sqlerrmc: SP_sample_routine SQL110608152544700
sqlerrp : SQL09073
sqlerrd : (1) 0xFFFFFFFF (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 38504 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 v97fp4 and lower *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 may abend with memory corruption errors during user *
* interrupt handling. *
* *
* This happens due to interrupt is occurring in the context of *
* the open cursor and that some internal processing relating *
* to BDS counter management results in the interrupt not being *
* handled properly resulting in an inconsistency where the *
* open did not succeed, but no error was returned. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97fp5+ *
**************************************************************** |
| Local Fix: |
No Local Fix |
| available fix packs: |
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
|
| Solution |
v97fp5 addresses this issue. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.06.2011
19.12.2011
19.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5,
9.7.FP5+
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
