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

NNL-00012: invalid "string" value "string"

1 Answers  

---

ORA-22877: invalid option specified for a HASH partition or subpartition of a LOB column

1 Answers  

---

LPX-00005: ~1s buffer overflow, maximum size is ~2u bytes

1 Answers  

---

display details of employee's who are seniour to there own manager ? ( In a Emp Table )

2 Answers  

---

CLSR-00531: Can not get primary group name

1 Answers  

---

---

ORA-02236: invalid file name

1 Answers  

---

ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring

1 Answers  

---

ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP

1 Answers  

---

PLS-00363: expression 'string' cannot be used as an assignment target

1 Answers  

---

ORA-25452: duplicate attribute value for variable: string, attribute: string

1 Answers  

---

ORA-07840: sllfop: LIB$GET_VM failure

1 Answers  

---

ORA-27194: skgfdvcmd: sbtcommand returned error

1 Answers  

---