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

ORA-13275: spatial index creation failure on unsupported type

1 Answers  

---

ORA-29537: class or resource cannot be created or dropped directly

1 Answers  

---

ORA-14455: attempt to create referential integrity constraint on temporary table

1 Answers  

---

ORA-02458: HASHKEYS must be specified for a HASH CLUSTER

1 Answers  

---

ORA-02703: osnpopipe: pipe creation failed

1 Answers  

---

ORA-25257: consumer must be specified with a multi-consumer queue

1 Answers  

---

RMAN-06455: point-in-time tablespace recovery requires Enterprise Edition

1 Answers  

---

ORA-24778: cannot open connections

1 Answers  

---

PLS-01474: Use of ANY is non_ANSI

1 Answers  

---

ORA-29396: cannot switch group to string

1 Answers  

---

ORA-30087: Adding two datetime values is not allowed

1 Answers   Oracle,

---

RMAN-20009: database incarnation already registered

1 Answers  

---