docs.oracle.com Open in urlscan Pro
23.45.106.57  Public Scan

Form analysis
1 forms found in the DOM

https://docs.oracle.com/search/

<form action="https://docs.oracle.com/search/" class="uk-search uk-search-default vl-search uk-width-1-1">
  <div id="vl-header-search-label" class="vl-screen-reader-only">Search</div><input aria-labelledby="vl-header-search-label" class="vl-search-input uk-input uk-search-input uk-form-width-small uk-width-1-1 vl-search-input-search-chip-enabled"
    type="text" placeholder="Search" name="q"><input type="hidden" name="lang" value="en">
  <div class="vl-header-search-chip"><input type="hidden" name="product" value="en/cloud/oracle-cloud-infrastructure">
    <div class="uk-inline" aria-expanded="false"><svg class="vl-header-search-chip-book-icon" width="14px" height="14px" viewBox="0 0 14 14" version="1.1" xmlns="http://www.w3.org/2000/svg">
        <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
          <g transform="translate(-1.000000, -1.000000)" fill="#FFFFFF">
            <g>
              <path
                d="M12.5647514,1.33333333 L14.7869736,14.6666667 L10.1019153,14.6666667 L9.33333333,10.0583333 L9.33333333,14.6666667 L1.33333333,14.6666667 L1.33333333,1.33333333 L12.5647514,1.33333333 Z M4.66633333,11.9993333 L2.66633333,11.9993333 L2.66666667,13.3333333 L4.66666667,13.3333333 L4.66633333,11.9993333 Z M7.99933333,11.9993333 L5.99933333,11.9993333 L6,13.3333333 L8,13.3333333 L7.99933333,11.9993333 Z M11.4346667,2.66666667 L9.45333333,2.66666667 L11.2313333,13.3333333 L13.2126667,13.3333333 L11.4346667,2.66666667 Z M4.66633333,5.33233333 L2.66633333,5.33233333 L2.66633333,10.6663333 L4.66633333,10.6663333 L4.66633333,5.33233333 Z M7.99933333,5.33233333 L5.99933333,5.33233333 L5.99933333,10.6663333 L7.99933333,10.6663333 L7.99933333,5.33233333 Z M4.66666667,2.66666667 L2.66666667,2.66666667 L2.66633333,3.99933333 L4.66633333,3.99933333 L4.66666667,2.66666667 Z M8,2.66666667 L6,2.66666667 L5.99933333,3.99933333 L7.99933333,3.99933333 L8,2.66666667 Z">
              </path>
            </g>
          </g>
        </g>
      </svg><strong class="uk-visible@s">Oracle Cloud Infrastructure</strong><button aria-label="Search scoped to this page. Use this button to use site search instead." type="button" uk-icon="icon: close; ratio: .6"
        class="uk-button vl-header-search-remove-scope-button uk-icon"><svg width="12" height="12" viewBox="0 0 20 20" xmlns="http://www.w3.org/2000/svg" data-svg="close">
          <path fill="none" stroke="#000" stroke-width="1.06" d="M16,16 L4,4"></path>
          <path fill="none" stroke="#000" stroke-width="1.06" d="M16,4 L4,16"></path>
        </svg></button></div>
    <div uk-drop="mode: hover; offset: 10; delay-show: 1000" class="uk-drop">
      <div class="uk-card uk-card-small uk-card-body uk-card-default vl-header-search-chip-dropdown">
        <p class="vl-header-search-chip-dropdown-label">Search is scoped to:</p>
        <p>Oracle Cloud Infrastructure</p>
      </div>
    </div>
  </div>
</form>

