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 |
ORA-02468: Constant or system variable wrongly specified in expression
ORA-23474: definition of "string"."string" has changed since generation of replication support
PLS-00126: selector ALL is not allowed
ORA-09770: pws_look_up: translation failure.
PCC-00121: Arrays of VARCHAR pointers are not supported
NNL-01072: Administrative region name: string
KUP-04025: field extends beyond end of record
ORA-22626: Type Mismatch while constructing or accessing OCIAnyData
RMAN-06173: no set newname command has been issued for datafile string when restore auxiliary
ORA-27013: skgfqdel: cannot delete an open file
ORA-04934: unable to obtain the current sequence number
ORA-13195: failed to generate maximum tile value