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

PLS-00244: Multiple declarations in foreign function formal parameter list

1 Answers  

---

TNS-12539: TNS:buffer over- or under-flow

1 Answers  

---

NNL-00352: Cancelled save config

1 Answers  

---

DRG-12018: Encountered an automatic request for changing proxy - continue?

1 Answers  

---

ORA-00276: CHANGE keyword specified but no change number given

1 Answers  

---

---

ORA-01611: thread number string is invalid - must be between 1 and string

1 Answers  

---

SQL*Loader-00478: unable to continue due to missing filename for LOBFILE or SDF

1 Answers  

---

ORA-16413: Unsupported database type for ONDEMAND archivelog destinations

1 Answers  

---

ORA-21703: cannot flush an object that is not modified

1 Answers  

---

ORA-29283: invalid file operation

1 Answers  

---

PLS-00518: This INSERT statement requires VALUES clause containing a parenthesised list of values

1 Answers  

---

PLS-00393: wrong number of columns in SELECT...INTO statement

1 Answers  

---