ST06 data not reflecting

[Former Member]

Dear Experts,

WE are running on ECC 6.0 on Windows MSSQL 2005 platform kernel level 146.

Since yesterday we are not able to see any value in ST06 transaction code. ( 0 values found )

We have not done any changes in system and SAPOSCOL is running fine.

What could be the reason for the same. I have also rebooted system twice but didnt helped.

Best Regards,

AjitR

[Former Member]

Hi Ajit,

Apart from your SAPOSCOL running fine, if you want the information in ST06 there are certain housekeeping jobs that you need to schedule in frequency to get the latest data.

Check and schedule SAP_COLLECTOR_FOR_PERFMONITOR

use SM36 -> Standard Jobs -> select jobs and schedule them.

If you want the recent data click on Refresh Display in ST06 to get the recent data.

Regards,

Nilesh

[Former Member]

Nilesh ,

Job SAP_COLLECTOR_FOR_PERFMONITOR is running fine on hourly basis and even after refresh data i am not getting any values.

here is the log of saposcol for your ref.

SAPOSCOL version COLL 20.95 700 - 20.64 NT 07/10/17, 64 bit, multithreaded, Non-Unicode

compiled at Feb 3 2008

systemid 562 (PC with Windows NT)

relno 7000

patch text COLL 20.95 700 - 20.64 NT 07/10/17

patchno 146

intno 20050900

running on SAPDEV Windows NT 5.2 3790 Service Pack 1 8x AMD64 Level 6 (Mod 15 Step 7)

02:22:21 26.05.2008 LOG: Profile : no profile used

02:22:21 26.05.2008 LOG: Saposcol Version : [COLL 20.95 700 - 20.64 NT 07/10/17]

02:22:21 26.05.2008 LOG: Working directory : K:\usr\sap\PRFCLOG

02:22:21 26.05.2008 LOG: Allocate Counter Buffer [10000 Bytes]

02:22:21 26.05.2008 LOG: Allocate Instance Buffer [10000 Bytes]

02:22:22 26.05.2008 LOG: Shared Memory Size: 29074.

02:22:22 26.05.2008 LOG: Connected to existing shared memory.

02:22:22 26.05.2008 LOG: Reused shared memory. Clearing contents.

02:22:25 26.05.2008 LOG: Collector daemon started

02:22:25 26.05.2008 LOG: read coll.put Mon May 26 02:22:20 2008

02:22:25 26.05.2008 LOG: Collector PID: 2308

02:22:35 26.05.2008 LOG: Process Monitoring active.

02:22:35 26.05.2008 LOG: searching for Process Monitoring Templates in K:\usr\sap\PRFCLOG\dev_proc

02:22:35 26.05.2008 LOG: searching for Process Monitoring Templates in K:\usr\sap\PRFCLOG\procmon\

02:22:35 26.05.2008 LOG: The following processes will be monitored:

02:22:35 26.05.2008 LOG: Process: jlaunch-DSAPINFO=DEV_00_dispatcher* for user: SYSTEM

02:22:35 26.05.2008 LOG: Process: jlaunch-DSAPINFO=DEV_00_server* for user: SYSTEM

02:22:35 26.05.2008 LOG: Process: jlaunch-DSAPINFO=DEV_00_sdm* for user: SYSTEM

02:22:35 26.05.2008 LOG: Process: jlaunch-DSAPINFO=NDV_10_dispatcher* for user: SAPServiceNDV

02:22:35 26.05.2008 LOG: Process: jlaunch-DSAPINFO=NDV_10_server* for user: SAPServiceNDV

02:22:35 26.05.2008 LOG: Process: jlaunch-DSAPINFO=NDV_10_sdm* for user: SAPServiceNDV

[Former Member]

Ajit,

Is your ECC 6.0 system a Non-Unicode System ?

Regards,

Nilesh

[Former Member]

NON Unicode

[Former Member]

non unicode installation for ABAP + JAVA system

[Former Member]

Dear Experts,

Could you recommend any SAP note which talks about replacing SAP Unicode kernel for NON-Unicode system after Java-ADD IN installation.

About SAPOSCOL service ...its running under user SAPSERVICESID and path for executable is

K:\usr\sap\DEV\SYS\exe\run

Ideally for any Unicode ABAP+java installation it should be

K:\usr\sap\DEV\SCS01\exe

I tried to change the path in services through REGEDIT but still results are same as before

[Former Member]

Hi dear ajju rane. Read this : Note 688131 - Windows: missing data in ST06/OS06

Regards.

[Former Member]

No i have required files under system32 directory and

Registry does not contain parameter 'Disable Performance Counters'

[Former Member]

Hi,

Can you try using OS07 and select your RFC destination <hostname>_<SID>_<nr>.

and check through OS06.

Other option could be to lower down the patch level of SAPOSCOL only. Try replacing the current SAPOSCOL with previous patch level. Confirm your exe path with AL11 and directory name DIR_EXECUTABLE. You will need to stop/start SAPOSCOL only for this option.

Meanwhile raise a call with SAP.

Regards,

Nilesh

[Former Member]

Hi,

Please make sure that SAP_COLLECTOR_FOR_PERFMONITOR is scheduled in client 000 with user DDIC or with a user with the same authorization.

It is also important that it is scheduled only once per hour and close to o'clock (it has been observed that jobs planned at half past or at anytime not close to o'clock may not collect data correctly).

Confirm this before you try to lower down the patch level of SAPOSCOL.

Regards,

Nilesh

[Former Member]

In fact problem solved after changing the owner .... Unfortunately it started working fine after OS level restart ( once owner is changed )

Thanks to all.

[Former Member]

saposcol need to run using an account with administrators group membership.

SAPServiceSID isn't member of the local administrators group.

Therefore with 700 and later based systems SAPoscol is started using the SIDadm account.

regards

Peter