Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a nonconforming keyword such as
NOTFOUND, STOP, RAISE, or DO was used in the WHENEVER
statement. (Note that NOT FOUND is ANSI-compliant.) For
example, the offending code might look like: EXEC SQL
WHENEVER SQLERROR STOP; This informational message is issued
by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, do not use the nonconforming keyword.

Please add more information about this Error

PCC-02360: This array type is invalid for use with ARRAYLEN statement

1 Answers  

---

ORA-23403: refresh group "string"."string" already exists

1 Answers  

---

ORA-35074: (QFHEAD02) EIF file string cannot be read by this version of string.

1 Answers  

---

NNL-00012: invalid "string" value "string"

1 Answers  

---

ORA-22631: attribute [string] is is not well-formed or does not match the type

1 Answers  

---

---

ORA-38417: attribute set string does not exist

1 Answers  

---

ORA-12470: NULL or invalid user label: string

1 Answers  

---

NNO-00301: server will shut down in number seconds

1 Answers  

---

ORA-25438: invalid variable name: string

1 Answers  

---

ORA-16100: not a valid Logical Standby database

1 Answers  

---

ORA-35180: (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}

1 Answers  

---

ORA-01616: instance string (thread string) is open - cannot disable

1 Answers  

---