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

ORA-12982: cannot drop column from a nested table

1 Answers  

---

ORA-23501: refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0

1 Answers  

---

ORA-14044: only one partition may be moved

1 Answers  

---

ORA-06322: IPA: Fatal shared memory error

1 Answers  

---

RMAN-08182: channel string: validation complete, elapsed time: string

1 Answers  

---

ORA-00128: this command requires a dispatcher name

1 Answers  

---

ORA-16520: unable to allocate resource id

1 Answers  

---

TNS-12648: Encryption or data integrity algorithm list empty

1 Answers  

---

NCR-02009: NCRF: Unable to open trace file

1 Answers  

---

ORA-29502: NAMED keyword required in CREATE JAVA RESOURCE

1 Answers  

---

EXP-00093: Could not convert to server character set's handle

2 Answers  

---

PCC-02023: Found end of file while scanning a PL/SQL statement

1 Answers  

---