Symptom
- While performing an upgrade using Software Update Manager (SUM) on a system with multiple SIDs, an error occurs during the phase MAIN_SWITCH/STARTSAP_TRANS.
- The PHYS_MEMSIZE parameter is set to a specific value to limit each SID from using up all of the system's resources.
- The dispatcher process fails to start, the error reported by SUM has an output similar to:
- In SAPup.ECO:
-
2 name: disp+work
2 description: Dispatcher
2 dispstatus: YELLOW
2 textstatus: Request handling without progress
2 starttime: <time>
2 elapsedtime: 0:04:59
2 pid: <pid>
-
In dev_wN logs (N being a number), you can see a similar error message:
-
I *** ERROR => shmget(10006,80530636800,2016) (12: Not enough space) [shmux.c 1529]
-
You also see in the SUM log MODPROF_TRANS.LOG:
-
2 ETQ399 Commenting out key 'PHYS_MEMSIZE' value '2048'.
- Checking the central instance profile, you see that the PHYS_MEMSIZE parameter is commented out by SUM:
-
# *** TEMPORARY 740 CHANGE ***
#PHYS_MEMSIZE = 2048# *** TEMPORARY 740 CHANGE ***
- Why is SUM commenting out this value?
Read more...
Environment
- SAP NetWeaver
- Kernel >= 740
Keywords
KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , 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.