OpenVMS: Problems Recreating The OCR or Starting CRS When LOGIN.COM Contains Invalid Commands. (Doc ID 1102604.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.2 to 10.2.0.5 [Release 10.2]
HP OpenVMS Itanium
HP OpenVMS Alpha
***Checked for relevance on 06-Jan-2014***

Symptoms


Running Oracle CRS 10gR2 on OpenVMS (Alpha or Itanium).

The following error is reported when executing CRSSETUP as part of the installation process or when starting CRS using INIT_CRS START:

       %SYSTEM-E-ACCVIO, access violation, reason mask=00, virtual address=000000000000000A, PC=0000000001010020, PS=00000000

A review of the following CRS Batch log files also show that all batch jobs terminated with the error %SYSTEM-F-IVLOGNAM, invalid logical name

       ORA_ROOT:[log.<node>.crsd]crsd_batch.log;
       ORA_ROOT:[log.<node>.cssd]ocssd_batch.log;
       ORA_ROOT:[log.<node>.cssd.oclsomon]oclsomon_batch.log;
       ORA_ROOT:[log.<node>.cssd.oclsvmon]oclsvmon_batch.log;
       ORA_ROOT:[log.<node>.evmd]evmd_batch.log;

Where <node> is the nodename of the node where CRSSETUP or INIT_CRS START was executed.

When executing CRSSETUP.COM, errors similar to the following will have been reported:

Example for release 10.2.0.2:

      Creating OCR keys for user 'GIHRAC', privgrp 'RDBVMS'..
      Operation successful.
      Now formatting voting device: oracle_device:[oracle_code.ocr_vot]vot.dat
      CLSFMT returned with error [255].
      Preparing Oracle Cluster Ready Services (CRS):
      Oracle Cluster Synchronization Service starting by user request.
      Expecting the CRS daemons to be up within 600 seconds.
      Timed out waiting for the CRS stack to start

Example for release 10.2.0.4:

      Creating OCR keys for user 'GIHRAC', privgrp 'RDBVMS'..
      Operation successful.
      Now formatting voting device: oracle_device:[oracle_code.ocr_vot]vot.dat
      SCLS error [1] in joining child process.
      SLOS msgbuf [error 0].
      SLOS errbuf [0].
      SLOS other info is [Abnormal termination of the child].

      Preparing Oracle Cluster Ready Services (CRS):
      Oracle Cluster Synchronization Service starting by user request.
      Expecting the CRS daemons to be up within 600 seconds.
      Timed out waiting for the CRS stack to start


Changes

One of the OpenVMS login scripts (SYS$MANAGER:SYLOGIN.COM or SYS$LOGIN:LOGIN.COM) have recently been created or changed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms