A COST-EFFECTIVE METHOD FOR OPM UPGRADE VIA REIMPLEMENTATION
SUMMARY OF UPGRADE VS. RE-IMPLEMENT DECISION
The initial position of both Oracle and most GEMMS customers who wished to move into OPM on Oracle 11i was that a series of upgrade scripts presented the optimal path. The base release of Oracle 11i is sufficiently different from prior GEMMS and OPM11 versions that a series of upgrade scripts and processes were developed and offered by Oracle to the market at large. The biggest disadvantage was/is that they are very complex, and required a significant blackout period during the upgrade. First experiences with upgrading GEMMS to OPM 11i showed a blackout period of 70-90 hours.
Oracle attacked this blackout problem by first making it possible for (HP) users to upgrade to an 8.1.6 database prior to the upgrade of the applications. Subsequently, the complexity of the upgrade scripting and procedures themselves has been reduced. For many users, however, the blackout period is still a problem. There is data validation, scrubbing and reconfiguration which occurs in the middle of the process and which can affect the blackout schedule from customer to customer. The older the established instance of GEMMS, the larger this piece of the activity is likely to be.
Almost every GEMMS client looking at OPM 11i has considered re-implementation as an alternative. It permits the "raising" of a parallel 11i instance that can be patched and populated prior to cutover. It also allows purging of errors and revision of one-time-loaded configuration data from the old GEMMS instance before going forward on OPM 11i. After going live, the user can extract historic data from the old GEMMS instance at leisure and retain it in a data warehouse, then "kill" the old GEMMS instance.
Download
Download full seminar papers At
http://www.enjineer.com/forum
No comments:
Post a Comment