cancel
Showing results for 
Search instead for 
Did you mean: 

SAPOSCOL Issue

Former Member
0 Kudos

Dears,

We are using SAP R/3 4.7 on Unix with Oracle 9i.Issue is that in ST06 when I click on OS log in details analysis ->Previous 24 hours i get an error message :

"Can not get OS log information for msldbci_PRD_00".

"Problem on remote host,Please check your SAPOSCOL and your CCMS agent".

In SAPOSCOL log file:

It shows error:

"Can not identify system, assume Series 800"

"Can not open /usr/sap/tmp/dev_proc fopen() failed.

Please suggest how to resolve the issue.

Deepak

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hello Deepak

Please Take A Look At This Note

Note 173160 - SAPOSCOL not running ? HPUX 11

May be this is going to work in your Case

Thanks & Regards

Shishir

Former Member
0 Kudos

Hello Deepak,

Please dowmload the Latest SAPOSCOL SAR File from the market place & new replace the old files with new files.

Trust Me Its going to solve your problem.

Thanks & Regards

Shishir

Former Member
0 Kudos

Hi Shishir,

So if I will upgrade SAPOSCOL only without upgrading other kernel components,Will it create any problem in future and can i apply latest patch of 700 kernel also of SAPOSCOL or as I am having kernel 640,i should apply latest patch of SAPOSCOL of kernel 640 only.

Deepak.

Edited by: Deepak Mittal on Aug 18, 2008 8:47 AM

Former Member
0 Kudos

Read 2 notes

Note 548699 - FAQ: OS collector SAPOSCOL

Note 918279 - Version history for saposcol on HP-UX

Regards.

Former Member
0 Kudos

> "Problem on remote host,Please check your SAPOSCOL and your CCMS agent".

Hi Deepak,

can you ping to the remote host?

do you see the message "NiConnect Unsuccessful, Return Code: -0012" in your system log? or alerts? if so please contact the network team as there is a communication failure due to network issues.

Regards,

Srihari

Former Member
0 Kudos

Hi Srihari,

I do not find any such message in my system log.

Deepak.

Former Member
0 Kudos

Hello. About "Can't identify system, assume Series 800" this warning are fixed in new SAPOSCOL -->

Note 918279 - Version history for saposcol on HP-UX

About Can not open /usr/sap/tmp/dev_proc fopen() failed

are you see this file? Are you able to openit ? Check permissions and owner, check BDF are all ok?

Try to check your saposclo status --> ST06 --> OPERATING SYSTEM COLLECTOR --> you can start , stop , and check status from here.

Regards.

Former Member
0 Kudos

Hi,

I checked that SAPOSCOL is running fine and its status shows:

Mon Aug 18 09:50:44 2008 interval 10 sec.

HP-UX MSLCIDB B.11.23 U ia64 0012175506

Collector Version: COLL 20.85 04/03/01 620 - hpxOscol 07/2003

Date/time 18.08.2008 10:12:25 Start of Collector Mon Aug 18 09:44:43 2008#

Status report

Collector Versions

running COLL 20.85 04/03/01 620 - hpxOscol 07/2003

dialog COLL 20.85 04/03/01 620 - hpxOscol 07/2003

Shared Memory attached

Number of records 3798

Active Flag active (01)

Operating System HP-UX MSLCIDB B.11.23 U ia64 0012175506

Collector PID 12429 (0000308D)

Collector running

Start time coll. Mon Aug 18 09:52:42 2008

Current Time Mon Aug 18 10:12:25 2008

Last write 12429 (0000308D)

Collector running

Start time coll. Mon Aug 18 09:52:42 2008

Current Time Mon Aug 18 10:12:25 2008

Last write access Mon Aug 18 10:12:16 2008

Last Read Access Mon Aug 18 10:08:32 2008

Collection Interval 10 sec (next delay).

Collection Interval 10 sec (last ).

Status

Collect Details ? required

Refresh required

Header extention structure

number of x-header records 1

records 60

number of free com. records 60

resulting offset to 1.data rec. 61

Trace level 2

Collector in IDLE - mode ? NO

become idle after 300 sec without read access.

without read access.

length of idle interval 60 sec

length of norm.interval 10 sec

Deepak

Former Member
0 Kudos

Hi Sergo

About

"

are you see this file? Are you able to openit ? Check permissions and owner, check BDF are all ok?"

I do not see that file but that is also not available in other systems in which system is working fine.

Beside it permissions on usr/sap/trans is also same same on all servers and bdf is also Ok.

Deepak.

Former Member
0 Kudos

When you execute --> ST06 --> OS log in details analysis ->Previous 24 hours , it trys to open :

/var/adm/syslog/syslog.log file.

try to open ut manualy , are you can? try to restart SAPOSCOL.

P.S. i'm not say about TRANS directory , chek /usr/sap/tmp/dev_proc file in tmp directory

Regards.

Former Member
0 Kudos

Hi Sergo,

Checked /var/adm/syslog/syslog.log file,I am able to open it.Also checked its permissions,Its also same to the servers on which we dnt have any issue.

Also checked /usr/sap/tmp/dev_proc file it doesnot exist in servers,but this file is also not available on other servers.

Already restarted SAPOSCOL but issue is same.

Deepak.

Former Member
0 Kudos

Hi,

I think your oscol process not started on your server. So first of all login with sidadm user and fire command "saposcol -s" and check the status of oscol.

If oscol is not started then start it by firing command "saposcol -l".

If still it gives error then please paste the oscol log.