Re: kolccst obj: large streams pool memory segment

Any workaround? I am curious if turning off the evil ASMM will bypass the issue or not. Surely we can set hard memory limits, but does that have other ramifications for this Streams-specific bug?

On 10/4/07, Rajeev Prabhakar <rprabha01_at_gmail.com> wrote:
>
> Charles
>
> From what I could find, it looks like the "kolccst obj" are used to
> maintain the streams heap collection.
>
> Rajeev
>

-- 
Charles Schultz

--
http://www.freelists.org/webpage/oracle-l