Skip to Content
Author's profile photo Tamas Istenes

Known warnings and error messages of dev_coll and possible problems with SAPOSCOL

After you have installed and started the operating system collector SAPOSCOL, it automatically begins to collect operating system data for its local host and to store this data in the shared memory.
SAPOSCOL provides various settings that you can use to improve its performance, to customize the quantity of collected data to your requirements, and to help you find the causes of errors.
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. Also other type of agents like SMD Agent and the SLD application can connect to the SAPOSCOL shared memory segment by executing a SAPOSCOL command like “saposcol –b”.
The operating system collector SAPOsCol is a stand-alone program that runs in the operating system background. It runs independently of SAPinstances exactly once per host.Saposcol is not Unicode-dependent, so it makes no difference to download it from Unicode or Non-unicode directory on Service Market Place.The highest available saposcol version can always be used backwards.

Please refer to dokumentation:
SAPOSCOL: Clearing Shared Memory and Updating Saposcol

First step:

SAPOSCOL should always be started with root permissions, to be able to collect all the OS statistics (see notes: #19227 and #726094).
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 it with comand if SapOsCol is runing under ‘root’ user : ‘ps -ef  | grep saposcol’  or   ‘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
After it the dev_coll file can be checked:
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.

Know Warning messages in SAPOSCOL log file:

======================= LOG: WaitFree: could not set new shared memory status after 15 sec
LOG: No Write Access to Shared Memory: Skip this interval.
WARNING: pfhpux.c 575: WaitFree() failed. No write access to shared memory
WARNING: The saposcol process is not running with effective root
WARNING: Effective user ID of this process is 0 (noroot privileges required)
WARNING: can’t open put-file /usr/sap/tmp/coll.put
WARNING: Unable to resolve hostname for address
WARNING:   authority. Virtual Memeory parameter settings can not be captured.
WARNING:   Please change executable permissions if you wish to capture this information.
WARNING: data with record type (RT_DISK,RST_SUM) incomplete
WARNING: Could not open pid file [/usr/tmp/]
WARNING: Start attempt pid [ …] but saposcol already running [/usr/tmp/]
WARNING: statfs() of `/nfsimport/raps’ failed
WARNING: VIRT- Error: This value is not available on this host.
WARNING: Error in VMware guest library.
WARNING: VMware: Can’t get host information.
WARNING: Kernel parameter iostat is FALSE.
WARNING: For accurate disk statistics, ensure that kernel is set to continuously maintain DISK I/O history, e.g.,
WARNING:   # chdev -l sys0 -a iostat=’true’.
WARNING:   Deleting /NIM/MKSYSB from statistics collection.
WARNING: Unable to collect snapshot data for /mnt.
WARNING: *Linux*: Calling ccm_CPU_Utilization

LOG: This Linux kernel operates at 100 HZ (compile-time HZ was 100).

WARNING: statfs() of `/hana/shared/AR1/.snapshot/nas_hourly.2015-06-01_1900′ failed

ERROR: Execution of buffer failed — OS: Permission denied

LOG: exec of pflinux_getpatchdata failed

23:02:23 17.06.2015     LOG: system config changed:

cpus[new/old]:        120/120

lans[new/old]:        19/19

disks[new/old]:       14/14

filesystems[new/old]: 56/55

— hour data will be invalid

LOG: *LINUX*: statistics value of res->C.pages_in is zero.
LOG: UID incorrect: ruid: 0 euid: 99 both should be 99)
LOG: SAPPdhAddCounter(\Memory\Available Bytes) failed! c0000bb8
LOG: SAPPdhAddCounter(\Memory\Available Bytes) failed! c0000bb8
LOG: *Action*: Please use device filteringWARNING: Maximum number of disks reached (hard limit)
0516-010 : Volume group must be varied on; use varyonvg command.
LOG: Symbol wpar_getcid not found in /usr/lib/libperfstat.a(shr_64.o).      (see below:)

                                                        “The warning regarding the symbol ‘wpar_getcid’ indicates that the

                                                            perfstat library does not expose this symbol. Possibly, this a bug in

                                                                 the SAPOSCOL coding, because the perfstat library does not provide

                                                                      this function. Please check whether this issue is still apparent after

                                                                           performing the above steps.”

======================= LOG: caught signal 2 – exiting

======================= LOG: ==== Trying to stop saposcol while it is still collecting.

======================= LOG: ==== Stop Flag set: collector will stop as soon as possible.

======================= LOG: ====

hpvmdaemon: EOF on stdin: Error 0

On Solaris OS:

/usr/bin/showrev: get_env_var(SUNWofk, SUNW_PATCHID)

VxVM vxprint ERROR V-5-1-14479 Please execute this operation in global zone

File: pfutil2.c, Line: 3320 tmpfile() failed!

