O2U-00204: Unable to convert from the database character set
to the compiler character set
- 1 Answers
- 2244 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-14319: DEFAULT cannot be specified with other values
DRG-10510: stopword is missing
NNL-00952: Cache lookup failures: number
ORA-14406: updated partition key is beyond highest legal partition key
ORA-14000: only one LOCAL clause may be specified
ORA-28045: SSL authentication between database and OID failed
TNS-12633: No shared authentication services
ORA-16807: unable to set protection mode to the database
ORA-01536: space quota exceeded for tablespace 'string'
3 Answers Bloom Soft Tech, TCS,
LPX-00120: entity "~1S" NDATA (notation) "~2S" is undefined
ORA-29325: SET COMPATIBILITY release number lower than string
ORA-06021: NETASY: connect failed
Oracle Errors 
