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 END-EXEC. 01
USERNAME PIC X(10) VARYING. EXEC SQL END DECLARE SECTION
END-EXEC. This informational message is issued by the FIPS
Flagger when FIPS=YES.

Action: none

Please add more information about this Error

QSM-02068: relation is not a partitioned table

1 Answers  

---

DRG-10601: failed to remove pending DML for this index

1 Answers  

---

ORA-00259: log string of open instance string (thread string) is the current log, cannot archive

1 Answers  

---

ORA-29314: tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY

1 Answers  

---

ORA-36966: (XSRELTBL10) workspace object must be a dimension.

1 Answers  

---

ORA-29530: could not create shortened name for string

1 Answers  

---

ORA-22905: cannot access rows from a non-nested table item

1 Answers  

---

RMAN-06159: error while looking up backup set

1 Answers  

---

LSX-00162: string "~S" is an invalid default for the complex type

1 Answers  

---

RMAN-20217: datafile not part of the database

1 Answers  

---

RMAN-08128: uncataloged backuppiece

1 Answers  

---

ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.

1 Answers  

---