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 |
NNC-00425: meta-data violation
ORA-06143: NETTCP: maximum connections exceeded
NNF-02001: NIS client error string: string
ORA-31062: Cannot delete an unsaved resource
PCB-00558: Invalid external datatype specified in EXEC SQL VAR statement
ORA-25246: listen failed, the address string is an 8.0 style exception queue
ORA-00357: too many members specified for log file, the maximum is string
DRG-12411: SQL processing error: string
ORA-37127: (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list.
ORA-06136: NETTCP: error during connection handshake
ORA-31104: Cannot find lock with token "string" on "string" for unlock
ORA-07418: sfareq: Database writer got error in timing function.