My Oracle Support Banner

Troubleshooting - Heartbeat failed to connect to standby (Doc ID 1432367.1)

Last updated on JULY 16, 2019

Applies to:

Oracle Database Exadata 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***

Purpose

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-16191/ORA-1017

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.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.