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 :password; 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

PROC-00006: User does not have permission to perform a cluster registry operation on this key.

1 Answers  

---

DRG-11856: FTP Server Doesn't Reply

1 Answers  

---

TNS-12645: Parameter does not exist.

1 Answers  

---

ORA-30196: reserved for future use

1 Answers  

---

QSM-00505: syntax error

1 Answers  

---

ORA-01620: no public threads are available for mounting

1 Answers  

---

SQL*Loader-00521: lfilini failed for file (string)

1 Answers  

---

SQL*Loader-00500: Unable to open file (string)

1 Answers  

---

ORA-01278: error creating file 'string'

1 Answers  

---

ORA-12713: Character data loss in NCHAR/CHAR conversion

1 Answers  

---

ORA-04093: references to columns of type LONG are not allowed in triggers

1 Answers  

---

DRG-11828: Conflict

1 Answers  

---