A customer, citing a justification for the request, may seek a delay in updating a production environment. You can seek to delay the upgrade of production environments in the following scenarios:
You identified a regressive bug in the test environment. In this scenario, Oracle will fix the bug and then upgrade your environment without further delay. No customer approval is necessary for upgrading to the mainline.
You are in the critical phase of your implementation project. In this scenario, Oracle will postpone the upgrade to the date that you agreed upon when requesting the delay. If you do not make an additional upgrade delay request, Oracle automatically upgrades the environment on the date that you agreed upon when requesting the delay.
You want to skip this month's update because you do not have the time to test the monthly update. In this scenario, Oracle automatically upgrades the environment in the next monthly update cycle.
You want to skip this month or few months' update because of quarter close or year end close. In this scenario, Oracle automatically upgrades the environment on the date or monthly cycle that was agreed upon.
Generally, customers migrating from on-premises to Oracle Enterprise Performance Management Cloud use the upgrade delay process. After they are comfortable with the upgrade cadence, they upgrade to the main line and then do not request upgrade delays.
Monthly update notifications will still be sent to the Service Administrators of the environments for which upgrade has been put on hold.
Repercussions of an Update Delay
Downside of an update delay includes the following:
- An environment that has not been updated in a monthly cycle requires a longer time to upgrade to the main line.
- After the production environment is brought to the mainline, you will incur more time to test (you will, essentially, be testing features and changes from multiple monthly updates).
- Security updates and bug fixes are applied to environments only when it is upgraded to the mainline
How to Request an Upgrade Delay
To request an upgrade delay, file a service request and provide the following information:
URL of the environment for which upgrade is to be delayed.
Reason (for example, regressive bug information, critical phase of implementation project, test environment not tested, quarter or year end close) why upgrade delay is being requested.
If the upgrade delay is not because of a regressive bug, month when Oracle can merge the environment back to the mainline.
Formal request in the following format:
I, <Your name>, request Oracle to delay the upgrade of the environment <URL of the environment>