Oracle Cloud Infrastructure Documentation

How-to Guides

A collection of tasks and procedures for managing Exadata Fleet Update.

Manage Collections

Make sure to first go over the prerequisites listed in the Getting Started chapter.

Parent topic: How-to Guides

Create a Collection

To create a collection, be prepared to provide values for the fields required for configuring the collection.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click Create Collection.

    Create collection page is displayed.

    In the Create collection page, provide the requested information:

    • Enter attributes:
      • Collection name: Enter a descriptive name.
      • Compartment: The compartment for the collection. Targets may be added from multiple compartments to a collection.
      • Collection type: Select database or Grid Infrastructure.
      • Cloud service: Select Oracle Exadata Database Service on Cloud@Customer (ExaDB-C@C) or Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D).
      • Current major version: Select the current major version. Target in a collection must be of the same version, but can be of different patch levels.
      • Show Advanced Options: You have the option to configure advanced options.
        • 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.
      • Click Next.
    • Add targets:

      Search Criteria page is displayed.

      1. Click Edit search criteria.

        Search for targets that you would like to add to the collection. Search results will only include targets that match all criteria. Fields left empty will return all values

        • Compartment: Select a compartment.

          Compartment is a required field. Other fields are disabled until a value is entered for the Compartment field.

          Click Another compartment to add more compartments to expand your search.

        • The available choices vary depending on your Collection type (database or Grid Infrastructure).
          • Database:
            • Database release update: Select one or more database release updates.
            • Custom database software image: Select one or more custom database software images.
            • Exadata infrastructure: Select one or more Exadata infrastructures.

            • VM cluster: Select one or more VM Clusters.

              This field is disabled until you select an Exadata infrastructure. When enabled, this field displays only the VM Clusters that belong to the selected compartments and infrastructures.

            • Database home name: Enter a comma-delimited list of database home names. Use asterisk (*) for wildcard searches.
            • Database name: Enter a comma-delimited list of database names. Use asterisk (*) for wildcard searches.
            • Database unique name: Enter a comma-delimited list of database unique names. Use asterisk (*) for wildcard searches.
          • Grid Infrastructure:
            • Grid Infrastructure release update: Select one or more Grid Infrastructure release updates.
            • Custom Grid Infrastructure software image: Select one or more custom Grid Infrastructure software images.

              For more information, see Create a Custom Oracle Grid Infrastructure Software Image.

            • Exadata infrastructure: Select one or more Exadata infrastructures.

            • VM cluster: Select one or more VM Clusters.

              This field is disabled until you select an Exadata infrastructure. When enabled, this field displays only the VM Clusters that belong to the selected compartments and infrastructures.

        • Database release update: Select database one or more release updates.
        • Custom database software image: Select one or more custom database software images.
        • Exadata infrastructure: Select one or more Exadata infrastructures.
        • VM cluster: Select one or more VM Clusters.

          This field is disabled until you select an Exadata infrastructure. When enabled, this field displays only the VM Clusters that belong to the selected compartments and infrastructures.

        • Database home name: Enter a comma-delimited list of database home names. Use asterisk (*) for wildcard searches.
        • Database name: Enter a comma-delimited list of database names. Use asterisk (*) for wildcard searches.
        • Database unique name: Enter a comma-delimited list of database unique names. Use asterisk (*) for wildcard searches.
        • Collection name: Select one or more collection names.
        • Include targets already in an active maintenance cycle in another collection: Select this checkbox if you want to add targets that are already in an active maintenance cycle in another collection.
          Note

          Each target can only belong to one active maintenance cycle at a time. Adding targets that are already in an active maintenance cycle in another collection will not allow a maintenance cycle to be created until the other maintenance cycle(s) have been completed or these targets have been removed from the collection.
        • 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.
          Note

          If you attempt to clear a compartment, then the system displays the Clear associated criteria dialog box to clear the associated criteria first. Similarly, if you attempt to clear an Exadata infrastructure, then the system displays the Clear associated criteria dialog box to clear the associated criteria first.
        • Click Apply search criteria.

          The search may take a few minutes to complete. Results will be populated once they are available.

          1. To cancel the search, click Cancel search.
            Note

            Leaving the search page or canceling the search before it completes will not yield any results.

            Cancel search dialog is displayed.

          2. Click Cancel search.

          If you have selected to include targets in active maintenance cycles, then an info block is displayed.

          1. Click Unselect targets in active maintenance cycle to remove the targets.

          If you go back and change the collection type, cloud service, or current major version value, then the system will clear all selected criteria and target search results in the subsequent step.

          Changing value will clear target search results dialog is displayed.

          1. Click Change value and clear target search results to proceed.
      2. Click Next.
    • Review:

      Review the list of selected targets and then click Create collection.

