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-25353: branch marked for deletion

1 Answers  

---

NZE-29156: conditional RNG self-test failure

1 Answers  

---

EXP-00099: Table "string"."string" is not in a valid state, table will not be exported

1 Answers  

---

RMAN-06404: database dismounted

1 Answers  

---

PLS-00391: undefined column 'string' in UPDATE statement

1 Answers  

---

ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters.

1 Answers  

---

ORA-23382: materialized view repgroup "string"."string" is not registered at site string

1 Answers  

---

ORA-30678: too many open connections

1 Answers  

---

ORA-30348: ADD and DROP cannot both be specified

1 Answers  

---

TNS-04142: CMAN.ORA file has an invalid format.

1 Answers  

---

NPL-00307: ASN.1 sequence has already been ended on write

1 Answers  

---

ORA-16516: The current state is invalid for the attempted operation.

0 Answers  

---