Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!news-out.cwix.com!newsfeed.cwix.com!newsfeed.icl.net!newsfeed.fjserv.net!opentransit.net!darth-vader.mobilixnet.dk!10.0.0.1.MISMATCH!newsreader!not-for-mail
From: kennethkoenraadt@no-spam.hotmail.com
Newsgroups: comp.databases.oracle.server
Subject: Re: PL/SQL:   -- pkg runtime Size Limitations?
Date: Thu, 10 Oct 2002 19:00:56 GMT
Organization: Orange A/S
Lines: 61
Message-ID: <3da5cd6b.4654532@news.mobilixnet.dk>
References: <2e2fc08e.0210101032.75d082cf@posting.google.com>
NNTP-Posting-Host: ras-10-123.mobilixnet.dk
X-Trace: jarjarbinks.mobilixnet.dk 1034276489 99179 212.97.240.123 (10 Oct 2002 19:01:29 GMT)
X-Complaints-To: usenet@jarjarbinks.mobilixnet.dk
NNTP-Posting-Date: Thu, 10 Oct 2002 19:01:29 +0000 (UTC)
X-Newsreader: Forte Free Agent 1.21/32.243
Xref: newsfeed1.easynews.com comp.databases.oracle.server:163767
X-Received-Date: Thu, 10 Oct 2002 12:00:54 MST (news.easynews.com)

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




On 10 Oct 2002 11:32:38 -0700, raghav_vinjamuri@hotmail.com (Raghav
Vinjamuri) wrote:

>Hi,
>   Is there a limit on the max size a PLSQL pkg can
>   takeup at runtime on the server?
>  
>   The issue in essence, is that - we have a 3000 
>   line pkg, that works for 299,999 cases out of 
>   300,000 cases. 
>
>   But, for that 1 case in 300,000,   the 
>   processing breaks down.  
>
>   -  There are no PLSQL exceptions raised.  
>   -  We get a ORA-3113 - "end of file on communication
>      channel" error in the front end.
>   -  Sometimes the db crashes. 
>
>   There is nothing different in terms of data
>   volumes or elements being processed.  
>
>   However, given the reproducibility of this error,
>   it lead us into thinking that there are some 
>   implicit size restrictions on PLSQL packages.
>
>   We have experimented on breaking the package into
>   smaller packages, and, per expectations - we do have
>   a version that works.  It works SOLID. 
>
>   But, except for this one version that works, 
>   there are 4 other versions, similarly "downsized",
>   that do NOT work.
>
>   How do we get a clue into breaking this impasse?
>
>   Any pointers/suggestions/comments are gratefully accepted,
>Thanks,
>Sincerely,
>-Raghav Vinjamuri
>
>PS Do let me know if there is a different forum
>   where this message should be addressed to. Thanks.