OpenVMS: RAC/CRS: How to Recover from a CRSD Process Crash without Impacting Services
(Doc ID 1073226.1)
Last updated on AUGUST 01, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
HP OpenVMS Itanium
HP OpenVMS Alpha
Goal
There are a number of reasons why the CRS related CRSD batch process (process name ORA_HAS_CRSDREB or ORA_HAS_CRSDRES) may crash due to an Access Violation.
These crashes can happen at different times and for no apparent reason.
At the time of writing this document, there are a number of open bugs which are still being investigated.
For example:
<Bug:9027898> CRSD PROCESS ACCESS VIOLATION IN ROUTINES - NSEVIOC, NSEVBRECV AND NTEVGET
<Bug:9218651> CRSD CRASH IN NLQUDEQ
All other CRS related processes are still present.
However, the following error is reported when issuing CRS_STAT -t
CRS-0184: Cannot communicate with the CRS daemon.
%SYSTEM-E-ABORT, abort
Under these conditions, it is not necessary to shutdown the entire CRS stack in order to get CRSD running again.
This article explains the steps needed to restart CRSD without disruption to remaining CRS services and related RAC instances.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |