Answer / guest

Cause: A broker operation was attempted on a database that
is permanently disabled. This occurs when the broker detects
that this database cannot function as a viable standby to
the current primary database, generally following a role
change, i.e., failover or switchover.

Action: Remove the database from the broker configuration,
reinstantiate the database and then add it back into the
configuration.

Please add more information about this Error

PLS-00621: at least one operand in the COALESCE expression must not be NULL

1 Answers  

---

ORA-32820: subscriber queue and exception queue must use same message system link

1 Answers  

---

ORA-23467: flavor lacks object "string"."string"

1 Answers  

---

PROC-00028: Oracle Cluster Registry already in current version

1 Answers  

---

ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.

1 Answers  

---

LSX-00241: bad double "~S"

1 Answers  

---

ORA-13043: failed to read metadata from the <layer>_SDOLAYER table

1 Answers  

---

PCC-02394: Input file name and output filename are identical

1 Answers  

---

RMAN-06439: RMAN must be upgraded to version string to work with this package

1 Answers  

---

PLS-00606: cursor subquery is not supported on client side in this release

1 Answers  

---

ORA-01340: NLS error

1 Answers  

---

ORA-23453: requested operation is not supported on top flavor

1 Answers  

---