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-07746: slemrd: invalid error message file handle

1 Answers  

---

ORA-36677: (XSDPART15) Duplicate value in value lists of number and number

1 Answers  

---

ORA-23473: replication RPC processing for "string"."string" is disabled

1 Answers  

---

PLS-00595: the TABLE operator is not allowed in this context

1 Answers  

---

ORA-12807: process queue could not receive parallel query message

1 Answers  

---

PCB-00700: This statement can only be used with DYNAMIC=ANSI

1 Answers  

---

ORA-06764: TLI Driver: error reading disconnect

1 Answers  

---

NID-00308: Control File string - dbid changed

1 Answers  

---

TNS-04007: Internal error number.

1 Answers  

---

ORA-12564: TNS:connection refused

1 Answers  

---

PLS-00658: constructor method name must match type name

1 Answers  

---

RMAN-06173: no set newname command has been issued for datafile string when restore auxiliary

1 Answers  

---