|
Problem IC70049
|
Status: Closed |
SOLARIS: DB2VEND MAY FAIL WITH ERROR ENOMEM DURING SHMAT() SYSTEM CALL |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Under rare circumstances the db2vend process may fail with error
ENOMEM during the
shmat() system call. This happens on the Solaris operating
system only.
In db2diag.log you will see the following message:
2010-06-09-07.30.25.552036+120 I64626650A1439 LEVEL: Error
(OS)
PID : 5808 TID : 1 PROC : db2vend
(db2logmgr.userexit - 23
INSTANCE: xxxxxx NODE : 000
EDUID : 1 EDUNAME: db2vend
(db2logmgr.userexit - 23
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:210
MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG
"No Storage Available for allocation"
DIA8305C Memory allocation failure occurred.
CALLED : OS, -, shmat
OSERR : ENOMEM (12) "Not enough space"
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See problem description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
First fixed in DB2 Version 9.7 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.07.2010
01.05.2011
01.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
