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 |
DRG-50931: parser not opened
ORA-01571: redo version string incompatible with ORACLE version string
IMG-00861: assert failure, inconsistency in area merge operation
PCC-00097: Use of DECIMAL and DISPLAY types allowed only for COBOL and PL/I
ORA-01685: max # extents (string) reached in index string.string partition string
PCC-02101: Unable to open input file
ORA-31190: Resource string is not a version-controlled resource
DRG-11855: FTP Server Replies
RMAN-05011: auxiliary instance must be in nomount state for TSPITR
AMD-00105: Level "string" cannot be added to the hierarchy; the specified parent level "string" is already the parent of "string"
RMAN-08521: offline range recid=string stamp=string
ORA-24169: rule condition has unrecognized variables