As a first step please make sure Saposcol is on latest version because version 720 not supported , refer to:
2180933 - Saposcol 721 fixes summary note

2179798 - Saposcol 720 run out of maintenance

SAPOSCOL is installed on one physical server with different virtual OS systems on which different SAP systems are running with different system releases and a different UNICODE/NON-UNICODE system type. Transactions like ST06 and OS07 on all these ABAP systems can connect to the same SAPOSCOL shared memory segment which is available on the physical host. Also the CCMS agents which are installed on the server can access the SAPOSCOL shared memory and update the OS monitoring structure which is located in the CCMS shared memory segment, for which the agent is responsible.

In case SAPOSCOL is not collecting all the requred OS statistics :

If SAPOSCOL does not collect all the required OS performance statistics then at first should be checked if the missing statistics are available on OS level. For example on a Windows system the command ‘diskperf –Y’ should be executed to activate the disk statistics on OS level (note 189072). If this is not correctly done, SAPOSCOL will not collect Disk and FileSystem statistics.

SAPOSCOL will also not collect all the required statistics when there is not enough memory allocated. Always check in the dev_coll file how much memory is allocated and for example compare this with another SAPOSCOL process which is collecting all the required information.

SAPOSCOL is started by using the command syntax “saposcol –l”, this will create a SAPOSCOL process and this process will create the SAPOSCOL shared memory segment. The SAPOSCOL startup information is reported in the dev_coll file which is located in the SAPOSCOL working directory.

On UNIX systems the SAPOSCOL directory will be by default the /usr/sap/tmp directory. For Windows systems SAPOSCOL does always tries to use the ‘saploc’ share name and the SAPOSCOL working directory will be <saploc>\PRFCLOG. You have to create this directory manually before you can start SAPOSCOL correctly.
If the SAPHOSTAGENT is installed on a server then SAPOSCOL is started by the program saphostexec (note 1064968). On a UNIX system you will see the following line for this in the process table:

ps –edaf | grep saposcol

If the SAPHOSTAGENT is installed the operating system user ‘sapadm’ will be used to start the SAPHOSTAGENT and the SAPHOSTAGENT will start SAPOSCOL by using the ‘root’ user on UNIX systems or the ‘SYSTEM’ user on Windows systems.

There can only be one “saposcol –l” process started on one physical server because the SAPOSCOL shared memory segment can only be owned by one process.

Please make sure the SAPOSCOL is up to date according to SAP note:
19227 - Open newest saposcol and 548699 - FAQ: OS collector SAPOSCOL

Itis recommended to check the configuration according to notes:
994025 - Virtualized OS environments in the operating system
1122387 - Linux: SAP Support in virtualized environments
1409604 - Virtualization on Windows: Enhanced monitoring

How to upgrade SAPOSCOL:

Stop the old SAPOSCOL process
If there are SAPCCMSR or SAPCCM4X agents running on the same server it is also better to stop these processes too.
Check if the shared memory segment is correctly removed (On Windows systems you can try to start SAPOSCOL in dialog mode and execute the ‘leave’ command. If this does not remove the shared memory segment on an OS restart will help. On UNIX systems you can use the OS command ‘cleanipc 99 remove’)
Delete the coll.put file which is stored in the SAPOSCOL working directory
Install the new SAPOSCOL executable in the correct executable directory
Start SAPOSCOL (and the CCMS agents) again.
After this always check the dev_coll file to see if the new collector process also did recreate the shared memory segment again.

SHM Segment of the SAPOSCOL:
http://scn.sap.com/community/netweaver-administrator/blog/2013/11/20/shm-segment-of-saposcol

SAPOSCOL should always be started with root permissions, to be able to collect all the OS statistics.

If the SAPHOSTAGENT is installed the operating system user ‘sapadm’ will be used to start the SAPHOSTAGENT and the SAPHOSTAGENT will start SAPOSCOL by using the ‘root’ user on UNIX systems or the ‘SYSTEM’ user on Windows systems.

1.) Please check with command if SapOsCol is runing under 'root' user : 'ps -ef | grep saposcol' and how it is connected to SHM segment 'ipcs -ma | grep 4dbe'

2.) check if the status of saposcol is correct

saposcol -s

     - the running and dialog version must be the same
     - shared memory is 'attached'
     - collector is in state 'running'
     - collection interval should be 60 (by lower you are risking performance problems from ABAP side - GetPerfData/Get1PerfData)

3.) check if the snapshot data are available in shared memory

saposcol -m

- the result should contain numbers and OS data
- the last write time (first line of output) is recent
- data could not be available right after starting saposcol

4.) check if synchronous WebService calls are working correctly

