KUP-11003: bad data encountered while reading from file string
Answer / guest
Cause: There was a datatype conversion error while
attempting to convert the data in the data file to match the
datatype of a column in the external table. The message that
follows this one displays the name of the column and the
start of the data for the column that could not be
converted. The row containing the bad data is rejected and
not included as a row in the external table.
Action: If the row containing the bad data should not be
filtered out, then modify the definition of the external
table so that the datatypes of the columns match the
datatypes of the fields in the data file.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-25182: feature not currently available for index-organized tables
SQL*Loader-00929: Error parsing insert statement for table string.
ORA-01212: MAXLOGMEMBERS may not exceed string
ORA-13047: unable to determine ordinate count from table <layer>_SDOLAYER
ORA-13702: Snapshot IDs specified by the range [string, string] are equal.
NZE-28757: system attempt to allocate 0 bytes of memory
RMAN-08039: channel string: starting incremental datafile backupset restore
ORA-12035: could not use materialized view log on "string"."string"
ORA-28293: No matched Kerberos Principal found in any user entry
ORA-01247: database recovery through TSPITR of tablespace string
RMAN-08045: channel string: finished piece string at string with string copies
RMAN-06102: no channel to restore a backup or copy of log thread number seq number lowscn string