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 : 30-04-2017

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

  • ora-36986 : (XSRELGID05) Relation workspace object must be dimensioned by workspace object.
  • ora-27053 : blocksize in file header not a multiple of logical block size
  • ora-24239 : object could not be invalidated
  • ora-32002 : cannot create SPFILE already being used by the instance
  • ora-30204 : buffer is not large enougth
  • ora-23334 : column string does not exist in table or column group
  • ora-13053 : maximum number of geometric elements in argument list exceeded
  • ora-24318 : call not allowed for scalar data types
  • ora-39727 : COMPATIBLE must be set to or higher
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-01974 : Illegal archive option
  • ora-17620 : failed to register the network adapter with Oracle Disk Manager library: string
  • ora-36182 : (XSAGGR09) Could not locate a value for variable number in measure dimension workspace object.
  • ora-16151 : Managed Standby Recovery not available
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-30458 : 'string.string' cannot be refreshed because the refresh mask is string
  • ora-02360 : fatal error during data export/import initialization
  • ora-19681 : block media recovery on control file not possible
  • ora-16506 : out of memory
  • ora-13293 : cannot specify unit for geometry without a georeferenced SRID
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-02056 : 2PC: string: bad two-phase command number string from string
  • ora-00071 : process number must be between 1 and string
  • ora-24082 : propagation may still be happening for the schedule for QUEUE string and DESTINATION string
  • ora-28278 : No domain policy registered for password based GLOBAL users.
  • ora-14119 : specified partition bound is too long
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-28108 : circular security policies detected
  • ora-02710 : osnpop: fork failed
  • 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.