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

DRG-50924: PL/SQL inside PL/SQL not supported

1 Answers  

---

DRG-11480: ctxkbtc memory allocation error: %(1)

1 Answers  

---

ORA-30337: multiple JOIN KEY clauses specified for the same parent level

1 Answers  

---

TNS-12525: TNS:listener has not received client's request in time allowed

1 Answers  

---

ORA-07844: sllfop: LIB$GET_VM failure

1 Answers  

---

RMAN-06146: changes found for file number beyond offline SCN

1 Answers  

---

ORA-16038: log string sequence# string cannot be archived

4 Answers  

---

ORA-01061: cannot start up a V8 server using a V7 client application

1 Answers  

---

KUP-04074: no write access to directory object string

2 Answers  

---

ORA-24303: call not supported in non-deferred linkage

1 Answers  

---

ORA-29917: cannot lock a table which gets its rows from a collection operand

1 Answers  

---

NNL-00960: Time until cache flush: string

1 Answers  

---