Re: Why is UGA size so large?

Noons <wizofoz2k_at_yahoo.com.au> wrote in message news:<42435c74$0$24549$5a62ac22_at_per-qv1-newsreader-01.iinet.net.au>...
> Marcel D?rr apparently said,on my timestamp of 25/03/2005 6:58 AM:
>
> > If so, how can I distinguish between open cursors that are just cached
> > (PL/SQL Cache or Session Cached Cursors) and Cursors that are still
> > open in the application?
>
> Good question. I don't think you can. Anyone?

I made some mor investigations.
I can get the different contributors to the UGA of my own session from x$ksmup. My findings are:
sort_area_reained_size is included in "kxs per/exe he" pl/sql global variables are included in "koh-kghu sessi" from this I was able to rule out that my large UGA sizes steem from open cursors.
In fact the problem is caused by large temporary pl/sql tables that get not deallocated by pl/sql, see my othe post on this for details.

Regards,
Marcel Received on Fri Apr 01 2005 - 02:18:16 CST