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 |
TNS-00513: Destination host unreachable
TNS-12612: TNS:connection is busy
ORA-23320: the request failed because of values string and string
ORA-22327: cannot change a type to NOT INSTANTIABLE if it has dependent tables
ORA-12164: TNS:Sqlnet.fdf file not present
ORA-26513: push error: master proc. string$RP.string failed for trans:string seq:string
ORA-26525: session connection attempt failed for string (@string)
SQL*Loader-00626: Character set conversion buffer overflow.
NZE-28768: bad magic number
ORA-29848: error occurred in the execution of ODCIINDEXMERGEPARTITION routine
ORA-04062: %s of string has been changed
ORA-29532: Java call terminated by uncaught Java exception: string