|
Problem IC84598
|
Status: Closed |
CALLING SNAP_WRITE_FILE MAY CAUSE MEMORY CORRUPTION IN FMP PROCESS LEADING TO OUT OF MEMORY CONDITIONS IN DB2 |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
You may encounter the following messages in db2diag.log
indicating memory corruption in FMP process:
DATA #1 : String, 146 bytes
NON-FATAL ASSERTION FAILED!!!
ASSERTION EXPRESSION: Invalid block eye-catcher (0x26E7D47F)
found at:
SOURCE FILENAME: snapPROC.C
LINE NUMBER: 208
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00002AAAAAF6D183 pdLog + 0x1FF
[1] 0x00002AAAAB8CA2B1 sqlzAssertFailedValist + 0x189
[2] 0x00002AAAAC9C95EE ossAssertFailureAction + 0x1CA
[3] 0x00002AAAAC9C9422 _Z21ossAssertMemoryFailedPKcS0_mS0_ + 0xE
[4] 0x00002AAAAC9E712E _ossMemAllocCheck + 0x904
[5] 0x00002AAAAC9E60A4 _ossMemFree + 0x104
[6] 0x00002AAABBB235D8 snap_write_file + 0x2A4
[7] 0x00002AAAAB02DB18 sqloInvokeFnArgs + 0x40
[8] 0x00002AAAAB621515 /home/pcinst/sqllib/lib64/libdb2.so.1 +
0xB70515
[9] 0x00002AAAAB621897 sqlerDyload + 0x11B
DATA #1 : String, 136 bytes
NON-FATAL ASSERTION FAILED!!!
ASSERTION EXPRESSION: Invalid pad type (0x43F66FB) found at:
SOURCE FILENAME: snapPROC.C
LINE NUMBER: 208
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00002AAAAAF6D183 pdLog + 0x1FF
[1] 0x00002AAAAB8CA2B1 sqlzAssertFailedValist + 0x189
[2] 0x00002AAAAC9C95EE ossAssertFailureAction + 0x1CA
[3] 0x00002AAAAC9C9422 _Z21ossAssertMemoryFailedPKcS0_mS0_ + 0xE
[4] 0x00002AAAAC9E6CA6 _ossMemAllocCheck + 0x47C
[5] 0x00002AAAAC9E60A4 _ossMemFree + 0x104
[6] 0x00002AAABBB235D8 snap_write_file + 0x2A4
[7] 0x00002AAAAB02DB18 sqloInvokeFnArgs + 0x40
[8] 0x00002AAAAB621515 /home/pcinst/sqllib/lib64/libdb2.so.1 +
0xB70515
[9] 0x00002AAAAB621897 sqlerDyload + 0x11B
These messages may get logged when snap_write_file stored
procedure is called. The system may run out of memory if this
stored procedure gets called continuously over a period of time |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fixpack 1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
Fixed in DB2 Version 10.1 Fixpack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
28.03.2013
28.03.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
