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-12426: invalid audit option
SQL-02119: Invalid HSTDEF argument
NNO-00251: missing administrative region parameter string
RMAN-06903: backup of datafile string was cancelled
ORA-40004: penalty must be negative for BLAST-N
ORA-19692: missing creation stamp on piece string
ORA-28000: the account is locked
RMAN-06021: FROM DATAFILECCOPY/BACKUPSET may not be specified with archive logs
ORA-31208: DBMS_LDAP: PL/SQL - Invalid LDAP Message.
PCB-00001: %s
ORA-01296: character set mismatch between dictionary string and logfiles
ORA-01185: logfile group number string is invalid