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

ORA-24416: Invalid session Poolname was specified.

1 Answers  

---

ORA-16228: Insufficient recovery for logical standby

1 Answers  

---

NNL-00558: set|show namesctl_trace_level : set|show the controller's tracing level

1 Answers  

---

ORA-04099: trigger 'string' is valid but not stored in compiled form

1 Answers  

---

SQL*Loader-00463: secondary data file for LOB is string

1 Answers  

---

PLS-00338: unable to resolve "string" as a column or row expression

1 Answers  

---

ORA-31506: duplicate subscription name string

1 Answers  

---

DRG-12517: cannot add stopthemes to a MULTI_STOPLIST

1 Answers  

---

AMD-00106: parent string "string" must be removed before child string "string" can be removed

1 Answers  

---

PCC-00095: Missing PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA statement

1 Answers  

---

ORA-02472: PL/SQL functions not allowed in hash expressions

1 Answers  

---

PLS-00599: SAMPLE percentage must be in the range [0.000001,100)

1 Answers  

---