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 : 22-08-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-38465 : failed to create the privilege checking trigger due to: string
  • ora-38305 : object not in RECYCLE BIN
  • ora-36634 : (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
  • ora-15075 : disk(s) are not visible cluster-wide
  • ora-06105 : NETTCP: remote host is unknown
  • ora-28674 : cannot reference transient index-organized table
  • ora-06431 : ssaio: Invalid Block number
  • ora-08185 : Flashback not supported for user SYS
  • ora-31465 : cannot obtain a lock on the subscription
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-31406 : change source string is referenced by a change set
  • ora-01077 : background process initialization failure
  • ora-09743 : smscre: could not attach shared memory.
  • ora-09915 : Password encryption failed.
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-24322 : unable to delete an initialized mutex
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-14073 : bootstrap table or cluster may not be truncated
  • ora-02481 : Too many processes specified for events (max string)
  • ora-01116 : error in opening database file string
  • ora-00473 : ARCH process terminated with error
  • ora-16243 : paging out string bytes of memory to disk
  • ora-08264 : ora_addr: cannot close nameserver
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-19629 : no files in specified archivelog SCN range
  • ora-22281 : cannot perform operation with an updated locator
  • ora-06952 : Remote end of the communication issued a forward-reset packet.
  • ora-38733 : Physical size string less than needed string.
  • ora-38104 : Columns referenced in the ON Clause cannot be updated: string
  • 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.