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-10641: Cannot find a rollback segment to bind to

1 Answers  

---

ORA-07754: slemcf: fwrite failure

1 Answers  

---

O2U-00211: A type without attributes was translated

1 Answers  

---

PLS-01407: One of the identifiers CHAR, CHARACTER, or INTEGER has been redefined by the programmer

1 Answers  

---

ORA-01124: cannot recover data file string - file is in use or recovery

1 Answers  

---

ORA-39000: bad dump file specification

1 Answers   Oracle,

---

ORA-22996: NEXT extent size is smaller than LOB chunksize

1 Answers  

---

ORA-31634: job already exists

1 Answers  

---

IMP-00086: TOID "string" not found in export file

1 Answers  

---

QSM-02088: mv omits at least one grouping key from the select list

1 Answers  

---

TNS-12633: No shared authentication services

1 Answers  

---

ORA-39129: Object type string not imported. Name conflicts with the master table

1 Answers  

---