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

ORA-32607: invalid ITERATE value in MODEL clause

1 Answers  

---

PLS-00130: Pragma string expects 1st argument to be a procedure/function/package/cursor

1 Answers  

---

ORA-29380: resource plan string is currently active and cannot be deleted

1 Answers  

---

RMAN-06606: RMAN configuration parameters are successfully reset to default value

1 Answers  

---

NNO-00610: detected possible alias loop involving name "string"

1 Answers  

---

CLSS-02205: remote node string signaled our eviction via voting device: cause string

1 Answers  

---

ORA-23303: application raised generic exception during deferred RPC

1 Answers  

---

PCC-02209: Macro invocation has incorrect number of arguments

1 Answers  

---

ORA-16793: Logical Standby Database Guard is unexpectedly OFF

1 Answers  

---

TNS-01095: %s * string * string * number

1 Answers  

---

ORA-39125: Worker unexpected fatal error in string while calling string [string]

1 Answers  

---

ORA-31440: change set string is empty and cannot be advanced

1 Answers  

---