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

DRG-51100: invalid program argument index

1 Answers  

---

SQL*Loader-00607: partition not empty for INSERT option; table string, partition string

1 Answers  

---

ORA-24367: user handle has not been set in service handle

1 Answers  

---

ORA-14031: partitioning column may not be of type LONG or LONG RAW

1 Answers  

---

ORA-19628: invalid SCN range

1 Answers  

---

---

DRG-12012: Proxy authentication failed - retry?

1 Answers  

---

QSM-02147: default date format is sensitive to session settings

1 Answers  

---

ORA-02160: index-organized table can not contain columns of type LONG

1 Answers  

---

ORA-06133: NETTCP: file not found

1 Answers  

---

NZE-29150: DES self-test failure

1 Answers  

---

TNS-12224: TNS:no listener

1 Answers  

---

UDI-00052: incorrect Data Pump client for operation: string

1 Answers  

---