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

LFI-00145: User buffer too short.

1 Answers  

---

IMG-00899: signature cannot be generated

1 Answers  

---

RMAN-00574: rman aborting due to errors read/writing dbms_pipe

1 Answers  

---

ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.

1 Answers  

---

NNL-01031: Name: string

1 Answers  

---

ORA-29300: ORACLE error, tablespace point-in-time recovery

1 Answers  

---

ORA-02724: osnpbr: cannot send break message to orapop

1 Answers  

---

ORA-13764: Value "string" is illegal as a result percentage.

1 Answers  

---

TNS-12569: TNS:packet checksum failure

1 Answers  

---

ORA-14006: invalid partition name

1 Answers  

---

ORA-29379: resource plan string is involved in a loop in top-plan string

1 Answers  

---

NNL-01070: System parameter file name: string

1 Answers  

---