Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, the FOR clause was used in an
array-processing SQL statement. For example, the offending
code might look like: EXEC SQL FOR :limit INSERT INTO EMP
(EMPNO, JOB, DEPTNO) VALUES (:emp_number, :job_title,
:dept_number); This informational message is issued by the
FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, do not use the FOR clause.

Please add more information about this Error

NNL-01066: Statistic counter logging interval: string

1 Answers  

---

ORA-30936: Maximum number (string) of 'string' XML node elements exceeded

1 Answers  

---

ORA-29823: object being analyzed is not a table

1 Answers  

---

ORA-13227: SDO_LEVEL values for the two index tables do not match

1 Answers  

---

ORA-02762: file number to be cancelled is greater than the maximum.

1 Answers  

---

ORA-00099: timed out while waiting for resource, potential PDML deadlock

1 Answers  

---

ORA-09703: sem_release: cannot release latch semaphore

1 Answers  

---

PCC-02325: illegal indirection operation

1 Answers  

---

ORA-22994: source offset is beyond the end of the source LOB

1 Answers  

---

ORA-14102: only one LOGGING or NOLOGGING clause may be specified

1 Answers  

---

ORA-06441: ssvwatev: Incorrect parameter passed to function call

1 Answers  

---

QSM-01061: illegal query expression

1 Answers  

---