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-02066: missing or invalid DISPATCHERS text

1 Answers  

---

ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.

1 Answers  

---

ORA-00489: ARB* process terminated with error

1 Answers  

---

LPX-00401: invalid QName in the XSL file

1 Answers  

---

ORA-04081: trigger 'string' already exists

1 Answers  

---

ORA-13138: could not determine name of object string

1 Answers  

---

ORA-14059: partition "string": INITRANS value must be less than MAXTRANS value

1 Answers  

---

ORA-40272: apply rules prohibited for this model mode

1 Answers  

---

PLS-00231: function 'string' may not be used in SQL

1 Answers  

---

ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition

1 Answers  

---

TNS-12655: Password check failed

1 Answers  

---

ORA-27509: IPC error receiving a message

1 Answers  

---