Text Content

 * Getting Started
 * Oracle Cloud Infrastructure Cloud Adoption Framework
 * Oracle Cloud's Free Tier
 * Oracle Multicloud
 * Oracle Cloud Infrastructure Government Cloud
 * Oracle EU Sovereign Cloud
 * Applications Services
 * Infrastructure Services
   * Service Essentials
   * Access Governance
   * Analytics Cloud
   * Anomaly Detection
   * API Gateway
   * Application Dependency Management
   * Application Performance Monitoring
   * Archive Storage
   * Artifact Registry
   * Audit
   * Automated CEMLI Execution
   * Bastion
   * Big Data Service
   * Billing and Cost Management
   * Block Volume
   * Blockchain Platform
   * New Cache with Redis
   * Certificates
   * Classic Migration
   * Cloud Advisor
   * Cloud Guard
   * Cloud Shell
   * Compartment Quotas
   * Compliance Documents
   * Compute
   * Compute Cloud@Customer
   * Connector Hub
   * Console Dashboards
   * Container Engine
   * Container Instances
   * Container Registry
   * Content Management
   * Data Catalog
   * Data Flow
   * Data Integration
   * Data Labeling
   * Data Safe
   * Data Science
   * Data Transfer
   * Database
     * Autonomous Recovery Service
     * Performance Hub
     * External Database
     * Exadata Database on Dedicated Infrastructure
       * Oracle Exadata Database Service on Dedicated Infrastructure Overview
       * What’s New in Oracle Exadata Database Service on Dedicated
         Infrastructure
       * Preparing for Exadata Cloud Infrastructure
       * Getting Started with Exadata Cloud Infrastructure Deployment
       * How-to Guides
         * Manage Database Security with Oracle Data Safe
         * Connecting to an Exadata Cloud Infrastructure Instance
         * Manage Exadata Cloud Infrastructure
         * Cloud Infrastructure Maintenance Updates
         * Manage VM Clusters
         * Manage Oracle Database Software Images
         * Create Oracle Database Homes on an Exadata Cloud Infrastructure
           System
         * Managing Oracle Database Homes on an Exadata Cloud Infrastructure
           Instance
         * Manage Databases on Exadata Cloud Infrastructure
         * Manage Database Backup and Recovery on Oracle Exadata Database
           Service on Dedicated Infrastructure
         * Patch and Update an Exadata Cloud Infrastructure System
         * Use Oracle Data Guard with Exadata Cloud Infrastructure
         * Configure Oracle Database Features for Exadata Cloud Infrastructure
         * Managing Exadata Cloud Infrastructure I/O Resource Management (IORM)
         * Migrate to Exadata Cloud Infrastructure
         * Switch an Exadata DB System to the New Resource Model and APIs
         * Connect Identity and Access Management (IAM) Users to Oracle Exadata
           Database Service on Dedicated Infrastructure
         * Authenticating and Authorizing Microsoft Azure Active Directory Users
           for Oracle Databases
       * Reference Guides for Exadata Cloud Infrastructure
     * Exadata Database on Cloud@Customer
     * Base Database
     * Oracle Database Overview
     * Oracle Operator Access Control
     * Exadata Fleet Update
     * Oracle Autonomous Database on Dedicated Exadata Infrastructure
     * Oracle Autonomous Database Serverless
     * Oracle Maximum Availability Architecture in Oracle Cloud Infrastructure
     * Migrating Databases to the Cloud
     * Security Zone Integration
   * Database Management
   * Database Migration
   * Database Tools
   * DevOps
   * Digital Assistant
   * Disaster Recovery
   * DNS and Traffic Management
   * Document Understanding
   * Email Delivery
   * Events
   * File Storage
   * Functions
   * Fusion Analytics Warehouse
   * Generative AI (Beta)
   * GoldenGate
   * Health Checks
   * IAM with Identity Domains
   * IAM without Identity Domains
   * Integration 3
   * Integration Generation 2
   * Java Management
   * Language
   * Load Balancer
   * Logging
   * Logging Analytics
   * Managed Access
   * Managed Cloud Self Service Platform
   * Management Agent
   * Management Dashboard
   * Marketplace
   * Media Services
   * Monitoring
   * MySQL Heatwave
   * Network Firewall
   * Network Load Balancer
   * Networking
   * NoSQL Database
   * Notifications
   * Object Storage
   * OCI Control Center
   * New OCI Database with PostgreSQL
   * Operations Insights
   * Oracle APEX Application Development
   * Oracle Cloud Marketplace
   * Oracle Cloud Migrations
   * Oracle Linux
   * OS Management
   * OS Management Hub
   * Partner Portal
   * Oracle Cloud Marketplace Territory and Export Compliance Policy
   * Process Automation
   * New Publisher
   * Pulse
   * Queue
   * Resource Manager
   * Roving Edge Infrastructure
   * Search
   * Search with OpenSearch
   * Secure Desktops
   * Security Advisor
   * Security Zones
   * Service Catalog
   * Service Mesh
   * Speech
   * Stack Monitoring
   * Storage Gateway
   * Streaming
   * Tagging
   * Threat Intelligence
   * Vault
   * Vision
   * Visual Builder
   * Visual Builder Studio
   * VMware Solution
   * Vulnerability Scanning
   * Web Application Acceleration
   * Web Application Firewall
 * Developer Resources
 * Security
 * More Resources
 * Glossary
 * Oracle Cloud Console

Main Navigation
 * Getting Started with Oracle Cloud Infrastructure
 * Cloud Adoption Framework
 * Oracle Cloud's Free Tier
 * Multicloud
 * Oracle Cloud Infrastructure Government Cloud
 * Applications Services
 * Infrastructure Services
 * Developer Resources
 * Security
 * More Resources
 * Oracle Cloud Console
 * 
 * Cloud Applications Documentation
 * Oracle.com Home
 * Oracle Help Center Home

Help Center
Search
Oracle Cloud Infrastructure

Search is scoped to:

Oracle Cloud Infrastructure

Select Language
DeutschEnglish (US)EspañolFrançais (Canada)FrançaisItaliano日本語Português (Brasil)


ORACLE CLOUD INFRASTRUCTURE DOCUMENTATION
TRY FREE TIER

--------------------------------------------------------------------------------

