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-11004: duplicate or conflicting value for string

1 Answers  

---

ORA-30200: Wrong NLS item was passed into OCINlsGetInfo()

1 Answers  

---

TNS-01415: Listening Endpoints Summary...

1 Answers  

---

ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.

1 Answers  

---

PLS-00513: PL/SQL function called from SQL must return value of legal SQL type

1 Answers  

---

QSM-02022: aggregate selections

1 Answers  

---

ORA-19619: cannot call restoreValidate after files have been named

1 Answers  

---

ORA-38767: flashback retention target parameter mismatch

1 Answers  

---

ORA-30018: Create Rollback Segment failed, USN string is out of range

1 Answers  

---

ORA-19330: Type 'string'.'string' not installed. Please install the type before using the CREATE_DBURI operator

1 Answers  

---

ORA-31105: User does not own lock "string"

1 Answers  

---

ORA-30462: unsupported operator: string

1 Answers  

---