Mandatory or Optional | Mandatory for Fast Lane Customers Optional for Cutover / Production Lane Customers |
Delivery Schedule | General Availability releases are delivered three times per year. Please refer to the Oracle Utilities Release Calendar for details. |
Environment Update Plan | During implementation / Customers on fast lane, General Availability releases are scheduled promptly at General Availability, first to non-production environments, then to production. As go-live approaches, you can stay on your current General Availability release to stabilize for final acceptance as long as you are on the fifth or sixth maintenance pack (see Maintenance Packs for more information about maintenance packs). Once in Production after go-live, we recommend scheduling uptake of the next General Availability release for testing between the fifth and sixth maintenance packs. This will give you time to perform quick regression before uptake to production (see Maintenance Packs for more information about maintenance packs). Non-production early adopters (remaining non-production environments): First Maintenance window (typically first Saturday) of the month. Production environment and late adopters: Second Maintenance window (typically third Saturday) of the month or next maintenance window. |
Planned Outage Times | Outage times are according to the Planned Maintenance Times section. |
Readiness Material and Documentation | You will receive advance notice of Readiness material, which describe the new features/functions in upcoming releases. This material is published on the Oracle Cloud Readiness site at least 30 days prior to update availability. This Readiness material along with the documentation will help you prepare for the features/functions introduced with each new release. |
Mandatory or Optional | Mandatory while in Fast Lane. Optional to temporarily freeze on a maintenance pack for go-live (up to two months), followed by mandatory 'catch up'. |
Delivery Schedule | Maintenance Packs are prepared for the first weekend of each calendar month (with rare exceptions for holidays). |
Environment Update Plan | Non-production early adopter environments: First Maintenance window (typically first Saturday) of the month or subsequent maintenance windows. Production environment and late adopters: Second maintenance window (typically third Saturday) of the month or subsequent maintenance windows. |
Planned Outage Times | Outage times are according to the Planned Maintenance Times section. |
Readiness Material and Documentation | Documentation for the included fixes can be found in My Oracle Support. (Doc ID 2616460.1). |
Mandatory or Optional | Mandatory |
Delivery Schedule | Platform updates are released monthly. Please refer to Environment Update Plan below for details concerning when platform updates are rolled out for different types of environments. Note that platform updates are applied to all environments regardless of whether you are accepting application patches or fixes to your environment. |
Environment Update Plan | All Non-production environments: First weekend of the calendar month. Production environments: Third weekend of the calendar month (may adjust in certain months due to holidays). |
Planned Outage Times | Outage times are according to the Planned Maintenance Times section. |
Readiness Material and Documentation | N/A |
Category | Delivery Schedule | Environment Update Plan |
Critical | Zero day | As soon as available |
High Priority | Monthly | During Early Adopter week (First Saturday of the month) for all non-staging environments and Late Adopter week (Third Saturday of the month) for Production environments |
Less Priority | With each General Availability release | As part of new release updates in Early Adopter environments |
Mandatory or Optional | Functional fixes are Optional. Exception: Oracle declares a patch is critical and mandatory. |
Delivery Schedule | Hot fix updates are delivered after approval, coding and testing. |
Environment Update Plan | For all environments, the next available hot fix window after agreed upon with Customer Success Manager (CSM). Note: Hot fixes will always be applied to non-prod environment first and after validation., applied in the Production environment. |
Planned Outage Times | Outage times are either as outlined in the Planned Maintenance Times section or as negotiated depending on the criticality. |
Readiness Material and Documentation | Documentation for the included fixes can be found in My Oracle Support (Doc ID 2616460.1). |
Mandatory or Optional | Mandatory |
Delivery Schedule | Quarterly or as needed. Cloud Operations will communicate the specific dates for each quarter prior to patching. |
Planned Outage Times | Downtime is not planned for infrastructure patching. |
Readiness Material and Documentation | N/A |