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

LPX-00314: an internal failure occurred

1 Answers  

---

ORA-25194: invalid COMPRESS prefix length value

1 Answers  

---

ORA-12438: repeated policy option: string

1 Answers  

---

ORA-02736: osnfpm: illegal default shared memory address

1 Answers  

---

ORA-21705: service context is invalid

1 Answers  

---

ORA-31604: invalid string parameter "string" for object type string in function string

1 Answers  

---

ORA-00096: invalid value string for parameter string, must be from among string

1 Answers  

---

ORA-19583: conversation terminated due to error

1 Answers  

---

ORA-14173: illegal subpartition-extended table name syntax

1 Answers  

---

DRG-11003: invalid value string for string

1 Answers  

---

PLS-00120: inappropriate argument in OPEN statement

1 Answers  

---

TNS-00136: Did not register product/facility for TNS error message

1 Answers  

---