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 |
SQL*Loader-00131: Invalid multithreading option
ORA-39027: wrong version of master table
ORA-25253: listen failed, queue string.string is not enabled for dequeue
ORA-15104: conflicting CONTENTS options
ORA-06774: TLI Driver: error sending break mode
QSM-02067: no partition key or PMARKER or join dependent expression in select list
ORA-29931: specified association does not exist
ORA-30567: name already used by an existing log group
ORA-25116: invalid block number specified in the DUMP DATAFILE/TEMPFILE command
RMAN-10004: unable to connect to recovery catalog
RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from autobackup, found: string
ORA-30037: Cannot perform parallel DML after a prior DML on the object