Answer / guest

Cause: The SKIP parameter was specified on the command line
or in the OPTIONS statement, but the load was specified as
continued with CONTINUE_LOAD. When a multiple-table direct
load is interrupted, it is possible that a different number
of records were loaded into each table. As a result, the
number of records to skip must be specified for each table
when continuing the load. In this case, the load is
specified as continued with the CONTINUE_LOAD statement, and
the number of records to skip is given in each INTO TABLE
statement. See also messages 410 and 411 for more information.

Action: Check the log file to determine the appropriate
number of records to skip for each table and specify this
number in the INTO TABLE statement for each table in a
continued load or with the command-line SKIP parameter in a
standard load.

Please add more information about this Error

ORA-29398: invalid privilege name specified

1 Answers  

---

ORA-32013: failure in verifying parameters from the restored SPFILE

1 Answers  

---

ORA-12463: undefined group string for policy string

1 Answers  

---

ORA-14043: only one partition may be added

1 Answers  

---

ORA-30077: illegal casting between specified datetime types

1 Answers  

---

ORA-25136: this cluster can contain only one table

1 Answers  

---

ORA-32333: disable table scn update for Materialized view

1 Answers  

---

ORA-24411: Session pool already exists.

1 Answers  

---

DRG-11118: object string does not exist

1 Answers  

---

ORA-16537: child count exceeded

1 Answers  

---

ORA-38741: Formatted blocks value string is not valid.

1 Answers  

---

PLS-01909: : cannot assign supertype instance to subtype

1 Answers  

---