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-19572: cannot process file string, file is being being resized
PLS-00110: bind variable 'string' not allowed in this context
O2F-00314: AS expected but not seen in the INTYPE file
ORA-27463: invalid program type string
PCB-00581: "string" used as both host variable and indicator
ORA-03119: two-task detected inconsistent datatype specification
RMAN-08026: channel string: copied archive log
ORA-12682: Login failed: the SecurID card is in next PRN mode
TNS-01402: TYPE: string
ORA-08441: closed parenthesis missing in picture mask
ORA-19720: Error occurred when converting an OCI number into an SCN
TNS-12153: TNS:not connected