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

SQL*Loader-00808: error creating sequence: string

1 Answers  

---

RMAN-06724: backup not done; all files already backed up

1 Answers  

---

ORA-02045: too many local sessions participating in global transaction

1 Answers  

---

DRG-50703: listener startup error

1 Answers  

---

ORA-14262: new subpartition name must differ from the old subpartition name

1 Answers  

---

LFI-01502: Base filename does not exist.

1 Answers  

---

DRG-50801: failed to parse cursor

1 Answers  

---

LPX-00269: all three access functions (open/close/read) must be provided

1 Answers  

---

ORA-30744: "string" is not an object table

1 Answers  

---

ORA-18009: one or more outline system tables do not exist

1 Answers  

---

NNF-04004: Invalid string in inputfile

1 Answers  

---

PCC-02356: Warning at line number, column number, file string:

1 Answers  

---