Answer / guest

Cause: An Oracle extension to the ANSI/ISO standard was
used. Specifically, aa pointer or nonconforming datatype
such as VARCHAR was used. For example, the offending code
might look like: EXEC SQL BEGIN DECLARE SECTION VARCHAR
username[20]; EXEC SQL END DECLARE SECTION This
informational message is issued by the FIPS Flagger when
FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, do not use pointers or nonconforming datatypes.

Please add more information about this Error

TNS-00524: Current operation is still in progress

1 Answers  

---

ORA-31619: invalid dump file "string"

1 Answers  

---

LPX-00604: Invalid attribute value '~1S', for attribute '~2s'.

1 Answers  

---

ORA-08312: sllfop: unrecognized processing option

1 Answers  

---

ORA-16033: parameter string destination cannot be the same as parameter string destination

1 Answers  

---

---

SQL-02129: Fetched number of bytes is odd.

1 Answers  

---

ORA-18010: command missing mandatory CATEGORY keyword

1 Answers  

---

PLS-00642: local collection types not allowed in SQL statements

1 Answers  

---

ORA-36706: (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.

1 Answers  

---

TNS-01102: TNS application contacted was not the listener

1 Answers  

---

ORA-31441: table is not a change table

1 Answers  

---

ORA-16146: standby destination control file enqueue unavailable

1 Answers  

---