Organization Name
Angel Trains Limited
Description
- maintain Production and Non Production Oracle Analytics environments separately
- enable customers to schedule maintenance within a timeframe specified by Oracle
Use Case and Business Need
The practice of updating Production and Non Production environments at the same time introduces unnecessary risk. It denies customers the opportunity to test the new software before the changes are introduced to Production.
It is an industry standard, to whenever possible, test changes before they are promoted to Production.
More details
We have experienced an incident where a vital report was impacted adversely by maintenance.
We need the opportunity to have our non Production environment updated first. We would then test the most important functionality and then Production would be updated.
This is something Oracle already does with EPBCS, where there is a regular monthly schedule. Would it be possible to offer this with OAC?
Original Idea Number: d8eb1d8d20