Problem with OSLOG in ST06: SAP R3, Oracle9i, Sunsolaris

[Former Member]

Hi Experts!!

Am getting the following error from ST06 ->OSLog

.......................................................................

cannot get OS Log information for prd47e_P47_00

error message:Invalid Request Id

Please check your Saposcol and your CCMS Agents

................................................................................

But when I see OS collector status it is showing "Running" as below

-

---

Collector Versions

running COLL 20.94 640 - V3.73 64Bit

dialog COLL 20.94 640 - V3.73 64Bit

Shared Memory attached

Number of records 3541

Active Flag active (01)

Operating System SunOS prd47e 5.9 Generic_117171-08 sun4u

Collector PID 939 (000003AB)

Collector running

Start time coll. Sat May 17 22:36:35 2008

Current Time Mon May 19 16:50:31 2008

Last write access Mon May 19 16:50:26 2008

Last Read Access Mon May 19 16:48:20 2008

Collection Interval 10 sec (next delay).

Collection Interval 10 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 56

Resulting offset to 1.data rec. 61

Trace level 2

Collector in IDLE - mode ? NO

become idle after 300 sec without read access.

Length of Idle Interval 60 sec

Length of norm.Interval 10 sec

-

---

Can please guide how to fix this problem!!!

Thanks in advance

Rgds

[JPReyes]

have you tried to restart you SAPOSCOL?

Regards

Juan

[Former Member]

Hi Juan Reyes,

Thanks for reply!!!

Just couple days before I restarted SAPOSCOL and whole system. Can I try one more time ONLINE???

rgds

[JPReyes]

sure... restart SAPOSCOL won't hurt your system.

Also check the saposcol log for errors.

Regards

Juan

[Former Member]

Hi Juan,

Yes! I stopped and restarted SAPOSCOL fron ST06.

But there is no improvement

Regards

vrjalli

[Former Member]

SAPOSCOL Log contents are:

SAPOSCOL version COLL 20.94 640 - V3.73 64Bit, 64 bit, single threaded, Non-Unicode

compiled at Mar 17 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text COLL 20.94 640 - V3.73 64Bit

patchno 175

intno 20020600

running on prd47e SunOS 5.9 Generic_117171-08 sun4u

-

---

17:17:24 19.05.2008 LOG: Profile : no profile used

17:17:24 19.05.2008 LOG: Saposcol Version : [COLL 20.94 640 - V3.73 64Bit]

17:17:24 19.05.2008 LOG: Working directory : /usr/sap/tmp

17:17:24 19.05.2008 LOG: Process Monitoring active.

17:17:24 19.05.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc

17:17:24 19.05.2008 LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

17:17:24 19.05.2008 LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.

17:17:24 19.05.2008 LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.

17:17:24 19.05.2008 LOG: RefreshDeviceFiltering failed - no filtering done!

17:17:25 19.05.2008 LOG: Shared Memory Size: 375694.

17:17:25 19.05.2008 LOG: Shared Memory was created by process:10630

17:17:25 19.05.2008 LOG: ==== Collector submitted. This is the parent process after fork.=====

17:17:28 19.05.2008 LOG: ==== Collector submitted. This is the child process after fork()=====

17:17:31 19.05.2008 LOG: Collector daemon started

17:17:31 19.05.2008 LOG: read coll.put Tue Jul 26 17:00:07 2005

17:17:31 19.05.2008 LOG: Collector PID: 10651

rgds

[JPReyes]

/usr/sap/tmp/procmon does not exist or cannot be opened.

check if the permission are correct and if or the file exist.

Regards

Juan

[Former Member]

Hi juan,

I do have Development server there also there is no /usr/sap/tmp/procmon and same log it is showing as

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

But in ST06 - - > oslog am getting entries in Developemnt server

regds

[Former Member]

Have you cleaned up the ipc's before restarting the instance? if not, shutdown the instance completely (make sure all <sid>adm processes are dead), clean shared memory and restart the instance again.

-RK

[Former Member]

Hi RK,

May be your are correct!!!

Let me check and revert you. Since this is production environment I need to wait for the window to check the same.

Rgds

[Former Member]

Hi ,

Still the problem is existing!!!

Here is the whole process how I cleared the processes and started SAP application:

-

---

bash-2.05$ id

