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-02494: invalid or missing maximum file size in MAXSIZE clause

1 Answers  

---

ORA-13703: The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.

1 Answers  

---

ORA-07757: slemcc: invalid handle

1 Answers  

---

EXP-00074: rounding VOLSIZE down, new value is string

1 Answers  

---

ORA-24770: cannot forget a prepared transaction

1 Answers  

---

---

ORA-23515: materialized views and/or their indices exist in the tablespace

1 Answers  

---

ORA-19672: media management software returned invalid file status

1 Answers  

---

RMAN-06559: MAXSIZE must be larger than 1 kb

1 Answers  

---

DRG-12217: tags cannot be more than 64 bytes

1 Answers  

---

AMD-00156: formula "string" to modify does not exist in Workspace "string"

1 Answers  

---

ORA-38448: Indexing predicates with "string" operator is not supported.

1 Answers  

---

ORA-14116: partition bound of partition "string" is too long

1 Answers  

---