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 |
DRG-11114: result table format is not correct for this operation
RMAN-08507: input datafilecopy recid=string stamp=string filename=string
ORA-27012: skgfrd: read from file failed
DRG-10533: invalid user name: string
ORA-07242: slembfn: translation error, unable to translate error file name.
ORA-15000: command disallowed by current instance type
LSX-00162: string "~S" is an invalid default for the complex type
KUP-00554: error encountered while parsing access parameters
ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area
ORA-06706: TLI Driver: service not found
ORA-06025: NETASY: Configuration error
QSM-02079: mv log must have ROWID