Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, dynamic SQL or embedded PL/SQL was used.
For example, the offending code might look like: EXEC SQL
EXECUTE BEGIN SELECT ... END; 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 dynamic SQL or embedded PL/SQL.

Please add more information about this Error

PLS-00524: The parameter type in an ORDER method must be the containing object type.

1 Answers  

---

ORA-22972: NULL value not allowed in PRIMARY KEY-based object identifier

1 Answers  

---

ORA-21606: can not free this object

1 Answers  

---

NNL-00505: log_stats [<server_list>] : write Names server statistics to the log file

1 Answers  

---

ORA-24376: cannot register/get user callback for non-environment handle

1 Answers  

---

LSX-00112: facet "~S" duplicated

1 Answers  

---

ORA-13182: failed to read element string.string.string

1 Answers  

---

PCC-02361: Use of ARRAYLEN with SQL bind arrays is ignored

1 Answers  

---

ORA-30940: Cannot resolve prefix 'string' for QName node 'string'

1 Answers  

---

SQL*Loader-00271: Not a Parallel load. Table level OPTIONS statement ignored.

1 Answers  

---

ORA-26103: V6 or V7 data file used to create control file

1 Answers  

---

ORA-07510: scgbrm: $getlki unexpected return on lockid string

1 Answers  

---