Infrastructure ServicesDatabaseExadata Database on Dedicated
InfrastructureHow-to Guides
All Pages
 * Getting Started
 * Oracle Cloud Infrastructure Cloud Adoption Framework
 * Oracle Cloud's Free Tier
 * Oracle Multicloud
 * Oracle Cloud Infrastructure Government Cloud
 * Oracle EU Sovereign Cloud
 * Applications Services
 * Infrastructure Services
   * Service Essentials
   * Access Governance
   * Analytics Cloud
   * Anomaly Detection
   * API Gateway
   * Application Dependency Management
   * Application Performance Monitoring
   * Archive Storage
   * Artifact Registry
   * Audit
   * Automated CEMLI Execution
   * Bastion
   * Big Data Service
   * Billing and Cost Management
   * Block Volume
   * Blockchain Platform
   * New Cache with Redis
   * Certificates
   * Classic Migration
   * Cloud Advisor
   * Cloud Guard
   * Cloud Shell
   * Compartment Quotas
   * Compliance Documents
   * Compute
   * Compute Cloud@Customer
   * Connector Hub
   * Console Dashboards
   * Container Engine
   * Container Instances
   * Container Registry
   * Content Management
   * Data Catalog
   * Data Flow
   * Data Integration
   * Data Labeling
   * Data Safe
   * Data Science
   * Data Transfer
   * Database
     * Autonomous Recovery Service
     * Performance Hub
     * External Database
     * Exadata Database on Dedicated Infrastructure
       * Oracle Exadata Database Service on Dedicated Infrastructure Overview
       * What’s New in Oracle Exadata Database Service on Dedicated
         Infrastructure
       * Preparing for Exadata Cloud Infrastructure
       * Getting Started with Exadata Cloud Infrastructure Deployment
       * How-to Guides
         * Manage Database Security with Oracle Data Safe
         * Connecting to an Exadata Cloud Infrastructure Instance
         * Manage Exadata Cloud Infrastructure
         * Cloud Infrastructure Maintenance Updates
         * Manage VM Clusters
         * Manage Oracle Database Software Images
         * Create Oracle Database Homes on an Exadata Cloud Infrastructure
           System
         * Managing Oracle Database Homes on an Exadata Cloud Infrastructure
           Instance
         * Manage Databases on Exadata Cloud Infrastructure
         * Manage Database Backup and Recovery on Oracle Exadata Database
           Service on Dedicated Infrastructure
         * Patch and Update an Exadata Cloud Infrastructure System
         * Use Oracle Data Guard with Exadata Cloud Infrastructure
         * Configure Oracle Database Features for Exadata Cloud Infrastructure
         * Managing Exadata Cloud Infrastructure I/O Resource Management (IORM)
         * Migrate to Exadata Cloud Infrastructure
         * Switch an Exadata DB System to the New Resource Model and APIs
         * Connect Identity and Access Management (IAM) Users to Oracle Exadata
           Database Service on Dedicated Infrastructure
         * Authenticating and Authorizing Microsoft Azure Active Directory Users
           for Oracle Databases
       * Reference Guides for Exadata Cloud Infrastructure
     * Exadata Database on Cloud@Customer
     * Base Database
     * Oracle Database Overview
     * Oracle Operator Access Control
     * Exadata Fleet Update
     * Oracle Autonomous Database on Dedicated Exadata Infrastructure
     * Oracle Autonomous Database Serverless
     * Oracle Maximum Availability Architecture in Oracle Cloud Infrastructure
     * Migrating Databases to the Cloud
     * Security Zone Integration
   * Database Management
   * Database Migration
   * Database Tools
   * DevOps
   * Digital Assistant
   * Disaster Recovery
   * DNS and Traffic Management
   * Document Understanding
   * Email Delivery
   * Events
   * File Storage
   * Functions
   * Fusion Analytics Warehouse
   * Generative AI (Beta)
   * GoldenGate
   * Health Checks
   * IAM with Identity Domains
   * IAM without Identity Domains
   * Integration 3
   * Integration Generation 2
   * Java Management
   * Language
   * Load Balancer
   * Logging
   * Logging Analytics
   * Managed Access
   * Managed Cloud Self Service Platform
   * Management Agent
   * Management Dashboard
   * Marketplace
   * Media Services
   * Monitoring
   * MySQL Heatwave
   * Network Firewall
   * Network Load Balancer
   * Networking
   * NoSQL Database
   * Notifications
   * Object Storage
   * OCI Control Center
   * New OCI Database with PostgreSQL
   * Operations Insights
   * Oracle APEX Application Development
   * Oracle Cloud Marketplace
   * Oracle Cloud Migrations
   * Oracle Linux
   * OS Management
   * OS Management Hub
   * Partner Portal
   * Oracle Cloud Marketplace Territory and Export Compliance Policy
   * Process Automation
   * New Publisher
   * Pulse
   * Queue
   * Resource Manager
   * Roving Edge Infrastructure
   * Search
   * Search with OpenSearch
   * Secure Desktops
   * Security Advisor
   * Security Zones
   * Service Catalog
   * Service Mesh
   * Speech
   * Stack Monitoring
   * Storage Gateway
   * Streaming
   * Tagging
   * Threat Intelligence
   * Vault
   * Vision
   * Visual Builder
   * Visual Builder Studio
   * VMware Solution
   * Vulnerability Scanning
   * Web Application Acceleration
   * Web Application Firewall
 * Developer Resources
 * Security
 * More Resources
 * Glossary
 * Oracle Cloud Console

Skip to main content
Updated 2023-12-08


CLOUD INFRASTRUCTURE MAINTENANCE UPDATES 🔗

Oracle performs the updates to all of the Oracle-managed infrastructure
components on Exadata Cloud Infrastructure.

