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

ORA-02380: profile string does not exist

1 Answers  

---

ORA-27020: named devices not supported

1 Answers  

---

ORA-25307: Enqueue rate too high. Enable flow control

3 Answers  

---

KUP-04078: invalid file name specified: string

1 Answers  

---

ORA-03277: invalid SIZE specified

1 Answers  

---

TNS-00252: Unable to handle route request: string

1 Answers  

---

ORA-30509: client logoff triggers cannot have AFTER type

1 Answers  

---

PLS-01409: Use of 'PRIOR_' token

1 Answers  

---

SQL*Loader-00650: incomplete lob data written for column string, row number, table string

1 Answers  

---

ORA-13015: the window definition is not valid

1 Answers  

---

RMAN-06700: error parsing text script in file string

1 Answers  

---

ORA-12064: invalid refresh sequence number: string

1 Answers  

---