How to fix the Oracle error ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down?

In this post, you’ll learn more about the Oracle ErrorORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down with the details on why you receive this error and the possible solution to fix it.

Oracle Error Description

ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down

Reason for the Error ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down

The primary database was isolated from both the observer and target standby database for longer than the seconds specified by the FastStartFailoverThreshold property. A fast-start failover probably occurred. If the FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker will shut down the primary database in this situation.

How to fix the Error ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down ?

You can fix this error in Oracle by following the below steps

Ensure one instance of this database is running and the database is mounted on that instance so that the broker may reinstate the old primary database.