Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a nonconforming keyword such as
NOTFOUND, STOP, RAISE, or DO was used in the WHENEVER
statement. (Note that NOT FOUND is ANSI-compliant.) For
example, the offending code might look like: EXEC SQL
WHENEVER SQLERROR STOP 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 nonconforming keyword.

Please add more information about this Error

ORA-01235: END BACKUP failed for string file(s) and succeeded for string

1 Answers  

---

LSX-00163: duplicated content specification in "~S"

1 Answers  

---

PLS-00214: BEGIN...END block nesting is too deep

1 Answers  

---

LPX-00285: invalid Unicode surrogate ~X ~X

1 Answers  

---

ORA-26683: invalid value for value_type

1 Answers  

---

SQL*Loader-00279: Only APPEND mode allowed when parallel load specified.

1 Answers  

---

ORA-00254: error in archive control string 'string'

1 Answers  

---

ORA-01613: instance string (thread string) only has string logs - at least 2 logs required to enable.

1 Answers  

---

ORA-31220: DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location.

1 Answers  

---

ORA-10574: Test recovery did not corrupt any data block

1 Answers  

---

LRM-00103: 'string' contains an illegal integer radix for 'string'

1 Answers  

---

ORA-10635: Invalid segment or tablespace type

1 Answers  

---