O2F-00324: Unable to convert from the database character set
to the compiler character set
- 1 Answers
- 2144 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 can be translated to the
compiler character set. The compiler character set itself 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 |
PLS-00317: incomplete type "string" was not completed in its declarative region
LFI-01500: Error condition on call to OSD function string.
ORA-01948: identifier's name length (string) exceeds maximum (string)
QSM-02034: no joins are present in the HAVING clause
SQL-02141: Collection descriptor has not been allocated
ORA-14038: GLOBAL partitioned index must be prefixed
RMAN-08516: controlfile copy filename=string recid=string stamp=string
EXP-00082: Invalid function name passed to procedural object support: string
NZE-28754: object storage failure
ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.
ORA-29394: session id string and serial# string do not exist
ORA-27077: too many files open
Oracle Errors 
