ORA-16620: one or more databases could not be contacted for
a delete operation
- 1 Answers
- 3078 Views
- I also Faced
- E-Mail Answers
Answer / guest
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: This typically indicates a network problem where the
standby database is unable to respond to the primary. In the
event of this situation, examine the Data Guard broker log
for the primary database 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's
dg_broker_config_file[1|2] parameter values and delete them.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PCC-00118: Use of host variable initialization not supported by ANSI SQL
TNS-00204: Started tracing in intlsnr
RMAN-08042: channel string: copied standby controlfile
ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
NNL-01060: Cache next checkpointed in: string
ORA-28041: Authentication protocol internal error
ORA-22627: tc [string] must be that of object/varray/nested table
PLS-00564: lob arguments are not permitted in calls to remote server
ORA-28045: SSL authentication between database and OID failed
NID-00480: Database is intact - database is ready to be open or shut down.
ORA-13124: unable to determine column id for column string
RMAN-08512: waiting for snapshot controlfile enqueue
Oracle Errors 
