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-30770: Cannot specify storage options for fixed size opaque type

1 Answers  

---

ORA-06405: NETCMN: reset protocol error

1 Answers  

---

ORA-16151: Managed Standby Recovery not available

1 Answers  

---

ORA-30750: cannot enable column string to store objects of type string.string

1 Answers  

---

ORA-13704: Invalid value "string" specified for parameter "string".

1 Answers  

---

ORA-23346: primary key or object ID is undefined for table or materialized view string

1 Answers  

---

ORA-25213: message with specified RELATIVE_MSGID has been dequeued

1 Answers  

---

ORA-30476: PLAN_TABLE does not exist in the user's schema

2 Answers  

---

TNS-04081: Event groups:

1 Answers  

---

NZE-28751: memory allocation failure

1 Answers  

---

ORA-09828: SCLFR: atomic latch return error.

1 Answers  

---

NZE-29020: The handshake record length is too long.

1 Answers  

---