Answer / guest

Cause: The name of a type, attribute, or method cannot be
converted from the client character set in effect when OTT
was invoked to the compiler character set (typically ASCII
or EBCDIC).

Action: A name is translated first from the database
character set to the client character set, and then from the
client character set to the compiler character set. The
client character set is specified in a platform-dependent
manner (On UNIX platforms, the client character set is
specified by setting the NLS_LANG environment variable). Use
a client character set that can be translated to the
compiler character set. The compiler character set itself is
one such character set. Specify synonyms in the INTYPE file
for any names of database objects that cannot be
successfully translated to the client character set.

Please add more information about this Error

PCC-02107: You may not specify PARSE = FULL when CODE = CPP

1 Answers  

---

ORA-25103: NOPARALLEL option can only be used with ALTER INDEX REBUILD

1 Answers  

---

ORA-01903: EVENTS keyword expected

1 Answers  

---

ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table string.string

1 Answers  

---

ORA-23348: cannot replicate procedure string; only IN parameters supported

1 Answers  

---

ORA-30108: invalid positional parameter value 'string'

1 Answers  

---

RMAN-05013: auxiliary control filename string conflicts with a file used by the target database

1 Answers  

---

ORA-02290: check constraint (string.string) violated

1 Answers  

---

IMG-00551: invalid quantize method specified

1 Answers  

---

DRG-10709: this preference is referenced by string and cannot be dropped

1 Answers  

---

ORA-22296: invalid ALTER TABLE option for conversion of LONG datatype to LOB

1 Answers  

---

ORA-29304: tablespace 'string' does not exist

1 Answers  

---