Creating an Oracle patch package


BMC Database Automation provides granular control over the application and rollback of Oracle molecule-based patches. Oracle patches that contain molecules can be installed as either a complete package (all molecules) or as a subset of molecules that can be defined in the Patch Package Attributes in the OPatch IDs section.

Before you begin

Download the appropriate Oracle patches and patch media. The patch file must be a ZIP file (.zip).

To create an Oracle patch package

  1. From the Management Console, select Patching > Patch Repository in the Context Frame.
  2. In the Patch Repository page, click Create New Package.
  3. In the Package Configuration page, populate the following fields, and click Next.

  4. In the Package Settings page, populate the following fields, and click Next.

In the Package Attributes page, populate the following fields, and click Next.

Note

If you want to upgrade OPatch as part of a patch job, make sure that the upgrade file is in the appropriate location. For Oracle on Linux/UNIX, see Oracle location for OPatch upgrades.

 

  1. In the Package Targets page, populate the values by moving the items that you want to the Selected box for each field, and click Next.

    Note

    To add to the list of available choices for the Target Operating Systems and Target Applications fields, see Adding-target-OS-and-applications-to-a-patch-package.

  2. In the Package Scripts page, populate the following fields, and click Next.

    Note

    The default pre- and post-provisioning scripts for OPatch provided by BMC Database Automation must be run as root. Modifications to these scripts or other scripts uploaded in this step should run as the user to which they were designed to run.

    Note

    Sample scripts are provided in pre- and post-installation steps to manage common pre- and post-provisioning procedures related to Oracle patches. For example, if they exist in the pre-installation step, run the prepatch.sh and prerootpatch.sh scripts, and then run the postpatch.sh and postrootpatch.sh scripts in the post-installation step. You can modify these scripts and upload custom scripts based on your specific patching requirements.

  3. In the Package Additional Files page, specify any additional files as follows, and click Next.
    Additional files can be added to a patch package. They can be added one at a time or as a prepackaged .zip file.

  4. 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.
  5. Click Create Package.

 

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