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-13906: The tablepace is not of the right type.

1 Answers  

---

ORA-26053: Row was not loaded due to conversion error.

1 Answers  

---

DRG-10597: invalid rebuild online operation

1 Answers  

---

LPX-00312: cannot construct XML PI with content: ~S

1 Answers  

---

ORA-00477: SNP* process terminated with error

1 Answers  

---

ORA-00231: snapshot controlfile has not been named

1 Answers  

---

QSM-01003: no query rewrite on DDL queries

1 Answers  

---

ORA-07393: unable to delete text file

1 Answers  

---

ORA-19589: %s is not a snapshot or backup controlfile

1 Answers  

---

ORA-39134: Cannot include "string" tablespace as a Transportable Tablespace

1 Answers  

---

NZE-28853: Initialization failure

1 Answers  

---

ORA-00129: listener address validation failed 'string'

1 Answers  

---