The upgrade team should:
Oracle recommends reviewing escalation policies and assigning Severity 1 (Sev1) issues as appropriate. These issues are typically on the critical path for your go-live and resolving them early will help you stay on schedule. You should always log Sev1 cases via My Oracle Support to document the issue fully, but the best practice is to follow-up with a call to Support to ensure efficient follow-through.
Even when you encounter noncritical issues (non-Sev1s), Oracle recommends reporting issues on the My Oracle Support site. Issues logged on the site are resolved faster than calls to the Support Center.
Treating Your Upgrade Activity as a Formal Company Project
Using an Appropriate Change Management Strategy
Building an Upgrade Team with Broad and Complementary Skills
Utilizing Peer and Oracle Resources
Deciding When to Change or Add Business Processes
Ensuring the Quality of Your Data
Taking Inventory for Your System
Understanding and Mitigating Project Risks
Calculating New Hardware Sizing
Identifying Custom Code and Scripting
Adhering to Current Tested Configurations Requirements
Implementing the Current P6 EPPM Release and Patches
Minimizing Application Data to Upgrade
Testing a Copy of the Production Database
Leveraging Existing Test Scripts and Plans
Training End Users on the New Solution
Legal Notices
Copyright © 1999, 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Friday, September 23, 2016