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-13858: Invalid action name

1 Answers  

---

PLS-00386: type mismatch found at 'string' between FETCH cursor and INTO variables

1 Answers  

---

ORA-10567: Redo is inconsistent with data block (file# string, block# string)

1 Answers  

---

LSX-00008: feature "~s" is not implemented

1 Answers  

---

ORA-00023: session references process private memory; cannot detach session

2 Answers  

---

---

ORA-06443: ssvpstev: Incorrect parameter passed to function call

1 Answers  

---

ORA-12549: TNS:operating system resource quota exceeded

1 Answers  

---

ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

2 Answers  

---

ORA-16622: Two or more broker database objects resolve to one physical database.

1 Answers  

---

ORA-02083: database name has illegal character 'string'

1 Answers  

---

SQL*Loader-00126: Invalid read size

1 Answers  

---

ORA-22816: unsupported feature with RETURNING clause

1 Answers  

---