O2U-00204: Unable to convert from the database character set
to the compiler character set
- 1 Answers
- 1993 Views
- I also Faced
- E-Mail Answers
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 |
ORA-15025: could not open disk 'string'
ORA-14628: specification of bounds is inconsistent with LIST method
ORA-02349: invalid user-defined type - type is incomplete
ORA-12656: Cryptographic checksum mismatch
ORA-27152: attempt to post process failed
QSM-01010: table(s) in the query not found in materialized view, string
PLS-00249: Invalid WITH CONTEXT Syntax
NMP-00001: value too big
ORA-02064: distributed operation not supported
ORA-07270: spalck: setitimer error, unable to set interval timer.
TNS-00293: Trace File Name : string
ORA-30175: invalid type given for an argument
Oracle Errors 
