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 |
RMAN-08092: channel string: specifying datafilecopy of datafile string for proxy backup
ORA-06709: TLI Driver: message send failure
SQL*Loader-00963: Error clearing user-side Ctrl-C handler
ORA-12508: TNS:listener could not resolve the COMMAND given
ORA-30335: JOIN KEY clause references a level not in this hierarchy
ORA-14103: LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
ORA-13207: incorrect use of the [string] operator
ORA-21704: cannot terminate cache or connection without flushing first
ORA-36874: (XSFTDSC04) Expression string cannot be used to define a column in a LIMITMAP.
ORA-27542: Failed to unprepare a buffer prepared for remote update
RMAN-06028: duplicate operand specified in restore specification: string
ORA-16412: ONDEMAND archival requires active SQL apply operation