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-06794: TLI Driver: shadow process could not retrieve protocol info
NNO-00065: loading cached data from checkpoint file "string"
DRG-10821: contains cursor is not open
QSM-02029: PL/SQL function invocation
ORA-29814: expecting USING or DEFAULT keyword
KUP-01008: the bad identifier was: string
RMAN-06290: Report of database schema
AMD-00131: dimension #string: RDBMS parent column data type not specified
TNS-01157: Can only listen on number addresses - ignoring string
ORA-07412: sfaslv: Error getting entry in asynchronous write array.
NZE-29019: The protocol version is incorrect.
RMAN-04012: auxiliary database Password: