Interested to Buy Any Domain ? << Click Here >> for more details...
O2F-00324: Unable to convert from the database character set
to the compiler character set
- 1 Answers
- 2939 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 |
LPX-00211: attribute default must be REQUIRED, IMPLIED, or FIXED
ORA-16174: user requested thread/sequence termination of managed recovery
ORA-04005: INCREMENT must be less than MAXVALUE minus MINVALUE
QSM-01025: materialized view, string, not found
ORA-12562: TNS:bad global handle
PLS-00249: Invalid WITH CONTEXT Syntax
PCC-00023: Unable to log off from ORACLE
DRG-50704: Net8 listener is not running or cannot start external procedures
ORA-38424: no attribute set currently assigned to the expression set
ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table
ORA-14126: only a <parallel clause> may follow description(s) of resulting partitions
RMAN-06593: platform name 'string' specified in FROM PLATFORM is not valid
Oracle Errors 
