The Operating System

Monitor - SAPOSCOL

Sudhansu Swain (SUSE)

 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

SAPOSCOL stands for (SAP Operating System Collector).

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.

SAPOSCOL can be started only one time on a physical host. It is started by command “saposcol
–l”, so it will stay in the process table and create the SHM.

SAPOSCOL is started by the start script, but not stopped with the stop script; this is because
there can be more SAP systems on a host, so we must not stop it if an SAP system is stopped.
Overview:
SAPOSCOL is designed to collect OS statistics for the physical operating system but because
operating systems are getting virtualized more and more the SAPOSCOL functionality is
extended and is also able to collect statistics which are related to the virtual operating systems.
Please be aware that in the ABAP system the old transaction ST06 is not able to report these new
virtualized operating system statistics and you have to use the new transaction ST06N or RZ20
for this.
The transaction ST06 is ABAP instance specific, it will only report the SAPOSCOL OS statistics
for the server on which the ABAP instance is running and on which the transaction ST06 is
started.
To stop and start SAPOSCOL or the report the status of SAPOSCOL the kernel will execute the
commands like ‘saposcol –k’, ‘saposcol –l’ or ‘saposcol –s’ and for this the kernel must be able
to access the SAPOSCOL executable program.
If the SAPHOSTAGENT is installed on the server the SAPOSCOL executable is not located in
the kernel executable directory anymore.

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

In ST06 can be checked if SAPOSCOL connected to SHM.

It is important that the Collector version is the same see below (running / dialog):

The transaction OS07 cannot be used for the SAPHOSTAGENT integrated SAPCCMSR agent
because you cannot select the HTTP RFC destination which is defined for the Web Service port
and transaction OS07 does not support the Web Service functionality. This means that when
there is only a SAPHOSTAGENT running on a remote server the SAPOSCOL information
cannot be accessed by OS07.
Only the snapshot and 24-hour data is stored in the SAPOSCOL shared memory segment. If
there are complete lines missing in the 24-hours statistics, it could be that SAPOSCOL was not
started for these particular hours.
SHM Segment of the SAPOSCOL: http://scn.sap.com/community/netweaver-
administrator/blog/2013/11/20/shm-segment-of-saposcol
Sudhansu Swain © 2024
This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

The new ST06 transaction (OS07N) is available with the SP levels outlined in SAP note
1084019. Note 1084019 also briefly describes the new ST06 and some of the advantages:
• 1084019 - OS07N: New operating system monitor
Starting with SAP_BASIS 710 the old ST06 is not displayed by default anymore. However in
the new ST06 you can select from the menu: Environment -> Old ST06.
The SAP note 1483047 lists out the SAP releases and exactly which versions of ST06 / OS07 /
OS07N are available with each release:
• 1483047 - "Old" version of operating system monitor not available
Old ST06:

The old ST06 transaction shows Operating Statistics information for each SAP instance. As it is
instance dependant it will open the ST06 stats for the instance you are currently on. The old
ST06 takes its information from SAPOSCOL shared memory. You can use transaction OS07 to
view the OS stats of another instance or monitored host when setup in AL15. See SAP note
371023:

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

• 371023 - OS07/ST06: Monitoring operating system data

Old ST06 only reports old style OS data for the physical CPU of the server, ie. it does not report
separate virtualized environments for 2 or more instances on one server for example. It takes 10
second snapshots of the OS data. You can adjust the default 10 second collection interval as
described in SAP note 1284656:
• 1284656 - Saposcol collection interval
The "Detail Analysis Menu" button allows you to display information by OS statistics category
or data over the last 24 hours or 30 days averages:

New ST06:

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

