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-27415: repeat interval must start with the FREQ= clause

1 Answers  

---

ORA-12590: TNS:no I/O buffer

1 Answers  

---

ORA-06736: TLI Driver: server not running

1 Answers  

---

ORA-25153: Temporary Tablespace is Empty

1 Answers  

---

LSX-00003: invalid attribute "~1S" for element "~2S"

1 Answers  

---

LFI-00111: No other flags allowed in fixed length format.

1 Answers  

---

ORA-25442: too many column values for table alias: string

1 Answers  

---

ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.

1 Answers  

---

ORA-00024: logins from more than one process not allowed in single-process mode

1 Answers  

---

ORA-02151: invalid tablespace name: string

1 Answers  

---

PROT-00016: Internal Error

1 Answers  

---

ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier

1 Answers  

---