SAPOSCOL File system monitor does not show all drives (OS06 / ST06 / OS07)

[Former Member]

Hi everyone,

Iu2019m facing an issue with certain drives not being monitored in saposcol / CCMS Filesystem monitor after ECC6 upgrade.

I can only see 3 drives.

The following errors are showing up in saposcol log.

01:05:15 26.01.2010 LOG: Allocate Instance Buffer [10000 Bytes]

01:05:47 26.01.2010 LOG: Shared Memory Size: 69672.

01:05:47 26.01.2010 LOG: Shared Memory was created by process:2836

01:05:50 26.01.2010 LOG: Collector daemon started

01:05:50 26.01.2010 LOG: read coll.put Tue Jan 26 00:59:12 2010

01:05:50 26.01.2010 LOG: Collector PID: 2836

01:06:00 26.01.2010 LOG: Process Monitoring active.

01:06:00 26.01.2010 LOG: searching for Process Monitoring Templates in C:\usr\sap\PRFCLOG\dev_proc

01:06:00 26.01.2010 LOG: searching for Process Monitoring Templates in C:\usr\sap\PRFCLOG\procmon\

01:06:00 26.01.2010 LOG: The following processes will be monitored:

01:08:01 26.01.2010 LOG: InitFsysData: PX_fsys_anz 4 > PX_fsys_anz_max 3

01:08:01 26.01.2010 LOG: only retrieving data for 3 logical disks

01:08:01 26.01.2010 LOG: PX_fsys_name[3]: L: not logged!

01:12:42 26.01.2010 LOG: InitFsysData: PX_fsys_anz 8 > PX_fsys_anz_max 3

01:12:42 26.01.2010 LOG: only retrieving data for 3 logical disks

01:12:42 26.01.2010 LOG: PX_fsys_name[3]: L: not logged!

01:12:42 26.01.2010 LOG: PX_fsys_name[4]: J: not logged!

01:12:42 26.01.2010 LOG: PX_fsys_name[5]: M: not logged!

01:12:42 26.01.2010 LOG: PX_fsys_name[6]: N: not logged!

01:12:42 26.01.2010 LOG: PX_fsys_name[7]: O: not logged!

01:12:52 26.01.2010 LOG: InitFsysData: PX_fsys_anz 9 > PX_fsys_anz_max 3

01:12:52 26.01.2010 LOG: only retrieving data for 3 logical disks

01:12:52 26.01.2010 LOG: PX_fsys_name[3]: L: not logged!

01:12:52 26.01.2010 LOG: PX_fsys_name[4]: J: not logged!

01:12:52 26.01.2010 LOG: PX_fsys_name[5]: M: not logged!

01:12:52 26.01.2010 LOG: PX_fsys_name[6]: K: not logged!

01:12:52 26.01.2010 LOG: PX_fsys_name[7]: N: not logged!

01:12:52 26.01.2010 LOG: PX_fsys_name[8]: O: not logged!

01:17:51 26.01.2010 LOG: InitFsysData: PX_fsys_anz 8 > PX_fsys_anz_max 3

01:17:51 26.01.2010 LOG: only retrieving data for 3 logical disks

01:17:51 26.01.2010 LOG: PX_fsys_name[3]: J: not logged!

01:17:51 26.01.2010 LOG: PX_fsys_name[4]: M: not logged!

Does anyone know where this parameter is set? (PX_fsys_anz_max)

Greatly appreciate any help.

Regards,

Ahmad M.

[Former Member · Accepted solution]

Hi,

Check if following files are missing in the %windir%\system32 directory:

perfc009.dat

perfd009.dat

perfh009.dat

perfi009.dat

and PDH.dll

also update the "saposcol" with the latest version..

Regards.

Rajesh Narkhede

[Former Member · Accepted solution]

Hi Rajesh,

The files you mentioned below are in C:\WINDOWS\system32

01/26/2010 01:09 AM 70,170 perfc009.dat

11/30/2005 08:00 PM 29,710 perfd009.dat