Parent topic: Manage Collections

Edit a Collection

You can only edit the name of the collection.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to edit.

    Collection details page is displayed.

  3. Click Edit.

    Edit collection dialog is displayed.

  4. Edit the name and the click Save.

Parent topic: Manage Collections

Add Targets to an Existing Collection

Add targets that are not part of an active maintenance cycle.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to add targets.

    Collection details page is displayed.

    Under Resources, Targets is selected by default.

    The Target section displays the list of targets in the collection.

  3. Click Add Targets.

    Add Targets page is displayed.

  4. Click Edit search criteria.

    Edit search criteria screen is displayed.

  5. Select a compartment from where you want to search the targets.

    Targets may be added from multiple compartments to a collection.

  6. Click Another compartment to add more compartments to expand your search.
  7. Click Apply search criteria.

    The search may take a few minutes to complete. Results will be populated once they are available.

    If the search result includes targets that are already part of an active maintenance cycle, then a banner is displayed with an option to Unselect targets in active maintenance cycle.

    The Database name includes appropriate information and warning icons to indicate whether the targets are already part of this collection or they are part of collections that are part of an active maintenance cycle.

    Note

    • If a collection is part of an active maintenance cycle and the targets are also part of an active maintenance cycle in another collection, then those targets will be disabled and may not be added to this collection.
    • If the Collection has an active Maintenance cycle and if you try to add Targets after a successful Stage software Acion, then the system displays an alert message indicating that you will have to rerun the Stage software action after adding the Targets.
    • If you try to add or remove Targets after an Apply update Action has run but not successfully completed, then the system displays an alert message indicating that you cannot add or remove Targets until the Apply update Action completes successfully.
    • If the targets are not part of an active maintenance cycle, then those targets will be enabled and can be added to this collection.

    The Select targets from all pages and Unselect targets from all pages buttons are displayed only when the search returns 21 or more targets.

  8. Click Next.
  9. Review the list of selected targets and then click Add Targets.

    The status of the collection changes to Updating.

  10. Under Resources, click Work requests to view the progress.

The status of the collection changes to Available when adding targets to the collection completes successfully.

Parent topic: Manage Collections

Remove Targets from an Existing Collection

To remove targets from a collection, be prepared to provide values for the fields required for removing the targets.

Note

If you try to add or remove Targets after an Apply update Action has run but not successfully completed, then the system displays an alert message indicating that you cannot add or remove Targets until the Apply update Action completes successfully.
  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to add targets.

    Collection details page is displayed.

    Under Resources, Targets is selected by default.

    The Target section displays the list of targets in the collection.

  3. Click Remove targets, or in the list of targets, click the Actions icon (three dots) for a target, and then click Remove Target.

    Remove Targets page is displayed.

  4. Click Edit search criteria to identify the targets to remove.

    Edit search criteria screen is displayed.

  5. Enter appropriate values to narrow down your search criteria.

    For example, select Exadata infrastructure and the associated VM Clusters.

  6. Click Select targets from all pages.
  7. Review the list of selected targets.
  8. Click Remove targets.

    The status of the collection changes to Updating.

  9. Under Resources, click Work requests to view the progress.

The status of the collection changes to Available when removing targets from the collection completes successfully.

Parent topic: Manage Collections

Delete a Collection

Be cautious, you cannot recover a deleted Collection.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to delete.

    Collection details page is displayed.

  3. Click Delete.

    Or, click the Actions icon (three dots), and then click Delete..

    Delete dialog is displayed.

  4. Enter the name of the Collection, and then click Delete.

Parent topic: Manage Collections

Move a Collection to a Different Compartment

To change the compartment that contains your Collection, use this procedure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to move.

    Collection details page is displayed.

  3. Click Move Resource.

    Move Resource to a Different Compartment dialog is displayed.

  4. Choose a compartment where you want to move the resource, and then click Submit.

Parent topic: Manage Collections

Filter Collections by Compartment

To find Collections specific to an individual compartment, you can use List Scope to filter Collections by compartment.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Under List Scope, select a compartment from the list.

