ORA-16619: health check timed out

Cause : This status is returned when the Data Guard broker could not reach a standby database during a routine health check.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame.

update : 25-06-2017
ORA-16619

ORA-16619 - health check timed out
ORA-16619 - health check timed out

  • ora-19901 : database needs more recovery to create new incarnation
  • ora-13797 : invalid SQL Id specified, string
  • ora-22865 : more than one column specified
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-19622 : archivelog thread string sequence string not restored due to string
  • ora-02203 : INITIAL storage options not allowed
  • ora-19244 : XQ0024 - invalid attribute node in element constructor
  • ora-00391 : All threads must switch to new log format at the same time
  • ora-01230 : cannot make read only - file string is offline
  • ora-16513 : maximum requests exceeded
  • ora-12688 : Login failed: the SecurID server rejected the new pincode
  • ora-26093 : input data column size (number) exceeds the maximum input size (number)
  • ora-00962 : too many group-by / order-by expressions
  • ora-14039 : partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-09760 : osnpui: cannot send break message
  • ora-02198 : ONLINE/OFFLINE option already specified
  • ora-08453 : more than one V symbol specified in picture mask
  • ora-39146 : schema "string" does not exist
  • ora-29556 : object type has changed
  • ora-32836 : database user string must be granted role string
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-16529 : bad sender id
  • ora-38707 : Media recovery is not enabled.
  • ora-04046 : results of compilation are too large to support
  • ora-08184 : attempting to re-enable Flashback while in Flashback mode
  • ora-32340 : cannot tune the materialized view definition
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.