01/26/2010 01:09 AM 421,584 perfh009.dat

11/30/2005 08:00 PM 275,128 perfi009.dat

11/30/2005 08:00 PM 576,512 pdh.dll

Regards,

Ahmad M.

[Former Member · Accepted solution]

Hi,

Have you tried updating your SAPOSCOL with the latest version ?

Regards.

Rajesh Narkhede

[former_member524429 · Accepted solution]

Hi,

SAPOSCOL Version ?

saposcol -v

Upgrade your SAPOSCOL with latest version, if it is required.

Please refer the following SAP Notes to get more information.

Note 456902 - Incorrect file system values under Windows NT

Note 19227 - Open newest saposcol

Note 688131 - Windows: missing data in ST06/OS06

Note 189072 - ST06/OS06: No data or incorrect data displayed

Regards,

Bhavik G. Shroff

[Former Member · Accepted solution]

Hi Bhavik,

I tried patching the saposcol service but still no luck.

I was using patchno 32, now patchno 55. I read and followed all the steps in the notes you provided but still can't resolve the issue. I even cleared all the dev_coll and log files after patching. Below is the output of the logfile. Same error.

10:14:40 29.01.2010 LOG: Shared Memory Size: 427422.

10:14:40 29.01.2010 LOG: Connected to existing shared memory.

10:14:40 29.01.2010 LOG: MaxRecords = 654 <> RecordCnt + Dta_offset = 3968 + 61

10:14:40 29.01.2010 LOG: CountDynParts 225 records for RT_DISK

10:14:40 29.01.2010 LOG: CountDynParts 75 records for RT_FSYS

10:14:40 29.01.2010 LOG: CountDynParts 33 records for RT_CPU

10:14:40 29.01.2010 LOG: CountDynParts 75 records for RT_LAN

10:14:40 29.01.2010 LOG: Disk 9 Fsys 3 Cpu 8 Lan 3

10:14:40 29.01.2010 LOG: AdaptDynParts

10:14:40 29.01.2010 LOG: from shm computed

10:14:40 29.01.2010 LOG: CPU max: 8 8

10:14:40 29.01.2010 LOG: LAN max: 3 50

10:14:40 29.01.2010 LOG: FSYS max: 3 50

10:14:40 29.01.2010 LOG: DISK max: 9 50

10:14:40 29.01.2010 LOG: InitFsysData: PX_fsys_anz 5 > PX_fsys_anz_max 3

10:14:40 29.01.2010 LOG: only retrieving data for 3 logical disks

10:14:40 29.01.2010 LOG: PX_fsys_name[3]: Q: not logged!

10:14:40 29.01.2010 LOG: PX_fsys_name[4]: L: not logged!

10:14:40 29.01.2010 LOG: /* validation records */ 20

10:14:40 29.01.2010 LOG: /* disks * 25 */ + PX_disk_anz_max * 25 = 9 * 25 = 225

version

SAPOSCOL version COLL 20.95 701 - 20.68 NT 09/03/27, 64 bit, multithreaded, Non-Unicode

compiled at Aug 10 2009

systemid 562 (PC with Windows NT)

relno 7010

patch text COLL 20.95 701 - 20.68 NT 09/03/27

patchno 55

intno 20020600

running on MYBWESSPRD01 Windows NT 5.2 3790 Service Pack 1 8x AMD64 Level 15

Regards,

Ahmad M.

Edited by: EAC EAC on Jan 29, 2010 10:54 AM

[former_member524429 · Accepted solution]

Hi,

Have you performed following steps, which are mentioned in SAP Note [189072|https://service.sap.com/sap/support/notes/189072].

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.

----------------------------------

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 on the "diskperf" command, call "diskperf /?"

Regards,

Bhavik G. Shroff

[Former Member · Accepted solution]

Hi Bhavik,

Thanks for the help. My apologies for the late answer.

The following steps worked but only when the server was rebooted. (When I didn't reboot the server, the problem persisted.)

saposcol -d

kill

leave

exit

Reboot server.

Regards,

Ahmad M.