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

PCC-00121: Arrays of VARCHAR pointers are not supported

1 Answers  

---

NNL-00413: Total response time: string

1 Answers  

---

LSX-00233: invalid long "~S"

1 Answers  

---

RMAN-03015: error occurred in stored script string

1 Answers  

---

ORA-25111: creation of BITMAP cluster indices is not supported

1 Answers  

---

ORA-14133: ALTER TABLE MOVE cannot be combined with other operations

1 Answers  

---

ORA-22346: Type has cyclical dependency. Should use CASCADE option

1 Answers  

---

SQL*Loader-00422: constant element count of number for column string is greater than maximum, number

1 Answers  

---

DRG-11503: insert statement overflows maximum statement size

1 Answers  

---

TNS-00307: Navigator: Reread parameter data

1 Answers  

---

ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor

1 Answers  

---

NID-00501: ----------------------------------------------------

1 Answers  

---