O2U-00204: Unable to convert from the database character set
to the compiler character set
- 1 Answers
- 2294 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 |
NNL-00295: Controller's local trace level is currently number
ORA-19854: error obtaining connect string from target
ORA-24151: no evaluation context is associated with rule string.string or rule set string.string
ORA-00445: background process "string" did not start after string seconds
ORA-07646: sszfck: $CREATE failure
ORA-31422: owner schema string does not exist
RMAN-08046: channel string: starting compressed full datafile backupset
ORA-02782: Both read and write functions were not specified
ORA-14168: only one subpartition may be modified
ORA-31692: The following SQL statement failed trying to insert a row into the Master table: string
LFI-01507: fwrite() failed(OSD return value = string) in string.
ORA-23419: regenerate replication support before resuming master activity
Oracle Errors 
