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 END-EXEC. 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

QSM-00788: the table string is invalid for directive string

1 Answers  

---

ORA-32009: cannot reset the memory value for instance string from instance string

1 Answers  

---

RMAN-10010: error while checking for RPC completion

1 Answers  

---

ORA-30942: XML Schema Evolution error for schema 'string' table string column 'string'

1 Answers  

---

ORA-25125: BUFFER_POOL storage option not allowed

1 Answers  

---

TNS-00009: INTCTL: could not contact destination Connection Manager

1 Answers  

---

NCR-04009: NCRR: Object exists

1 Answers  

---

ORA-24292: no more tables permitted in this sorted hash cluster

1 Answers  

---

ORA-26663: error queue for apply process string must be empty

1 Answers  

---

ORA-23493: "string" is not a new site for extension request "string"

1 Answers  

---

ORA-30073: invalid adjustment value

1 Answers  

---

RMAN-05004: target database log mode is NOARCHIVELOG

1 Answers  

---