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-15127: ASM file name 'string' cannot use templates

1 Answers  

---

ORA-12483: label not in OS system accreditation range

1 Answers  

---

ORA-09987: unable to attach to SGA in READ-ONLY mode

1 Answers  

---

ORA-01618: redo thread string is not enabled - cannot mount

1 Answers  

---

ORA-01898: too many precision specifiers

1 Answers  

---

---

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

1 Answers  

---

NNF-00001: Not a TNS address

1 Answers  

---

ORA-01502: index 'string.string' or partition of such index is in unusable state

1 Answers  

---

IMG-02002: 2FF02 - incorrect average color feature specification

1 Answers  

---

ORA-14517: subpartition of index 'string.string' is in unusable state

1 Answers  

---

SQL*Loader-00275: Data is in control file but "INFILE *" has not been specified.

1 Answers  

---

PCC-02347: PL/SQL found syntax errors

1 Answers  

---