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

ORA-24055: cannot delete propagation status rows that are in prepared state

1 Answers  

---

ORA-27477: "string.string" already exists

1 Answers  

---

ORA-16156: LGWR archive log dependency not allowed if database is standby protected

1 Answers  

---

ORA-16591: unknown field "string" in document

1 Answers  

---

QSM-01108: maximum number of disjuncts exceeded in the query string

1 Answers  

---

---

ORA-02719: osnfop: fork failed

1 Answers  

---

ORA-31157: Invalid Content-Type charset

1 Answers  

---

ORA-01983: invalid auditing option for DEFAULT

1 Answers  

---

ORA-24779: detach not allowed with open remote cursor

1 Answers  

---

ORA-01632: max # extents (string) reached in index string.string

1 Answers  

---

TNS-00126: Missing Connection Manager name and address in TNSNET.ORA

1 Answers  

---

NZE-29177: certificate serial number is not in CRL

1 Answers  

---