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

DRG-10528: primary keys of type string are not allowed

1 Answers  

---

NNL-00254: Server-generated requests currently do not request forwarding

1 Answers  

---

ORA-31100: XDB Locking Internal Error

1 Answers  

---

ORA-14605: Name missing for subpartition / lob segment in template

1 Answers  

---

PLS-00540: object not supported in this context.

1 Answers  

---

KUP-11009: data for row: string

1 Answers  

---

CLSS-02204: voting device not configured. [string] [string]

1 Answers  

---

IMG-00584: output format does not support the specified compressionQuality

1 Answers  

---

ORA-13009: the specified date string is invalid

1 Answers  

---

NCR-00003: NCR: Initialization failure

1 Answers  

---

PCC-00005: Unsupported datatype in line number of file string

1 Answers  

---

RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row

1 Answers  

---