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-28020: IDENTIFIED GLOBALLY already specified

1 Answers  

---

RMAN-08519: channel string: scanning datafilecopy string

1 Answers  

---

ORA-19696: controlfile not found in backup set

1 Answers  

---

TNS-01409: Instance "string"

1 Answers  

---

DRG-11841: Bad Gateway

1 Answers  

---

---

ORA-02162: invalid value for MAXDATAFILES

1 Answers  

---

ORA-15047: ASM file name 'string' is not in multiple-file creation form

1 Answers  

---

ORA-15053: diskgroup "string" contains existing files

1 Answers  

---

ORA-36676: (XSDPART14) Missing dimension list for string.

1 Answers  

---

ORA-13366: invalid combination of interior exterior rings

1 Answers  

---

ORA-00130: invalid listener address 'string'

2 Answers  

---

PROC-00015: Failed to initialize the cluster registry successfully

1 Answers  

---