O2U-00204: Unable to convert from the database character set
to the compiler character set
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
Is This Answer Correct ? | 0 Yes | 0 No |
IMG-00805: SIGNATURE data has been corrupted or is invalid
ORA-01101: database being created currently mounted by some other instance
ORA-01147: SYSTEM tablespace file string is offline
NCR-03008: NCRO: Call rejected
ORA-02062: distributed recovery received DBID string, expected string
ORA-29858: error occurred in the execution of ODCIINDEXALTER routine
PLS-00160: AUTHID must specify CURRENT_USER or DEFINER
ORA-01906: BACKUP keyword expected
RMAN-05506: error during recursive execution
ORA-25114: invalid file number specified in the DUMP DATAFILE/TEMPFILE command
ORA-06720: TLI Driver: SID lookup failure
ORA-29741: IMR active for some, but not all members of cluster