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. This informational message is;
the precompiler ignores the inline value and continues
processing.

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

Please add more information about this Error

SQL*Loader-00942: partition string not part of table string

1 Answers  

---

ORA-21705: service context is invalid

1 Answers  

---

ORA-01332: internal Logminer Dictionary error

1 Answers  

---

ORA-24762: server failed due to unspecified error

1 Answers  

---

ORA-02380: profile string does not exist

1 Answers  

---

---

PLS-00351: Not logged onto database 'string'

1 Answers  

---

ORA-12041: cannot record ROWIDs for index-organized table "string"."string"

1 Answers  

---

ORA-25103: NOPARALLEL option can only be used with ALTER INDEX REBUILD

1 Answers  

---

ORA-30011: Error simulated: psite=string, ptype=string

1 Answers  

---

ORA-27141: invalid process ID

1 Answers  

---

ORA-26664: cannot create STREAMS process string

1 Answers  

---

PLS-00233: function name used as an exception name in when clause

1 Answers  

---