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 includes the character set of
the INTYPE file and can be translated to the compiler
character set. The database character set 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

ORA-09762: sNeXT_instanceName: translation error.

1 Answers  

---

SQL-02116: FATAL ERROR: Reentrant code generator gave invalid context

1 Answers  

---

LPX-00122: undefined ID "~S" in IDREF

1 Answers  

---

ORA-07447: ssarena: usinit failed.

1 Answers  

---

RMAN-06172: no autobackup found or specified handle is not a valid copy or piece

1 Answers  

---

ORA-27007: failed to open file

1 Answers  

---

ORA-15036: disk 'string' is truncated

1 Answers  

---

DRG-10822: duplicate query name

1 Answers  

---

PLS-00108: declarative units must be a single variable declaration

1 Answers  

---

ORA-01863: the year is not supported for the current calendar

1 Answers  

---

ORA-02457: The HASH IS option must specify a valid column

1 Answers  

---

LFI-00006: Invalid parameter to function string.

1 Answers  

---