Re: stored package size limitation?

>AngeloJS wrote:
>
>I've written a procedure (not a package) which has a code size of 97078.
>I didn't know there was supposed to be a limit, but maybe I can try to
>get it to do just a few more things so that I can claim to have broken
>the limit.
 

>According to sys.dba_object_size, the source size is 82451 and the parsed
>size is 114838.
 

>The only problem I have come across is that it sometimes fails to compile
>- I get a memory allocation error. Fortunately, I have DBA access and can
>issue a 'Alter system flush shared_pool' command, after which it compiles
>successfully.
 

>Brent Smith

Apologies if you have header all this before.

I believe 100K is the maximum reccomend package size for 7.1.6 (and 7.1.4). ORACLE say that you can go to about 200K in 7.3.

With a package size of 100K you may hit serious memory allocation problems when trying to execute the package in a production environment when it is in competition with other packages for shared memory and you may have to think about pinning the package.

You may also find you need a massive shared pool.

We originally hit this problem in 7.0.16 and it caused SERIOUS problems. Now we keep out package sizes smaller.

For the system we are working on just now we try to keep packages below 100K which is half the max reccomended size for 7.3 on which we will probably be implementing. For 7.1.4 a max package size of 50K may be better.

It is highly unlikely that any opinions expressed match those of Logica "It is better to travel hopefully, than to arrive"