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

ORA-31660: metadata filter name can not be defaulted

1 Answers  

---

ORA-24172: rule set string.string has errors

1 Answers  

---

DRG-11818: Temporary Redirect

1 Answers  

---

NNO-00083: domain "string" server "string" has no addresses

1 Answers  

---

PCC-02101: Unable to open input file

1 Answers  

---

QSM-01023: materialized view, string, has GRANT errors

1 Answers  

---

ORA-01612: instance string (thread string) is already enabled

1 Answers  

---

NNL-00810: Queries received with no type: number

1 Answers  

---

IMP-00033: Warning: Table "string" not found in export file

2 Answers  

---

DRG-10597: invalid rebuild online operation

1 Answers  

---

ORA-02034: speed bind not permitted

1 Answers  

---

ORA-30658: attempt was made to create a temporary table with EXTERNAL organization

1 Answers  

---