O2F-00324: Unable to convert from the database character set
to the compiler character set
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 |
ORA-31609: error loading file "string" from file system directory "string"
ORA-01112: media recovery not started
ORA-29286: internal error
ORA-21526: initialization failed
ORA-32146: Cannot perform operation on a null date
ORA-02443: Cannot drop constraint - nonexistent constraint
ORA-29277: invalid SMTP operation
LSX-00259: invalid character found in the pattern
NNL-00531: flush_name <name> : removes a name from caches along a route to an authoritative server
ORA-28166: duplicate rolename in list
PCB-00221: OCCURS DEPENDING ON clause not allowed for host variable "string"
ORA-09749: pws_look_up: port lookup failure