SQL*Loader-00409: Number to skip must be table-level, not
load-level on continued loads
- 1 Answers
- 5607 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 |
ORA-03128: connection is in blocking mode
LSX-00158: base type of "~S" must be simple type or primitive datatype
ORA-19766: missing CHANGE keyword
ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.
ORA-24421: OCISessionRelease cannot be used to release this session.
QSM-02002: DISTINCT aggregate measure in SELECT list
ORA-15066: offlining disk "string" may result in a data loss
ORA-02801: Operations timed out
ORA-01921: role name 'string' conflicts with another user or role name
RMAN-06706: could not close file: "string" (reason=string)
ORA-32586: multiple specification of a supplemental logging attribute
SQL*Loader-00950: Error shipping data structures across 2-task
Oracle Errors 