You may manage contacts who are notified regarding infrastructure maintenance,
set a maintenance window to determine the time your quarterly infrastructure
maintenance will begin, and also view scheduled maintenance runs and the
maintenance history of your Exadata Cloud Infrastructure in the Oracle Cloud
Infrastructure Console. For details regarding the infrastructure maintenance
process and configuring the maintenance controls refer to the following:

 * About Oracle-managed Exadata Cloud Infrastructure Maintenance
   Oracle performs patches and updates to all of the Oracle-managed system
   components on Exadata Cloud Infrastructure.
 * Overview of the Quarterly Infrastructure Maintenance Process
   By default, infrastructure maintenance updates the Exadata database server
   hosts in a rolling fashion, followed by updating the storage servers.
 * Overview of Monthly Security Maintenance
   Security maintenance, performed alongside the quarterly maintenance, is
   executed in months when important security updates are needed and includes
   fixes for vulnerabilities with CVSS scores greater than or equal to 7.
 * Using the Console to Configure Oracle-Managed Infrastructure Updates
   Software updates are scheduled quarterly and monthly. You can use the the
   console to schedule and plan for them.
 * Monitor Infrastructure Maintenance Using Lifecycle State Information
   The lifecycle state of your Exadata Infrastructure resource enables you to
   monitor when the maintenance of your infrastructure resource begins and ends.
 * Receive Notifications about Your Infrastructure Maintenance Updates
   There are two ways to receive notifications. One is through email to
   infrastructure maintenance contacts and the other one is to subscribe to the
   maintenance events and get notified.
 * Managing Infrastructure Maintenance Contacts
   Learn to manage your Exadata infrastructure maintenance contacts.
 * Using the API to Manage Exadata Cloud Infrastructure Maintenance Controls
   Use these API operations to manage Exadata Cloud Infrastructure maintenance
   controls and resources.

Parent topic: How-to Guides


ABOUT ORACLE-MANAGED EXADATA CLOUD INFRASTRUCTURE MAINTENANCE 🔗

Oracle performs patches and updates to all of the Oracle-managed system
components on Exadata Cloud Infrastructure.

Oracle patches and updates include the physical database server hosts, Exadata
Storage Servers, Network Fabric Switches, management switch, power distribution
units (PDUs), integrated lights-out management (ILOM) interfaces, and Control
Plane Servers. This is referred to as infrastructure maintenance.

The frequency of the updates depends on the region type, as follows:

 * Commercial regions: Oracle performs full quarterly infrastructure updates and
   monthly security infrastructure updates.
 * Government regions: Oracle performs monthly full infrastructure maintenance
   updates.

In all but rare exceptional circumstances, you receive advance communication
about these updates to help you plan for them. If there are corresponding
recommended updates for your VM cluster virtual machines (VMs), then Oracle
provides notifications about them.

Wherever possible, scheduled updates are performed in a manner that preserves
service availability throughout the update process. However, there can be some
noticeable impact on performance and throughput while individual system
components are unavailable during the update process.

For example, database server patching typically requires a reboot. In such
cases, wherever possible, the database servers are restarted in a rolling
manner, one at a time, to ensure that the service remains available throughout
the process. However, each database server is unavailable for a short time while
it restarts, and the overall service capacity diminishes accordingly. If your
applications cannot tolerate the restarts, then take mitigating action as
needed. For example, shut down an application while database server patching
occurs.

Parent topic: Cloud Infrastructure Maintenance Updates


OVERVIEW OF THE QUARTERLY INFRASTRUCTURE MAINTENANCE PROCESS 🔗

By default, infrastructure maintenance updates the Exadata database server hosts
in a rolling fashion, followed by updating the storage servers.

You can also choose non-rolling maintenance to update database and storage
servers. The non-rolling maintenance method first updates your storage servers
at the same time, then your database servers at the same time. Although
non-rolling maintenance minimizes maintenance time, it incurs full system
downtime while the storage servers and database servers are being updated.

Rolling infrastructure maintenance begins with the Exadata database server
hosts. For the rolling maintenance method, database servers are updated one at a
time. Each of the database server host's VMs is shut down, the host is updated,
restarted, and then the VMs are started, while other database servers remain
operational. This process continues until all servers are updated. After
database server maintenance completes, storage server maintenance begins. For
the rolling maintenance method, storage servers are updated one at a time and do
not impact VM cluster VM's availability.

Note

While databases are expected to be available during the rolling maintenance
process, the automated maintenance verifies Oracle Clusterware is running but
does not verify that all database services and pluggable databases (PDBs) are
available after a server is brought back online. The availability of database
services and PDBs after maintenance can depend on the application service
definition. For example, a database service, configured with certain preferred
and available nodes, may be relocated during the maintenance and wouldn't
automatically be relocated back to its original node after the maintenance
completes. Oracle recommends reviewing the documentation on Achieving Continuous
Availability for Your Applications on Exadata Cloud Systems to reduce the
potential for impact to your applications. By following the documentation's
guidelines, the impact of infrastructure maintenance will be only minor service
degradation as database servers are sequentially updated.

Oracle recommends that you follow the Maximum Availability Architecture (MAA)
best practices and use Data Guard to ensure the highest availability for your
critical applications. For databases with Data Guard enabled, Oracle recommends
that you separate the maintenance windows for the infrastructure instances
running the primary and standby databases. You may also perform a switchover
prior to the maintenance operations for the infrastructure instance hosting the
primary database. This allows you to avoid any impact on your primary database
during infrastructure maintenance.

Prechecks are performed on the Exadata Cloud Infrastructure components prior to
the start of the maintenance window. The goal of the prechecks is to identify
issues that may prevent the infrastructure maintenance from succeeding. The
Exadata infrastructure and all components remain online during the prechecks. An
initial precheck is run approximately 5 days prior to the maintenance start and
another precheck is run approximately 24 hours prior to maintenance start. If
the prechecks identify an issue that requires rescheduling the maintenance
notification is sent to the maintenance contacts.

Note

Do not perform major maintenance operations on your databases or applications
during the patching window, as these operations could be impacted by the
infrastructure maintenance operations

Related Topics

 * Achieving Continuous Availability For Your Applications
 * Maximum Availability Architecture (MAA) Best Practices

