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

ORA-02780: Name given for the core dump directory is invalid

1 Answers  

---

SQL-02153: Invalid character variable for use in a GET/SET statement

1 Answers  

---

ORA-23485: Column group "string" must consist of a single numeric column only

1 Answers  

---

ORA-22292: Cannot open a LOB in read-write mode without a transaction

1 Answers  

---

ORA-27020: named devices not supported

1 Answers  

---

TNS-12654: Authentication conversion failed

1 Answers  

---

ORA-30347: a table name is required to qualify the column specification

1 Answers  

---

SQL*Loader-00262: PIECED keyword (on column string) allowed only when path is direct

1 Answers  

---

ORA-02800: Requests timed out

1 Answers  

---

ORA-13511: invalid INTERVAL string, must be in the range (string, string)

1 Answers  

---

ORA-25117: MIN/MAX/Block Number expected

1 Answers  

---

NNO-00624: setting auto-refresh expiration period to number seconds

1 Answers  

---