Parent topic: Manage Collections

Filter Collections by State

Filter Collectionss by selecting a state from the list of states.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Under Filters, select a state from the list.

Parent topic: Manage Collections

Manage Maintenance Cycles

Make sure to first go over the prerequisites listed in the Getting Started chapter.

Parent topic: How-to Guides

Create a Maintenance Cycle

For a given collection, create Maintenance Cycles, representing a full patching event to a specific target version. Each Collection may have zero or more maintenance cycles. If more than one, then only one maintenance cycle may be active at a time.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to edit.

    Collection details page is displayed.

  3. Under Resources, click Maintenance cycles.
  4. Click Create maintenance cycle.

    Create maintenance cycle page is displayed.

  5. In the Create maintenance cycle page, provide the requested information:
    • Maintenance cycle name: Enter a descriptive name.
    • The available choices vary depending on your Collection type (database or Grid Infrastructure).
      • Database:
        • Target database image: Defaults to the latest Oracle-provided image. Click Change database image to select a different target database image.
          • Oracle-provided database software images: These images contain generally available versions of Oracle Database software.
          • Custom database software images: These images are created by your organization and contain customized configurations of software updates and patches.
            • Choose a Compartment.
            • Choose a Region.

              Region filter defaults to the currently connected region and lists all the software images created in that region. When you choose a different region, the software image list is refreshed to display the software images created in the selected region.

        • Database home: As part of the software update, databases will be moved to a new home at the target image version. A new home may be created during the maintenance cycle or an existing home may be reused if one already exists in the VM Cluster.
          • Create new home: When creating new homes, the databases in the collection will maintain a similar structure. Databases in a shared home (shared with other databases) prior to the software update will be moved to a shared home as part of the update. Databases not in a shared home prior to the software update will be moved into a separate home as part of the update.
          • Use existing home if available: When using an existing home, all database targets in the same VM Cluster will be moved to a shared database home. If an existing home for the selected image is not found in the VM Cluster for a target database, then a new home will be created. If more than one existing home for the selected image is found, then the home with the least number of databases will be used. If multiple homes have the least number of databases, then a home will be selected at random.
          • Database home display name prefix: Display name for new database homes created as part of the maintenance cycle. An ordinal number will be appended to the name of the database home to make it unique.
      • Grid Infrastructure:
        • Target Grid Infrastructure image: Defaults to the latest Oracle-provided image. Click Change Grid Infrastructure image to select a different target Grid Infrastructure image.
          • Oracle-provided Grid Infrastructure software images: These images contain generally available versions of Oracle Grid Infrastructure software.
          • Custom Grid Infrastructure software images: These images are created by your organization and contain customized configurations of software updates and patches. For more information, see Create a Custom Oracle Grid Infrastructure Software Image.
            • Choose a Compartment.
            • Choose a Region.

              Region filter defaults to the currently connected region and lists all the software images created in that region. When you choose a different region, the software image list is refreshed to display the software images created in the selected region.

    • Target database image: Defaults to the latest Oracle provided image. Click Change database image to select a different target database image.
      • Oracle provided database software images: These images contain generally available version Oracle Database software.
      • Custom database software images: These images are created by your organization and contain customized configurations of software updates and patches.
    • Database home: As part of the software update, databases will be moved to a new home at the target image version. A new home may be created during the maintenance cycle or an existing home may be reused if one already exists in the VM Cluster.
      • Create new home: When creating new homes, the databases in the collection will maintain a similar structure. Databases in a shared home (shared with other databases) prior to the software update will be moved to a shared home as part of the update. Databases not in a shared home prior to the software update will be moved into a separate home as part of the update.
      • Use existing home if available: When using an existing home, all database targets in the same VM Cluster will be moved to a shared database home. If an existing home for the selected image is not found in the VM Cluster for a target database, then a new home will be created. If more than one existing home for the selected image is found, then the home with the least number of databases will be used. If multiple homes have the least number of databases, then a home will be selected at random.
      • Database home display name prefix: Display name for new database homes created as part of the maintenance cycle. An ordinal number will be appended to the name of the database home to make it unique.
    • Maintenance method: Maintenance method determines how VMs in a VM Cluster are batched and which nodes are updated together when applying the software updates.
      • One node at a time (rolling): (Default) Database instances are updated on one VM in the cluster at a time while the other instances remain operational.
      • Smart batch (rolling): Database instances are updated on one or more VMs at a time. VMs are batched based on the database services configured. This ensures that all services remain available as long as they are configured on multiple nodes while minimizing the total number of batches needed.
      • Non-rolling: All database instances across all VMs in the cluster are updated in parallel incurring full downtime.
      • 50/50 (rolling): The database instances on half of the VMs are updated in one batch, while the other half in another batch. The two batches are determined by the configuration of the database services. This ensures that all services remain available.
        • Enable one batch at a time: Select this checkbox to apply updates to one batch at a time.

          After applying the update to the first batch, the Apply action will wait to be continued before starting the second batch.

    • Stage software start time: Optionally, set the start time for staging the software.
    • Apply update start time: Optionally, set the start time for applying the update. Apply update start time must be at least 24 hours after the stage software start time.

      Apply update action will not run until the Stage Software action has been completed.

    • Enable Incident Logs and Trace Collection: Allow Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution.
      Note

      Any changes to this configuration are only supported when all actions for the maintenance cycle are in a scheduled state. You cannot make changes to this setting once any action for the maintenance cycle has started.

      Enable for all targets for this cycle and future events: Enable diagnostics log collection for all targets for this cycle and future events. Oracle recommends this for easy troubleshooting and better support.

      Enable for all targets for this cycle only: Enable diagnostic log collection for all targets only in the current maintenance cycle. After the cycle finishes, log collection settings will revert to the settings before the start of the maintenance cycle.

      Use existing diagnostic log collection settings: Only collect logs for targets with log collection already enabled.

      For more information, see:
    • Advanced options:
      • Database start/stop options:
        • Maximum drain timeout (in seconds): Specify a Drain Timeout in seconds between nodes. This would be used during a rolling update to provide time for database connection relocation. The drain timeout used will be the maximum of this value or the maximum configured drain timeout of the services running on a particular instance. Default is 600.
        • Keep service placement: When enabled, database service will be restored to the placement prior to the Apply update action.
      • Software update options:
        • Ignore missing bug fixes: Select this checkbox to perform the move as part of the software update even though the target home is missing patches for bug fixes present in the source home.
          • Bug numbers to ignore: Optionally, enter the bug numbers to ignore. If you don’t specify a bug number, then any bug that is fixed in the source but not in the target is ignored.
        • Force rolling patch: Select this checkbox to force the patch operation to be performed in a rolling manner even with any non-rolling patches.
      • 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.
  6. Click Create maintenance cycle.