Parent topic: Cloud Infrastructure Maintenance Updates


OVERVIEW OF MONTHLY SECURITY MAINTENANCE 🔗

Security maintenance, performed alongside the quarterly maintenance, is executed
in months when important security updates are needed and includes fixes for
vulnerabilities with CVSS scores greater than or equal to 7.

Security maintenance, when needed, is scheduled to be applied during a 21-day
window that begins between the 18th-21st of each month and will run till the
9th-12th of the next month. Customers will receive notification of the proposed
schedule at least 7 days before the start of the monthly maintenance window, and
can reschedule monthly maintenance to another date in the window if desired. The
monthly security maintenance process updates database servers to fix critical
security vulnerabilities and critical product issues. Monthly maintenance also
updates storage servers to an Exadata Storage Software image that resolves known
security vulnerabilities and product issues. Updates to database servers are
applied online via Ksplice technology, while updates to storage servers are
applied in a rolling fashion.

While updating your services infrastructure, some operations including memory,
and storage scaling, operating system and Grid Infrastructure patching
(including prechecks), and elastic expansion of compute and storage servers may
be blocked.
Note

CPU scaling and VM startup/shutdown are the only operations supported during
monthly infrastructure maintenance.
Please plan to defer these operations until after the updates are complete.
Application of security updates takes about 15 minutes per DB server host, plus
60 minutes per storage server depending on the I/O activity. If you attempt an
affected operation, the console will notify you of the ongoing security updates.
No software is updated in the guest VMs.

If quarterly maintenance is scheduled within 24 hours of the time the monthly is
scheduled, the scheduled monthly maintenance will be skipped and the monthly
update will instead be applied immediately following the quarterly maintenance.

 * When scheduled at the same time, the monthly update is executed immediately
   following the completion of the quarterly maintenance.
 * If monthly maintenance is scheduled to begin 0-24 hours ahead of the
   quarterly maintenance, then the monthly maintenance will not execute as
   scheduled, but instead, wait and be executed immediately following the
   quarterly maintenance. If the quarterly maintenance is subsequently
   rescheduled, then the monthly security maintenance will begin immediately.
   Oracle, therefore, recommends scheduling quarterly and monthly maintenance at
   the same time. As a result, if you reschedule the quarterly at the last
   moment, the monthly maintenance will run at the scheduled time instead of
   immediately upon editing the schedule. You can also reschedule the monthly
   security maintenance when rescheduling the quarterly maintenance as long as
   you keep the monthly within the current maintenance window. Monthly
   maintenance can be rescheduled to another time in the maintenance window, but
   cannot be skipped.
 * If you are unable to select the same time slot because the time selected for
   quarterly maintenance is not available in the monthly scheduler (grayed out),
   then you will need to select the next available time slot.

Note



If the Exadata Infrastructure is provisioned before Oracle schedules the
security maintenance, then it will be eligible for security maintenance.

If quarterly maintenance is scheduled outside the 24-hour window of the security
maintenance in the same month, customers will need one maintenance window for
quarterly maintenance and one maintenance window for security maintenance.

Note



Any time before the scheduled monthly Exadata Infrastructure maintenance, you
can reschedule it.

The storage servers will only be updated once if you schedule the monthly
security maintenance at least 25 hours before the quarterly maintenance in the
month where both quarterly and monthly security maintenance has been scheduled.

Parent topic: Cloud Infrastructure Maintenance Updates


USING THE CONSOLE TO CONFIGURE ORACLE-MANAGED INFRASTRUCTURE UPDATES 🔗

Software updates are scheduled quarterly and monthly. You can use the the
console to schedule and plan for them.

Full Exadata Cloud Infrastructure software updates are scheduled on a quarterly
basis for commercial regions, and monthly for government regions. In addition,
important security updates are scheduled monthly. While you cannot opt-out of
these infrastructure updates, Oracle alerts you in advance through the Cloud
Notification Portal and allows scheduling flexibility to help you plan for them.

For quarterly infrastructure maintenance, you can set a maintenance window to
determine when the maintenance will begin. You can also edit the maintenance
method, enable custom action, view the scheduled maintenance runs and the
maintenance history, and manage maintenance contacts in the in the Exadata
Infrastructure Details page of the Oracle Cloud Infrastructure Console.

 * To set the automatic quarterly maintenance schedule for Exadata Cloud
   Infrastructure
   
 * To view or edit the properties of the next scheduled quarterly maintenance
   for Exadata Cloud Infrastructure
   Review and change the properties of the Exadata Cloud Infrastructure
   scheduled quarterly maintenance.
 * To view the maintenance history of an Exadata Cloud Infrastructure resource
   This task describes how to view the maintenance history for a cloud Exadata
   infrastructure or DB system. resource.
 * To set the node patching order for a scheduled infrastructure maintenance run
   This task describes how to set the node patching order for a scheduled
   infrastructure maintenance run for a cloud Exadata infrastructure or Exadata
   DB system resource.

Parent topic: Cloud Infrastructure Maintenance Updates

TO SET THE AUTOMATIC QUARTERLY MAINTENANCE SCHEDULE FOR EXADATA CLOUD
INFRASTRUCTURE 🔗

This task describes how to set the maintenance schedule for a cloud Exadata
infrastructure resource.
Note