saphostctrl -function GetSAPOSColVersion
- if saposcol version will not be returned, check if SAPOscol porttype is present in the host_profile
service/porttypes = SAPHostControl SAPCCMS SAPOscol
- if not, please add it and restart saphostagent :
restart saphostagent
saphostexec -restart

It is allways recommended to check the log file of the SAPOSCOL , it is called : dev_coll

On UNIX systems the SAPOSCOL directory will be by default the /usr/sap/tmp directory. For Windows systems SAPOSCOL does always tries to use the ‘saploc’ share name and the SAPOSCOL working directory will be <saploc>\PRFCLOG. You have to create this directory manually before you can start SAPOSCOL correctly.

SAPOSCOL Log Files
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c4/3a6c67505211d189550000e829fbbd/content.htm

First steps by checking dev_coll file

If for the Operating System monitoring tree no CCMS agent is activated the SAPOSCOL date will be collected by an ABAP report which is only started every 5 minutes. This means that in this case the previous hour information is only updated every 5 minutes and in total about 12 measurements for the average hourly value will be used. If an agent is installed the values will be updated each minute and 60 measurements will be used to calculate the average hourly value, which is much better.

If the error message “No Performance MTEs availbale for category XXXXX” is reported in the transaction ST06N when one of the Previous hours categories is selected, it means that in the related RZ20 shared memory segment the MTE for the selected category does not exist. For example on a Windows system this can happen for the Disk category when the Disk monitoring is not activated on OS level.

If you want to monitor a remote systems by using the ST06N transaction on a Central Monitoring system the remote system needs to be available in the transaction “RZ21>Topology>System overview”. If the remote system is correctly connected to the Central Monitoring system, in the transaction ST06N System map the remote system with all the ABAP instances will be reported. In this way only the SAPOSCOL’s on server with an ABAP instance can be reached. If on the remote server also an SAPCCMSR agent is installed for a standalone database server than the standalone database server can only be monitored by ST06N centrally if also the SAPCCMSR agent is connected to the central system.

To check the SAPOSCOL status or to stop and start SAPOSCOL on a remote server the parameter exe/saposcol should be correctly maintained in the agent profile.

The SAPOSCOL destinations are maintained in the transaction AL15. These destinations should only be related to the CCMS agent TCP/IP RFC destination names. When SAP did not have the CCMS agent the program rfcoscol was used for this but this program is not supported anymore (note 371023).
If a database is installed on a remote server than the SAPLOCALHOST parameter should be maintained correctly in the agent profile, the value for this parameter should be exactly the same as the SAPDBHOST parameter value in the instance profile. If this is correctly done than in the transaction AL15 automatically the flag “DB server” will be selected for the related SAPCCMSR agent RFC destination (note 444947). For cluster configurations have a look at note 536954

For SAPOSCOL and the new virtualization metrics, please have a look at the following notes:

AIX 1588660 saposcol on AIX: Additional Virtualization metrics

HP-UX 1491406 Virtualization with HP-UX: Enhanced monitoring

Linux 1102124 SAPOSCOL on Linux: Enhanced function

1122387 Linux: SAP Support in virtualized environments

Windows 1260719 SAPOSCOL: Detailed virtualization data

1409604 Virtualization on Windows: Enhanced monitoring

Use full notes :
2179983 - Basic 'missing OS data' troubleshooting

2180933 - Saposcol 721 fixes summary note
2179798 - Saposcol 720 run out of maintenance

19227 - Open newest saposcol
1627564 - SAPOSCOL: Clearing Shared Memory and Updating Saposcol

162980 - saposcol for 64-bit Solaris
710975 - FAQ: which saposcol should be used on AIX
1756498 - saposcol on AIX: multiple saposcol processes
1084019 - OS07N: New operating system monitor

1937227 - Missing history data in ST06
1068204 - New monitor template for database monitoring
371023 - OS07/ST06: Monitoring operating system data
536954 - OS data in a cluster environment for OS07
144595 - OS06/ST06 delivers no hardware info under NT
189072 - ST06/OS06: No data or incorrect data displayed
1439391 - SAPOSCOL Service deleted after SAPHostAgent Installation
1909856 - performance counter saposcol windows ST06

-How to use SAP transaction ST06 for SAP performance analysis
http://www.sap-perf.ca/sap-st06-for-performance-analysis/

-Please visit the Blog too:
Known:Warnings and error messages of dev_coll and possible problems with SAPOSCOL

See for more:Computing Center Management System (CCMS)

Page tree

How to analyse the missing performace data situation and how to check SAPOsCol issues

First steps by checking dev_coll file