ORA-16620: one or more databases could not be contacted for
a delete operation
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 |
ORA-31007: Attempted to delete non-empty container string/string
ORA-15004: alias "string" does not exist
PCB-00318: ARRAYLEN is an Oracle extension
ORA-22165: given index [string] must be in the range of 0 to [string]
PLS-01414: Use of qualified expression here
ORA-28047: database is not a member of any enterprise domain in OID
QSM-01093: anti-join marker not found in materialized join view
ORA-40225: model is currently in use by another process
NNL-01052: Server has been running for: string
ORA-16537: child count exceeded
ORA-39032: function string is not supported in string jobs
UDE-00015: invalid context or job state for parameter, 'string'.