Installing an Oracle patch package


Before you begin

To install an Oracle patch package, you must have a role with patch capabilities.

Note

  • Patches for the Oracle Installation media cannot be applied by using BMC Database Automation.
  • Although BMC Database Automation stops Cluster Ready Services (CRS) when patching a CRS home, the software does not natively start it back up. Startup is actually performed by postrootpatch.sh, which is run by the default patch post-script inserted upon patch definition.

To install an Oracle patch package

  1. From the Management Console, select Patching > Patch Repository in the Context Frame.
  2. In the Patch Repository page, select a patch package and select Install from the list box for that row.
  3. In the Oracle Patch Install Candidates page, populate the following fields, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

    Note

    Databases that are in an Up state before the patch package is installed are restarted after the installation is complete.

    BMC Database Automation uses the OPatch IDs that are defined for the patch package to determine the list of installation candidates to display for a patch package. Target databases appear on the installation candidates list until all of the OPatch IDs that are defined for the patch package are installed. Unapproved GI Homes and DB homes will not appear as candidates.

    Note

    For high-availability databases configured with Veritas Cluster Server, the Patch Candidates page displays both active and standby nodes as available to be patched. Select any of the candidates that appear for the database to patch the database on the active node.

    The following example shows RAC One Node databases displayed in the Oracle Patch Install Candidates page. Active nodes display with a green icon. Inactive nodes display only with a dash as the name.

    https://docs.bmc.com/docs/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2

    The screen in the following example shows multiple CDBs displayed in the Oracle Patch Install Candidates page.

    https://docs.bmc.com/docs/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2
    You can view a list of the targets that were excluded from the installation candidates list, and the reason why each target was excluded, by clicking Excluded Candidates on the Oracle Patch Install Candidates page.

  4. In the Custom Fields page, populate the custom fields you have defined in the template, and click Next.

    Note

    This page appears only when in the BMC Database Automation XML template, either custom fields are defined used for this activity or New in 8.9.03any custom fields are defined for the scheduling options (present on the Scheduling page in this wizard). If you have defined custom fields, value of those options on the Scheduling page will be derived from these custom fields. For more information, see Adding-custom-fields-to-a-template.

  5. In the Job Options page, specify any of the following Job options, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

  6. In the Scheduling page, select when to run this job in the Job Execution field, and click Next.
    New in 8.9.03If you choose to run the job now or at a future time, optionally, you can use the Set Maintenance Window option to specify the Maintenance Window Start Time and the Maintenance Window End Time during which the job should be scheduled and running.
  7. If the Change Control page appears, populate the following fields, and click Next.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

    Note

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

  8. In the Summary page, review the information.
    To make changes, do the following actions:
    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.
  9. Specify your verification preferences.
    • To continue with database creation after the pre-verification tests have been run successfully 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.

  10. Click Execute Job or Schedule Job (depending on your selection in the Scheduling page).
     For scheduled jobs, an Information Page appears.
     For jobs set to run now, a progress page appears.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*