Troubleshooting - Heartbeat failed to connect to standby
(Doc ID 1432367.1)
Last updated on MARCH 03, 2020
Applies to:Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 20-Aug-2013***
***Checked for relevance on 26-OCT-2016***
The Purpose of this Document is to troubleshoot the generic Error
Heartbeat failed to connect to standby
in the Primary ALERT.LOG. It shows most common and possible Causes along with Solutions to get rid of this Problem.
The Errors in general look like this:
PING[ARCn]: Heartbeat failed to connect to standby '<Standby>'. Error is xxxxx
ORA-3135 :The Communication between the ARCn and the RFS-Process died unexpectedly
ORA-12514 : The Standby Database is down or the specified Service you want to connect to is not registered with Listener on the Standby Site
Many more Common errors described in this document.
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