Maintenance Cycle lifecycle states:
  • Maintenance Cycle will be in an Active state when created. It may go into an Updating state, if needed, when attributes are being updated.
  • When an action is executing the Maintenance Cycle will go into a Maintenance In Progress state.
  • If any action has failed jobs, and a subsequent action hasn't yet been run to successfully complete the failed jobs, the maintenance cycle will be in a Needs Attention state.
  • Once the Apply action has succeeded, the maintenance cycle will move into a Succeeded state and the cleanup action would become available.

    The cleanup action is an optional action on the maintenance cycle. Run the cleanup action to delete the maintenance cycle's source database and Grid Infrastructure homes, for the databases and Grid Infrastructures in the collection, after the maintenance cycle completes successfully. You can schedule a cleanup or cleanup immediately.

Note

If you try to create another maintenance cycle if a maintenance cycle already exists, then the system displays a dialog intimating that only one active maintenance cycle can exist on a collection.

Edit a Maintenance Cycle

To edit a maintenance cycle, be prepared to provide values for the fields required for editing the maintenance cycle.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to edit.

    Collection details page is displayed.

  3. Under Resources, click Maintenance cycles.
  4. In the list of maintenance cycles, click the name of the maintenance cycle to view details, or click the Actions icon (three dots) for a target, and then click View Details.

    Maintenance cycle details page is displayed.

  5. Click Edit maintenance cycle.
  6. Enter appropriate values in the required fields.
    Note

    The Target image can only be modified prior to the Apply being executed. Once an Apply is executed, then you cannot edit this field.

    • Enable Incident Logs and Trace Collection: Allow Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution.
      Note

      Any changes to this configuration are only supported when all actions for the maintenance cycle are in a scheduled state. You cannot make changes to this setting once any action for the maintenance cycle has started.

      Enable for all targets for this cycle and future events: Enable diagnostics log collection for all targets for this cycle and future events. Oracle recommends this for easy troubleshooting and better support.

      Enable for all targets for this cycle only: Enable diagnostic log collection for all targets only in the current maintenance cycle. After the cycle finishes, log collection settings will revert to the settings before the start of the maintenance cycle.

      Use existing diagnostic log collection settings: Only collect logs for targets with log collection already enabled.

      For more information, see:
  7. Click Save Changes.

