SQL*Loader-00409: Number to skip must be table-level, not
load-level on continued loads
- 1 Answers
- 4852 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The SKIP parameter was specified on the command line
or in the OPTIONS statement, but the load was specified as
continued with CONTINUE_LOAD. When a multiple-table direct
load is interrupted, it is possible that a different number
of records were loaded into each table. As a result, the
number of records to skip must be specified for each table
when continuing the load. In this case, the load is
specified as continued with the CONTINUE_LOAD statement, and
the number of records to skip is given in each INTO TABLE
statement. See also messages 410 and 411 for more information.
Action: Check the log file to determine the appropriate
number of records to skip for each table and specify this
number in the INTO TABLE statement for each table in a
continued load or with the command-line SKIP parameter in a
standard load.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
NNO-00331: error saving new value string of string to the save config table.
ORA-16625: cannot reach the primary
ORA-01641: tablespace 'string' is not online - cannot add data file
ORA-06137: NETTCP: error during connection handshake
ORA-01538: failed to acquire any rollback segment
TNS-01157: Can only listen on number addresses - ignoring string
UDE-00013: internal expdp error.
DRG-50925: could not parse return value of PL/SQL
RMAN-06517: KEEP option is not supported for archive log backups
ORA-24422: error occurred while trying to destroy the Session Pool
QSM-02148: many to many subquery joins require 9.0 compatibility or higher
NID-00371: Change database name of database string to string? (Y/[N]) =>
Oracle Errors 