uid=60004(p47adm) gid=100(sapsys)

bash-2.05$ ipcs

IPC status from <running system> as of Sun May 25 14:41:59 IST 2008

T ID KEY MODE OWNER GROUP

Message Queues:

Shared Memory:

m 257 0 rw-r--- orap47 dba

m 2 0x1aea19b0 rw-r--- orap47 dba

m 4 0x382be84 --rw-rw-rw- p47adm sapsys

m 27 0x274f rw-r--- p47adm sapsys

Semaphores:

s 0 0xf9008962 ra-rr-- root root

s 1 0xf9008963 ra-rr-- root root

s 2 0xf9008966 ra-rr-- root root

s 65539 0xf9008969 ra-rr-- root root

s 65540 0xf900896a ra-rr-- root root

s 65541 0xf900896c ra-rr-- root root

s 65542 0xf9008967 ra-rr-- root root

s 262151 0x81b11ba4 ra-r--- orap47 dba

s 83 0x2dca11 ra-r--- p47adm sapsys

bash-2.05$ ipcrm -s 83

bash-2.05$ ipcrm -m 27

bash-2.05$ ipcrm -m 4

bash-2.05$ ipcs

IPC status from <running system> as of Sun May 25 14:43:05 IST 2008

T ID KEY MODE OWNER GROUP

Message Queues:

Shared Memory:

m 257 0 rw-r--- orap47 dba

m 2 0x1aea19b0 rw-r--- orap47 dba

Semaphores:

s 0 0xf9008962 ra-rr-- root root

s 1 0xf9008963 ra-rr-- root root

s 2 0xf9008966 ra-rr-- root root

s 65539 0xf9008969 ra-rr-- root root

s 65540 0xf900896a ra-rr-- root root

s 65541 0xf900896c ra-rr-- root root

s 65542 0xf9008967 ra-rr-- root root

s 262151 0x81b11ba4 ra-r--- orap47 dba

bash-2.05$ saposcol

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

*****

• This is Saposcol Version COLL 20.94 640 - V3.73 64Bit

• Usage: saposcol -l: Start OS Collector

• saposcol -k: Stop OS Collector

• saposcol -d: OS Collector Dialog Mode

• saposcol -s: OS Collector Status

• Starting collector (create new process)

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

*****

bash-2.05$ startsap

Checking P47 Database

-

---

ABAP Database is running

Checking P47 Database

-

---

Starting SAP-Collector Daemon

-

---

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

• This is Saposcol Version COLL 20.94 640 - V3.73 64Bit

• Usage: saposcol -l: Start OS Collector

• saposcol -k: Stop OS Collector

• saposcol -d: OS Collector Dialog Mode

• saposcol -s: OS Collector Status

• The OS Collector (PID 10858) is already running .....

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

saposcol already running

Starting SAP Instance DVEBMGS00

-

---

Startup-Log is written to /usr/sap/p47adm/startsap_DVEBMGS00.log

Instance on host prd47e started

bash-2.05$

-

---

Rgds

[Former Member]

Hi. May be problem in sapccmsr ?

Read this,and try to restatr sapccmsr.

http://help.sap.com/saphelp_nw70/helpdata/EN/8b/f64352e1bfbd4eb43e432860504a1c/frameset.htm

Also read Note 548699 - FAQ: OS collector SAPOSCOL

Regards.

[Former Member]

Hi Sergo Beradze,

I think sapccmsr is not running.

-

---

bash-2.05$ 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

ERROR: cannot open config file /usr/sap/tmp/sapccmsr/csmconf.

INFO: Checking shared memory status of sapccmsr

• CCMS Agent is not registered ********

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

EXITING with code -1

-

---

bash-2.05$ sapccmsr -v

CCMS version 20040229, 64 bit, multithreaded, Non-Unicode

compiled at Jun 20 2004

systemid 370 (SUN on SPARC CPU with Solaris 2.2)

relno 6200

patch text patch collection 2004/3, OSS note 694057

patchno 1528

intno 20020600

running on prd47e SunOS 5.9 Generic_117171-08 sun4u

-

---

1. Do I need to register before starting???

2. Register/start/stop sapccmsr agent can be doen while application running???

I was able to see OSlog in ST06 previously, how come it goes all of sudden!!!

Rgds