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

NNO-00081: domain "string" has no name servers

1 Answers  

---

DRG-52108: failed to delete knowledge base user extension

1 Answers  

---

PLS-00640: a pipelined function cannot be called from PL/SQL context

1 Answers  

---

ORA-16098: inaccessible standby database forced shutdown to protect primary

1 Answers  

---

ORA-01531: a database already open by the instance

1 Answers  

---

ORA-01463: cannot modify column datatype with current constraint(s)

1 Answers  

---

ORA-15196: invalid ASM block header [string:string] [string] [string] [string] [string != string]

1 Answers  

---

ORA-08102: index key not found, obj# string, file string, block string (string)

1 Answers  

---

ORA-12853: insufficient memory for PX buffers: current stringK, max needed stringK

1 Answers  

---

ORA-36668: (XSDPART06) string is not a legal RANGE partition.

1 Answers  

---

LSX-00274: invalid padding in base64-encoded binary

1 Answers  

---

ORA-12420: required procedures and functions not in policy package "string"

1 Answers  

---