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-10517: index string is already valid

1 Answers  

---

ORA-06914: CMX: unexepected event during start of oracle

1 Answers  

---

ORA-22321: method does not return any result

1 Answers  

---

ORA-30114: error when processing from command line

1 Answers  

---

CLSR-01005: Error number encountered during altering database open mode

1 Answers  

---

RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used

1 Answers  

---

ORA-26565: Call to <type>_arg made before calling dbms_defer.call

1 Answers  

---

TNS-00061: INTCTL: Bad command or syntax error: You must specify a trace level

1 Answers  

---

DRG-11216: length of datastore data exceeds limit

1 Answers  

---

ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.

1 Answers  

---

LSX-00015: failed to parse document

1 Answers  

---

ORA-33002: (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.

1 Answers  

---