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

ORA-23318: a ddl failure has occurred

1 Answers  

---

ORA-24904: invalid callback attribute passed into OCI call

1 Answers  

---

ORA-24184: transformation string.string, already exists

1 Answers  

---

ORA-07504: scgcmn: $hiber unexpected return

1 Answers  

---

ORA-31052: Cannot delete ACL with other references

1 Answers  

---

---

ORA-25152: TEMPFILE cannot be dropped at this time

1 Answers  

---

ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST

1 Answers  

---

ORA-22933: cannot change object with type or table dependents

1 Answers  

---

RMAN-20231: ambiguous datafilecopy name

1 Answers  

---

ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP

1 Answers  

---

PCB-00241: A host variable is required here

1 Answers  

---

ORA-31695: Inconsistent master table on restart. The following SQL statement returned string identical objects. string

1 Answers  

---