SQL*Loader-00409: Number to skip must be table-level, not
load-level on continued loads
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-01799: a column may not be outer-joined to a subquery
ORA-12418: user string not found
ORA-38760: This database instance failed to turn on flashback database
ORA-12084: must use ALTER MATERIALIZED VIEW to alter "string"."string"
ORA-01931: cannot grant string to a role
ORA-12545: Connect failed because target host or object does not exist
ORA-13008: the specified date format has an invalid component
ORA-29809: cannot drop an operator with dependent objects
PLS-00510: Float cannot have scale
ORA-37122: AW Session cache disabled
ORA-15025: could not open disk 'string'
ORA-13433: GeoRaster metadata default RGB error