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 |
LPX-00305: missing token
TNS-12522: TNS:listener could not find available instance with given INSTANCE_ROLE
ORA-00301: error in adding log file 'string' - file cannot be created
ORA-24154: rule string.string already in rule set string.string
ORA-31416: invalid SOURCE_COLMAP value
ORA-08264: ora_addr: cannot close nameserver
PROC-00006: User does not have permission to perform a cluster registry operation on this key.
ORA-15050: disk "string" contains string error(s)
ORA-28023: must revoke grants of this role to other user(s) first
TNS-04211: Trace Assistant Internal ERROR: CORE
ORA-39600: Queue keys needs to be a suffix of cluster key.
NNL-00935: Requests refused, SINGLE-VALUE violation: number