1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click Create maintenance scheduling policy.
4. In the resulting Create maintenance scheduling policy window, enter the following:
   1. Name: Enter a descriptive name for the policy.
   2. Compartment: Choose a compartment where you want to create this resource.
   3. Cadence: Choose a frequency.
      Available options:

      1. Every six months
      2. Every quarter
         Note
         
         To use the scheduling policy to plan and automate quarterly infrastructure maintenance, you must create a policy with a 'Quarterly' cadence and a scheduled start month value set to 'February.'
      3. Every month
   4. Schedule start month: Choose a start month.

      Oracle automation requires a quarterly maintenance schedule to start in February if this policy is used for infrastructure maintenance.

   5. Maintenance window: Oracle automation will perform maintenance to run scheduled actions as per your maintenance windows defined in the schedule.
      1. Month: Choose a month. The month selection option depends on the selected policy cadence. For a six-month cadence, you can choose between the First, Second, Third, Fourth, Fifth, or Sixth months. For a quarterly cadence, you can choose between the First, Second, or Third months of every quarter.
      2. Week: You can choose between the month's First, Second, Third, or Fourth weeks.
      3. Day: You can choose between the week's days: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
      4. Start time: Specify the start time when you want to begin maintenance.
      5. Duration: Plan your maintenance window based on average time estimates to complete Database Cloud service actions. Refer to Overview of the Quarterly Infrastructure Maintenance Process for time estimates.
      6. Enforce window duration: With this option enabled, any scheduled action that goes over the configured window duration will be paused and re-scheduled to resume in a future maintenance window.
         Note
         
         If an update or action is already underway and cannot be paused and resumed without causing disruption, we will continue and complete the action. Oracle automation will reschedule any action planned to start after the configured window duration to a future maintenance window.
   6. Show Advanced Options:
      1. Tags: (Optional) You can choose to apply tags. If you have permission to create a resource, then you also have permission to apply free-form tags to that resource. To apply a defined tag, you must have permission to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, then skip this option (you can apply tags later) or ask your administrator.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to view details.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to edit.
4. In the resulting Maintenance scheduling policy details page, click Edit scheduling policy.
5. In the resulting Edit scheduling policy window, you can only edit the name of the policy.
6. Edit the name and then click Edit scheduling policy.

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

2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that's in Needs attention state.
4. In the resulting Maintenance scheduling policy details page, click Edit scheduling policy.
5. In the resulting Edit scheduling policy window, update the policy settings.
6. Click Edit scheduling policy.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to view Maintenance window details.

   The Maintenance windows section in the resulting Maintenance scheduling policy details page lists the maintenance windows associated with the policy.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to edit Maintenance window details.

   The Maintenance windows section in the resulting Maintenance scheduling policy details page lists the maintenance windows associated with the policy.

4. Click the Actions menu (three dots) of the Maintenance window you want to edit and then select Edit maintenance window.
5. In the resulting Edit maintenance window page, make changes and then click Save.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to add Maintenance windows.

   The Maintenance windows section in the resulting Maintenance scheduling policy details page lists the maintenance windows associated with the policy.

4. Click Add maintenance window.
   Note
   
   For security maintenance, you can add the scheduled start time within the 21-day window.
5. In the resulting Add maintenance window page, add details and then click Add.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to view the associated resources.

   The Associated resources section in the resulting Maintenance scheduling policy details page lists the resources associated with the policy.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to delete Maintenance windows.

   The Maintenance windows section in the resulting Maintenance scheduling policy details page lists the maintenance windows associated with the policy.

4. Click the Actions menu (three dots) of the Maintenance window you want to delete and then select Delete.
5. In the resulting Delete maintenance window dialog, enter the name of the Maintenance window, and then click Delete maintenance window.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to move to a different compartment.
4. In the resulting Maintenance scheduling policy details page, click Move resource.
5. In the resulting Move resource to a different compartment dialog, choose a compartment, and then click Move resource.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to add tags to.
4. In the resulting Maintenance scheduling policy details page, click Add tags.
5. In the resulting Add tags dialog, add tags, and then click Add tags.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Click the name of the policy that you want to delete.
4. In the resulting Maintenance scheduling policy details page, click Delete.
5. In the resulting Delete maintenance policy dialog, enter the name of the policy, and then click Delete maintenance policy.
   Note
   
   You cannot delete a policy if it's used in a maintenance scheduling plan.

