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-24163: dblink is not supported in rules engine DDLs

1 Answers  

---

ORA-06817: TLI Driver: could not read the Novell network address

1 Answers  

---

DRG-50907: score threshold string outside valid range 1 to 100

1 Answers  

---

RMAN-12014: multiple records for default channel configuration for string found in catalog

1 Answers  

---

ORA-16129: unsupported dml encountered

1 Answers  

---

---

LSX-00146: element or attribute is improperly defined

1 Answers  

---

ORA-13017: unrecognized line partition shape

1 Answers  

---

SQL-02112: SELECT..INTO returns too many rows

1 Answers  

---

ORA-07244: ssfccf: create file failed, file size limit reached.

1 Answers  

---

ORA-00056: DDL lock on object 'string.string' is already held in an incompatible mode

1 Answers  

---

DRG-11709: too many terms in thesaurus

1 Answers  

---

ORA-07702: unrecognized device type in archive text

1 Answers  

---