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 |
RMAN-06053: unable to perform media recovery because of missing log
ORA-29299: Invalid handle for piecewise compress or uncompress
ORA-32032: free temporary object number not available
ORA-24271: translation type must be either T, S or M
NNL-00280: No restart currently scheduled
ORA-23423: job number string is not positive
ORA-12444: policy already applied to table
ORA-02434: cannot enable unique(string) - unique key not defined for table
ORA-23418: cannot unregister the propagator who is currently in use
ORA-02057: 2PC: string: bad two-phase recovery state number string from string
NPL-00311: cannot end constructed ASN.1 encoding, string encoding octets unread
ORA-15104: conflicting CONTENTS options