After the scheduling policy is selected, Oracle generates a recommended maintenance scheduling plan to apply updates to all the components in your infrastructure. The recommended plan schedules all DB Servers, followed by Storage Servers, into the maintenance windows from your policy based on duration. You can update the maintenance scheduling plan and customize the update to specific components to align with different windows in your scheduling policy.

• View Quarterly Maintenance Scheduling Policy
  To view the quarterly maintenance scheduling policy for your infrastructure, use this procedure.
• Change the Quarterly Maintenance Scheduling Policy
  To change the quarterly maintenance scheduling policy for your infrastructure, use this procedure.
• View Maintenance Scheduling Plan
  To view the maintenance scheduling plan for your infrastructure, use this procedure.
• Edit Maintenance Plan Scheduled Actions
  To edit scheduled actions of an Exadata Cloud@Customer Infrastructure maintenance scheduling plan, use this procedure.

While maintenance is in progress, you can enable or disable custom action and change the custom action timeout. While maintenance is waiting for a custom action, you can resume the maintenance prior to the timeout or extend the timeout.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Select Region and Compartment, and provide the region and the compartment where the Oracle Exadata infrastructure you want to edit is located.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to edit.

   The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

   Note
   
   Maintenance In Progress status is displayed in the Next Quarterly Maintenance field.
5. Click the View link in the Next Quarterly Maintenance field.

   The Exadata Infrastructure Maintenance page is displayed.

6. Click Edit Maintenance Run.

   Edit Maintenance page is displayed.

   Note
   
   You can only make edits to the custom action configuration, not the maintenance method or scheduled start time. Enabling or disabling the custom action or modifying the custom action timeout while maintenance is in progress will apply to all database servers that have yet to be updated.
7. On the Edit Maintenance page, do the following:
   • 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): Timeout available to perform custom action before starting maintenance on the DB Servers.

       Default: 30 minutes

       Maximum: 120 minutes

8. Click Save Changes.

   If you have configured the rolling maintenance method, then the View link is displayed in the Total Estimated Maintenance Time field.

   1. Click View.
      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
      • Network Switches Estimated Maintenance Time (InfiniBand systems only)
      • Order in which components are updated. In rolling maintenance, components are updated in the sequence displayed.
   2. Click Close.

While maintenance is in progress, you can enable or disable custom action and change the custom action timeout. While maintenance is waiting for custom action, you can resume the maintenance prior to the timeout or extend the timeout.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Select Region and Compartment, and provide the region and the compartment where the Oracle Exadata infrastructure you want to edit is located.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to edit.

   The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

   Note
   
   Maintenance In Progress status is displayed in the Next Quarterly Maintenance field.
5. Click the View link in the Next Quarterly Maintenance field.

   Exadata Infrastructure Maintenance page is displayed.

   Note
   
   

   • Editing a maintenance run is not available while waiting for custom action.
   • While maintenance is waiting for custom action, an information block is displayed. The information block is removed after the maintenance resumes.
6. On the information block, do one of the following:
   1. Click Resume Maintenance Now to resume the maintenance, proceeding to the next database server.

      Resume Maintenance dialog is displayed. Click Resume Maintenance Now.

   2. Click Extend Custom Action Timeout.

      You can extend timeout multiple times within the maximum allowable time of 2 hours. If you try extending beyond the maximum limit, then the system displays the Cannot Extend Custom Action Timeout dialog indicating that the custom action timeout has already been extended to the maximum allowable 2 hours and you cannot extend it further.