Specifying a maintenance schedule is not available in Government regions.
 1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata
    Database Service on Dedicated Infrastructure.

 2. Navigate to the Cloud Exadata infrastructure you want to access:
    
    In the Oracle Exadata Database Service on Dedicated Infrastructure section,
    click Exadata Infrastructure. In the list of infrastructure resources, find
    the infrastructure you want to access and click its highlighted name to view
    its details page.
    
    On the resource details page, under Maintenance or Infrastructure
    Maintenance, click the edit link in the Quarterly Maintenance Schedule
    field.
 3. In the Automatic Maintenance Schedule dialog, select Specify a schedule.
 4. Under Maintenance months, specify at least one month for each quarter during
    which Exadata infrastructure maintenance will take place. You can select
    more than one month per quarter. If you specify a long lead time for
    advanced notification (for example, 4 weeks), then you may want to specify
    two or three months per quarter during which maintenance runs can occur.
    This will ensure that your maintenance updates are applied in a timely
    manner after accounting for your required lead time. Lead time is discussed
    in the following steps.
    Note
    
    Maintenance quarters begin in February, May, August, and November, with the
    first maintenance quarter of the year beginning in February.
 5. Under Week of the month, specify which week of the month maintenance will
    take place. Weeks start on the 1st, 8th, 15th, and 22nd days of the month,
    and have a duration of seven days. Weeks start and end based on calendar
    dates, not days of the week. Maintenance cannot be scheduled for the fifth
    week of months that contain more than 28 days.
 6. Optional. Under Day of the week, specify the day of the week on which the
    maintenance will occur. If you do not specify a day of the week, then Oracle
    will run the maintenance update on a weekend day to minimize disruption.
 7. Optional. Under Start hour, specify the hour during which the maintenance
    run will begin. If you do not specify a start hour, then Oracle will choose
    the least disruptive time to run the maintenance update.
 8. Under Lead time, specify the number of weeks ahead of the maintenance event
    you would like to receive a notification message. Your lead time ensures
    that a newly released maintenance update is scheduled to account for your
    required period of advanced notification.
 9. Update Maintenance Schedule.

Related Topics

 * The New Exadata Cloud Infrastructure Resource Model

Parent topic: Using the Console to Configure Oracle-Managed Infrastructure
Updates

TO VIEW OR EDIT THE PROPERTIES OF THE NEXT SCHEDULED QUARTERLY MAINTENANCE FOR
EXADATA CLOUD INFRASTRUCTURE 🔗

Review and change the properties of the Exadata Cloud Infrastructure scheduled
quarterly maintenance.

 1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata
    Database Service on Dedicated Infrastructure.”
 2. Navigate to the Cloud Exadata infrastructure or DB system you want to
    access:
    
    Cloud Exadata infrastructure ( new resource model ): Under Exadata at Oracle
    Cloud, click Exadata Infrastructure. In the list of infrastructure
    resources, find the infrastructure you want to access and click its
    highlighted name to view its details page.
    
    DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the list
    of DB systems, find the Exadata DB system you want to access, and then click
    its name to display details about it.
    
    The Infrastructure Details page displays information about the selected
    Oracle Exadata infrastructure.

 3. On the resource details page, under Maintenance, click the View link in the
    Next Quarterly Maintenance field.
    
    The Exadata Infrastructure Maintenance page is displayed.

 4. On the Exadata Infrastructure Maintenance page, scheduled maintenance
    details are listed.
    
    Target DB Server Version and Target Storage Server Version: These fields
    display the Exadata software version to be applied by the scheduled
    maintenance. The version applied will be the most recent certified update
    for Exadata infrastructures in the cloud. If the next quarterly update is
    not yet certified when the maintenance is scheduled, then the versions may
    show "LATEST" until the new quarterly update becomes available. Once the
    update becomes available the new version will be displayed.
    
    To find information on the Database Server Exadata software version or the
    Storage Server Exadata software version, see My Oracle Support note Exadata
    Database Machine and Exadata Storage Server Supported Versions (Doc ID
    888828.1).
    
    For each scheduled Exadata Infrastructure resource maintenance event, the
    Maintenance page lists the following details:
    
    * The status of the event
    * The OCID of the event
    * The scheduled start time and date of the event
    * Click Patch Now to start the maintenance event immediately. When prompted,
      click Run Maintenance to confirm that you want to start the event now.
    
    If a maintenance event is already in progress on one or more of the VM
    Clusters hosted by an Exadata Infrastructure resource when a maintenance
    event on that resource is to start, the Exadata Infrastructure resource
    maintenance event is queued and begins immediately after all VM Cluster
    maintenance events complete.

 5. To change the next scheduled maintenance settings, click Edit Maintenance
    Run.
 6. On the Edit Maintenance page, do the following:
    * Select a maintenance method, Rolling or Non-rolling.
      Note
      
      If you select the Non-rolling option, components will be updated
      simultaneously, resulting in full system downtime.
    * Enable custom action before performing maintenance on DB servers: Enable
      custom action only if you want to perform additional actions outside of
      Oracle’s purview. For maintenance configured with a rolling software
      update, enabling this option will force the maintenance run to wait for a
      custom action with a configured timeout before starting maintenance on
      each DB server. For maintenance configured with non-rolling software
      updates, the maintenance run will wait for a custom action with a
      configured timeout before starting maintenance across all DB servers. The
      maintenance run, while waiting for the custom action, may also be resumed
      prior to the timeout.
      * Custom action timeout (in minutes): Maximum timeout available to perform
        custom action before starting maintenance on the DB Servers.
        
        Default: 30 minutes
        
        Minimum: 15 minutes
        
        Maximum: 120 minutes
    * To reschedule the next maintenance run, enter a date and time in the
      Scheduled Start time field.
      The following restrictions apply:
       * You can reschedule the infrastructure maintenance to a date no more
         than 180 days from the prior infrastructure maintenance. If a new
         maintenance release is announced prior to your rescheduled maintenance
         run, the newer release will be applied on your specified date. You can
         reschedule your maintenance to take place earlier than it is currently
         scheduled. You cannot reschedule the maintenance if the current time is
         within 2 hours of the scheduled maintenance start time.
       * Oracle reserves certain dates each quarter for internal maintenance
         operations, and you cannot schedule your maintenance on these dates.
    
    * Click Save Changes.
 7. To view estimated maintenance time details for various components, click the
    View link is displayed in the Total Estimated Maintenance Time field.
    
    The View link is displayed in the Total Estimated Maintenance Time field
    only if the Maintenance Method is Rolling.
    
    The Estimated Maintenance Time Details page is displayed with details that
    include:
     * Total Estimated Maintenance Time
     * Database Servers Estimated Maintenance Time
     * Storage Servers Estimated Maintenance Time
     * Order in which components are updated. In rolling maintenance, components
       are updated in the sequence displayed
    
     a. To view the number of VMs that will be restarted as part of Database
        Server maintenance, click the Show details link.
        
        The VM Location dialog is displayed.
    
     b. In the VM Cluster Name field, you can find out what VM cluster a
        particular VM belongs to.
     c. Click Close.

 8. Click Close to close the Estimated Maintenance Time Details page.

