on 08-18-2008 6:35 AM
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
> "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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.