Page tree

Skip to end of metadata
Go to start of metadata

You can roll back an Oracle patch package that has been applied to a node, and return the node to the previous patch level.

Before you begin

Ensure the following prerequisites are met:

  • The Can Rollback option is selected in the attributes for the package.
  • All OPatch IDs defined for the patch package are installed on that node.

To roll back an Oracle patch package that has already been applied to a node

  1. From the Management Console main page, select Patching > Patch Repository in the Context Frame.
  2. In the Patch Repository page, select the patch package that you want to uninstall, and select Rollback from the list box for that row.
  3. In the Homes section of the Oracle Patch Rollback Candidates page, select a host, and click Next.



    You can view a list of the targets that were excluded from the rollback candidates list, including the reason why, by clicking Excluded Candidates.
  4. In the Job Options page, specify any of the following Job options, and click Next.

    Type

    Option

    Description

    Notification Emails

    Email List

    (Optional) Click Add Email to add email addresses to the notification list.

     

    SNMP

    (Displays when SNMP is configured) Select to send the results of this job to an SNMP destination. See Configuring SNMP.

    Job Administration

    Cleanup Agent Logs

    (Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the job is complete.

  5. In the Scheduling page, select when to run this job in the Job Execution field, and click Next.
  6. If the Change Control page displays, populate the following fields, and click Next.

    Section

    Field

    Description

     

    Bypass Change Control

    (Optional) Select to bypass using BMC Remedy ITSM to control the change process. Selecting this option removes the rest of the fields from this page.

     

    Change Control Options

    Select to determine whether to open a new BMC Remedy ITSM change ticket, or to use an existing BMC Remedy ITSM change ticket to control the change process.

    • Selecting Use Existing Change Ticket displays the fields in the Use Existing Change Ticket section on this page.
    • Selecting Create New Change Ticket displays the fields in the Create New Change Ticket section on this page.

    Use Existing Change Ticket

    ITSM Change ID

    Specify the BMC Remedy ITSM change ticket number to associate with this change process.

     

    ITSM Task ID

    Specify the BMC Remedy ITSM task ID number to associate with this change process.

    Create New Change Ticket

    Change Type

    Assign the type of change for the new BMC Remedy ITSM change ticket.

     

    Change Impact

    Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.

     

    Change Urgency

    Assign the urgency level for the new BMC Remedy ITSM change ticket.

     

    Change Risk-Level

    Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.

     

    Change Class

    Assign the change class for the new BMC Remedy ITSM change ticket.

     

    Change Summary

    Type a summary of the change process.

    Note

    The Change Control page appears only when change control is configured for your environment. See Configuring change control.

  7. In the Summary page, review the information.
    To make changes, do the following:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
  8. Specify your verification preferences.
    • To continue with database creation after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
    • To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.

      Note

      The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to the actual provisioning activity.

  9. Click Execute Job or Schedule Job (depending on your selection in the Scheduling page).