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-04065: not executed, altered or dropped string
LSX-00013: element "~S" not from Schema of Schemas
LSX-00311: local element or attribute shouldn't be namespace qualified
NCR-03009: NCRO: Protocol version mismatch
ORA-14100: partition extended table name cannot refer to a remote object
ORA-13025: polygon does not close
ORA-00331: log version string incompatible with ORACLE version string
RMAN-06169: could not read file header for datafile string error reason string
RMAN-06607: RMAN configuration parameters are:
ORA-12033: cannot use filter columns from materialized view log on "string"."string"
ORA-01863: the year is not supported for the current calendar
SQL*Loader-00434: Can not load LOB/XML in a nested table along with the parent table.