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-25176: storage specification not permitted for primary key

1 Answers  

---

RMAN-06401: database is already started

1 Answers  

---

ORA-38448: Indexing predicates with "string" operator is not supported.

1 Answers  

---

ORA-28276: Invalid ORACLE password attribute.

1 Answers  

---

PLS-01406: An identifier has been found that is considered a keyword in ANSI's grammar but not in PL/SQL's

1 Answers  

---

ORA-30348: ADD and DROP cannot both be specified

1 Answers  

---

ORA-06622: LU6.2 Driver: Unable to attach to SNA

1 Answers  

---

CLSS-02200: Received node deletion request for active node string.

1 Answers  

---

ORA-19001: Invalid storage option specified

1 Answers  

---

ORA-01274: cannot add datafile 'string' - file could not be created

1 Answers  

---

ORA-00374: parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]

1 Answers  

---

ORA-02461: Inappropriate use of the INDEX option

1 Answers  

---