Re: Closing Cursors

You may have a memory allocation/release problem with your PL/SQL tables.

I always (when I remember) declare two of every type of table:

declare

    ......
    table_to_work_with my_table_type;     empty_table my_table_type;     .....
begin

    .....

• do the work with the real table
• make sure the memory is freed

    table_to_work_with := empty_table;

end;

This shouldn't be your problem, but there are more bugs in heaven and earth, Horatio ...

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Peter L wrote in message <38a48a9a.14362301_at_news.freeserve.net>...
>On Fri, 11 Feb 2000 14:43:50 -0500, K Stahl

>We have a number of jobs we are running on an 8i database. Basically
>they are PL/SQL procedures that open a cursor, on account records, and
>loop through each record. For each account record they open another
>cursor, to retrieve all the transaction details for the account, then
>loop through these transaction records to load a PL/SQL table. An
>interest calculation is then performed using the PL/SQL table.
>
Received on Mon Feb 14 2000 - 13:42:18 CST