Answer / guest

Cause: A SKIP clause was found in the INTO TABLE statement
of a standard (non-continued) load. In a standard load,
specified with LOAD DATA, it is not possible to skip a
different number of records for each table. The number of
records to skip must be specified for the entire load by
using the SKIP parameter on the command line or in the
OPTIONS clause. If table-level skip is required, because a
different number of records were loaded into each table
(only possible for a multiple- table direct load), then
specify a continued load with the CONTINUE_LOAD statement.
See also messages 409 and 411 for more information.

Action: If the load was not a multiple-table, direct path
load, then move the SKIP clause from the INTO TABLE
statements to the command line or to the OPTIONS clause.
Otherwise, specify the load as continued with CONTINUE_LOAD.

Please add more information about this Error

DRG-12507: stop word string already exists in this stoplist

1 Answers  

---

ORA-01878: specified field not found in datetime or interval

1 Answers  

---

SQL*Loader-00642: Relative start position > absolute field end position.

1 Answers  

---

ORA-13360: invalid subtype in a compound type

1 Answers  

---

ORA-02353: files not from the same unload operation

1 Answers  

---

PLS-00242: invalid external type specification for CONTEXT

1 Answers  

---

ORA-39309: schema sync operation failed

1 Answers  

---

ORA-15034: disk 'string' does not require the FORCE option

1 Answers  

---

ORA-13861: Statistics aggregation for client identifier string is already enabled

1 Answers  

---

ORA-26524: nls subsystem initialization failure for product=string, facility=string

1 Answers  

---

ORA-26012: No data found while executing sql statement string for column string - check input for: string

1 Answers  

---

NNO-00114: line string: other data exists, alias data ignored

1 Answers  

---