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

ORA-28552: pass-through SQL: call flow error

1 Answers  

---

ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window

1 Answers  

---

ORA-08118: Deferred FK constraints cannot be enforced, index too big (string)

1 Answers  

---

LSX-00205: element "~1S" value "~2S" is wrong (must be "~3S")

1 Answers  

---

ORA-07607: szaud: $SNDOPR failure

1 Answers  

---

ORA-27141: invalid process ID

1 Answers  

---

TNS-00537: Index into protocol adapter table is out of legal range

1 Answers  

---

RMAN-08541: channel string: SPFILE restore from autobackup complete

1 Answers  

---

PLS-00535: A VARRAY type may not contain a NESTED TABLE, VARRAY or LOB

1 Answers  

---

ORA-32139: Cannot write to the stream

1 Answers  

---

ORA-15183: ASMLIB initialization error [string]

1 Answers  

---

ORA-00473: ARCH process terminated with error

1 Answers  

---