ORA-16620: one or more databases could not be contacted for a delete operation

Cause : The Data Guard broker could not reach one or more standby databases for either a delete database operation or a delete broker configuration operation.

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. In the event of this situation, examine the primary database's Data Guard broker log for to determine which standby databases could not be reached. Then for each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, dg_broker_start, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database's dg_broker_config_file[1|2] parameter values and delete them.

update : 29-04-2017

ORA-16620 - one or more databases could not be contacted for a delete operation
ORA-16620 - one or more databases could not be contacted for a delete operation

  • ora-26699 : STREAMS message consumer string already exists
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-19709 : numeric parameter must be non-negative integer
  • ora-39309 : schema sync operation failed
  • ora-30653 : reject limit reached
  • ora-02475 : maximum cluster chain block count of string has been exceeded
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-23600 : cannot create PROPAGATION, string already exists
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-01287 : file string is from a different database incarnation
  • ora-27431 : chain string.string has a user-managed rule set
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-13520 : Database id (string) not registered, Status = string
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-29304 : tablespace 'string' does not exist
  • ora-01438 : value larger than specified precision allowed for this column
  • ora-14023 : creation of GLOBAL partitioned cluster indices is not supported
  • ora-13024 : polygon has less than three segments
  • ora-00276 : CHANGE keyword specified but no change number given
  • ora-09714 : Two Task interface: cannot obtain puname
  • ora-23308 : object string.string does not exist or is invalid
  • ora-29886 : feature not supported for domain indexes
  • ora-02379 : profile string already exists
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-12546 : TNS:permission denied
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-29975 : Cannot register a query in the middle of an active transaction
  • 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.