Skip to Main Content
Forums

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

deploying pl/sql-package to a 7x24h producition environment

mbispingMay 2 2008 — edited May 2 2008
Hello,
in our Oracle-database (9.2.0) we are using self-written plsql-packages with dependencies to each other (for example: package pkg_a calls function pkg_b.fct_b()...).

If we install a newer version of the packages, the application fails with an error "...package has been discarded...".

As our application has to work 24 hours 7 days a week how can one avoid this error?

I know about compiling the package-body only but what if I have to add new functions/procedures to the specification?
In this case I have to compile whole the specification and the body and the package state will be changed.


Tank you for your answers.

Regards
Marc Bisping

Comments

599169
First compile package b (spec and body) then compile package a (spec and body) that should be it.

Regards
635300
Hi,

You can query the view USER_DEPENDENCIES for all the dependent objects on this package.
http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/statviews_2513.htm#sthref2587

And after compiling package you can compile all of them. I guess you need to do it iteratively.
William Robertson
It's a fact of life if you have packages with state. At one 24x7 site I worked, every deployment was classified as either Hot or Cold, and developers would be careful to minimise cold deployments (those requiring expensive downtime) by avoiding package-level variables wherever possible.
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 30 2008
Added on May 2 2008
3 comments
464 views