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 |
TNS-04003: Syntax Error.
ORA-19614: archivelog thread string sequence string not found in backup set
DRG-52208: the specified attribute already exist: string
ORA-30079: cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
ORA-21561: OID generation failed
ORA-12232: TNS:No path available to destination
ORA-25964: column type incompatible with join column type
ORA-10565: Another test recovery session is active
LPX-00405: unable to allocate memory
LPX-00253: missing required version number in XML declaration
TNS-01005: trace OFF | USER | ADMIN | SUPPORT [<listener_name>] : set tracing to the specified level
ORA-16617: unknown object identifier specified in request