The new ST06 (or OS07N) displays the OS stats for all instances and other monitored systems
and hosts. It is therefore instance independent. OS07N takes its information from SAPOSCOL,
plus RZ20, plus the RZ23N CPH (central performance history) information. It is therefore a
much more complicated setup than the old ST06. As mentioned at the top of this article, the new
ST06 / OS07N is also outlined in the SAP note 1084019:
• 1084019 - OS07N: New operating system monitor
The top-left corner of the display lets you choose your instance, servers from other monitored
systems, or the Hosts section for monitored non-SAP servers (such as standalone DB for
example, see KBA note 2164753).
OS07N handles virtualization. With OS07N and virtualization, the structure of the OS data and
how it is collected has changed. Now on the left column you have:
• Snapshot information which is the current OS info at the moment. Taken from
SAPOSCOL shared memory, every 10 seconds.
• Previous Hours information which is taken from RZ20 CCMS shared memory
segment. So if the Operating System nodes in RZ20 are not working for any reason, then
you will be missing data here in Previous Hours also.
• History information which is taken from the CPH (central performance history). Again,
if the CPH is not setup, then you will be missing the History data in OS07N.
For missing data in Previous Hours or History, check the KBA note 1915341 and the SAP notes
listed within it:

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

• 1915341 - No History Data in OS07N / ST06

For further details on virtualization and setup, depending on your Operating System, check the
SAP note 994025:
• 994025 - Virtualized OS environments in the operating system monitor

Monitoring of the Operating System

To access SAPOSCOL information from within the SAP system, you can choose different
functions in SAP systems. The most direct method is using transaction ST06.
(Identical) Transactions for accessing operating system information in SAP systems
● Transaction ST06 – the look and feel are different, depending on the release of the SAP
system.
● Transaction OS07N has been changed, so that it points to the same function as transaction
code ST06, depending on the release of the SAP system.
● Transaction ST06N points to the same function as transaction code ST06, depending on the
release of the SAP system

In ST06 you find the following information on the entry screen.

Essential Information on the Entry Screen of ST06

CPU Utilization

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

The CPU utilization will always sum up to 100%. User utilization should not exceed a value of
50% to 60%. System utilization should be below 20%, and Idle time should be above 20%. An
idle time below 20% will lead to CPU bottleneck situations.
I/O wait “utilization” accrues when the CPU would be able to do some work, but the CPU is
waiting for I/O responses. Therefore, I/O wait utilization is absolutely unwanted and a value of
more than 10% is of concern. In this situation, you should check the I/O performance of disk
subsystems, network, and so on. Fortunately, I/O wait usually is a state seldom observed. During
upgrade, client copy and similar I/O intensive activities I/O wait can play a critical role in SAP
system performance.
Average processes waiting (1, 5, and 15 minute averages): Average number of processes that
are ready for execution, but which must wait for the CPU. If the average number of processes
waiting is higher than the number of available CPUs, this indicates that the CPU is reducing the
overall performance of the SAP system.
A high value here and a high value for utilization can indicate that too many processes are active
on this host. A high value here and a low value for utilization can indicate that the main memory
is too small.
Number of CPUs - This is the number of the CPUs available on the host.
Memory: Physical memory - This number gives the size of the RAM of the host.
Swap size: Configured swap size - This is the sum of physical RAM and swap/page space. This
sum is also known as virtual memory in SAP systems.
Swap size: Maximum swap size - This number gives the amount of configured swap/page space
on this host.
Additional Functions of ST06:
Choose Additional Functions → Administrate SAPOSCOL on the entry screen
Here can you find functions for starting and stopping SAPOSCOL from within the SAP system.
You can also access SAPOSCOL log and status information.
Choose Snapshot All → Top 40 CPU processes

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

Here you will find the top 40 processes sorted by CPU usage and their current memory
consumption (physical RAM used).
Hint: The sum of CPU usage usually is normalized to 100% for the sum of all CPU (cores).
However, in older releases there was also the normalization of 100% per CPU (core) in use.
Remember this fact if you encounter CPU usage summing up to more than 100% on a multi-
CPU (core) host.
Choose Previous hours All → Memory
The swap/paging activity on OS level per hour should not be higher than one-fourth the size of
the physical RAM. Otherwise, it's likely that you will observe a decrease in SAP system
performance caused by heavy CPU and I/O utilization.

Issues and Solutions:

