Answer / guest

Cause: The SQLCHECK option was entered inline and specified
a level of checking higher than the level specified (or
accepted by default) on the command line. This is not
allowed. For example, if SQLCHECK={SYNTAX | LIMITED} is
specified on the command line, SQLCHECK={SEMANTICS | FULL}
cannot be specified inline.

Action: Revise the EXEC ORACLE statement or specify a lower
level of checking on the command line.

Please add more information about this Error

ORA-12085: materialized view log on "string"."string" already has object id

1 Answers  

---

ORA-31693: Table data object string failed to load/unload and is being skipped due to error: string

1 Answers  

---

NID-00133: Database should have only consistent datafiles

1 Answers  

---

SQL*Loader-00467: attribute string does not exist in type string for table string.

1 Answers  

---

TNS-01180: Missing listener object string in Directory Server

1 Answers  

---

LPX-00111: invalid ~1s "~2S" (not a Nmtoken)

1 Answers  

---

ORA-22281: cannot perform operation with an updated locator

1 Answers  

---

ORA-36380: (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.

1 Answers  

---

ORA-21611: key length [string] is invalid

1 Answers  

---

ORA-22878: duplicate LOB partition or subpartition specified

1 Answers  

---

ORA-06603: LU6.2 Driver: Error allocating memory

1 Answers  

---

ORA-30677: session is already connected to a debugger

1 Answers  

---