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

ORA-02365: error seeking in file: string

1 Answers  

---

ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.

1 Answers  

---

ORA-38721: Invalid file number.

1 Answers  

---

ORA-09988: error while detaching SGA

1 Answers  

---

ORA-01977: Missing thread number

1 Answers  

---

ORA-25100: TABLESPACE option can only be used with ALTER INDEX REBUILD

1 Answers  

---

ORA-14153: only one of STORE IN or <partition-description> clause may be specified

1 Answers  

---

PCC-02380: Cannot specify a connect mode when altering a user password

1 Answers  

---

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

1 Answers  

---

ORA-22898: existing scope clause on "string" points to a table other than the one mentioned in the referential constraint

1 Answers  

---

ORA-12715: invalid character set specified

1 Answers  

---

ORA-16538: no match on requested item

1 Answers  

---