Answer Posted / 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
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-26028: index string.string initially in unusable state
ORA-16627: No standby databases support the overall protection mode.
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-16516: The current state is invalid for the attempted operation.
NZE-28890: Entrust Login Failed
IMG-02003: 2FF03 - incorrect color histogram feature specification
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-26094: stream format error: input column overflow
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-26079: file "string" is not part of table string.string
ORA-26029: index string.string partition string initially in unusable state