Hi
Look in Database PL/SQL Language Reference appendix C PL/SQL Program Limits
where it defines "magnitude of a PLS_INTEGER or BINARY_INTEGER value
-2147483648..2147483647"
Best regards/Venlig hilsen
Peter Gram
Sæbyholmsvej 18 DK-2500 Valby
Mobile: (+45) 5374 7107
Email: peter.m.gram@xxxxxxxxx
<http://oaktable.net/members>
On Tue, 27 Sept 2022 at 19:11, Rich J <rich242j@xxxxxxxxx> wrote:
Howdy,
In 19.16, a dev has a quick anonymous block that fails with "ORA-1426:
numeric overflow". It appears that the FOR...LOOP has a limit of 2G-1. I
can't see where that would be documented or there's some implicit typing
going on that I'm missing. From experimentation:
DECLARE
sseq NUMBER:=2147483647;
eseq NUMBER:=2147483647;
BEGIN
FOR x IN sseq..eseq LOOP
dbms_output.put_line(TO_CHAR(x));
END LOOP;
/
This works. Bumping the end sequence up by 1 and it fails at the FOR
statement with ORA-1426 and nothing is output, so at compile time. I've
tried adding an explicit declaration of "x", changing them all to
NUMBER(12) or PLS_INTEGER, but still get the same error. I can't find any
reference to this limit at:
https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/database-limits.htm
Am I missing something (very possible) or is this an undocumented limit?
Thanks,
Rich
