SQL*Loader-00410: Number to skip must be load-level, not
table-level
Answer / guest
Cause: A SKIP clause was found in the INTO TABLE statement
of a standard (non-continued) load. In a standard load,
specified with LOAD DATA, it is not possible to skip a
different number of records for each table. The number of
records to skip must be specified for the entire load by
using the SKIP parameter on the command line or in the
OPTIONS clause. If table-level skip is required, because a
different number of records were loaded into each table
(only possible for a multiple- table direct load), then
specify a continued load with the CONTINUE_LOAD statement.
See also messages 409 and 411 for more information.
Action: If the load was not a multiple-table, direct path
load, then move the SKIP clause from the INTO TABLE
statements to the command line or to the OPTIONS clause.
Otherwise, specify the load as continued with CONTINUE_LOAD.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 0 No |
PLS-00535: A VARRAY type may not contain a NESTED TABLE, VARRAY or LOB
ORA-19810: Cannot create temporary controlfile file string in DB_RECOVERY_FILE_DEST
ORA-13484: the file format and/or compression type is not supported
ORA-00028: your session has been killed
RMAN-06455: point-in-time tablespace recovery requires Enterprise Edition
ORA-08269: destroy_ora_addr: cannot destroy name
TNS-00075: NOTE: the user may get the status info of a remote
TNS-04015: Current instance string is not yet started
ORA-27072: File I/O error
ORA-07217: sltln: environment variable cannot be evaluated.
ORA-29548: Java system class reported: string
SQL*Loader-00654: Variable length field exceeds maximum length.