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

QSM-01107: Partition Containment Tracking (PCT) rewrite is not allowed

1 Answers  

---

NCR-01012: NCRS: Receive message failure.

1 Answers  

---

ORA-03122: attempt to close ORACLE-side window on user side

1 Answers  

---

ORA-29827: keyword USING is missing

1 Answers  

---

NZE-29136: The allocated buffer is too small.

1 Answers  

---

ORA-00268: specified log file does not exist 'string'

1 Answers  

---

RMAN-06204: Changed string objects to UNAVAILABLE status

1 Answers  

---

ORA-38460: filtering based on datatype "string" not supported for XML Tags

1 Answers  

---

KUP-11008: conversion error loading table string.string partition string

1 Answers  

---

ORA-31504: cannot alter or drop predefined change source

1 Answers  

---

PLS-00407: '*' not allowed here; a list of columns is required

1 Answers  

---

ORA-16401: archivelog rejected by RFS

1 Answers  

---