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.
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-07624: smsdes: $DGBLSC failure
ORA-30377: MV_CAPABILITIES_TABLE not found
ORA-31198: Mismatch in number of bytes transferred due to non-binary mode
LFI-00005: Free some memory failed in string.
DRG-10312: logfile name must be specified
ORA-10614: Operation not allowed on this segment
ORA-07550: sftopn: $CONNECT failure
ORA-22930: directory does not exist
RMAN-03030: echo set off
IMG-00856: adjacency matrix free failed
DRG-12223: section name string is a reserved name
ORA-32036: unsupported case for inlining of query name in WITH clause