Issue: Missing OS data from standalone DB host in OS07, OS07N, ST06, ST06N
Solution:
Upgrade SAP_BASIS of the monitoring system to 7.01 or higher or implement the following
workaround.
Workaround: Disable an integrated CCMS agent in the saphostagent and install a standalone
CCMS hostagent "sapccmsr“.
You can get it from the related ccmagent.sar under SAP Market Place.
The standalone CCMS agent sapccmsr uses only RFC for communication, thus the
monitoring would be possible.
More steps, please refer to the note 1368389 II) You are configuring the host monitoring
(saphostagent).
Issue: SAP_COLLECTOR_FOR_PERFMONITOR job is cancelled because of the dump
LOGDB_SSCR_NOT_FOUND
Solution:
The report RSSTAT83 should be removed from table TCOLL for SAP_BASIS 7xx system.
Please remove the report name from the table TCOLL following KBA 2069030.
Issue: SAPOsCol terminates on Windows

Solution:
saposcol terminates on Windows periodically (weekly).
You may find relevant info from event log for saposcol.exe with exception code 0xc0000409,
and "Saposcol isn't running anymore. Try to restart it" in dev_saphostexec.
For more detailed info, please refer to SAP note:
2141935 - SAPOsCol Terminates During Hardware Information Data Collection
Please apply SAPHOSTAGENT SP 207 or upgrade to SAPHOSTAGENT 721.
Issue: SAPOSCOL: Clearing Shared Memory and Updating Saposcol

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

Solution:
In transaction ST06 or OS07N, many issues can be resolved by clearing the shared memory
and/or updating SAPOSCOL to the latest patch level, as follows:
1. Updating SAPOCOL:
• As described in note 19227, SAPOSCOL is downwards compatible with regards to the
SAP system release. This means, for example, you can use SAPOSCOL 720 on a 700
system. If you experience SAPOSCOL issues it is recommended to use the latest
SAPOSCOL release which is available for the highest available system release.
• The procedure to install SAPOSCOL is described in note 19227:

19227 - Open newest saposcol

548699 - FAQ: OS collector SAPOSCOL
710975 - FAQ: which saposcol should be used on AIX
2. Clearing SAPOSCOL Shared Memory Segment:
• Use the following procedure to delete the shared memory for SAPOSCOL:
saposcol -d (start in dialog mode)
Collector > clean
Collector > quit
saposcol -k (stops saposcol)
saposcol -d (before restarting)
Collector > leave (should get a message Shared memory deleted)
Collector > quit
cd /usr/sap/tmp
mv coll.put coll.old (rename the file; this stores the saposcol history data)
cd
saposcol (start saposcol again)
• If you cannot delete the shared memory segment with the above procedure then:
o On Unix systems:
▪ You can use 'cleanipc 99 remove' on O/S level (this will remove all the ipc
objects for the system number 99, also for the SAPCCMSR agent).
▪ You could alternatively use 'ipcrm -M 0x00004dbe', which will delete
saposcol’s SHM, but not anything related to host agent.
o On Windows:
▪ You can use Microsoft Process Explorer to check the shared memory
handle of saposcol and then try to find if another process holds it. You
should see that some disp+work has the handle. Kill this and then you
should be able to stop saposcol and clean the memory.
▪ If you cannot delete the shared memory segment manually as above, then
a sure method to delete the existing shared memory segment is a restart of
the Windows OS. If you are using CCMS patch collection 2011/3, a
Windows restart should no longer be required.
• After restarting SAPOSCOL again you can check the dev_coll file to see if the actual
SAPOSCOL process also created the shared memory segment:
10:51:18 01.07.2011 LOG: Shared Memory Size: 532786.
10:51:18 01.07.2011 LOG: Shared Memory was created by process:5708 <<<<<<
10:51:21 01.07.2011 LOG: Collector daemon started

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

10:51:21 01.07.2011 LOG: read coll.put Fri Jul 01 10:47:12 2011

