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

SQL*Loader-00428: count for field string not stored in character or integer field

1 Answers  

---

ORA-06138: NETTCP: error during connection handshake

1 Answers  

---

RMAN-08520: channel string: scanning archive log string

1 Answers  

---

RMAN-03019: asynchronous RPCs are NOT working

1 Answers  

---

ORA-02377: invalid resource limit

1 Answers  

---

RMAN-06590: tablespace string cannot be converted

1 Answers  

---

RMAN-06246: List of Database Incarnations

1 Answers  

---

LPX-00002: out of memory

1 Answers  

---

ORA-12548: TNS:incomplete read or write

1 Answers  

---

ORA-31157: Invalid Content-Type charset

1 Answers  

---

ORA-16003: standby database is restricted to read-only access

1 Answers  

---

DRG-10315: logging is not supported on MTS

1 Answers  

---