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

TNS-00317: Failed to contact Connection Manager

1 Answers  

---

ORA-19010: Cannot insert XML fragments

1 Answers  

---

ORA-24310: length specified for null connect string

1 Answers  

---

NZE-28828: invalid identity type passed

1 Answers  

---

DRG-11852: Can't Locate Remote Host

1 Answers  

---

PCC-02397: VARCHAR declarations not permitted in #include file

1 Answers  

---

ORA-26040: Data block was loaded using the NOLOGGING option

1 Answers  

---

RMAN-01008: the bad identifier was: string

1 Answers  

---

ORA-12446: Insufficient authorization for administration of policy string

1 Answers  

---

TNS-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

1 Answers  

---

ORA-13388: invalid value for dst_spec parameter

1 Answers  

---

ORA-13416: invalid geometry parameter

1 Answers  

---