ACCM | Attentional Content & Collaborate Model | Machine Learning library

The profiler you're using will run the function you pass to memory_usage multiple times as it tries to identify a memory sampling interval that will let it get enough samples to have an accurate reading. If your code runs too quickly, it will need to shrink the sample size more, so the function will get called more often.

You can see how it works in the source code of memory_profiler. Here's the important loop (with irrelevant stuff cut out):

Try this

There is absolutely nothing wrong with that stored procedure. Just be sure to put a forward slash on a separate line after each PL/SQL block that you are compiling if you are using TOAD or SQL*Plus. Forward slash is the default block terminator in TOAD and SQL*Plus.

I'm not sure if I understood correctly what exactly are you doing. If you need just fill items with data, create a before header process (in Page Designer mode, it is in Pre-rendering -> Before Header. Write your code there, it should be enough.

If you want to do it in Dynamic Action (I wouldn't recommend this way), you need to create a Dynamic Action with Event - Page Load, which will contain a True Action with properties: Action - Execute PL/SQL Code, PL/SQL Code - your code and Items to Return - LCD_NO,CURR_DEP,TOT_DEP,NBV
But make sure your items really have such names, because by default APEX creates items with names like P10_LCD_NO, where 10 (for example) is a number of the page.