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; 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-01154: database busy. Open, close, mount, and dismount not allowed now

1 Answers  

---

NNC-00423: invalid data item syntax code string

1 Answers  

---

PLS-00313: 'string' not declared in this scope

1 Answers  

---

ORA-32592: all columns in log group can not be no log columns

1 Answers  

---

TNS-01409: Instance "string"

1 Answers  

---

LSX-00200: element "~S" not empty

1 Answers  

---

ORA-02882: sou2o: Could not register SGA for protection

1 Answers  

---

DRG-11613: URL store: connection refused to host specified by string

1 Answers  

---

ORA-01865: not a valid era

1 Answers  

---

ORA-31441: table is not a change table

1 Answers  

---

ORA-32763: Turn off N-Pass Temp LOB cleanup

1 Answers  

---

PCB-00219: Invalid size specified in EXEC SQL VAR statement

1 Answers  

---