TCode OS07 not giving the Disk Info

[Former Member]

Hi All,

I wanted to know the Server Disk Status i.e. Free Space on Server , I don' have root access. I use OS07 > Server Name > Detail Analysis Menu ..but, I don't see any data . At the end I see the message " OS Collector not running ( Shared Memory Not Available )

" ..Any input to solve this.. ?

Also, how would I check the Disk Space on JAVA only Server which has Portal on it ?

Thanks in Advance,

- Ishan

[Former Member · Accepted solution]

Hi Ishan,

You should execute "diskperf -y" at the OS level then restart the system. OSS note #8767 indicated this problem.

Best regards,

Orkun Gedik

[Former Member]

Hi

Also you can restart SAPOSCOL from OS level (command prompt, if using Windows) with following command:

saposcol -l

Regards

Rahul

[Former Member]

Hello,

Go to st06 - OS collector and start saposcol. If problem persists, click on the "Log File" and paste the output of saposcol log file.

Also ensure that you are using the latest SAPOSCOL version as per the note 19227

.

Best regards,

Warren

[Former Member]

Thanks, Warren.

At the time of posting the Q, matter was quite urgent ..so, the OS Admin gave me the info about free disk space.

However, just for my knowledge / record :

I started the OS Collectore through ST06 but, still I don't see the required info.

- I see only zeros under the columns i.e. Disk, Resp [ ms ], Utilization [ % ] , Queue Len, Wait [ ms ], Serv [ ms ], Kbyte [/s], Oper

[s] etc.

- OSCol Version seems ok as per note ( It's not THE latest, but it is as per the SAP Kernel Version i.e. 640 )

I have copy/paste the log file here. Pl. let me know what would be the workaround. As, not having the root access , I frequently need

to know the Free Disk Space Available on a Specific Server. Even if there's some data in the above columns, I don't see any column like ' Free ' or ' Available Disk Space ' . So, is this ST06 is the right one to check the free disk Space ?

Your help is sincerely appreiciated and would be rewarded with Appropriate Points.

Thanks n' Regards,

- Ishan

>>> Content of the Log File :

Contents of log file

SAPOSCOL version COLL 20.90 640 - 20.54 NT 06/06/06, 32 bit, multithreaded, Non-Unicode

compiled at Jul 17 2006

systemid 560 (PC with Windows NT)

relno 6400

patch text COLL 20.90 640 - 20.54 NT 06/06/06

patchno 139

intno 20020600

running on LEXUS Windows NT 5.2 3790 Service Pack 2 4x Intel 801586 (Mod 3 Step 4)

12:13:59 27.05.2008 LOG: Profile : no profile used

12:13:59 27.05.2008 LOG: Saposcol Version : [COLL 20.90 640 - 20.54 NT 06/06/06]

12:13:59 27.05.2008 LOG: Working directory : D:\usr\sap\PRFCLOG

12:13:59 27.05.2008 LOG: Allocate Counter Buffer [10000 Bytes]

12:13:59 27.05.2008 LOG: Allocate Instance Buffer [10000 Bytes]

12:13:59 27.05.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

12:13:59 27.05.2008 LOG: Shared Memory Size: 53348.

12:13:59 27.05.2008 LOG: Connected to existing shared memory.

12:13:59 27.05.2008 LOG: Reused shared memory. Clearing contents.

12:14:02 27.05.2008 LOG: Collector daemon started

12:14:02 27.05.2008 LOG: Don't use put-file (Taken on other system)

12:14:02 27.05.2008 LOG: Collector PID: 5092

12:14:12 27.05.2008 LOG: Process Monitoring active.

12:14:12 27.05.2008 LOG: searching for Process Monitoring Templates in D:\usr\sap\PRFCLOG\dev_proc

12:14:12 27.05.2008 LOG: searching for Process Monitoring Templates in D:\usr\sap\PRFCLOG\procmon\

12:14:12 27.05.2008 LOG: The following processes will be monitored:

12:14:12 27.05.2008 LOG: Process: jlaunch-DSAPINFO=B35_00_dispatcher* for user: SAPServiceB35

12:14:12 27.05.2008 LOG: Process: jlaunch-DSAPINFO=B35_00_server* for user: SAPServiceB35

12:14:12 27.05.2008 LOG: Process: jlaunch-DSAPINFO=B35_00_sdm* for user: SAPServiceB35

<<<<<

[Former Member]

Hi

Once you restart the SAPOSCOL, it takes certain amount of time for the data to get refreshed (Around 10 sec).

But if you are getting no values at all try these commands at OS level in the sequence:

saposcol -k will stop the SAPOSCOL

saposcol -c will clear the shared memory

saposcol -l will start the SAPOSCOL

Also updating kernel to the latest version could help you.

Regards

Rahul