Answer / guest

Cause: Either an Oracle datatype could not be mapped to a
non-Oracle datatype, or a non-Oracle datatype could not be
mapped to an Oracle datatype. These mappings are defined as
capability definitions in the ORACLE server's data dictionary.

Action: Verify that the ORACLE server's data dictionary has
been initialized with correct capability definitions for the
connected FDS_CLASS_NAME and FDS_INST_NAME. If table
contents are incorrect, a DBA should restore all data
dictionary content for this FDS_CLASS_NAME and/or
FDS_INST_NAME. It usually is sufficient to delete all
current data dictionary content for this class and/or
instance and initiate a new connection to let the connected
agent upload new data dictionary content to the server. If
the error persists contact the customer support
representative of the agent vendor.

Please add more information about this Error

ORA-02775: Invalid request done signal

1 Answers  

---

ORA-16121: applying transaction with commit SCN string

1 Answers  

---

ORA-07445: exception encountered: core dump [string] [string] [string] [string] [string] [string]

1 Answers  

---

RMAN-06030: the DELETE [ALL] INPUT option may not be used with a datafile backup set

1 Answers  

---

QSM-00795: the SQL Tuning Set repository has not been implemented

1 Answers  

---

DGM-16903: Unable to connect to database

1 Answers  

---

IMG-00521: invalid value for dataOffset

1 Answers  

---

ORA-19578: end of volume while duplexing to sequential files, backup piece incomplete

1 Answers  

---

ORA-22130: buffer size [string] is less than the required size [string]

1 Answers  

---

DRG-13303: value of wildcard offset must be in the range string..string, at line string

1 Answers  

---

TNS-00559: load of Entrust certificate failed

1 Answers  

---

NID-00403: DBNEWID - Completed with validation errors.

1 Answers  

---