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-12674: Shared server: proxy context not saved

1 Answers  

---

ORA-06419: NETCMN: server can not start oracle

1 Answers  

---

ORA-30389: the source statement is not compatible with the destination statement

1 Answers  

---

NID-00109: DBNAME string length number exceeds maximum length of number

1 Answers  

---

RMAN-08087: channel string: started backup set validation

1 Answers  

---

ORA-13424: the GeoRaster object is not spatially referenced

1 Answers  

---

NNO-00850: Error: LDAP query returns string

1 Answers  

---

ORA-33008: (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.

1 Answers  

---

ORA-30160: Unable to access the file

1 Answers  

---

ORA-29521: referenced name string could not be found

1 Answers  

---

ORA-25184: column name expected

1 Answers  

---

ORA-22951: NULL returned by ORDER method

1 Answers  

---