Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects
using string for the EIF file character set can cause loss
of data. To preserve all NTEXT data, export using the UTF8
character set for the EIF file.
- 1 Answers
- 2813 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
LSX-00283: referenced notation "~S" is not defined
ORA-32578: password for SYS already specified
ORA-07633: smsdbp: illegal protection value
ORA-13454: GeoRaster metadata is invalid
ORA-13860: Invalid service name
RMAN-06562: available space of number kb needed to avoid reading the backup set multiple times
DRG-11818: Temporary Redirect
ORA-07706: error in archive text: need disk file name
ORA-31102: Already locked in exclusive mode. Cannot add lock.
NNL-00893: Similar requests received: number
ORA-00072: process "string" is not active
ORA-36691: (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string.
Oracle Errors 
