Oracle Analytics Cloud and Server Idea Lab

Home› Oracle Analytics› Oracle Analytics Idea Labs› Oracle Analytics Cloud and Server Idea Lab

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Separate Maintenance Schedule for Oracle Analytics Non Prod and Prod Environments

Needs Votes
73
Views
4
Comments
User_FWVAI
User_FWVAI Rank 1 - Community Starter
in Oracle Analytics Cloud and Server Idea Lab

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

Tagged:
4
Up
4 votes

Needs Votes · Last Updated

Comments

  • Doug Ross
    Doug Ross Rank 6 - Analytics Lead

    This is available already but not widely known. 

    Please reference support document:

    How To Submit a Service Request With Support To Request Patching Schedule Change for Oracle Analytics Cloud (Doc ID 2657866.1)

    Provide following Details :

    • What is your Identity Domain : Example idcs-xxxx
    • What is your Region : Example : Frankfurt

    NOTE: If you have multiple instances to be patched, we can patch them in one or two batches. Please provide the details accordingly below:

    Example : Provide complete URLs of your OAC instances

    Batch 1 Patching: DEV/TEST/UAT OAC URLs
    Batch 2 Patching : PROD1/PROD2 OAC URLs

    • What is your preferred patching time window? Choose a time using the below guidelines or enter N/A if you do not have a preference :

    North America customers : 9:30 PM PST (Sun-Thu) to 2:30 AM PST (Mon-Fri)

    EU customers : 9:30 AM PST (Mon-Fri) to 2:30 PM PST (Mon-Fri)

     

    • A minimum of 5 days advance notice is required to process a patch schedule change.
    • We will make every effort to honor your preferred time but this cannot be guaranteed.
    • Oracle will keep you updated of the new patching time frame once confirmed. 

     

  • Ronan Kelehan
    Ronan Kelehan Rank 3 - Community Apprentice

    Can we have updates done the same way as is now available for Oracle Integration Cloud (new this month). Schedule is done automatically based on tags?

     

    https://blogs.oracle.com/integration/choosing-your-update-window

     

     

  • Ronan Kelehan
    Ronan Kelehan Rank 3 - Community Apprentice

    Useful for every customer with test/dev instances

  • gmigotto
    gmigotto Rank 4 - Community Specialist

    I think it's already planned, but is a must-have feature for Gen2 OAC.