Run Actions

For each Maintenance Cycle, perform Actions on the targets in the collection. You can run the Actions manually or configure to run at a scheduled date and time.

The Actions for a Maintenance Cycle are run sequentially in the same order as follows: Precheck (Stage) > Stage software > Precheck (Apply) > Apply update.

You can run the Apply action at a scheduled date and time but you cannot run it until the Stage action has been completed successfully. A Precheck is available to run for the Stage and Apply actions respectively. You can manually run a precheck. However, prechecks are run automatically as part of the Stage and Apply actions. You can configure Stage and Apply actions to run at a scheduled date and time or run them on demand.

Action lifecycle states:
  • Scheduling an action will create the action resource in the Scheduled state.
    • If scheduled run is canceled, then the action would go into Canceled state.
  • When the action runs, it will go into the In Progress state
    • When it completes, it will change to Succeeded state if all associated jobs complete successfully, or to Failed state if one or more of the jobs fail.
  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to edit.

    Collection details page is displayed.

  3. Under Resources, click Maintenance cycles.
  4. In the list of maintenance cycles, click the name of the maintenance cycle to view details, or click the Actions icon (three dots) for a target, and then click View Details.

    Maintenance cycle details page is displayed.

    Under Resources, Actions is selected by default.

  5. Click Precheck.

    Precheck prior to staging software dialog is displayed.

    In the Precheck prior to staging software dialog, do the following:
    1. Schedule precheck: Select this option and set the precheck start date and time and then click Schedule.
    2. Run precheck now: Select this option to run the precheck on demand and then click Run Precheck.

      While the precheck is being run, the statuses of both the resources, Maintenance cycle and Action change to In Progress.

      If the precheck fails to run and the issue has not yet been resolved, then the status of the Maintenance cycle changes to Needs Attention.

      The Actions section provides details about the Scheduled, In Progress, Succeeded, and Failed Actions.

      For a failed action, view the errors on the action page, and then retry the action after resolving the errors, or remove the targets from the collection.

      1. To view error details, click the name of the failed Action.

        Action details page is displayed.

        Under Resources, Jobs is selected by default.

        The Jobs section provides details about the Scheduled, In Progress, Succeeded, and Failed Jobs.

      2. To view error details, click the Actions icon (three dots) for a target, and then click View errors.

        View errors page is displayed.

      3. Fix the errors.
      4. To retry failed actions, on the Maintenance details page, click the Actions icon (three dots) for an Action, and then click Run Precheck Now.

        The precheck run succeeds.

  6. On the Maintenance cycle details page, click Stage software.

    Stage software dialog is displayed.

    In the Stage software dialog, do the following:
    1. Schedule stage: Select this option and set the Stage software start date and time and then click Schedule.
    2. Stage now: Select this option to run the Stage software on demand and then click Stage now.

      While the Stage software is being run, the statuses of both the resources, Maintenance cycle and Action change to In Progress.

      If the Stage software fails to run and the issue has not yet been resolved, then the status of the Maintenance cycle changes to Needs Attention.

      The Actions section provides details about the Scheduled, In Progress, Succeeded, and Failed Actions.

      For a failed action, view the errors on the action page, and then retry the action after resolving the errors, or remove the targets from the collection.

      1. To view error details, click the name of the failed Action.

        Action details page is displayed.

        Under Resources, Jobs is selected by default.

        The Jobs section provides details about the Scheduled, In Progress, Succeeded, and Failed Jobs.

      2. To view error details, click the Actions icon (three dots) for a target, and then click View errors.

        View errors page is displayed.

      3. Fix the errors.
      4. To retry failed actions, on the Maintenance details page, click Stage software.

        Retry stage software page is displayed.

        If you click to retry a failed target, then the default is to run the action now. Otherwise, the default is to schedule the action.

      5. Click Retry stage software.

        The Stage software run succeeds.

  7. On the Maintenance cycle details page, click Precheck.

    Precheck prior to applying software updates dialog is displayed.

    In the Precheck prior to applying software updates dialog, do the following:
    1. Schedule precheck: Select this option and set the precheck start date and time and then click Schedule.
    2. Run precheck now: Select this option to run the precheck on demand and then click Run Precheck.

      While the precheck is being run, the statuses of both the resources, Maintenance cycle and Action change to In Progress.

      The precheck run succeeds.

  8. On the Maintenance cycle details page, click Apply update.

    Apply software updates dialog is displayed.

    In the Apply software updates dialog, do the following:
    1. Schedule update: Select this option and set the Apply update start date and time and then click Schedule.
    2. Apply update now: Select this option to run the Apply update on demand and then click Apply update now.

      While the Apply update is being run, the statuses of both the resources, Maintenance cycle and Action change to In Progress.

      The Actions section provides details about the Scheduled, In Progress, Succeeded, Failed, and Canceled Actions.

      Note

      If the Stage software Action does not complete successfully at the scheduled start time for the Apply update Action, then the Apply update Action is canceled automatically.

      Hover the mouse over the tooltip icon for the canceled action to view the reason why the Action was canceled.

      1. To view details, click the name of the Action

        Action details page is displayed.

        Under Resources, Jobs is selected by default.

        The Jobs section provides details about the Scheduled, In Progress, Succeeded, and Failed Jobs.

      2. To retry failed job, click the Actions icon (three dots) for a Job, and then click Retry.

        The failed job returns to the In progress state.

      3. Click the Actions icon (three dots) for a Job, and then click View log.

        View log page is displayed.

      4. If there are still failed jobs, then click Retry failed targets.

        Retry apply update dialog is displayed.

        By default, Apply update now is selected if you retry failed targets.

      5. Click Retry apply update.

        A notification appears indicating that the new action is in progress.

      6. Click the link to view details.

        Apply update (retry) page is displayed.

        If one of the jobs fails, then you can choose to rollback and remove the target from the collection.

      7. Click the Actions icon (three dots) for a failed Job, and then click Rollback and remove target from collection.

        Rollback and remove target dialog is displayed.

      8. Review the information and then click Rollback and remove target.

        A notification appears indicating that the Rollback and remove action is in progress.

      9. The statuses of both the resources, Maintenance cycle and Action change to In Progress.

        The rollback and remove action succeeds.

      10. Click the name of the Action to view details.

        Action details page is displayed.

        The status of the resource, Maintenance cycle changes to Succeeded.

  9. On the Maintenance cycle details page, click Cleanup.

    Cleanup dialog is displayed.

    In the Cleanup dialog, do the following:
    1. Schedule cleanup: Select this option and set the Cleanup start date and time and then click Schedule.
    2. Cleanup now: Select this option to run the Cleanup on demand and then click Cleanup.
    3. If the Cleanup completes and if there are Jobs in Needs Attention state, then click the name of the action to view details.

      Action details page is displayed.

    4. Hover the cursor over the information icons for the Needs attention jobs to view details.
    5. Click Work requests to view details.

