Skip to Content

Unable to view st06n data on Database

Hi,

From st06n we were able to access, DB server information . (cpu info, memeory info, file system, top 40 cpu processes, swap size etc)

But suddenly , from 2 days time..... these details are not shown on st06n

(On other application servers, those details are shown)

Details are not shown only on DB Server.

I have checked the saposcol status on DB. It was like this.

**************************************************************

Collector Versions :

running : COLL 20.95 700 - v2.16, AMD/Intel x86_64 with Linux

dialog : COLL 20.95 700 - v2.16, AMD/Intel x86_64 with Linux, 2008/08/28

Shared Memory : attached

Number of records : 6066

Active Flag : active (01)

Operating System : Linux erpdb101 2.6.16.60-0.54.5-smp #1 SMP Fri Sep

Collector PID : 7996 (00001F3C)

Collector : running

Start time coll. : Mon Dec 27 18:15:15 2010

Current Time : Thu Aug 25 14:12:16 2011

Last write access : Thu Aug 25 14:11:18 2011

Last Read Access : Tue Aug 23 11:57:20 2011

Collection Interval : 60 sec (next delay).

Collection Interval : 61 sec (last ).

Status : free

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 1

Collector in IDLE - mode ? : YES

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 10 sec

**************************************************************

Then I have , stop and restarted the saposcol.

Now new status is like this;

**************************************************************

Collector Versions :

running : COLL 20.95 700 - v2.16, AMD/Intel x86_64 with Linux

dialog : COLL 20.95 700 - v2.16, AMD/Intel x86_64 with Linux, 2008/08/28

Shared Memory : attached

Number of records : 6066

Active Flag : active (01)

Operating System : Linux erpdb101 2.6.16.60-0.54.5-smp #1 SMP Fri Sep

Collector PID : 26379 (0000670B)

Collector : running

Start time coll. : Thu Aug 25 14:22:07 2011

Current Time : Thu Aug 25 15:15:24 2011

Last write access : Thu Aug 25 15:14:36 2011

Last Read Access : Thu Jan 1 05:30:00 1970

Collection Interval : 60 sec (next delay).

Collection Interval : 60 sec (last ).

Status : free

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 2

Collector in IDLE - mode ? : YES

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 10 sec

**************************************************************

But Still, data cannot be seen from st06n for the DB server.

The status of the sapccmsr is like follows;

-


erpdb101:prdadm 68> sapccmsr -status

INFO: CCMS agent sapccmsr working directory is /usr/sap/tmp/sapccmsr

INFO: CCMS agent sapccmsr config file is /usr/sap/tmp/sapccmsr/csmconf

INFO: Central Monitoring System is [PRD]. (found in config file)

INFO: No agent running (no actual pid, no actual shared memory)

  • CCMS Agent is registered at central system PRD ********

  • sapccmsr Agent is not running ********

EXITING with code -1

-


pls, let me know how can i proceed with this issue.

How to display the db o/s values (CPU info, Mem info, File sys...) from st06n/os07 ?

regards,

Zerandib

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 26, 2011 at 02:24 AM

    SAP note 189072, 19227

    Ensure that SAPOSCOL is running under <sid>adm at OS level, and try clearing the shared memory by the following

    method:

    saposcol -d

    Collector > clean

    Collector > quit

    saposcol -k to stop the collector

    saposcol -d (before restarting)

    Collector > leave (You should get a message Shared memory deleted)

    Collector > quit

    cd /usr/sap/tmp

    mv coll.put coll.old (rename the file - it stores the saposcol history data)

    cd

    saposcol (run it again)

    Regards,

    Vincent

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 25, 2011 at 07:20 PM

    Hi,

    Could you execute the command, below in order to understand whether the saposcol is collecting the data.

    saposcol -d
    dump cpu
    exit

    Could you verify that the saposcol can read the cpu performance data?

    Best regards,

    Orkun Gedik

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Orkun,

      I have checked,

      saposcol -d

      dump cpu

      Yes , it collects the data successfully.

      But still

      Collector in IDLE - mode ? : YES (What this means..... Is the collector is IDLE?)

      Will that be any issue with sapccmsr. Coz here ******** sapccmsr Agent is not running ********

      (For non SAP systems like DB, is it using SAPCCMSR to send OS data to SAP level)

      thx,

      Zerandib

  • Jul 16, 2012 at 11:41 AM

    Main reason is "sapccmr" is not running;

    # sapccmsr –DCCMS pf=/usr/sap/PRD/SYS/profile/sapccmsr.pfl

    # sapccmsr -status

    Add comment
    10|10000 characters needed characters exceeded