SQL*Loader-00409: Number to skip must be table-level, not
load-level on continued loads
- 1 Answers
- 4687 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 |
PCC-02353: Semantic error at line number, column number, file string:
ORA-06557: null values are not allowed for any parameters to pipe icd's
ORA-12654: Authentication conversion failed
ORA-02460: Inappropriate index operation on a hash cluster
SQL*Loader-00479: REF directive for column string expects number arguments; found number.
ORA-12019: master table is a synonym to a remote object
ORA-00088: command cannot be executed by shared server
ORA-25306: Queue table string has buffered queues. Cannot alter
ORA-39113: Unable to determine database version
EXP-00005: all allowable logon attempts failed
ORA-07203: sltln: attempt to translate a long environment variable.
ORA-29917: cannot lock a table which gets its rows from a collection operand
Oracle Errors 