Related Topics

 * The New Exadata Cloud Infrastructure Resource Model
 * Exadata Database Machine and Exadata Storage Server Supported Versions (Doc
   ID 888828.1)

Parent topic: Using the Console to Configure Oracle-Managed Infrastructure
Updates

TO VIEW THE MAINTENANCE HISTORY OF AN EXADATA CLOUD INFRASTRUCTURE RESOURCE 🔗

This task describes how to view the maintenance history for a cloud Exadata
infrastructure or DB system. resource.

 1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata
    Database Service on Dedicated Infrastructure.

 2. Navigate to the Cloud Exadata infrastructure or DB system you want to
    access:
    
    Under Oracle Exadata Database Service on Dedicated Infrastructure, click
    Exadata Infrastructure. In the list of infrastructure resources, find the
    infrastructure you want to access and click its highlighted name to view its
    details page.

 3. On the resource details page, under Bare Metal,VM, and Exadata, click the
    Maintenance History.
 4. The Maintenance jobs, State and type of patching are displayed.

Related Topics

 * The New Exadata Cloud Infrastructure Resource Model
 * My Oracle Support note Exadata Database Machine and Exadata Storage Server
   Supported Versions (Doc ID 888828.1)

Parent topic: Using the Console to Configure Oracle-Managed Infrastructure
Updates

TO SET THE NODE PATCHING ORDER FOR A SCHEDULED INFRASTRUCTURE MAINTENANCE RUN 🔗

This task describes how to set the node patching order for a scheduled
infrastructure maintenance run for a cloud Exadata infrastructure or Exadata DB
system resource.

Note



By default, all scheduled maintenance runs are initially set to use rolling
patching. To use non-rolling patching, you must change this setting for each
maintenance run after it is scheduled.

 1. Open the navigation menu. Click Oracle Database, then click Exadata on
    Oracle Public Cloud.
 2. Navigate to the cloud Exadata infrastructure or DB system you want to
    access:
    
    * Cloud Exadata infrastructure (new resource model): Under Oracle Exadata
      Database Service on Dedicated Infrastructure, click Exadata
      Infrastructure. In the list of infrastructure resources, find the
      infrastructure you want to access and click its highlighted name to view
      its details page.
    
    * DB systems: Under Bare Metal, VM, and Exadata, click DB Systems. In the
      list of DB systems, find the Exadata DB system you want to access, and
      then click its name to display details about it.
 3. On the resource details page, under Maintenance, click the view link in the
    Next Quarterly Maintenance field.
 4. On the Maintenance page, click the edit link in the Maintenance Method field
    for a scheduled cloud Exadata infrastructure maintenance run.
 5. In Update Exadata Infrastructure Node Patching Order, change the maintenance
    method to either Rolling or Non-rolling as needed.

Parent topic: Using the Console to Configure Oracle-Managed Infrastructure
Updates


MONITOR INFRASTRUCTURE MAINTENANCE USING LIFECYCLE STATE INFORMATION 🔗

The lifecycle state of your Exadata Infrastructure resource enables you to
monitor when the maintenance of your infrastructure resource begins and ends.

In the Oracle Cloud Infrastructure Console, you can see lifecycle state details
messages on the Exadata Infrastructure Details page when a tooltip is displayed
beside the Status field. You can also access these messages using the
ListCloudExadataInfrastructures API, and using tools based on the API, including
SDKs and the OCI CLI.

During infrastructure maintenance operations, you can expect the following:
 * If you specify a maintenance window, then patching begins at your specified
   start time. The infrastructure resource's lifecycle state changes from
   Available to Maintenance in Progress.
   Note
   
   The prechecks are now done prior to the start of the maintenance.
 * When Exadata database server maintenance starts, the infrastructure
   resource's lifecycle state is Maintenance in Progress, and the associated
   lifecycle state message is, The underlying infrastructure of this system
   (dbnodes) is being updated.
 * When storage server maintenance starts, the infrastructure resource's
   lifecycle state is Maintenance in Progress, and the associated lifecycle
   state message is, The underlying infrastructure of this system (cell storage)
   is being updated and this will not impact Database availability.
 * After storage server maintenance is complete, the networking switches are
   updated one at a time, in a rolling fashion.
 * When maintenance is complete, the infrastructure resource's lifecycle state
   is Available, and the Console and API-based tools do not provide a lifecycle
   state message.

