O2U-00204: Unable to convert from the database character set
to the compiler character set
- 1 Answers
- 1977 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 |
DRG-11532: error reading through end of line string for file string
ORA-16595: NetSlave process string failed to terminate
NNL-00293: Controller's trace level remains unchanged
ORA-33215: (CINSERT07) You cannot add session-only values to the workspace object dimension.
ORA-07605: szprv: $ASCTOID failure
ORA-02315: incorrect number of arguments for default constructor
QSM-02003: aggregate function nested within an expression
ORA-01769: duplicate CLUSTER option specifications
ORA-30938: No prefix defined for namespace 'string' (particle string)
DRG-11533: improper value of column string
ORA-02235: this table logs changes to another table already
ORA-19831: incompatible string.string.string DBMS_BACKUP_RESTORE package: string.string.string required
Oracle Errors 
