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-26078: file "string" is not part of database being loaded

1 Answers  

---

LCD-00219: nested include file [string] is too large

1 Answers  

---

NNL-00342: Log file name is currently string

1 Answers  

---

LSX-00013: element "~S" not from Schema of Schemas

1 Answers  

---

ORA-02364: error writing to file: string

1 Answers  

---

ORA-38950: Source platform string not cross platform compliant

1 Answers  

---

EXP-00007: dictionary shows no columns for string.string

1 Answers  

---

ORA-10579: Can not modify control file during test recovery

1 Answers  

---

ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.

1 Answers  

---

ORA-09201: sfcopy: error copying file

1 Answers  

---

NZE-28802: invalid mode or data source in configuration file

1 Answers  

---

TNS-02526: server proxy type does not match client type

1 Answers  

---