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

RMAN-05007: no channel allocated

1 Answers  

---

UDI-00050: unable to setup parameter processing.

1 Answers  

---

ORA-34210: (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.

1 Answers  

---

RMAN-06501: skipping datafile string; already backed up on string

1 Answers  

---

IMG-00545: invalid cut values specified

1 Answers  

---

NNO-00805: Error: OCI_CONTINUE

1 Answers  

---

DRG-50917: escape on at end of text query string

1 Answers  

---

ORA-12425: cannot apply policies or set authorizations for system schemas

1 Answers  

---

RMAN-02003: unrecognized character: string

1 Answers  

---

ORA-31029: Cannot bind to unsaved resource

1 Answers  

---

ORA-23601: PROPAGATION_NAME string does not exist

1 Answers  

---

ORA-12433: create trigger failed, policy not applied

1 Answers  

---