SQL*Loader-00409: Number to skip must be table-level, not
load-level on continued loads
- 1 Answers
- 3961 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-16413: Unsupported database type for ONDEMAND archivelog destinations
ORA-27369: job of type EXECUTABLE failed with exit code: string
ORA-09292: sksabln: unable to build archive file name
ORA-27469: %s is not a valid string attribute
ORA-22343: Compilation error for type invalidated by ALTER TYPE
ORA-15133: instance recovery required for diskgroup string
NNL-01032: Minimum TTL: string
TNS-00311: Connection Manager: Failed to start tracing after rereading parameter data
ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string
QSM-00802: An error occurred while implementing action string (string) string.
ORA-10651: incorrect file number block number specified
ORA-31697: aborting operation at process order number string
Oracle Errors 
