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

ORA-13377: invalid combination of elements with orientation

1 Answers  

---

ORA-39315: illegal swap() call: only applys after clone/sync_code

1 Answers  

---

IMG-00822: area queue reset failed

1 Answers  

---

TNS-12197: TNS:keyword-value resolution error

1 Answers  

---

NMP-00001: value too big

1 Answers  

---

NZE-29044: Renegotiation has already been requested.

1 Answers  

---

ORA-07253: spdes: semctl error, unable to destroy semaphore set.

1 Answers  

---

ORA-00328: archived log ends at change string, need later change string

1 Answers  

---

ORA-13367: wrong orientation for interior/exterior rings

1 Answers  

---

DRG-12439: highlight table read failed

1 Answers  

---

ORA-30689: improper value for ORA_DEBUG_JDWP

1 Answers  

---

ORA-02299: cannot validate (string.string) - duplicate keys found

2 Answers  

---