Answer / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a non-integer WHENEVER ... GOTO label
was in a Pro*Pascal program. For example, the offending code
might look like: EXEC SQL WHENEVER NOT FOUND GOTO quit; This
informational message is issued by the FIPS Flagger when
FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, use only integer WHENEVER... GOTO labels in a
Pro*Pascal program.

Please add more information about this Error

ORA-13036: Operation [string] not supported for Point Data

1 Answers  

---

ORA-21503: program terminated by fatal error

1 Answers  

---

ORA-22167: given trim size [string] must be less than or equal to [string]

1 Answers  

---

TNS-00281: Connection Manager: Forced Log output

1 Answers  

---

ORA-07213: slgcs: times error, unable to get wall clock.

1 Answers  

---

IMP-00089: Fine grain policy "string" not recreated on table/view "string"

1 Answers  

---

ORA-38711: Corrupt flashback log block header: block string

1 Answers  

---

QSM-00751: the file string could not be opened for write access

1 Answers  

---

ORA-32032: free temporary object number not available

1 Answers  

---

TNS-00556: no method specified for wallet retrieval

1 Answers  

---

ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string.

1 Answers  

---

ORA-07214: slgunm: uname error, unable to get system information.

1 Answers  

---