Re-Run Jobs While Action In Progress

You can restart a failed job while the Action is still in progress.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to edit.

    Collection details page is displayed.

  3. Under Resources, click Maintenance cycles.
  4. In the list of maintenance cycles, click the name of the maintenance cycle to view details, or click the Actions icon (three dots) for a target, and then click View Details.

    Maintenance cycle details page is displayed.

    Under Resources, Actions is selected by default.

  5. Click an Action that is In progress, for example, Stage software.

    Action details page is displayed.

  6. For a Failed job, click the Actions icon (three dots) for a target, and then click Retry.

    The Retry option is available only when a Stage or Apply Action is running.

    The status of the Failed job changes to In Progress.

    After completing successfully, the status changes to Succeeded.

Enable One Batch at a Time

When you choose the 50/50 (rolling) Maintenance method, the system provides an additional checkbox Enable one batch at a time appears to apply updates to one batch at a time.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the collection that you want to edit.

    Collection details page is displayed.

  3. Under Resources, click Maintenance cycles.
  4. Click Create maintenance cycle.

    Create maintenance cycle page is displayed.

  5. In the Create maintenance cycle page, provide the requested information.

    When you choose the 50/50 (rolling) Maintenance method, an additional checkbox Enable one batch at a time appears. Select this checkbox to apply updates to one batch at a time.

    After applying the update to the first batch, the Apply action will wait to be continued before starting the second batch.

  6. Click Create maintenance cycle.

    If you have scheduled, then the Stage software and Apply update Actions will run at the scheduled time.

    The Actions section on the Maintenance details page provides those details.

    If the scheduled Stage software and Apply precheck Actions are successful, then the first batch begins the update process.

    After applying the update to the first batch, the status of the Maintenance cycle changes to Needs Attention. The status of the Apply update for the second batch remains Waiting.

  7. Click Apply update.

    Apply update Action details page is displayed.

  8. Click Continue apply.

    The status of the Apply update for the second batch changes to In Progress.

    The status of the Maintenance cycle changes to In Progress.

    After applying the update to the second batch, the status of the Maintenance cycle changes to Succeeded.

    The status of the Apply update for the second batch changes to Succeeded.

