sapnote_0000189072

7/18/2019 sapnote_0000189072

http://slidepdf.com/reader/full/sapnote0000189072 1/3

21.10.2013 Page 1 of 3

SAP Note 189072 - ST06/OS06: No data or incorrect datadisplayed

Note Language: English Version: 17 Validity: Valid Since 21.11.2002

Summary

Symptom In ST06/OS06, data is either displayed incorrectly or not at all

and/or

messages such as 'shared memory not available' are displayed.

and/or

on Windows NT / Windows 2000:

In RZ20, the file systems are missing in the "Operating System" monitor.

Other termssaposcol, shared memory, 64-bit, swap space, cpu, disk, memory, lan, file

system, hardware info, operating system log, RZ20, os_sys.log, dev_coll

Reason and Prerequisites

The data for ST06/OS06 and RZ20 is collected by saposcol. The saposcol isan independent program that runs in the operating system background

regardless of the R/3 instances. It collects data about operating system

resources and makes this data available to every R/3 via shared memory.

Only one saposcol is needed per computer even if several R/3 instances or

even several R/3 systems are running there.

Solution

Possible error scenarios:

1. Incorrect values: The R/3 system reads ST06 and RZ20 values from

shared memory. Incorrect values may already be there. The saposcol hasa dialog interface on operating system level at its disposal. With

this you can directly view the values from the shared memory. Call

saposcol -d.

Using the command 'help' you can get an overview of all available

commands. The 'dump' command is important for displaying specific

values. If values are incorrectly or incompletely displayed here, you

can stop the collector and delete the values from shared memory.

saposcol -d

kill

leave

exit

Then the shared memory backup file coll.put must be deleted. coll.put

can by default be found in the directory /usr/sap/tmp.

In any case, check if your saposcol version is current (see below).

2. No values and/or problems with shared memory

Check whether saposcol belongs to user 'root' and whether the

authorizations are correct: -rwsr-x---

Because the values of saposcol must be visible for all R/3

systems/instances on a host, saposcol writes data in the shared memory

segment with key 1002. This shared memory segment must not be changed

(for example, by setting profile parameter ipc/shm_psize_1002). In all

profiles, check whether the parameter ipc/shm_psize_1002 is set. If it

is, this parameter must be removed from the profiles ---> Note 37537.

7/18/2019 sapnote_0000189072


21.10.2013 Page 2 of 3


3. In general, a current version of saposcol should be used. Because it

is an independent program, saposcol can be stopped and switched in a

running R/3 system If you want to replace saposcol, stop the collector

that is running, delete the coll.put file if necessary and install a

new saposcol version as specified in Note 19227.

The saposcol is not so dependent on the R/3 release but rather on the

operating system release. Therefore, the naming convention of the

saposcol versions refers to the operating system.

You can find the appropriate saposcol for your operating system

version(s) in the directory specified in Note 19227.

4. Windows 2000 and Windows NT

Saposcol can only collect the values for disk I/O and display them in

the SAP system, if the corresponding performance counters were

activated via the command

diskperf -Y

Then, the computer has to be started again. For further information onthe "diskperf" command, call "diskperf /?"

5. Windows NT

In the case of incorrect or empty displays in ST06/OS06 under

Windows NT, note that the NT SAPOSCOL requires the PDH.DLL (see Note19227) and NT40 Service Pack 5 as of version 4.0 in order to be able

to display the data correctly.

If there are problems with the display of the OS syslog or the

hardware info via OS06/ST06 under Windows NT, read Note 96397.

6. ST06/OS07 does not display the operating system log (button: OS Log).

The following error message is issued instead:

File is empty. Try Read again.

The information of where to find the operating system log is stored in

the shared memory of saposcol. With saposcol destinations that are no

SAP application servers (CCMS agents and rfcoscol destinations), the

patch of the operating system log is determined correctly but the

program tries to open file os_sys.log on the local application server.

The error was corrected for CCMS agent destinations by the Support

Packages below.

7. ST06/OS07 does not display the saposcol log file (Os Collector,

button: Log File), or a wrong file is displayed.

The error was corrected by the Support Packages below.

8. ST06/OS07 truncates the path name of the Saposcol log file, and an

error message is displayed:

Cannot open file: \\<hostname>\saploc\PRFCLOG\dev

The error is corrected with the current one of the Support Packages

listed below.

Header Data

Release Status: Released for Customer

Released on: 25.11.2002 07:22:17Master Language: German

Priority: Recommendations/additional info

7/18/2019 sapnote_0000189072


21.10.2013 Page 3 of 3


Category: Program error

Primary Component: BC-CCM-MON Monitoring

Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_APPL 30 300 31I X

SAP_APPL 40 40A 40B X



SAP_BASIS 46 46B 46D

SAP_BASIS 60 610 620 X

Support Packages

Support Packages Release Package Name

SAP_BASIS 46B SAPKB46B37

SAP_BASIS 46B SAPKB46B51

SAP_BASIS 46C SAPKB46C28

SAP_BASIS 46C SAPKB46C42

SAP_BASIS 46D SAPKB46D17

SAP_BASIS 46D SAPKB46D31

SAP_BASIS 610 SAPKB61006

SAP_BASIS 610 SAPKB61011

SAP_BASIS 610 SAPKB61030SAP_BASIS 620 SAPKB62019

Related Notes

Number Short Text

688131 Windows: missing data in ST06/OS06

96397 NT: No display of HW info and OS syslog in ST06

19227 Open newest saposcol

Attributes

Attribute Value

Transaction codes FILE

Transaction codes HIER

Transaction codes PACK

Transaction codes RZ20

Transaction codes ST06

old release 00145B. HR-PM

0189072

old release 00146C. R3STD

0189072

Documents

sapnote_0000189072