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

DRG-51200: open keymap failed for index id = string

1 Answers  

---

ORA-00231: snapshot controlfile has not been named

1 Answers  

---

ORA-22059: buffer size [string] is too small - [string] is needed

1 Answers  

---

ORA-21707: pin duration is longer than allocation duration

1 Answers  

---

ORA-01866: the datetime class is invalid

3 Answers  

---

PLS-00510: Float cannot have scale

1 Answers  

---

ORA-02477: can not perform parallel direct load on object string

1 Answers  

---

RMAN-08517: backup piece handle=string recid=string stamp=string

1 Answers  

---

ORA-07534: scginq: $getlki unexpected return on lockid string

1 Answers  

---

RMAN-08535: channel string: looking for autobackup on day: string

1 Answers  

---

ORA-16804: One or more configuration properties in metadata have invalid values.

1 Answers  

---

KUP-04032: internal error string while parsing field string:

1 Answers  

---