Answer / guest

Cause: The user exported an object with data type NTEXT, but
the EIF file that will result from the EXPORT command is not
written in Unicode. Because no non-Unicode file can
represent all possible Unicode data, it is possible that
some data will be lost when converting from the Unicode
NTEXT object to the EIF file. The EIF file will be written
in the character set indicated by the "nls_charset" argument
of the EXPORT command, or, if no such argument is present,
in the database character set.

Action: If the user is certain that the contents of the
NTEXT object can be represented in the specified character
set, then no action is necessary. Otherwise, the user can
add "nls_charset 'UTF8'" to the EXPORT command string. This
will result in the EIF file being written in UTF8 Unicode,
which can represent all the data contained in NTEXT objects.

Please add more information about this Error

RMAN-06449: deleted proxy copy

1 Answers  

---

ORA-39149: cannot link privileged user to non-privileged user

1 Answers  

---

ORA-30381: REWRITE_TABLE is not compatible with Oracle version

1 Answers  

---

ORA-10641: Cannot find a rollback segment to bind to

1 Answers  

---

NID-00395: Reverting database name from string to string

1 Answers  

---

---

NCR-00002: NCR: Invalid usage

1 Answers  

---

TNS-01172: Listener has shut down since all listen addresses have been deallocated

1 Answers  

---

ORA-14113: partitioned table cannot have column with LOB datatype

1 Answers  

---

DRG-12303: cannot add more than 99 indexes to an index set

1 Answers  

---

RMAN-06280: Report of obsolete backups and copies

1 Answers  

---

ORA-31114: XDB configuration has been deleted or is corrupted

1 Answers  

---

NNL-00204: Cancelled shutdown

1 Answers  

---