Learn how to view and edit the next scheduled security maintenance.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Select Region and Compartment, and provide the region and the compartment where the Oracle Exadata infrastructure you want to edit is located.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to view maintenance details.

   The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

   Quarterly and monthly maintenance details are displayed under the Maintenance section. Monthly security maintenance is labeled as Next Security Maintenance.

5. On the Infrastructure Details page, under Maintenance, click the view link in the Next Security Maintenance field.

   The Exadata Infrastructure Maintenance page is displayed. The Exadata Infrastructure Maintenance page includes details such as Type: Monthly Security Maintenance, Scheduled Start Time, and so on.

6. To reschedule monthly security maintenance, click the Edit link in the Scheduled Start Time field and pick a new date within the 21-day cycle.
   Note
   
   Certain black-out dates are not available for security maintenance and are grayed out in the rescheduling calendar.

   Edit Maintenance Start Time dialog is displayed.

7. Select a date and then click Save Changes.
8. To view the maintenance history, click Maintenance History.

   The Maintenance History page displays details including the type of maintenance, Monthly or Quarterly.

   When a monthly security maintenance is in progress, the Infrastructure resource state will be Available.

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.

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.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance updates scheduled to run in the chosen compartment.

5. Click the name of the activity you want to view associated maintenance windows.

   The Maintenance Windows section in the resulting Maintenance run page lists the maintenance windows associated with the chosen activity.

   • Start time (UTC): Window start time in UTC For example, Sun, Jun 23, 2024, 18:30:58 UTC.
     The following restrictions apply:

     • Oracle expects to be able to perform infrastructure maintenance at least once per quarter. You should not defer maintenance beyond the end of a maintenance quarter unless unexpected issues prevent your accommodating it before the next maintenance quarter.
     • In the event unexpected issues prevent your accommodating the scheduled infrastructure maintenance run, you can reschedule the infrastructure maintenance to another date no more than 180 days from the prior infrastructure maintenance. Since normal maintenance should be performed quarterly, this provides approximately 90 additional days for you to reschedule the infrastructure maintenance. Oracle strongly recommends you not schedule maintenance at or close to the 180 day limit, as you will have no flexibility to reschedule further if additional unexpected issues arise.
     • 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.
   • Type: Planned vs Unplanned. All windows created from the infrastructure maintenance scheduling plan or added by you to this maintenance run are 'Planned' windows. All other windows Oracle automation creates to address failures, duration enforcement, or unforeseen events are defined as 'Unplanned' windows. Always review activities scheduled to run in an 'Unplanned' window.
   • Maintenance action: The summary of actions scheduled to update in a given window.

     The server name identifies updates scheduled for DB servers. For example, Apply full update to DB servers dbServer-1 and dbServer-2. The storage server updates are identified as count since all storage servers have identical storage layouts. For example, Apply full update to 2 Storage Servers.

   • Estimated time: The estimated time for Oracle automation to complete maintenance actions scheduled to apply updates to all infrastructure components across all windows in the maintenance run.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance activities in the chosen compartment.

5. Click the name of the activity you want to view associated maintenance windows.

   The Maintenance Windows section in the resulting Maintenance run page lists the maintenance windows associated with the chosen activity.

6. Click the Actions menu (three dots) of the Maintenance window you want to edit, and then select Edit maintenance window.
7. In the resulting Edit maintenance window dialogs, update the Maintenance window start time, Duration in hours, and Enforce window duration fields
8. Click Edit maintenance window.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance activities in the chosen compartment.

5. Click the name of the activity you want to view associated maintenance actions.
6. Under Resources, click Maintenance actions.
7. To add actions:
   1. Click Add actions.
   2. In the resulting Add maintenance actions window, Select action type, and then click Add maintenance action.
8. To delete an action:
   1. Click the Actions menu (three dots) of the maintenance action, and then select Remove.

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

2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.

4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance activities in the chosen compartment.

5. Click the name of the activity you want to view associated maintenance windows.

   The Maintenance Windows section in the resulting Maintenance run page lists the maintenance windows associated with the chosen activity.

