Operating System - HP-UX
1829143 Members
2037 Online
109986 Solutions
New Discussion

Getting error OCR initialization failed accessing OCR device: PROC-26: in syslog

 
SOLVED
Go to solution
Ninad_1
Honored Contributor

Getting error OCR initialization failed accessing OCR device: PROC-26: in syslog

Hi All,

I am getting following errors every few minutes in the syslog.log.
Apr 20 10:00:02 xphx0201 syslog: OCR initialization failed accessing OCR device: PROC-26: Error while accessing the physical storage Operating System error [No such file or directory] [2]

System is rp7420 with HP-UX 11.11 Dec 2006.The server runs normally, but I am concerned about the errors.

Tried to find on net but did not find anything conclusive, hence need your help.

Thanks,
Ninad
2 REPLIES 2
Solution

Re: Getting error OCR initialization failed accessing OCR device: PROC-26: in syslog

Ninad,

These are Oracle CRS (Cluster Ready Services) errors. They indicate that an Oracle process (I think ocssd) can't access the Oracle Cluster Registry (OCR) and probably the voting disk as well.

If you aren't the DBA, you need to talk to them and determine what raw devices they are using for the OCR and voting disk, and then make sure they are accessible to the Oracle user.

A common problem on HPUX is when they systems are rebooted, if raw files in /dev/dsk or /dev/rdsk are used by applications like Oracle or Sybase, the ownership gets changed by insf back to root:sys.

HTH

Duncan





I am an HPE Employee
Accept or Kudo
Ninad_1
Honored Contributor

Re: Getting error OCR initialization failed accessing OCR device: PROC-26: in syslog

Oracle 10.1.x installs ASM by default as part of installation and there is no choice to not install it.
This installation adds an entry like
h1:3:respawn:/sbin/init.d/init.cssd run >/dev/null 2>&1 in /etc/inittab and adds files /sbin/rc3.d/NOTUSED_K960init.cssd /sbin/rc3.d/NOTUSED_S960init.cssd
If you are not using ASM, then the line in inittab can be safely commented and the startup files in /sbin/rc3.d can be renamed.
After rebooting the server, the errors stopped coming.

Regards,
Ninad