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

EXP-00103: The FLASHBACK_TIME parameter was invalid

1 Answers  

---

TNS-01301: TNS error structure:

1 Answers  

---

RMAN-08042: channel string: copied standby controlfile

1 Answers  

---

ORA-00321: log string of thread string, cannot update log file header

1 Answers  

---

LSX-00116: mutually exclusive facets are not allowed

1 Answers  

---

ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature

1 Answers  

---

ORA-30991: cannot use DOM to add special attribute to schema-based parent

1 Answers  

---

TNS-12225: TNS:destination host unreachable

1 Answers  

---

ORA-38749: A media recovery has been started.

1 Answers  

---

NZE-28751: memory allocation failure

1 Answers  

---

RMAN-04022: target database mount id string does not match channel's mount id string

1 Answers  

---

ORA-12496: cannot change existing level, category, or release numbers

1 Answers  

---