Answer / guest

Cause: The load is specified with CONTINUE_LOAD, but
DIRECT=FALSE. CONTINUE_LOAD is only possible for a direct
path load and is only necessary for a multiple-table, direct
path load when a different number of records have been
loaded into each table. See also messages 409 and 410 for
more information.

Action: If CONTINUE_LOAD is necessary, specify a direct load
and put the number of records to skip in each INTO TABLE
statement. Otherwise, use the command line or OPTIONS clause
to specify the number of records to skip and use LOAD DATA
instead of CONTINUE_LOAD.

Please add more information about this Error

QSM-01041: materialized view, string, does not match with a measure in the query

1 Answers  

---

DRG-11503: insert statement overflows maximum statement size

1 Answers  

---

ORA-01919: role 'string' does not exist

1 Answers  

---

ORA-14036: partition bound value too large for column

1 Answers  

---

IMG-00899: signature cannot be generated

1 Answers  

---

ORA-00606: Internal error code

1 Answers  

---

SQL*Loader-00404: Column string present more than once in string's INTO TABLE block.

1 Answers  

---

KUP-11012: file string in string already exists

1 Answers  

---

ORA-22868: table with LOBs contains segments in different tablespaces

1 Answers  

---

DRG-51312: DML lock internal error string

1 Answers  

---

ORA-27457: argument string of job "string.string" has no value

1 Answers  

---

ORA-08120: Need to create SYS.IND_ONLINE$ table in order to (re)build index

1 Answers  

---