Ok I understand you now. I do have a lot of compiled pl/sql procedures
that create cursors. We are moving to have all sql code stored in the
database verses passing in the sql code. But we don't page at all. Is
there something I need to tune for this or a parameter to change?
EscVector wrote:
> jeffchirco_at_gmail.com wrote:
> > I don't understand the question about suing PL/SQL to process.
>
> You can pass in sql or you can have your processes compiled in packages
> procedures and functions. If your database has compiled pl/sql
> procedures that create cursors, it can effectively eat up all your
> memory if you have no programmatic limit on the cursor.
>
> psuedo code example:
> call procedure GetRecords
> create cursor as select * from 1 terabyte table;
> Work with cursor
> End procedure
>
> All available os memory will be allocated to the offending process,
> system will swap, and die. It will die on the cursor create and never
> get to the work.
Received on Thu Jan 11 2007 - 18:03:36 CST
