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

RMAN-20261: ambiguous backup piece handle

1 Answers  

---

ORA-32624: illegal reordering of MODEL dimensions

1 Answers  

---

ORA-25448: rule string.string has errors

1 Answers  

---

ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy

1 Answers  

---

RMAN-05018: some datafile copies cannot be recovered, aborting the RECOVER command

1 Answers  

---

KUP-04021: field formatting error for field string

1 Answers  

---

ORA-02332: cannot create index on attributes of this column

1 Answers  

---

RMAN-08011: including current controlfile in backupset

1 Answers  

---

RMAN-03040: Spooling for trace turned off

1 Answers  

---

TNS-00263: Navigator: Request Failed

1 Answers  

---

ORA-07247: skgfrfms, skgfrnms: read error, unable to read block from database file

1 Answers  

---

ORA-16401: archivelog rejected by RFS

1 Answers  

---