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-10760: illegal format for procedure name

1 Answers  

---

O2I-00103: Two file names refer to the same HFILE file in the INTYPE file

1 Answers  

---

AMD-00109: Parent metadata entity has too many child entities. string "string" has more than string string

1 Answers  

---

QSM-01100: containment check failed for mv, string

1 Answers  

---

ORA-12436: no policy options specified

1 Answers  

---

---

ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.

1 Answers  

---

TNS-12562: TNS:bad global handle

1 Answers  

---

TNS-00554: write failed

1 Answers  

---

ORA-29856: error occurred in the execution of ODCIINDEXDROP routine

2 Answers  

---

ORA-25962: join index prevents multitable insert or merge

1 Answers  

---

ORA-31686: error creating worker processes

1 Answers  

---

SQL*Loader-00293: Missing XMLTYPE directive in control file for table string

1 Answers  

---