SAPOSCOL

[Former Member]

Hello Experts,

SAPOSCOL on our Quality system is giving issues.

I tried to start it from ST06 but was not able to start it.

Below is the log from ST06:

SAPOSCOL version COLL 20.95 700 - V2.6.1 2007-06-14 HP-UX IA64, 64 bit, single threaded, Non-Unicode

compiled at Apr 5 2008

systemid 274 (HP (IA-64) with HP-UX)

relno 7000

patch text COLL 20.95 700 - V2.6.1 2007-06-14 HP-UX IA64

patchno 146

intno 20050900

running on HP-UX B.11.23 U ia64

06:20:56 24.08.2008 LOG: Profile : no profile used

06:20:56 24.08.2008 LOG: Saposcol Version : [COLL 20.95 700 - V2.6.1 2007-06-14 HP-UX IA64]

06:20:56 24.08.2008 LOG: Working directory : /usr/sap/tmp

06:20:56 24.08.2008 LOG: Identified system as: HP-UX B.11.23 ia64 hp server BL860c

06:20:56 24.08.2008 LOG: Architecture identified as 64-bit

06:20:58 24.08.2008 LOG: Shared Memory Size: 1998448.

06:20:58 24.08.2008 LOG: Shared Memory was created by process:21290

06:20:58 24.08.2008 LOG: ==== Collector submitted. This is the parent process after fork.=====

06:21:01 24.08.2008 LOG: ==== Collector submitted. This is the child process after fork()=====

06:21:04 24.08.2008 LOG: Collector daemon started

06:21:04 24.08.2008 LOG: read coll.put Sun Aug 24 06:18:26 2008

06:21:04 24.08.2008 LOG: Collector PID: 21297

06:21:14 24.08.2008 LOG: Initialize Process Monitoring :

06:21:14 24.08.2008 LOG: Process Monitoring active.

06:21:14 24.08.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc

06:21:14 24.08.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

06:21:14 24.08.2008 LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.

06:21:14 24.08.2008 LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.

06:04:12 31.08.2008 LOG: Stop Signal received.

06:04:12 31.08.2008 LOG: ==== Starting to deactivate collector ==========

06:04:12 31.08.2008 LOG: ==== Collector deactivated ================

Pls tell me what to do to start the OS Collector.

Thanks!!!

[Former Member]

It's a shared memory problem.

your system was unable to create shared memory to start SAPOSCOL.

Above command will delete occupied shared memory and recreate for new processes

Regards'

Nick Loy

[Former Member]

Hello

Try this it might work ...

as root give ipcs -ma and it will give u many processs running ... check for the one process which ends with dbe , if you see that process give ipcrm -m PID and try to start SAPOSCOL it should work .

Regards,

Ershad Ahmed

[Former Member]

Dear Ershad,

Your solution worked for me. Thank you dude. Can you please explain why this propblem occurs & what does this ipcs command do???

Regards,

Ashish.

[Former Member]

Great !! It worked .. Thx lot

[Former Member]

Hi,

As per your above update

The system used is HP unix 64 bit non unicode system

patch text COLL 20.95 700 - V2.6.1 2007-06-14 HP-UX IA64
06:21:14 24.08.2008 LOG: Process Monitoring active.
06:21:14 24.08.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
06:21:14 24.08.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
06:21:14 24.08.2008 LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.

For your Information:-

-

---

As of Saposcol version 20.86 (saposcol - version) it is possible to permanently collect information for certain processes, regardless of whether they are in the top 40 of the CPU list.

I think Saposcol is looking for /usr/sap/tmp/procmon/ directory to collect informaiton of OS process.

I hope thats where it is failing as system unable to find the same.

See the below Snotes :-

-

---

Note 790639 - SAPOSCOL and ABAP server: Monitoring processes

Note 451166 - SAPOSCOL and CCMS agents: Monitoring processes

Rgds

Radhakrishna D S

[former_member227600]

hi ,

Login as <SID>adm & give the following command saposcol -l to start the saposcol.

The following option you have to start,show status ,stop the saposcol.

saposcol -l: Start OS Collector

saposcol -k: Stop OS Collector

saposcol -d: OS Collector Dialog Mode

saposcol -s: OS Collector Status

Regards

karan

[Former Member]

When I 'm trying to start SAPOSCOL i get a message :Cannot create shared memory.

[former_member204746]

reboot and try again.

[JPReyes]

Also make sure that SAPOSCOL has permisssion 4755.

Regards

Juan

[Former Member]

And the owner is root.

There is a saproot.sh in the exe dir. Re-run this script (as root) to set the appropriate ownership and permissions for the br*tools and saposcol.

Regards

Doug