Related Topics

 * ListCloudExadataInfrastructures
 * Software Development Kits and Command Line Interface
 * Command Line Interface (CLI)

Parent topic: Cloud Infrastructure Maintenance Updates


RECEIVE NOTIFICATIONS ABOUT YOUR INFRASTRUCTURE MAINTENANCE UPDATES 🔗

There are two ways to receive notifications. One is through email to
infrastructure maintenance contacts and the other one is to subscribe to the
maintenance events and get notified.

Oracle schedules maintenance run of your infrastructure based on your scheduling
preferences and sends email notifications to all your infrastructure maintenance
contacts. You can login to the console and view details of the schedule
maintenance run. Appropriate maintenance related events will be generated as
Oracle prepares for your scheduled maintenance run, for example, schedule
reminder, patching started, patching end, and so on. For more information about
all maintenance related events, see Oracle Cloud Exadata Infrastructure Events.
In case, if there are any failures, then Oracle reschedules your maintenance
run, generates related notification, and notifies your infrastructure
maintenance contacts.

For more information about Oracle Cloud Infrastructure Events, see Overview of
Events. To receive additional notifications other than the ones sent to
infrastructure maintenance contacts, you can subscribe to infrastructure
maintenance events and get notified using the Oracle Notification service, see
Notifications Overview.

Related Topics

 * Oracle Exadata Database Service on Dedicated Infrastructure Events
 * Overview of Events
 * Notifications Overview
 * Managing Infrastructure Maintenance Contacts

Parent topic: Cloud Infrastructure Maintenance Updates


MANAGING INFRASTRUCTURE MAINTENANCE CONTACTS 🔗

Learn to manage your Exadata infrastructure maintenance contacts.

 * To manage maintenance contacts in an Exadata Cloud Infrastructure
   Manage contacts for Exadata infrastructure maintenance notifications using
   the Console.

Parent topic: Cloud Infrastructure Maintenance Updates

TO MANAGE MAINTENANCE CONTACTS IN AN EXADATA CLOUD INFRASTRUCTURE 🔗

Manage contacts for Exadata infrastructure maintenance notifications using the
Console.

To prevent an Exadata infrastructure administrator from being overwhelmed by
system update notifications, you can specify up to 10 email addresses of people
to whom maintenance notifications are sent.

 1. Open the navigation menu. Click Oracle Database, then click Oracle Exadata
    Database Service on Dedicated Infrastructure.
 2. In the Oracle Exadata Database Service on Dedicated Infrastructure section,
    click Exadata Infrastructure to display a list of Exadata infrastructures in
    the default compartment. You can select a different compartment from the
    Compartment drop-down located in the List Scope section.
 3. In the list of Exadata infrastructure resources, find the infrastructure you
    want to access and click its highlighted name to view its details page.
 4. In the Maintenance section, click Manage in the Customer Contacts field to
    display the Manage Contacts dialog.
 5. Click the Add Contacts button to display a field in which to enter a valid
    email address. You can have up to 10 maintenance contacts for each Exadata
    infrastructure.
 6. To edit an email address, in the Manage Contacts dialog, select the box
    preceding the email address you want to edit and click the Edit button.
 7. To remove an email address from the list, in the Manage Contacts dialog,
    select the box preceding the email address you want to remove and click the
    Remove button.

Parent topic: Managing Infrastructure Maintenance Contacts


USING THE API TO MANAGE EXADATA CLOUD INFRASTRUCTURE MAINTENANCE CONTROLS 🔗

Use these API operations to manage Exadata Cloud Infrastructure maintenance
controls and resources.

For information about using the API and signing requests, see REST APIs and
Security Credentials. For information about SDKs, see Software Development Kits
and Command Line Interface.

Use these API operations to manage Exadata Cloud Infrastructure maintenance
controls.

Cloud Exadata infrastructure resource (new resource model):

 * ListCloudExadataInfrastructures
 * GetCloudExadataInfrastructure
 * UpdateCloudExadataInfrastructure
 * GetMaintenanceRun
 * ListMaintenanceRuns
 * UpdateMaintenanceRun

Parent topic: Cloud Infrastructure Maintenance Updates

Was this article helpful?

YesNo
 * Cloud Infrastructure Maintenance Updates
 * About Oracle-managed Exadata Cloud Infrastructure Maintenance
 * Overview of the Quarterly Infrastructure Maintenance Process
 * Overview of Monthly Security Maintenance
 * Using the Console to Configure Oracle-Managed Infrastructure Updates
 * Monitor Infrastructure Maintenance Using Lifecycle State Information
 * Receive Notifications about Your Infrastructure Maintenance Updates
 * Managing Infrastructure Maintenance Contacts
 * Using the API to Manage Exadata Cloud Infrastructure Maintenance Controls

Was this article helpful?

YesNo
Updated 2023-12-08
 * Copyright © 2023, Oracle and/or its affiliates.
 * About Oracle
 * Contact Us
 * Legal Notices
 * Terms of Use & Privacy
 * Document Conventions
 * Cookie-Einstellungen