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-27202: skgfpen: sbtpcend returned error

1 Answers  

---

ORA-00211: controlfile does not match previous controlfiles

1 Answers  

---

RMAN-06590: tablespace string cannot be converted

1 Answers  

---

ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.

1 Answers  

---

ORA-00077: dump string is not valid

1 Answers  

---

RMAN-08533: restoring blocks of datafile string

1 Answers  

---

ORA-15023: reached maximum allowable number of disks string

1 Answers  

---

ORA-09314: sltln: error translating logical name

1 Answers  

---

ORA-32116: Buffer size is less than amount specified

1 Answers  

---

ORA-24145: evaluation context string.string already exists

1 Answers  

---

ORA-07633: smsdbp: illegal protection value

1 Answers  

---

ORA-29294: A data error occurred during compression or uncompression.

1 Answers  

---