View the List of Maintenance Cycles

You can view the list of all Maintenance cycles for all Collections.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click Maintenance cycles.
  3. Under List Scope, select the Compartment to view the Maintenance cycles associated with that compartment.
  4. Under Filters, select a state.

    Any state is selected by default.

  5. Select the Show historical maintenance cycles to list all the maintenance runs.

    By default, only the latest maintenance cycles are listed for each collection.

  6. In the list of Maintenance cycles, click the name of the maintenance cycle to view details, or click the Actions icon (three dots) for a target, and then click View Details.
  7. From the shortcut menu, you can select the options to Add tags to the Maintenance cycle and Delete the Maintenance cycle.

Delete a Maintenance Cycle

Be cautious, you cannot recover a deleted Maintenance Cycle.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click Maintenance Cycles.
  3. Click the name of the maintenance cycle that you want to delete.

    Maintenance cycle details page is displayed.

  4. Click More actions, and then select Delete.

    Or, click the Actions icon (three dots), and then click Delete.

    Delete dialog is displayed.

  5. Enter the name of the Maintenance Cycle, and then click Delete.

Filter Maintenance Cycles by Compartment

To find Maintenance Cycles specific to an individual compartment, you can use List Scope to filter Maintenance Cycles by compartment.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click Maintenance Cycles.
  3. Under List Scope, select a compartment from the list.

Filter Maintenance Cycles by State

Filter Maintenance Cycles by selecting a state from the list of states.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click Maintenance Cycles.
  3. Under Filters, select a state from the list.

Download Failed Job Logs

To download the logs for a failed job, use this procedure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the maintenance cycle for which you want to download failed job logs.

    Maintenance cycle details page is displayed.

    Under Resources, Actions is selected by default.

  3. In the Actions section, find the action that has the status Failed.
  4. Click the Actions icon (three dots), and then click Download failed job logs.
    (or)
    1. Click the name of the Action.

      Action Details page is displayed.

    2. Click Download failed job logs.

View or Download Job Logs

To view the progress of a job or to download the logs for a job, use this procedure.

  1. Open the navigation menu. Under Oracle Database, click Exadata Fleet Update.

    Under Exadata Fleet Update, Collections is selected by default.

  2. Click the name of the maintenance cycle for which you want to download failed job logs.

    Maintenance cycle details page is displayed.

    Under Resources, Actions is selected by default.

  3. In the Actions section, click the name of the Action for which you want to view or download logs.

    Action details page is displayed.

    Jobs section displays the list of jobs associated with the selected Action.

  4. From the list of jobs, select one, click the Actions icon (three dots), and then click View log.

    View log page is displayed.

    The log is refreshed every two minutes automatically.

  5. Click Refresh log to refresh on-demand.
  6. Click Download log to download the log.

Roll Back After Successful Patching

To roll back to the original lower version after successfully applying a patch, use this procedure.

  1. Create a new Maintenance Cycle with the original source version as the goal version details of the new Maintenance Cycle.
  2. During the cycle setup, select the Use existing home if available option for DB collections.

    For DB Collections: If there are multiple DbHomes present for the specified goal version of the Maintenance Cycle in the CloudVmCluster or VmCluster related to the Collection targets, Exadata Fleet Update service will revert to the DbHome with the least number of databases.

    In some cases, there may be multiple homes of the same version. If this happens, there is a risk that Exadata Fleet Update service will select a home that is missing some patches compared to the original source home.

  3. Run Precheck action and check the action output. Or, you can run Apply action and check the action output for any errors.
  4. To proceed with the rollback, choose the Ignore missing bug fixes option from the cycle properties.