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-13023: interior element interacts with exterior element

1 Answers  

---

SQL*Loader-00411: Only a direct path load may be continued

1 Answers  

---

IMP-00043: export file character set inconsistent

1 Answers  

---

ORA-02880: smpini: Could not register PGA for protection

1 Answers  

---

ORA-00160: global transaction length string is greater than maximum (string)

1 Answers  

---

ORA-01987: client os username is too long

1 Answers  

---

ORA-12025: materialized view log on "string"."string" already has primary keys

1 Answers  

---

ORA-24755: OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported

1 Answers  

---

ORA-12675: External user name not available yet

1 Answers  

---

ORA-02771: Illegal request time out value

1 Answers  

---

QSM-02054: DISTINCT clause in select list in mv

1 Answers  

---

ORA-34286: (MXDCL53) workspace object cannot be used in this context because it is a string.

1 Answers  

---