Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, the CONNECT statement was used to log on
to ORACLE. For example, the offending code might look like:
EXEC SQL CONNECT :USERNAME IDENTIFIED BY :PSSWORD END-EXEC.
This informational message is issued by the FIPS Flagger
when FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, specify the AUTO_CONNECT command-line option
instead of using a CONNECT statement.

Please add more information about this Error

ORA-07700: sksarch: interrupt received

1 Answers  

---

ORA-25001: cannot create this trigger type on views

1 Answers  

---

ORA-01125: cannot disable media recovery - file string has online backup set

1 Answers  

---

ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause

1 Answers  

---

NNL-00909: META VIOLATION responses sent: number

1 Answers  

---

ORA-19203: Error occurred in DBMS_XMLGEN processingstring

1 Answers  

---

ORA-40214: duplicate setting: string

1 Answers  

---

ORA-02054: transaction string in-doubt

1 Answers  

---

TNS-00518: Incomplete read or write

1 Answers  

---

LPX-00257: invalid children specification in element declaration

1 Answers  

---

ORA-28115: policy with check option violation

1 Answers   Wipro,

---

ORA-23324: error string, while creating deferror entry at "string" with error string

1 Answers  

---