Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: VIRT - Virtualization Monitoring
Message number: 360
Message text: Number of Shared CP free
Error message extract from SAP system. Copyright SAP SE.
VIRT360
- Number of Shared CP free ?The SAP error message "VIRT360 Number of Shared CP free" typically relates to issues with the virtual memory or shared memory configuration in the SAP system. This error can occur when the system runs out of available shared memory for processes, which can lead to performance issues or system instability.
Cause:
- Insufficient Shared Memory Allocation: The system may not have enough shared memory allocated for the number of concurrent processes or users.
- High Load: A sudden increase in the number of users or processes can exhaust the available shared memory.
- Configuration Issues: Incorrect configuration settings in the SAP instance profile or operating system settings can lead to inadequate memory allocation.
- Memory Leaks: Applications or processes that do not release memory properly can lead to exhaustion of available shared memory.
Solution:
Increase Shared Memory Allocation:
- Adjust the parameters in the SAP instance profile (e.g.,
abap/heap_area_dia
,abap/heap_area_nondia
,rdisp/Shared_Pool_Size
) to allocate more shared memory.- Use transaction
RZ10
to modify the instance profile and then restart the SAP instance for changes to take effect.Monitor and Optimize Memory Usage:
- Use transaction
SM04
to monitor user sessions and identify any that are consuming excessive resources.- Check for long-running transactions or background jobs that may be consuming memory.
Review Operating System Settings:
- Ensure that the operating system's shared memory settings (e.g.,
shmmax
,shmall
on Unix/Linux systems) are configured to allow sufficient memory for SAP.- Use commands like
ipcs
to check current shared memory usage andsysctl
to adjust kernel parameters if necessary.Check for Memory Leaks:
- Analyze the application code for potential memory leaks, especially if custom developments are involved.
- Use tools like the SAP Memory Inspector or transaction
ST02
to analyze memory usage and identify potential issues.Restart the SAP System: If the issue persists and immediate resolution is required, a restart of the SAP system may temporarily alleviate the problem, but it is essential to address the underlying cause.
Related Information:
If the problem continues after trying these solutions, it may be beneficial to consult with SAP support or a professional with expertise in SAP system administration.
Get instant SAP help. Sign up for our Free Essentials Plan.
VIRT359
Number of dedicated CP
Total number of dedicated CPs on this physical host.Error message extract from SAP system. Copyright SAP SE. ...
VIRT358
Guaranteed Capacity (CP)
Number of CPs dedicated to this LPAR.Error message extract from SAP system. Copyright SAP SE. ...
VIRT361
Operating System
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
VIRT362
Avg. total phys. CP Usage
Average total utilization of the physical processors(CP) of this physical host within the last collection interval. This data is based on the total i...
Click on this link to search all SAP messages.