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-01092: ORACLE instance terminated. Disconnection forced

1 Answers  

---

KUP-11010: unable to open at least one dump file for load

1 Answers  

---

LSX-00200: element "~S" not empty

1 Answers  

---

TNS-00316: Ran out of data buffers in the pump

1 Answers  

---

ORA-30551: The index depends on a package/type body which does not exist

1 Answers  

---

---

ORA-31180: DOM Type mismatch in invalid PL/SQL DOM handle

1 Answers  

---

ORA-29656: Invalid option for USING

1 Answers  

---

ORA-19678: RMAN configuration value exceeds maximum length of string

1 Answers  

---

ORA-01631: max # extents (string) reached in table string.string

1 Answers  

---

NNL-00224: Scheduled statistic counters to be logged in string

1 Answers  

---

ORA-24037: schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE

1 Answers  

---

RMAN-08093: specifying current controlfile for proxy backup

1 Answers  

---