Hi Paul,
I agree completely with you and feel your pain.
I have a workaround though, if the changes made to your package does not
affect the specification(i.e no new parameters, no new functions/procedures)
really, for changes only to the package body,
You can do a ALTER PACKAGE package_name
On Thu, Jun 28, 2001 at 10:56:23AM -0800, Troiano, Paul (CAP, GEFA) wrote:
We have one package A that refers to package B. If package B's body and
specification are both recompiled by user 1, package A is correctly marked
as invalid. Another user, user 2, then attempts to execute package A
Paul,
From what I remember, if a package has been marked invalid and a user
tries to execute it, it DOES get re-compiled at that time, but does not get
executed. So the FIRST call to an invalid Package changes it's state to
valid. The Second call will actually execute the package.
The only
We have one package A that refers to package B. If package B's body and
specification are both recompiled by user 1, package A is correctly marked
as invalid. Another user, user 2, then attempts to execute package A and
gets the following error stack:
-- ORA-04068: existing state of packages
Does the owner of the package have a private database link that is utilized
by the package? The only person that can compile such a package it the
owner.
--Michael
-Original Message-
Sent: Thursday, June 28, 2001 2:56 PM
To: Multiple recipients of list ORACLE-L
We have one package A
Title: RE: Invalid packages not being recompiled by Oracle
HI Paul,
By chance can you use dbms_utility.compile_Schema after recompiling? Are you using it already? I know it doesn't answer your quesiton but this package is suppossed to follow the dependencies, no matter how odd
Title: RE: Invalid packages not being recompiled by Oracle
Paul,
Lisa
has the correct answer - you must recompile all dependent items.
This
behavior has been standard since the beginning of PL/SQL.
Actually, if your application could be changed to
capture the error, and just call
Mercadante Oracle Certified Professional
-Original Message-From: Koivu, Lisa
[mailto:[EMAIL PROTECTED]]Sent: Thursday, June 28, 2001
3:20 PMTo: Multiple recipients of list ORACLE-LSubject:
RE: Invalid packages not being recompiled by Oracle
HI Paul,
By chance can you use
You may run a script in cron to check invalids and recompile them. It may
run once or twice in a day...This problem pertains to custom code...
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Date: Thu, 28 Jun 2001 11:50:27 -0800
Are you
-From: JOE TESTA
[mailto:[EMAIL PROTECTED]]Sent: Thursday, June 28, 2001 4:03
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
Invalid packages not being recompiled by Oracle
later versions of oracle
$ORACLE_HOME/rdbms/admin/utlrp.sql
joe
[EMAIL PROTECTED] 06/28/01
Thanks Lisa and others,
The dbms_utility.compile_schema will work. It is a bit annoying though as
this involves six schemas and hundreds of packages to be recompiled.
Fortunatly I do keep control and there are no circular dependencies in the
packages. I am sending out an order of dependency
I have been experiencing some packages that cannot be automatically handled by Oracle
when they become invalidated. Here's the scenario: We have package1 that calls
package2 which, in turn, calls package3. Under normal circumstances, if package3's
specification gets recompiled,
package1(?)
Oracle Support never replied satisfactorly on this issue. What I have seen
it is a result of some corruption at dictionery level and as a last
resort they recommend to run catalog.ora file to rebuild dictionery and
compile all resultant invalid objects and then they will compile without
any
Title: RE: INVALID Packages
Hi Paul,
If the person logs out logs back in, is the problem solved? Or if they try to execute a second time, does the problem go away?
Lisa Rutland Koivu
Oracle Database Administrator
[EMAIL PROTECTED]
NeoMedia
2201 Second St., Suite 600
Fort Myers, FL
I think the problem does go away if they try again. However, the users panic when they
see an error message.
I just got finished re-writing a section of distributed transaction code that was
written so poorly Aargh! You'd think the developers could understand
transactions but then
15 matches
Mail list logo