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-15011: failure group "string" contains no members
TNS-12642: No session key
IMP-00082: Error during conversion ROWID from string format to internal
ORA-27370: job slave failed to launch a job of type EXECUTABLE
ORA-16181: SGA specified for Logical Standby is too large
ORA-01567: dropping log string would leave less than 2 log files for instance string (thread string)
RMAN-06062: can not backup SPFILE because the instance was not started with SPFILE
PLS-00631: PARTITION-BY and CLUSTER/ORDER-BY clauses must be used with the same function argument
ORA-29819: cannot associate default values with columns
PLS-00356: 'string' must name a table to which the user has access
NNL-00546: Displays delete request statistics
ORA-22970: name does not correspond to an object view