nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

OAC instances should support deferred/delayed patching on an instance-by-instan

Dhananjay Papde

Organization Name

SITA

Description

OAC instances should support deferred/delayed patching on an instance-by-instance basis. Oracle Cloud should support mechanisms or functionalities that allow customers to control themselves whether an instance qualifies for automatic patching or should be excluded from automatic patching. Also I reckon this should be valid for all Oracle PaaS services

After OAC 6.0 upgrade, we encountered issues in all environments, and Prod dashboards stopped working. So we have to need to wait for a fix from Oracle. To avoid such issues, OAC Maintenance changes on Prod and Non-Prod should not be done simultaneously, as seen in OAC 6.0 upgrade.

Use Case and Business Need

After OAC 6.0 upgrade, we encountered issues on all environments and some working dashboards stopped working. So we are awaiting for a fix from Oracle and we are told it will be resolved via OAC 6.0.x bug fix

Original Idea Number: 9d79b7c75e

Find more posts tagged with

Delivered

Reporting

Data Connectivity

Data Modelling and Datasets

Analysis and Data Visualization

Status: Delivered

Comments

Dhananjay Papde

ORadu-Oracle

very good idea, conforming to change management practice!

User763532-Oracle

Adhering to CM practice, and appeasing customers.

Gabby Rubin-Oracle

There is a path today for customers to request their test/dev environments to be patched before prod which will allow them to test the release prior to patching. If a customer identifies an issue they can also request to postpone their prod upgrade. The details of this process are outlined in the update notification, and it can be done once for all future updates.

Having said that, OAC is not a CM service and not an OMCS hosting service, for customers that would like to have complete flexibility on their update timeline we offer OAS and we are working on simplifying the deployment of OAS on IaaS. Similar to other cloud services, upgrades are inevitable - we definitely will not update an instance knowing that it will cause customer issues, but absent of bugs - upgrades will need to continue on regular basis. It is required both in order to maintain our ability to manage tens of thousands of instances, as well as the overall health and security of the fleet.

Going back the the first point, I do advise that customers that need to, will take advantage of the ability to create an upgrade schedule which accommodate their UAT/Prod needs (which is the original ask here).