Symptom

Cause

Solution

The saving of this data is not explicitly activated in transaction AL15.

See Setting the SAPOSCOL Destination in the Central System

The database tables are not filled regularly.

Check the reports RSHOSTDB and RSHOSTDC in accordance with SAP Note 12103.

The database table entries are deleted too early during the reorganization (up to SAP Basis 4.6A).

See SAP Note 336120

No values are displayed in the operating system monitor, or problems with the shared memory are reported.

SAPOSCOL does not have the correct authorizations (UNIX).

Set the authorizations (See Installing SAPOSCOL on a UNIX Host).

The shared memory segment with key 1002 was changed.

Check in the profiles of all instances whether the parameter ipc/shm_psize_1002 is set and delete it.

No values are displayed for hard disks under Windows NT/2000

The performance counter diskperf is not activated.

Activate it with the command diskperf –Y.

Incorrect data is displayed in the operating system monitor under Windows NT.

The file PDH.DLL is not in the Windows NT system directory.

Install the file (See Installing SAPOSCOL on a Windows Host).

The log files for the operating system (OS Log) and for SAPOSCOL (OS Collector ® Log File) are not displayed.

See SAP Notes 189072 and 178719

Hardware Info is not displayed in the operating system monitor.

Not every operating system provides this function; currently, HP-UX, NT, AS400, DEC, and SUN provide the relevant data about the hardware configuration.

Hardware Info is not displayed in the operating system monitor.

If the error occurs with Windows NT, it is usually due to the fact that DIR_PERF is not set or is set incorrectly.

See SAP Note 96397

The compare recent days function in the operating system monitor displays no values or incorrect values. However, the current values in the detail view and for Previous 24 hours are correct.

Error in SAPOSCOL

Import the Support Packages in accordance with SAP Note 431495.

The job SAP_COLLECTOR_FOR_PERFMONITOR is not running often enough.

Ensure that the job runs at least every 24 hours.

SAPOSCOL hangs when started under HP-UX 11.0. An analysis shows that SAPOSCOL is waiting for the result of the call sh -c echo lan ppa 1 display quit /usr/sbin /lanadmin -t.

With version 11.00.11, the data display is changed with the driver for a gigabit ethernet card (check with ps –ef | grep lanadmin).

Import the HP-UX patch PHNE_21865 or a later successor patch (such as PHNE_22930). The name of the patch is s7000_800 11.00 1000Base-SX/T B.11.00. [02-11] cumul. patch

SAPOSCOL and other tools for measuring the performance have a very high CPU utilization in AIX.

A change of the call vmgetinfo()leads to increased CPU load from tools for performance measurement (as of bos.mp.4.3.3.29 in AIX 4.3.3)

A memory leak in the routine fclose()leads to the termination of SAPOSCOL.

You can find corrections in http://techsupport.services.
ibm.com/server/support under:

APAR IY16813 (vmgetinfo)
APAR IY22308 (fclose in AIX 4.3.3)
APAR IY22844 (fclose in AIX 5.1)