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-11119: operation is not supported by this index type

1 Answers  

---

PLS-00304: cannot compile body of 'string' without its specification

1 Answers  

---

ORA-16051: parameter string contains an invalid delay time

1 Answers  

---

ORA-01209: data file is from before the last RESETLOGS

1 Answers  

---

TNS-04234: Trace Assistant WARNING: won't decode TTC

1 Answers  

---

ORA-30750: cannot enable column string to store objects of type string.string

1 Answers  

---

ORA-06516: PL/SQL: the Probe packages do not exist or are invalid

1 Answers  

---

ORA-13260: layer table string does not exist

1 Answers  

---

LSX-00202: contents of "~S" should be text only

1 Answers  

---

TNS-00295: Navigator: Security is enabled, you cannot STOP the Navigator

1 Answers  

---

ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the <LEAF: VALUE> format.

1 Answers  

---

ORA-01311: Illegal invocation of the mine_value function

1 Answers  

---