Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a nonconforming SQL statement such as
PREPARE was used. For example, the offending code might look
like: EXEC SQL PREPARE sql_statement FROM :sql_string; 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 statement.

Please add more information about this Error

RMAN-06054: media recovery requesting unknown log: thread string seq string lowscn string

1 Answers  

---

RMAN-06720: file "string" removed from catalog

1 Answers  

---

CLSR-00511: Error number encountered when handling incoming EVM message

1 Answers  

---

ORA-02070: database stringstring does not support string in this context

1 Answers  

---

AMD-00160: Warning! Exceeded maximum Custom Measure number of "string"

1 Answers  

---

ORA-03236: max # extents (string) reached in index string.string subpartition string

1 Answers  

---

PLS-00125: type name expected

1 Answers  

---

ORA-19715: invalid format string for generated name

1 Answers  

---

ORA-12063: unable to apply transaction from site string

1 Answers  

---

DRG-50910: max documents requested string outside valid range 1 to 65535

1 Answers  

---

ORA-07514: scgcan: $deq unexpected return while canceling lock

1 Answers  

---

UDI-00011: parameter string is incompatible with parameter string

1 Answers  

---