6. Click the Actions menu (three dots) of the Maintenance window you want to edit, and then select Edit maintenance actions.The resulting Edit maintenance action page displays the list of actions. You can either add more actions or delete the existing ones.
7. To add actions:
   1. Click Add actions.
   2. Do the following in the resulting Add maintenance action window:
      • Create new action: When you are creating a new maintenance action, you can choose to add components already scheduled to update in different maintenance windows to a new window.
        • Select action type:
          • DB Server Exadata full software update
            • Configure maintenance method:
              • Rolling: By default, Exadata Infrastructure is updated in a rolling fashion, one server at a time with no downtime.
              • Non-rolling: Update database and storage servers at the same time. The non-rolling maintenance method minimizes maintenance time but incurs 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): Timeout available to perform custom action before starting maintenance on the DB Servers.
                  Note
                  
                  Custom action timeout applies only to DB servers. Customer can specify a minimum 15 minutes and a maximum of 120 minutes of custom action time-out before DB server patching starts. Within this time, they can perform whatever actions they have planned. In case, they want to extend the custom action, they can extend the same by going to "edit maintenance window" option. If custom action is in progress, customer get 2 options - either extend Custom action timeout or resume maintenance window.

                  Default: 15 minutes

                  Maximum: 120 minutes

            • Add DB Servers:
              • Select DB Servers: Updates to selected DB Servers will be moved from their currently scheduled window to the window you are adding the maintenance action.
          • Storage Server Exadata full software update
            • Configure maintenance method:
              • Rolling: By default, Exadata Infrastructure is updated in a rolling fashion, one server at a time with no downtime.

              • Non-rolling: Update database and storage servers at the same time. The non-rolling maintenance method minimizes maintenance time but incurs full system downtime.

                Note
                
                All storage servers in the infrastructure must be scheduled to update in a single maintenance action to apply non-rolling storage updates. While these updates are applied, your database workloads will incur complete downtime.
            • Select storage server from: Select a window from where you want to add storage servers from.
            • Select maintenance action to add from: Select the action from where you want to add storage servers from.
            • Select number of storage servers to add: Select the number of storage servers to add to this action.
      • Move action from another window: When you are moving an action, you can choose to move all components scheduled to update in a specific window to a new window.
        • Select the window to move action from: Choose a window from the maintenance run.
        • Select the action to move: Choose a specific action from the maintenance window to move.
8. To delete an action:
   1. Click the Actions menu (three dots) of the maintenance action, and then select Remove.
      Note
      
      

      • Any action can be removed as long as there are no components scheduled for update in that action.
      • Any window can be removed as long as there are no actions scheduled for update in that window.

While maintenance is in progress, you can enable or disable custom action and change the custom action timeout. While maintenance is waiting for a custom action, you can resume the maintenance prior to the timeout or extend the timeout.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Select Region and Compartment, and provide the region and the compartment where the Oracle Exadata infrastructure you want to edit is located.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to edit.

   The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

   Note
   
   Maintenance In Progress status is displayed in the Next Quarterly Maintenance field.
5. Click the View link in the Next Quarterly Maintenance field.

   You will be on the maintenance run details page that is in progress.

6. Click Maintenance windows on the Maintenance Run details page.
7. Identify the maintenance window that's in progress
8. Click the Actions menu (three dots) and select Edit maintenance action.
9. Click the Actions menu (three dots) and select Edit custom action configuration.
10. In the resulting Edit custom action configuration page, enter Custom action in minutes.
    Note
    
    While maintenance is in progress you can only change the custom action time for DB Server action type. You cannot change the custom action time for support this option for any other action type.
11. Click Save changes.

While maintenance is in progress, you can enable or disable custom action and change the custom action timeout. While maintenance is waiting for a custom action, you can resume the maintenance prior to the timeout or extend the timeout.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Select Region and Compartment, and provide the region and the compartment where the Oracle Exadata infrastructure you want to edit is located.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to edit.

   The Infrastructure Details page displays information about the selected Oracle Exadata infrastructure.

   Note
   
   Maintenance In Progress status is displayed in the Next Quarterly Maintenance field.
