PLS-00438: value in LIMIT clause: 'string' use is invalid
- 1 Answers
- 3095 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: The evaluation value in the LIMIT clause of a bulk
fetch was found in an inappropriate context. For example,
the following statement is illegal because the LIMIT clause
in a bulk fetch expects a numeric value. FETCH c1 BULK
COLLECT INTO var_tab LIMIT '22333'; -- illegal
Action: Change the expression of the LIMIT clause so that
the evaluation result is compatible to a numeric value.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
NZE-28890: Entrust Login Failed
ORA-16626: failed to enable specified object
ORA-26027: unique index string.string partition string initially in unusable state
RMAN-05017: no copy of datafile number found to recover
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
NZE-28868: Peer certificate chain check failed.
IMP-00064: Definition of LOB was truncated by export
ORA-26084: direct path context already finished
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?
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26095: unprocessed stream data exists
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-26094: stream format error: input column overflow
IMP-00070: Lob definitions in dump file are inconsistent with database.
