Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, the AT <db_name> clause was used in a
SQL statement. For example, the offending code might look
like: EXEC SQL AT oracle3 COMMIT RELEASE END-EXEC. This
informational message is issued by the FIPS Flagger when
FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, do not use the AT <db_name> clause.

Please add more information about this Error

TNS-12630: Native service operation not supported

1 Answers  

---

ORA-27077: too many files open

1 Answers  

---

ORA-12821: invalid value for INSTANCES

1 Answers  

---

ORA-02488: Error encountered when accessing file [string] for trace conversion

1 Answers  

---

ORA-23536: the object "string"."string" is not cached at the middle tier as expected.

1 Answers  

---

ORA-09937: Chmod of ORACLE password file failed.

1 Answers  

---

LPX-00282: document cannot have both internal/external and shared DTDs

1 Answers  

---

ORA-06811: TLI Driver: could not set the IPX network number at init

1 Answers  

---

ORA-08331: Wait operation timed out

1 Answers  

---

ORA-02438: Column check constraint cannot reference other columns

1 Answers  

---

QSM-01090: no query rewrite after view merging

1 Answers  

---

ORA-02463: Duplicate HASH IS option specified

1 Answers  

---