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

ORA-12003: materialized view "string"."string" does not exist

1 Answers  

---

ORA-16538: no match on requested item

1 Answers  

---

ORA-01936: cannot specify owner when creating users or roles

1 Answers  

---

ORA-08450: invalid specification of CR in picture mask

1 Answers  

---

ORA-12652: String truncated

1 Answers  

---

SQL*Loader-00467: attribute string does not exist in type string for table string.

1 Answers  

---

ORA-04078: OLD and NEW values cannot be identical

1 Answers  

---

PCB-00301: Use of non-ANSI function is an Oracle extension

1 Answers  

---

ORA-12685: Native service required remotely but disabled locally

1 Answers  

---

ORA-21601: attribute is not an object

1 Answers  

---

TNS-00315: Failed to allocate larger connect data area for getting pump data: number

1 Answers  

---

DRG-10844: index cannot execute this structured predicate efficiently

1 Answers  

---