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-26501: RepAPI operation failure

1 Answers  

---

TNS-04065: The number of remote CMCTL sessions exceeds (MAX_CMCTL_SESSIONS-1)

1 Answers  

---

ORA-16159: Cannot change protected standby destination attributes

1 Answers  

---

ORA-07228: rtecho: unable to restore terminal to echo mode.

1 Answers  

---

ORA-16122: applying large dml transaction at SCN string

1 Answers  

---

RMAN-06540: tablespace string will be excluded from future whole database backups

1 Answers  

---

NNO-00308: server will restart in number seconds

1 Answers  

---

ORA-01311: Illegal invocation of the mine_value function

1 Answers  

---

NNO-00708: cache flush countdown aborted

1 Answers  

---

ORA-12351: cannot create view using a remote object which has a remote object reference

1 Answers  

---

NNO-00327: server statistic counter dump ends

1 Answers  

---

ORA-06564: object string does not exist

1 Answers  

---