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-01934: circular role grant detected

1 Answers  

---

ORA-27476: "string.string" does not exist

1 Answers  

---

ORA-16006: audit_trail destination incompatible with database open mode

1 Answers  

---

ORA-16582: Could not edit instance specific property.

1 Answers  

---

PCC-02144: CMD-LINE: Blank characters are not allowed on either side of an equal sign (=)

1 Answers  

---

ORA-13428: invalid modelCoordinateLocation

1 Answers  

---

ORA-29549: class string.string has changed, Java session state cleared

1 Answers  

---

ORA-25206: enqueue failed, enqueue to exception queue string.string not permitted

1 Answers  

---

LPX-00281: unsupported encoding "~s"

1 Answers  

---

ORA-22296: invalid ALTER TABLE option for conversion of LONG datatype to LOB

1 Answers  

---

ORA-25016: cannot specify column list for insert into nested table view column

1 Answers  

---

O2I-00117: Internal error: No message file for component O2U

1 Answers  

---