The operating system collector SAPOSCOL is a stand-alone program that runs in the operating system background. It runs independently of SAP instances exactly once per monitored host. SAPOSCOL collects data about operating system resources, including:
· Usage of virtual and physical memory
· CPU utilization
· Utilization of physical disks and file systems
· Resource usage of running processes
SAPOSCOL makes the data available using a segment of the shared memory for various applications and all SAP instances on a host. A CCMS agent or a dialog work process reads the data from the shared memory. You can display the data in various monitoring architecture monitors or in the operating system monitor (transactions OS07 and ST06). If the operating system data is read and sent by CCMS agents, you can display operating system data for any hosts in a central system.
Please check if the saposcol is running properly at OS level or not. The reason for this is saposcol should start before the sap application server, since it creates a shared memory segment where it store the information which is collected by it.
When the SAP application server starts up , it looks for the shared memory segment which was created earlier,if the memory segment is present SAP app server attaches to that segment and ST06 works fine.If saposcol was not running when SAP app server started. The shared memory segment isn't present and hence ST06 and other transactions relying in SAPOSCOL doesn't work even after you startup saposcol later.
Operating system and file system monitoring is part of it.
To start the file system monitor, follow the procedure below:
1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.
2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
3. Start the Filesystems monitor from the list by double clicking it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.