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; 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-02772: Invalid maximum server idle time

1 Answers  

---

RMAN-08086: replaced script string

1 Answers  

---

ORA-29914: ODCIGETINTERFACES routine does not return required stream version

1 Answers  

---

ORA-24434: OCIStmtRelease called before OCIStmtPrepare2.

1 Answers  

---

DRG-12513: valid stop classes are: string

1 Answers  

---

ORA-32142: maximum number of iterations exceeded

1 Answers  

---

NNL-00263: Request forwarding is now enabled

1 Answers  

---

ORA-23317: a communication failure has occurred

1 Answers  

---

TNS-12544: TNS:contexts have different wait/test functions

1 Answers  

---

ORA-14011: names assigned to resulting partitions must be distinct

1 Answers  

---

ORA-22287: invalid or modified directory occurred during string operation

1 Answers  

---

ORA-02794: Client unable to get key for shared memory

1 Answers  

---