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

SQL*Loader-00563: bad length for VAR record

1 Answers  

---

ORA-02456: The HASH IS column specification must be NUMBER(*,0)

1 Answers  

---

ORA-32504: expecting one of string, string, string, or string but found string

1 Answers  

---

AMD-00148: Workspace "string" is not currently open. No update done.

1 Answers  

---

IMP-00006: failed to allocate memory of size number

1 Answers  

---

PCB-00237: Declaration of "string" cannot have a level number greater than 48

1 Answers  

---

NNC-00005: cannot initialization stream subsystem

1 Answers  

---

PCC-02035: CMD-LINE: CONFIG= option is invalid in a config file

1 Answers  

---

ORA-16154: suspect attribute: string

1 Answers  

---

NNO-00118: line string: data length string exceeds maximum of string, data ignored

1 Answers  

---

TNS-00553: read failed

1 Answers  

---

ORA-12825: explicit degree of parallelism must be specified here

1 Answers  

---