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

SQL*Loader-00509: System error: string

1 Answers  

---

ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory

1 Answers  

---

ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.

1 Answers  

---

ORA-21524: object type mismatch

1 Answers  

---

ORA-23329: successful user-provided ddl but no materialized view "string"."string"

1 Answers  

---

ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string

1 Answers  

---

NZE-28813: invalid record type

1 Answers  

---

ORA-22604: TDS handle already generated

1 Answers  

---

NZE-28752: data source initialization failure

1 Answers  

---

ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree

1 Answers  

---

ORA-31051: Requested access privileges not supported

1 Answers  

---

ORA-23450: flavor already contains object "string"."string"

1 Answers  

---