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-23382: materialized view repgroup "string"."string" is not registered at site string

1 Answers  

---

ORA-16412: ONDEMAND archival requires active SQL apply operation

1 Answers  

---

ORA-26510: materialized view name: 'string' is greater than max. allowed length of string bytes

1 Answers  

---

ORA-12090: cannot online redefine table "string"."string"

1 Answers  

---

CLSR-01002: Unable to process instance startup

2 Answers  

---

PCB-00219: Invalid size specified in EXEC SQL VAR statement

1 Answers  

---

UDI-00014: invalid value for parameter, 'string'

1 Answers  

---

SQL*Loader-00531: OCI return status: still executing

1 Answers  

---

LSX-00256: empty character class expression

1 Answers  

---

ORA-06306: IPA: Message write length error

1 Answers  

---

ORA-07392: sftcls: fclose error, unable to close text file.

1 Answers  

---

ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword

1 Answers  

---