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-01041: internal error. hostdef extension doesn't exist

1 Answers  

---

ORA-13369: invalid value for etype in the 4-digit format

1 Answers  

---

RMAN-20231: ambiguous datafilecopy name

1 Answers  

---

NNO-00153: warning: hint domain number has invalid name "string", hint domain ignored

1 Answers  

---

ORA-23373: object group "string"."string" does not exist

1 Answers  

---

QSM-00790: the workload string cannot be modified or changed because it is being used by task string

1 Answers  

---

ORA-27039: create file failed, file size limit reached

1 Answers  

---

ORA-24383: Overflow segment of an IOT cannot be described

1 Answers  

---

PLS-00135: Pragma string expects 3rd argument to be an identifier, string or numeric literal

1 Answers  

---

ORA-13214: failed to compute supercell for window object

1 Answers  

---

NNO-00114: line string: other data exists, alias data ignored

1 Answers  

---

ORA-12461: undefined level string for policy string

1 Answers  

---