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 |
KUP-04061: directory object string specified for LOBFILE column string is not valid
ORA-00960: ambiguous column naming in select list
PROT-00807: Please ensure you have file creation privileges in the executing directory before running this tool.
RMAN-08117: channel string: the autobackup does not contain an SPFILE
ORA-09805: conversion of category number to string failed.
ORA-31207: DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
KUP-04008: access to file denied
ORA-07826: sspscm: SYS$GETDVIW failure
ORA-00051: timeout occurred while waiting for a resource
ORA-06255: NETNTT: cannot read pid of remote process
ORA-01484: arrays can only be bound to PL/SQL statements
LSX-00117: "minLength" should not be greater than "maxLength"