Re: Closing Cursors

The performance impact is a bit of a surprise, presumably there must be some fairly heavy table processing which results in lots of mallocing, freeing and fragmentation of memory.

First thought it to try and find some trade-offs over the frequency and size of the tables you free using this method.

Second thought - can you create some 'static' tables, populated with nulls say, and use them in some way to avoid memory manipulation.

What sort of sizes do you tables reach ?

--

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

Peter L wrote in message <38b18852.132395_at_news.freeserve.net>...
>On Mon, 14 Feb 2000 19:42:18 -0000, "Jonathan Lewis"
><jonathan_at_jlcomp.demon.co.uk> wrote:
>
>>
>>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;
Received on Mon Feb 21 2000 - 12:58:27 CST