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-11702: %(1)s

1 Answers  

---

ORA-00357: too many members specified for log file, the maximum is string

1 Answers  

---

ORA-03278: duplicate ALLOCATE EXTENT option specification

1 Answers  

---

ORA-16629: Database reports a different protection level from the protection mode.

2 Answers  

---

ORA-27365: job has been notified to stop, but failed to do so immediately

1 Answers  

---

ORA-31201: DBMS_LDAP: generic error: string

1 Answers  

---

ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.

1 Answers  

---

ORA-30352: inconsistent numeric precision or string length

1 Answers  

---

ORA-19729: File string is not the initial version of the plugged in datafile

1 Answers  

---

SQL*Loader-00914: Error locking table string in exclusive mode.

1 Answers  

---

ORA-31639: unexpected data found

1 Answers  

---

TNS-00230: Cannot start new pump process: string string Protocol Adapter errors:number

1 Answers  

---