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 : 24-06-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-09808 : Could not obtain user clearance.
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-30729 : maximum number of columns exceeded
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-38499 : expression set already configured for stored/indexed attributes
  • ora-31056 : The document being inserted does not conform to string
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-06521 : PL/SQL: Error mapping function
  • ora-12981 : cannot drop column from an object type table
  • ora-23400 : invalid materialized view name "string"
  • ora-26714 : User error encountered while applying
  • ora-28037 : Cannot Get Session Key for RACF Authentication
  • ora-01350 : must specify a tablespace name
  • ora-19335 : Invalid format type object
  • ora-16541 : site is not enabled
  • ora-14632 : cannot specify PARALLEL clause when adding a List subpartition
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-00469 : CKPT process terminated with error
  • ora-09920 : Unable to get sensitivity label from connection
  • ora-24033 : no recipients for message
  • ora-26673 : duplicate column name string
  • ora-28511 : lost RPC connection to heterogeneous remote agent using SID=string
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-31534 : Change Data Capture string publisher string is missing DBA role
  • ora-08310 : sllfop: Bad value for recsize
  • ora-25307 : Enqueue rate too high, flow control enabled
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-10571 : Test recovery canceled
  • 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.