Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, the FOR clause was used in an
table-processing SQL statement. For example, the offending
code might look like: EXEC SQL FOR :LIMIT INSERT INTO EMP
(EMPNO, JOB, DEPTNO) VALUES (:EMPNUM, :JOB, :DEPTNO)
END-EXEC. 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

PLS-01709: value list of INSERT statement, if specified with value list rather than subquery, must be value specification

1 Answers  

---

ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string

1 Answers  

---

ORA-19611: backup piece out of order. Expected string but found string

1 Answers  

---

ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME

1 Answers  

---

NNL-00236: Statistic counter reset interval is currently string

1 Answers  

---

ORA-30111: no closing quote for value 'string'

1 Answers  

---

ORA-36666: (XSDPART04) workspace object is not a concat dimension.

1 Answers  

---

DRG-11822: Forbidden

1 Answers  

---

SQL-02153: Invalid character variable for use in a GET/SET statement

1 Answers  

---

ORA-12064: invalid refresh sequence number: string

1 Answers  

---

ORA-15012: ASM file 'string' does not exist

1 Answers  

---

RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE

1 Answers  

---