Re: Interesting PGA/Memory puzzle (4030 error at 32GB used) - ulimit settings?

From: Tanel Poder <>
Date: Fri, 18 May 2018 14:02:04 -0500
Message-ID: <>

Yeah, *oddc.sql* is just using *O*RA*D*EBUG *D*OC *C*OMPONENT to list all Oracle kernel components registered with the 11g+ new diagnostic infrastructure.

I haven't officially announced it yet, but I recently put all my scripts in to Github and they're formally open sourced too (Apache 2.0 license):

Also, Frits has consolidated lots of function/module names (some are known for sure, some are educated guesses) here:


On Fri, May 18, 2018 at 12:41 PM, Chris Taylor <> wrote:

> Tanel,
> I was hoping you'd take a look - that's very helpful and I did consult
> with the developer earlier and indeed there is a CLOB object used.
> I need to go find your oddc script - that looks useful :)
> Thanks,
> Chris
> On Fri, May 18, 2018 at 12:34 PM, Tanel Poder <>
> wrote:
>> Looks like you have a LOB handle leak or something, plenty of bugs around
>> temporary LOB handles etc. A single process should normally not use that
>> much memory anyway (if you're not holding some big PL/SQL collection or
>> workarea in memory).
>> SQL> _at_oddc koll
>> ORADEBUG DOC COMPONENT | grep -i koll
>> LOB LOB (koll, kola)
>> LOB_Default LOB Default (koll, kole, kokl, koxs)
>> LOB_DBLINK LOB DBLink (koll, kokl, kpolobr, kkxlr)

Received on Fri May 18 2018 - 21:02:04 CEST

Original text of this message