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-14285: cannot COALESCE the only partition of this hash partitioned table or index

1 Answers  

---

ORA-38957: Target database not 10.0.0.0 compatible

1 Answers  

---

ORA-14459: missing GLOBAL keyword

2 Answers  

---

SQL*Loader-00518: Error reassembling file name (string)

1 Answers  

---

ORA-24158: invalid table alias

1 Answers  

---

ORA-01297: redo version mismatch between dictionary string and logfiles

1 Answers  

---

LCD-00114: illegal boolean response [string]

1 Answers  

---

ORA-07445: exception encountered: core dump [string] [string] [string] [string] [string] [string]

1 Answers  

---

ORA-32012: failure in processing system parameters from restored SPFILE

1 Answers  

---

NZE-29249: an unrecognized state was passed to a cryptographic function

1 Answers  

---

ORA-24775: cannot prepare or commit transaction with non-zero lock value

1 Answers  

---

ORA-28595: Extproc agent : Invalid DLL Path

1 Answers  

---