Symptom
- Why does Adaptive Server Enterprise fail to boot and raise os_create_region / shared memory errors
- ASE log shows an error sequence with messages including :
kernel: os_create_region can't allocate xxx
kbcreate: couldn't create kernel region
kistartup: could not create shared memory - Depending on the OS and circumstances, additonal (OS related) messages may be printed.
Examples of such messages are : - os_create_region: shmget (0xxxxxxx): No space left on device
- os_get_shmid: write to $SYBASE/ASE-XX_0/<Instace_name>.krg failed: No space left on device
- os_create_region: shmat(-1): Invalid argument
- Attach failed with 0. Retrying with NULL address
- Attempt to attach shared memory (id -1) at address (nil), with flags 0 failed
- Cannot attach shared memory : error = 22 (Invalid argument)
- kernel WARNING: shared memory segment is being held by another application
- kernel FATAL: shared memory region is being held at xxx bytes but yyy bytes are required
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) any version
- SAP Adaptive Server Enterprise (ASE) for Business Suite
Product
SAP Adaptive Server Enterprise all versions ; Sybase Adaptive Server Enterprise all versions
Keywords
"Could not create shared memory" , shget, shmat, SHMMAX, kbcreate, kistartup, shared memory, segments, abnormal exit, removed, deleted, ipcs, ipcrm, amount of memory in use, allocate max shared memory, fragmented memory , , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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