Answer / guest

Cause: The broker detected a network protocol version number
mismatch. This can happen if the databases in question are
not at the same version of Oracle. The broker will
permanently disable management of the databases that do not
have the same network protocol version number as the primary.

Action: Examine the version of Oracle installed for all
databases to make sure they are identical. Once the Oracle
versions are the same for all databases, remove and re-add
to the broker configuration those databases that had been
permanently disabled.

Please add more information about this Error

ORA-10651: incorrect file number block number specified

1 Answers  

---

ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.

1 Answers  

---

ORA-12980: checkpoint option not allowed with SET UNUSED

1 Answers  

---

ORA-14261: partition bound may not be specified when adding this Hash partition

1 Answers  

---

ORA-24183: invalid transformation

1 Answers  

---

ORA-10562: Error occurred while applying redo to data block (file# string, block# string)

1 Answers  

---

TNS-00280: Max Avg Bytes/Sec : number

1 Answers  

---

ORA-30054: invalid upper limit snapshot expression

1 Answers  

---

ORA-07346: slnrm: normalized file name is too long

1 Answers  

---

ORA-06031: NETDNT: connect failed, unrecognized object name

1 Answers  

---

SQL*Loader-00916: Error checking path homogeneity

1 Answers  

---

ORA-26686: cannot capture from specified SCN

1 Answers  

---