Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, an alphanumeric WHENEVER ... GOTO label
was not prefixed with a colon. For example the offending
code might look like: EXEC SSQL WHENEVER NOT FOUND GOTO
no_more; This informational message is issued by the FIPS
Flagger when FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, prefix alphanumeric (but not numeric) WHENEVER
... GOTO labels with a colon.

Please add more information about this Error

PLS-00325: non-integral numeric literal string is inappropriate in this context

1 Answers  

---

ORA-38482: no elementary attributes defined in the attribute set

1 Answers  

---

ORA-32590: log group specification not allowed here

1 Answers  

---

ORA-15064: communication failure with ASM instance

1 Answers  

---

IMG-02005: 2FF05 - incorrect color specification

1 Answers  

---

ORA-27061: waiting for async I/Os failed

2 Answers  

---

ORA-06442: ssvwatev: Failed with unexpected error number.

1 Answers  

---

ORA-25238: too many recipients specified for message destination string

1 Answers  

---

ORA-29518: name string resolved to an object in schema string that is not a Java class

1 Answers  

---

ORA-28110: policy function or package string.string has error

1 Answers  

---

ORA-32814: propagation schedule string does not exist

1 Answers  

---

ORA-02166: ARCHIVELOG and NOARCHIVELOG specified

1 Answers  

---