Symptom
db2start fails with a memory allocation error. The db2diag.log reports SQLO_NOSEG / DIA8305C ("No Storage Available for allocation") and the operating system reports ENOMEM (12) "Not enough space" when Db2 attempts to allocate the database shared memory set.
Example:
2026-10-03-17.12.42 LEVEL: Warning (OS)
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemCreateSingleSegment
CALLED: OS, -, shmget
OSERR: ENOMEM (12) "Not enough space"
MESSAGE: ZRC=0x850F0005=SQLO_NOSEG
"No Storage Available for allocation"
DIA8305C Memory allocation failure occurred.
Failed to allocate the desired database shared memory set.
The configured DATABASE_MEMORY plus desired overflow may have exceeded INSTANCE_MEMORY or the maximum shared memory on the system.
Desired database shared memory set size is (bytes):
Example: 190909054976
Read more...
Environment
Db2 LUW IBM
Product
Keywords
DB2 LUW, DB2START, INSTANCE_MEMORY, DATABASE_MEMORY, SQLO_NOSEG, DIA8305C, ENOMEM, shared memory, memory allocation, shmget, DB6, SAP , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview