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
- 2796 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 |
ORA-25407: connection terminated
TNS-00237: Failed to refuse connection
PLS-00655: only functions can be declared as PIPELINED
ORA-13013: the specified topology was not INTERIOR or BOUNDARY
ORA-25436: invalid table alias: string
ORA-09812: Unable to get user clearance from connection
ORA-12641: Authentication service failed to initialize
ORA-12208: TNS:could not find the TNSNAV.ORA file
ORA-38029: object statistics are locked
ORA-30757: cannot access type information
ORA-13291: conversion error between the specified unit and standard unit
ORA-06141: NETTCP: no privilege for user
Oracle Errors 
