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-13517: Baseline (id = string) does not exist

1 Answers  

---

DRG-10314: logging has not been started

1 Answers  

---

ORA-29706: incorrect value string for parameter ACTIVE_INSTANCE_COUNT

1 Answers  

---

ORA-02249: missing or invalid value for MAXLOGMEMBERS

1 Answers  

---

PLW-07204: conversion away from column type may result in sub-optimal query plan

1 Answers  

---

ORA-04060: insufficient privileges to execute string

1 Answers  

---

NNL-00981: Timeouts, server not responding: number

1 Answers  

---

ORA-24312: illegal parameters specified for allocating user memory

1 Answers  

---

ORA-32841: invalid value for property string

1 Answers  

---

ORA-35587: (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.

1 Answers  

---

ORA-22809: nonexistent attribute

1 Answers  

---

IMG-00546: invalid page number specified

1 Answers  

---