CRS-10132: Oracle High Availability Service was restarted at least 10 times within the last 60 seconds
(Doc ID 2342755.1)
Last updated on JUNE 20, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
Clusterware was not able to start from one node, out of a two node cluster, after an OS reboot.
In the Clusterware alert.log file, noticed that OHASD is having issues to start:
alert.log inside <oracle base>/diag/crs/<host name>/crs/trace location:
2017-12-24 02:09:10.059 [OHASD(4370)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4370
2017-12-24 02:09:10.070 [OHASD(4370)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:10.309 [OHASD(4419)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4419
2017-12-24 02:09:10.320 [OHASD(4419)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:10.559 [OHASD(4468)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4468
2017-12-24 02:09:10.570 [OHASD(4468)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:10.808 [OHASD(4517)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4517
2017-12-24 02:09:10.819 [OHASD(4517)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:11.057 [OHASD(4566)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4566
2017-12-24 02:09:11.067 [OHASD(4566)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:11.306 [OHASD(4617)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4617
2017-12-24 02:09:11.317 [OHASD(4617)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:11.553 [OHASD(4666)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4666
2017-12-24 02:09:11.564 [OHASD(4666)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:11.800 [OHASD(4715)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 4715
2017-12-24 02:09:11.811 [OHASD(4715)]CRS-2112: The OLR service started on node <rachost1>.
2017-12-24 02:09:11.987 [CLSECHO(4787)]CRS-10001: CRS-10132: Oracle High Availability Service was restarted at least 10 times within the last 60 seconds. Stop auto-restarting Oracle High Availability Service.
ohasd.trc reported discrepancy in the activeversion:
ohasd.trc inside <oracle base>/diag/crs/<host name>/crs/trace location:
2017-12-24 02:09:11.812545 :OHASDMAIN:1: Checking version compatibility...
2017-12-24 02:09:11.813148 : default:1: clsvactversion:4: Retrieving Active Version from local storage.
2017-12-24 02:09:11.813655 : OCRRAW:1: prgval:buffer passed is too small
default:1: Failure 9 in trying to get AV value SYSTEM.version.activeversion
default:1: procr_get_value error 9 errorbuf : PROCL-9: Cannot perform local registry operation because the buffer passed is too small.
2017-12-24 02:09:11.813836 :OHASDMAIN:1: Error retrieving version data from OLR. clsvswversion() return status: 0 clsvactversion() return status: 3
2017-12-24 02:09:11.813847 : default:1: [PANIC] OHASD exiting; Failed to retrieve version data from OLR
2017-12-24 02:09:11.813946 : default:1: Done.
Changes
No changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |