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-02064: distributed operation not supported
ORA-07482: snlmini: cannot create lock manager instance.
PCC-02325: illegal indirection operation
ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
ORA-39050: parameter string is incompatible with parameter string
LPX-00215: processing instruction did not end in "?>"
ORA-39040: Schema expression "string" must identify exactly one schema.
ORA-28233: double encryption not supported
ORA-14628: specification of bounds is inconsistent with LIST method
NZE-28854: Memory allocation failure
ORA-37060: (XSMCSESS08) number is not a valid custom member in dimension workspace object.
ORA-08175: discrete transaction restriction violated (string)