Re: Question: Package dependency and validation

In article <7piie9$vn4$1_at_nnrp1.deja.com>,   EnderW <ender29_at_my-deja.com> wrote:
> Hi,
> I have a small question. Suppose you have got two packages pkg1 and
> pkg2 and func1 and func2 as function respectively. Also assume that
> pkg1 body and specification is valid whereas only pkg2 specification
is
> valid. Also func1 calls pkg2.func2 in the package. If I call
> pkg1.func1, what happens to the pkg1 body validity ? Does it stay
valid
> or not ? Also is there any change on that depending on the version of
> Oracle you have been using. Thanks in Adv.
>
> Ender
>

When someone calls any procedure or function in pkg2 in your example Oracle will automatically attempt to recompile the package. I am thinking because only the body is invalid in your example that you will not need to worry about cascading invalidations for other packages that contain calls to pkg2. You can issue the 'alter package xxx compile body;' manually and this would be true as I have done this several times. Prior to ver 7.3 I have had recompiles fail due to shared pool fragmentation so we limit recompiles of our larger packages to maintenance windows. This means we do not allow alter's on tables that are referenced in large packages in production.

If the spec goes invalid then you get cascading invalidations on recompile. Applications running that use the affected packages get an 'package state changed' message that has a tendency to upset our users.

Ques: Is Ender your real name taken from Ender Wiggin in Orson Scott Card's book 'Enders Game'?
--
Mark D. Powell -- The only advice that counts is the advice that  you follow so follow your own advice --

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Fri Aug 20 1999 - 10:46:52 CDT