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-04231: Trace Assistant WARNING: Assuming Oracle trace format

1 Answers  

---

ORA-06302: IPA: Cannot connect to remote host

1 Answers  

---

ORA-13016: specified topology [string] is invalid

1 Answers  

---

ORA-40262: NMF: number of features not between [1, string]

1 Answers  

---

LPX-00005: ~1s buffer overflow, maximum size is ~2u bytes

1 Answers  

---

---

ORA-31122: The string operator has incorrect RHS value

1 Answers  

---

TNS-01030: The listener supports no services

1 Answers  

---

DRG-10701: preference string.string already exists

1 Answers  

---

TNS-12679: Native services disabled by other process but required

1 Answers  

---

KUP-03008: OCI error getting column parameters.

1 Answers  

---

ORA-23304: malformed deferred rpc at arg string of string in call string, in tid string

1 Answers  

---

ORA-30360: REF not supported with query rewrite

1 Answers  

---