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

DRG-10750: unknown parameter string

1 Answers  

---

ORA-27160: process requested to perform operation

1 Answers  

---

O2F-00339: CODE option has an illegal value

1 Answers  

---

ORA-29257: host string unknown

1 Answers  

---

ORA-01968: Only specify RESETLOGS or NORESETLOGS once

1 Answers  

---

ORA-14605: Name missing for subpartition / lob segment in template

1 Answers  

---

QSM-01001: query rewrite not enabled

1 Answers  

---

RMAN-08093: specifying current controlfile for proxy backup

1 Answers  

---

ORA-25218: enqueue failed, delay must be zero for queue string.string

1 Answers  

---

ORA-12541: TNS:no listener

1 Answers  

---

NNC-00408: name "string" exists but desired data does not

1 Answers  

---

ORA-14285: cannot COALESCE the only partition of this hash partitioned table or index

1 Answers  

---