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.

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-25352: no current transaction

1 Answers  

---

ORA-32809: foreign queue string is already registered

1 Answers  

---

ORA-31617: unable to open dump file "string" for write

1 Answers  

---

ORA-08456: no sign in picture mask but SIGN clause in mask options

1 Answers  

---

QSM-02083: mv references PL/SQL function that maintains state

1 Answers  

---

ORA-01686: max # files (string) reached for the tablespace string

1 Answers  

---

ORA-30493: The percentile value should be a number between 0 and 1.

1 Answers  

---

ORA-29950: warning in the execution of ODCIINDEXMERGEPARTITION routine

1 Answers  

---

TNS-00079: * log_off - ask process_name to turn logging off

1 Answers  

---

ORA-23541: tables do not match tables used while defining the redefinition

1 Answers  

---

ORA-28537: no more result sets

1 Answers  

---

ORA-00965: column aliases not allowed for '*'

1 Answers  

---