What is the Quarterly Updates Process?
We use quarterly updates to deliver new features and functionality for your Oracle Cloud Applications. Quarterly updates contain a smaller number of new features and functionality than on-premises upgrades did, nearly all of which are invisible to your end users until you choose to make them available. Quarterly updates also include resolutions for issues that occurred since the last update.
Quarterly Updates are deployed to our fleet of customers over a three-month period. For example, “B” Quarterly Updates will be completed in May, June and July. All customers must update to the latest version within these three months. Oracle SaaS policy allows for up to four Quarterly updates per year. For Oracle WMS/Logfire the standard will be four Quarterly updates per year and ALL updates are mandatory. Some years will have exceptions. For retail customers we understand that the D update might pose a challenge due to high season. If this is the case, please log a Service Request using My Oracle Support and Oracle will work with you on scheduling the D update.
The three Quarterly Schedules available for Oracle WMSCS/Logfire Cloud customers are:
- February-May-August-Nov
- March-June-September-Dec
- April-July-October-Jan
Customers will be assigned a Quarterly Schedule by Oracle. For customers with other Oracle Cloud products (e.g., Oracle Cloud ERP) already using a Quarterly Schedule, we will assign Fusion or OTM schedule for WMSCS/Logfire Cloud, whenever possible. Once assigned, customers will have a onetime opportunity to request a different Quarterly Schedule should their business needs dictate. All such requests will be considered on a case by case basis. Variations on the above three schedules are not possible.
The table below details how the Quarterly Updates get scheduled. Customers should expect and plan for the following updates based on their specific Quarterly Schedule:
| Quarterly Schedule | Update A | Update B | Update C | Update D |
|---|---|---|---|---|
| Feb-May-Aug | Feb | May | Aug | Nov |
| Mar-Jun-Sep | Mar | Jun | Sep | Dec |
| Apr-Jul-Oct | Apr | Jul |
Oct |
Jan |
Quarterly Update Process Details
The quarterly update schedule uses the following standard process:
- The first weekend of the month, customers (falling under that month’s cohort group) test environments would get upgraded to the monthly (M) patch bundle. (Xrelease, Mpatchbundle)
- The third weekend of the month, all customers (falling under that month’s cohort group) production environment would get upgraded to the monthly (M) patch bundle. (Xrelease, Mpatchbundle)