10:51:21 01.07.2011 LOG: Collector PID: 5708
<<<<<<
On UNIX systems you can use the SAP OS command ‘showipc 99’ to report the defined IPC
objects for the system area 99.
We can also use the UNIX command ‘ipcs –a’ to report some more detailed information, like
owner and permissions about the defined IPC objects.
Issue: st06n - not showing "history" of CPU,Memory, Swap size, Disk, Lan, File System in
servers
Solution:
To see the OS statistics History information in the transaction ST06N the CPH data collection
needs to be activated for the system and the related MTE-class. With the transaction RZ23N the
CPH (Central Performance History)
Please have a look at in documentation on Configuring the Central Performance History
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/19/4c773dd1210968e10000000a114084/fra
meset.htm
To collect and to reorganize the CPH data background jobs needs to be scheduled. Which
background jobs are activated can be checked in the transaction RZ23N.
Check in the transaction SM37 if the collector jobs are correctly executed and also check the job
output spool request to see for which systems the data is collected.
If for the History in the transaction ST06N not all the data or incorrect data is reported, you can
check in the transaction RZ23N which data exactly is available and exactly which measurements
and values are stored in the CPH database table ALPERFDB.
some notes can be referred:
1045559 - ST06: History data not available
548699 - FAQ: OS collector SAPOSCOL
371023 - OS07/ST06: Monitoring operating system data
1627564 - SAPOSCOL: Clearing Shared Memory and Updating Saposcol
How to analyse the missing performace data situation and how to check Saposcol issues?
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.

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

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
Sudhansu Swain © 2024
This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

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 always 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.

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

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/cont
ent.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.
Sudhansu Swain © 2024
This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

If you want to monitor a remote system 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

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

How to use SAP transaction ST06 for SAP performance analysis?

http://www.sap-perf.ca/sap-st06-for-performance-analysis/

Old SAPOSCOL and SAPOSCOL in SAPHOSTAGENT

Old Standalone SAPOSCOL:

The old saposcol is a simple standalone program. All it does is create a shared memory segment,

collect Operating System statistics and store them in shared memory (shared memory segment

99 area). The OS stats can then be read in transaction ST06. It is installed once on the physical

host, and it has nothing to do with the kernel or any other program.

Up until SAP_BASIS 710 (and until you upgrade to the 720 kernel as described in note

1636252), the old standalone saposcol executable is in the kernel directory. However it has

nothing to do with the kernel release of the system which means you can always use the highest

release of saposcol (downward compatibility). For a 46C system, you can use the 720 saposcol

for example.

Saposcol on Windows is started by a service (SAP note # 436186 - Installing saposcol as a

service).

Saposcol on Unix is started in the Unix startup script.

For more information on standalone saposcol refer to the 701 online documentation at:

"Operating System Collector SAPOSCOL":

Operating System Collector SAPOSCOL - Operating System Monitor - SAP Library

SAPOSCOL in SAPHOSTAGENT:

From SAP_BASIS 710 onwards, and also when you install saphostagent with the 720 kernel

(note 1636252), saposcol is contained in the saphostagent package. Saphostagent is also

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

completely downward compatible, so again you can install saphostagent 720 on a 46C system for

example.

• SAP note # 1031096 - Installing Package SAPHOSTAGENT

With saphostagent installed, saphostagent will start saposcol automatically.

On Windows with saphostagent the service is called SAPHostExec (SAP note # 1439391 -

SAPOSCOL Service deleted after SAPHostAgent Installation).

On Unix, when you install SAPHOSTAGENT as described in SAP note # 1636252 (Installing a

7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11):

"you must delete the call of the program SAPOSCOL from all the start profiles".

This way you will only be starting the correct SAPHOSTAGENT saposcol from the

HOSTAGENT directory, and not trying to start a second standalone saposcol from the kernel

directory, which can sometimes cause problems.

The dev_saphostexec trace file in /usr/sap/hostctrl/work provides details on your

SAPHOSTAGENT patch version and on the saphostexec process starting up.

Sudhansu Swain © 2024

This is your novel’s copyright information.
 SUDHANSU SWAIN - THE OPERATING SYSTEM MONITOR - SAPOSCOL

The saposcol trace file dev_coll is still located in the old /usr/sap/tmp directory. When saposcol

is being correctly started by SAPHOSTAGENT the dev_coll should have an opening line similar

to:

LOG: Profile : /usr/sap/hostctrl/exe/host_profile

on Unix, or:

LOG: "C:\Program Files\SAP\hostctrl\exe\saposcol.exe" -q -w60 pf="C:\Program

Files\SAP\hostctrl\exe\host on Windows.

When installing SAPHOSTAGENT on a remote host to monitor OS stats (for example to

monitor a standalone DB server) refer to SAP KBA Note # 2164753:

• 2164753 - CCMS Monitoring of non-SAP Server (eg. Standalone DB)

THE END

Sudhansu Swain © 2024

This is your novel’s copyright information.