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-24358: OCIBindObject not invoked for a Object type or Reference

1 Answers  

---

ORA-15041: diskgroup space exhausted

1 Answers  

---

PROT-00011: Failed to open the specified destination cluster registry

1 Answers  

---

PCC-00065: Userid required, but not specified.

1 Answers  

---

ORA-07226: rtneco: unable to get terminal mode.

1 Answers  

---

ORA-15180: Could not open dynamic library string, error [string]

1 Answers  

---

ORA-01764: new update value of join is not guaranteed to be unique

1 Answers  

---

ORA-02028: fetching an exact number of rows is not supported by the server

1 Answers  

---

ORA-01629: max # extents (string) reached saving undo for tablespace string

1 Answers  

---

NZE-29110: Invalid PKCS #12 bag type

1 Answers  

---

PCC-02415: Cannot manipulate Object attributes in an OBJECT GET or SET

1 Answers  

---

LPX-00261: invalid URL ~s

1 Answers  

---