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-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.

1 Answers  

---

ORA-07392: sftcls: fclose error, unable to close text file.

1 Answers  

---

NNL-01002: NOT AUTHORITY responses received: number

1 Answers  

---

ORA-02765: Invalid maximum number of servers

1 Answers  

---

ORA-19568: a device is already allocated to this session

1 Answers  

---

RMAN-00553: internal recovery manager package failed to load

1 Answers  

---

ORA-38414: invalid datatype for the attribute string

1 Answers  

---

RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE

1 Answers  

---

LFI-00140: Invalid option string were specified on input-output file.

1 Answers  

---

TNS-12537: TNS:connection closed

1 Answers   IBM,

---

ORA-02423: schema name does not match schema authorization identifier

1 Answers  

---

ORA-12663: Services required by client not available on the server

1 Answers  

---