RHEL6/OEL6: 11.2.0.2 root.sh failed with "CRS-4639: Could not contact Oracle High Availability Services"
(Doc ID 2132347.1)
Last updated on AUGUST 06, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.2.0 [Release 11.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
Linux x86-64
Symptoms
root.sh failed with following error for 11.2.0.2 grid installation on RHEL6.4.
2016-04-19 23:29:02: Checking the status of ohasd
2016-04-19 23:29:07: Executing cmd: /oracle/app/11.2.0/grid/product/db_1/bin/crsctl check has
2016-04-19 23:29:07: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
>End Command output
2016-04-19 23:29:07: Checking the status of ohasd
2016-04-19 23:29:12: Executing cmd: /oracle/app/11.2.0/grid/product/db_1/bin/crsctl check has
2016-04-19 23:29:12: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
>End Command output
2016-04-19 23:29:12: Checking the status of ohasd
2016-04-19 23:29:17: Executing cmd: /oracle/app/11.2.0/grid/product/db_1/bin/crsctl check has
2016-04-19 23:29:17: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
2016-04-19 23:29:07: Executing cmd: /oracle/app/11.2.0/grid/product/db_1/bin/crsctl check has
2016-04-19 23:29:07: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
>End Command output
2016-04-19 23:29:07: Checking the status of ohasd
2016-04-19 23:29:12: Executing cmd: /oracle/app/11.2.0/grid/product/db_1/bin/crsctl check has
2016-04-19 23:29:12: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
>End Command output
2016-04-19 23:29:12: Checking the status of ohasd
2016-04-19 23:29:17: Executing cmd: /oracle/app/11.2.0/grid/product/db_1/bin/crsctl check has
2016-04-19 23:29:17: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
In Grid alert log, find following error:
2016-04-19 23:24:23.214
[client(12967)]CRS-2317:Fatal error: cannot get local GPnP security keys (wallet).
2016-04-19 23:24:23.215
[client(12967)]CRS-2316:Fatal error: cannot initialize GPnP, CLSGPNP_ERR (Generic GPnP error).
2016-04-19 23:24:23.220
[client(12967)]CRS-1013:The OCR location in an ASM disk group is inaccessible. Details in /oracle/app/11.2.0/grid/product/db_1/log/oracle1/client/clscfg.log.
2016-04-19 23:45:25.637
[client(14102)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).
2016-04-19 23:45:25.642
[client(14102)]CRS-1013:The OCR location in an ASM disk group is inaccessible. Details in /oracle/app/11.2.0/grid/product/db_1/log/oracle1/client/ocrcheck_14102.log.
[client(12967)]CRS-2317:Fatal error: cannot get local GPnP security keys (wallet).
2016-04-19 23:24:23.215
[client(12967)]CRS-2316:Fatal error: cannot initialize GPnP, CLSGPNP_ERR (Generic GPnP error).
2016-04-19 23:24:23.220
[client(12967)]CRS-1013:The OCR location in an ASM disk group is inaccessible. Details in /oracle/app/11.2.0/grid/product/db_1/log/oracle1/client/clscfg.log.
2016-04-19 23:45:25.637
[client(14102)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).
2016-04-19 23:45:25.642
[client(14102)]CRS-1013:The OCR location in an ASM disk group is inaccessible. Details in /oracle/app/11.2.0/grid/product/db_1/log/oracle1/client/ocrcheck_14102.log.
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 |
| Cause |
| Solution |
| References |