5. Click the View link in the Next Quarterly Maintenance field.

   You will be on the maintenance run details page that is in progress.

6. In the resulting Maintenance Run details page, click Maintenance actions under Resources.

   While maintenance is waiting for custom action, an information block is displayed. The information block is removed after the maintenance resumes.

7. On the information block, do the following:
   1. Click Resume Maintenance Now to resume the maintenance, proceeding to the next database server.

      Resume Maintenance dialog is displayed. Click Resume Maintenance Now.

   2. Click Extend Custom Action Timeout.

      You can extend timeout multiple times within the maximum allowable time of 2 hours. If you try extending beyond the maximum limit, then the system displays the Cannot Extend Custom Action Timeout dialog indicating that the custom action timeout has already been extended to the maximum allowable 2 hours and you cannot extend it further.

To cancel a Maintenance Window Associated with a Maintenance Run, follow these steps:

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance activities in the chosen compartment.

5. Click the name of the activity you want to view associated maintenance windows.

   The Maintenance Windows section in the resulting Maintenance run page lists the maintenance windows associated with the chosen activity.

6. Click the Actions menu (three dots) of the Maintenance window you want to cancel, and then select Cancel maintenance window.

To cancel a Maintenance Run While In Progress, follow these steps:

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance activities in the chosen compartment.

5. Click the name of the 'In Progress' activity you want to cancel.
6. Click Maintenance windows on the Maintenance Run details page.
7. Identify the maintenance window that's in progress.
8. Click the Actions menu (three dots) and select Cancel maintenance window.
9. On the resulting Cancel maintenance run window, reconfigure Maintenance window start time.
10. Select the Enforce window duration checkbox to pause and re-schedule any scheduled action that goes over the configured window duration to resume in a future maintenance window.
11. Click Reschedule maintenance run.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance activities in the chosen compartment.

1. Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Dedicated Infrastructure.
2. Under Maintenance, click Scheduling policy.

   The resulting Scheduling Policy page displays the list of policies.

3. Choose a compartment from the Compartment filter.
4. Under Maintenance, click Activity.

   The resulting Activity page lists maintenance updates scheduled to run in the chosen compartment.

5. Click the Actions menu (three dots) of the maintenance activity you want to view details.

   The resulting Maintenance run page displays the details of the chosen maintenance activity.

Unplanned maintenance activity when infrastructure is scaled after maintenance is planned

• After scaling your infrastructure by adding DB or storage servers, you may need to update your maintenance scheduling plan to include these new components. If any infrastructure component is missing from the maintenance plan, a warning will appear in the infrastructure maintenance plan details section.
• When Oracle automation creates the maintenance run for the quarter, any components not included in the maintenance plan will be automatically added to an 'Unplanned' maintenance window. This ensures that all components have the correct system software applied each quarter, maintaining OCI software compliance.
• You can edit the scheduled start time of the 'Unplanned' window or move the updates for the missing components to an existing planned window as needed.

Unplanned maintenance activity when a scheduled update fails to apply

• If a scheduled update fails, the Oracle operations team will engage, evaluate the failure, and reschedule the failed update along with any unfinished updates to a future maintenance window. Oracle automation will mark this rescheduled window as 'Unplanned' and notify you to review the rescheduled maintenance activity.
• You can edit the 'Unplanned' window's scheduled start time or move the failed and unfinished updates to an existing planned window as needed.

Unplanned maintenance when schedule activity exceeds enforced window duration

• For maintenance windows configured with duration enforcement, Oracle automation will check if the estimated time to execute and apply the scheduled update is sufficient within the remaining window duration. If not, Oracle automation will automatically reschedule all unfinished updates to a future 'Unplanned' window, mark the current window as 'Duration Exceeded,' and notify you to review the rescheduled maintenance activity.
• Any updates already in progress will continue past the enforced window duration to ensure a consistent state of the underlying resources.

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.