Assertion `NULL != ret’ failed!

the log file of “SAP Host agent” dev_coll is full with messages:

WARNING: Record 132/3/0: Index (5033 + 61 ) out of range (0 .. 5086)

   – it cames from pfwntvirt.cpp:WriteDataToSHM() –

  LOG: *Action*: Please use device filtering

LOG: *SUNOS*: call: kstat_read failed. errno: 6

LOG: *ERROR*: saposcol CPU statistics disabled.

LOG: *ERROR*: get_kstat_cpu failed.

More information:

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

Monitoring Selected Processes with SAPOSCOL

SAPOSCOL: Error Analysis



#19227- Open newest saposcol
#1627564 – SAPOSCOL: Clearing Shared Memory and Updating Saposcol
#2179798 – Saposcol 720 run out of maintenance
#1915533 – New saposcol shared memory locking

#2075128 – Reasonable number of running saposcol processes
#2075689 – saposcol core dump on solaris

#1909856 – performance counter saposcol windows ST06
#1697515 – Inconsistencies in OS monitoring
#189072 – ST06/OS06: No data or incorrect data displayed
#371023 – OS07/ST06: Monitoring operating system data
#1706577 – ST06/OS07N: No performance MTEs available for category Disk
#498112 – SAPOSCOL: Disk and file system filter
#1084019 – OS07N: New operating system monitor
#536954 – OS data in a cluster environment for OS07
#692247   –  iSeries: No Monitor Data in ST06
#994025 – Virtualized OS environments in the operating system
#1122387 – Linux: SAP Support in virtualized environments
#1409604 – Virtualization on Windows: Enhanced monitoring
#1606643 – Linux: VMware vSphere host monitoring interface

#1692551 – Wrong log entry classification

#1837455 – Agent logs shows errors regarding OS data “[SAPOSColPortTypeHandler.recordOsData] Cannot find OS Data …”

#1834530 – AS Java Overview shows warning for stopped SAPOSCOL WS

#1483047 – “Old” version of operating system monitor not available

#1064968 – ST06: Unable to start saposcol

#1394128 – saposcol dies at start

#144595 – OS06/ST06 delivers no hardware info under NT

#1130252 – SAPOSCOL service doesn’t start, error 1053

#1439391 – SAPOSCOL Service deleted after SAPHostAgent Installation

#210713 – NT: SAPOSCOL servc dumps immedtly after start

#1113545 – Problems with SAP Host Agent

#1911995 – Deactivating the automatically start of SAPOSCOL

#1937227 – Missing history data in ST06
#548699 – FAQ: OS collector SAPOSCOL

AIX commands you should not leave home without

#710975 – FAQ: which saposcol should be used on AIX
#884393  –  AIX saposcol consumes large amount of memory
#1756498 – saposcol on AIX: multiple saposcol processes
#162980 – saposcol for 64-bit Solaris

#1301496 – Preventing saposcol startivng several times
#2075128 – Reasonable number of running saposcol processes

#1609892 – Saposcol reports negative or zero CPU utilization

#1784175 – SAPOSCOL or LSPV spawn many processes

#1515356 – saposcol on AIX: High cpu usage by saposcol in WPARs

#1379340 – Extended set of virtualization metrics for AIX Power Systems

#895816 – ST06 statistics are misleading in SPLPARS on AIX

1909856 – performance counter saposcol windows ST06

1926779 – RZ20 ST06 strange filesystem names
1748420 – Saposcol fails to create MO ‘General’

#175852 – iSeries: Authorization problems in SAPOSCOL

Hanging, zombie, defunct SAPOSCOL process on HP-UX

#918279 – HP-UX SAPOSCOL version history
#2020706 – Issue with saposcol on HP-UX

If You find it usfull please let me know and share with others

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      great job !

      Author's profile photo Christian Schwarzenberger
      Christian Schwarzenberger

      Hi Tamas,

      one clarification: As of now, SAPOSCOL is part of the SAP Host Agent and should not be started or stopped manually. The Host Agent will make sure, saposcol is started with the correct user.

      Otherwise, good basic explanation of SAPOSCOL.



      Author's profile photo Imre Takacsi-Nagy
      Imre Takacsi-Nagy

      Great Job Tamas!



      Author's profile photo Former Member
      Former Member

      Hello Team,

      I have the next error, how can  we fix them?

      WARNING: Error in VMware guest library.
      WARNING: VMware: Can’t get host information.


      Author's profile photo Tamas Istenes
      Tamas Istenes
      Blog Post Author


      Do you faceing with this in dev_coll ?
      Is it about UNIX ?

      #994025 - Virtualized OS environments in the operating system
      #1122387 - Linux: SAP Support in virtualized environments
      #1606643 - Linux: VMware vSphere host monitoring interface

      Author's profile photo Jorge Monteiro
      Jorge Monteiro


      I am also facing this issue and found info on SAP note 2463083 - VMware errors in saposcol dev_coll trace file on Linux.