Re: Implicit cursors and shared pool

implicit cursors are closed but not deallocated. This is one of the reasons to avoid using implicit cursors as much as possible.

Hth,

Sybrand Bakker, Oracle DBA

"Martin Trzaskalik" <martin_at_element5.de> wrote in message news:8spm3r$6il$1_at_nnrp1.deja.com...
> We have some pl/sql packages using implicit cursors to regularly
> do updates on some tables:
>
> begin
> update table set value = '123' where id = key;
> commit;
> end;
>
> Recently I found out that some of these queries appear as
> cursors after calling SYS.DBMS_SHARED_POOL.SIZES(xxx).
> Their amount of shared pool memory is increasing by time.
>
> Why is that? I guess after the procedure has been executed
> the implicit cursor should have been closed. So I do not
> expect him to allocated shared pool memory.
>
> Do I have to explicitly close these cursors?
>
> Any hint?
>
> Regards,
>
> Martin
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Fri Oct 20 2000 - 12:13:23 CDT