Re: PL/SQL: -- pkg runtime Size Limitations?

kennethkoenraadt_at_no-spam.hotmail.com wrote in message news:<3da5cd6b.4654532_at_news.mobilixnet.dk>...
> Hi Raghav,
>
> I don't see anything suggesting that your package is causing the
> problems, especially since the db crashes. What makes you so sure that
> the pacage is the sinner?
>
> What does the alert log say when you get ORA-3113 ? And when the db
> crashes ?
>
> Platform, version ?
>
>
> - Kenneth Koenraadt
>

Hi Kenneth,

   Thanks for your reply.

   I'd want to agree that the 3000 line package    is fine.

   These are our observations:

1. 299,999 cases of 300,000 cases works correctly.
2. Only 1 case (that too when run standalone) causes ORA-3113 exceptions. We get ORA-7445 errors with a SEGV error. e.g. ORA-07445: exception encountered: core dump [kocgpn2()+2660] [SIGSEGV] [Address not mapped to object] [0xFFFFFFF0] [] []
3. When this 1 case is processed amongst a batch of cases (-- not in the first place of the batch), then that goes thru fine.

   Based on the above observations:

1. Obviously, the data is fine - as the processing could not have gone thru - when this case is included in a batch of cases.
2. The package is also fine - as everything works when in the batch mode.

   And, considering that the problem is being    seen - on account of the "application", there is    something about the data - that is causing the    schizophrenic tendencies to surface :)    And, we've been thru the data repeatedly, but .. :)    

   Therefore, the thinking is that there is some    memory limit being hit - something to do with    memory init/utilization in PLSQL pkg variables/collections.

   On a related note, is there any way to monitor    runtime PLSQL memory consumption for pkg variables    and collections?

Thanks again,
-Raghav Received on Thu Oct 10 2002 - 18:54:54 CDT