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
- 2734 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-06515: PL/SQL: unhandled exception string
LSX-00176: circular reference detected in schema component named "~S"
ORA-16543: invalid request made to broker
ORA-32313: REFRESH FAST of "string"."string" unsupported after PMOPs
O2F-00319: No OUTTYPE file specified
ORA-04063: %s has errors
ORA-16073: archiving must be enabled
ORA-10662: Segment has long columns
ORA-28300: No permission to read user entry in LDAP directory service.
ORA-01155: the database is being opened, closed, mounted or dismounted
QSM-00797: the specified workload string does not exist for the current user
ORA-01870: the intervals or datetimes are not mutually comparable
Oracle Errors 
