A customer, citing a justification for the request, may seek a delay in updating an environment for a maximum of two upcoming monthly update cycles. You must specify an upgrade delay for each monthly cycle. 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 main code line.
- 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 the update for this month or several months because of quarter close or year end close. In this scenario, Oracle automatically upgrades the environment on the date or monthly cycle that is 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.
Weekly and emergency patches, if any, for the current month will continue to be applied to the environment. No updates will be made for the months for which the upgrade delay is requested.
Monthly update notifications will still be sent to the Service Administrators of the environments for which an upgrade has been put on hold.
Repercussions of an Update Delay
The negative impacts of an update delay include 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 main code line, you will incur more time to test (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 to Specify an Upgrade Delay
Setting an upgrade delay is a self-service operation that is performed using the skipUpdate EPM Automate command.
Using this command, you can skip one or two of the upcoming monthly updates. For example, if the environment is on the 20.12 monthly update, you can skip the 21.01 and 21.02 updates. In this case, you need to set two upgrade delays, one for the 21.01 monthly update and another for the 21.02 monthly update. Your environment will be updated to the main code line in the 21.03 monthly update cycle. You run the skipUpdate command as follows to skip the updates in this example scenario:
epmautomate skipupdate add version=21.01 comment="Example comment" epmautomate skipupdate add version=21.02 comment="Example comment"
If you need to request an upgrade delay for more than two monthly updates:
Create a Provide Feedback submission from the environment for which the upgrade is to be delayed. See Creating a Provide Feedback Submission.
- Create a technical service request that identifies the Provide Feedback reference number. See Submitting a Technical Service Request. The service request must contain the following additional information:
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, the date or month when Oracle can merge the environment back to the main code line.
A formal request in the following format:
I, <Your name>, request Oracle to delay the upgrade of the environment <URL of the environment>.