CRS-4535: Cannot communicate with Cluster Ready Services

Two nodes 12.2.0.1 GI clusterware is not healthy with warning as below, databases and services are all still available for applications to connect to.

$ crsctl stat res -t
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4000: Command Status failed, or completed with errors.

$ crsctl check cluster -all
**************************************************************
racnode1:
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
racnode2:
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

crsd process is still running on both nodes:

-- on racnode1
$ ps -eaf | grep -i crsd
root 5482 1 0 Mar01 ? 00:00:00 /u01/app/12.2.0.1/grid/bin/crsd.bin reboot

-- on racnode2
$ ps -eaf | grep -i crsd
root 66210 1 0 23:39 ? 00:00:02 /u01/app/12.2.0.1/grid/bin/crsd.bin reboot

Subscribe to get access

Read more of this content when you subscribe today.

“DGM-17016: failed to retrieve status for database” in Data Guard Broker

The following error occurred in DG broker command on primary database side:

DGMGRL> show database verbose 'STDBYDB'

Database - STDBYDB

 Role: PHYSICAL STANDBY
...
..
.
Database Status:
DGM-17016: failed to retrieve status for database "STDBYDB"
ORA-16664: unable to receive the result from a database

Subscribe to get access

Read more of this content when you subscribe today.

“Duplicate from Active Database” Failed With ORA-12528 When Connecting to Auxiliary Instance

SYMPTOM

RMAN “duplicate target database for standby from active database” failed with below errors:

Connection from target database server to the auxiliary database  
fails with error:

ORA-12528: TNS:listener: all appropriate instances are blocking new 
connections.

It is a little bit tricky in RAC environment, this post will provide the solution for both single and RAC environment.

INVSTIGATIONS and SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

OEM Blackout Stuck in “Stop Pending” Status

There is one blackout stuck in “Stop Pending” Status for OEM 13c, when manually stopped it with errors:

Error: The blackout is already pending stop

Subscribe to get access

Read more of this content when you subscribe today.

Now check from OEM console again, the problem is gone.