Enterprise Performance Management (EPM) Cloud Release Management
Thank you to Vinay Gupta, Rohini Potukuchi and Mathew Abraham for the presentation on this topic. You can also watch a recording of the webcast.
The presentation covers the Cloud EPM release change management processes. It will explain monthly updates, weekly patches, one-off patches, and emergency patches. It will also explain how Oracle addresses regression bugs to ensure that they don’t make their way to the production environments. The session will explain different types of requests customers can make related to release management. Oracle has now introduced the functionality for customers to be able to skip a monthly update. This session provides details of that functionality and how it can be used. It also covers the Operations Guide, and why you want to continue to utilize this valuable resources as it is continually updated with new and important information.
Oracle and Customer Responsibility
How does Oracle deliver software updates?
- Monthly Update:
- Contains a set of features and bug fixes for all business processes
- Applied to test environments on first Friday and to prod environments on third Friday of the month
- Weekly Patch:
- Includes fixes mainly for regression bugs found in test environments
- Applied to test environments on second Friday of the month
- One-Off Patch:
- Contains fixes for regression bugs, customer blocking bugs, or new features
- Applied to specific test environments on request
- After testing and approval by customer, applied to prod environments
- Emergency Patch:
- Contains one emergency bug fix
- Can be applied to test, production, or both as required
How does Oracle resolve regression bugs in test environments?
- Weekly patch on test environments
- Emergency patch on test environments
- Delay the update of prod environments of all impacted customers to allow time to test the bug fix in test environments
- Cancel the monthly update of production environments
How does Oracle resolve regression or blocking bugs in prod environments?
- One-off patch on test environments followed by prod environments after customer’s testing and approval
- Emergency patch on test environments followed by prod environments after 3 days
- Emergency patch on test and prod environments simultaneously
- Reverting the monthly update
How does Oracle send notifications for the monthly updates?
Notification E-mail is sent to all Service Administrators on last Friday of the month (one week before test environments are updated). The email includes:
- Exact dates and times when the test and prod environments will be updated
- Link to Readiness document which provides new features included in the monthly update
How can you control the updates?
- Request upgrade delay
- Request one-off patch
- Request rollback
- Request merge back
- Request prod environment to be updated before third Friday
Why would you request upgrade delay?
- You identified a regression in the test environment and there is no fix available from Oracle
- You are in the critical phase of your implementation project
- You do not have the time to test the monthly update
- You are approaching quarter close or year end close
Are there repercussions of upgrade delay?
- An environment that has not been updated in a monthly cycle requires a longer time to upgrade to the main code line
- After the prod environment is brought to the main code line, you will need to test features and changes from multiple monthly updates
- Security updates and bug fixes are applied to environments only when they are upgraded to the main code line
How can you request upgrade delay?
- Delay for 1 or 2 consecutive monthly updates -> Self-service via EPM Automate skipUpdate command
- Delay for more than 2 consecutive monthly updates -> Create a service request via Support
EPM Automate skipUpdate Command
When will the environment be merged back after upgrade delay?
- If you have issued EPM Automate skipUpdate add commands, the environment will be merged when either you issue EPM Automate skipUpdate remove command OR during the next month after the last skipped monthly update.
- If you have created a Service Request, the environment will be merged during the next month after the monthly updates that you requested to be skipped.
Why would you request a one-off patch?
- Oracle creates a fix for an issue you reported, and you want it to be applied to your test environment before it is included in the main code line.
- Oracle informs you that a fix for an issue you reported is already available as a one-off patch, and you want it to be applied to your test environment.
- After testing the one-off patch in your test environment, you want it to be applied to your prod environment or additional test environments.
When will the environment be merged back after one-off patch?
- An environment on a one-off patch is merged back to the main code line without any customer approval
- The merge back occurs in the monthly cycle in which the issue is fixed in the main code line
Rollback, Merge Back, Prod Environment Update Before Third Friday
- Rollback - A fix for a critical issue in an updated prod environment is not immediately available.
- Merge Back - You requested upgrade delay through a Service Request, but you want to merge the environment to the main code line before your originally request.
- Prod Environment Update Before Third Friday - You want a feature or bug fix which you have already tested on test environment, to be applied to prod environment before third Friday of the month.
- Part of Oracle’s “shift-left” strategy
- Resolve your issues, satisfy your requests, and answer your questions more efficiently
- Help you self-diagnose issues and provide all information to Oracle if you cannot resolve an issue yourself
- Help you provide all information needed by Oracle for various requests
- Provide you with the resources available to get the answers to your questions
- Explain release management process
How can you use the Cloud EPM Operations Guide?