By StuRamage on Aug 31, 2009
The Oracle Utilities Software Configuration Management guidelines have a number of recommendations which should be adhered to.. not least of which is the implementation of a structured method of deploying config/reference data in a manner which allows the on-site team to guarantee the environment content (code and data) for each release, before users start using it.
In the past I have always followed these guidelines in regards to migration of code, and associated technical reference data (batch controls, Algorithm Types, Lookups, etc), but I have been less diligent in tracking all Config through the recommended migration paths, and tended to adopt a Hub-and-Spoke approach to pushing reference data out from the Master copy environment.
Unfortunately this means that the management of this data then becomes a bit of a nightmare for the Config Team, and although the Bundling subsystem developed as part of 2.2 goes some way to providing version control functionality for some reference data, it is largely restricted to the new "Cool Tools" functionality (ie, Scripts, Zones, UI Maps, etc), although this can be extended for some data types via the Business Object configuration).
As a result of this, I have recommended that some of our local installs switch over to a reference data migration path which more closely aligns with the standard cascading migration, as detailed above.