Re: Stored Procedure Distribution

I don't think there is a difinitive answer to this. It depends on the processes that are already in place at your site. Here are two ways I have done it in two different shops. 1. Check out required packages/procedures. Apply. Run the built in procedure to recompile the whole schema(due to dependencies).

2. Have your packages/procedures, etc... check in. Have a series of database upgrade scripts. Starting with 1.... infinity. Apply them to the different databases. You need to track what version has been applied to each database. We have a k-shell script that stores this information in a table and we have an HTML screen that queries the table that we check. We have database upgrades categorized by releases. Different names for new development and for maintenance releases.

You could use export/import also.

When you dig into the depths of this it's far more complex than it appears on the surface. I have found change management to rather difficult in large shops. Takes alot of time and effort to keep databases at a proper state. If you do anything you need to have a defined process in place that is well thought out. You will probably have to make changes to it as you go. I have found that these kinds of tedious things can really cost alot of time and effort if you are not very careful.

--
http://www.freelists.org/webpage/oracle-l