Re: kolccst obj: large streams pool memory segment
- From: "Rajeev Prabhakar" <rprabha01@xxxxxxxxx>
- To: sacrophyte@xxxxxxxxx
- Date: Thu, 4 Oct 2007 10:31:28 -0400
Charles
Did you review this metalink note, it talks about a memory leak. It is
possible that you are hitting the same issue.
*Bug 5058318 - Memory leak (in "koh-kghu" heap of type "kolccst obj")* Doc
ID <https://metalink.oracle.com/help/usaeng/Search/search.html#file>: *Note:
5058318.8* Type: *PATCH* Last Revision Date: *07-SEP-2007* Status: *
PUBLISHED*
-Rajeev
On 10/4/07, Charles Schultz <sacrophyte@xxxxxxxxx> wrote:
>
> Anyone know where I can find more information about this KOLCCST object?
> And other KO objects for that matter?
>
> SQL > select * from (select * from v$sgastat where pool = 'streams pool'
> order by bytes desc) where rownum < 6;
>
> POOL NAME BYTES
> ------------ ---------------------------------------- ----------
> streams pool kolccst obj 1987055480
> streams pool kol raw 465430552
> streams pool kolcalm coll 464969704
> streams pool koicnfadt adt attr 419245184
> streams pool kol vstring 259053352
>
> Kinda curious why we are eating so much memory. This is a downstream
> database, so I expect to be using the Streams Pool. Perhaps there is a
> perfectly valid reason for this, and in that case I would like to learn
> about it.
>
> --
> Charles Schultz
Other related posts:
