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-15017: diskgroup "string" cannot be mounted

1 Answers  

---

ORA-12800: system appears too busy for parallel query execution

1 Answers  

---

DRG-10702: cannot create or modify preference in another user's schema

1 Answers  

---

ORA-25270: sender info does not match with the actual sender of the message

1 Answers  

---

ORA-15090: handle string is not a valid descriptor

1 Answers  

---

ORA-31468: cannot process DDL change record

1 Answers  

---

ORA-12055: materialized view definition contains cyclic dependencies with existing materialized views

1 Answers  

---

ORA-24909: call in progress. Current operation cancelled

1 Answers  

---

TNS-00525: Insufficient privilege for operation

1 Answers  

---

PLS-00242: invalid external type specification for CONTEXT

1 Answers  

---

RMAN-06490: WARNING: limit of autobackups for the day has been reached

1 Answers  

---

ORA-25251: exceeded maximum number of recipients for message

1 Answers  

---