Managing patch packages for Oracle quarterly packages

This section details how to prepare and apply BMC Database Automation (BDA) patch packages for Oracle quarterly patches.

Before you begin

  1. Ensure that you have downloaded the latest version of OPatch and have set up OPatch media on the Manager.
  2. Ensure that a response file exists under /app/clarity/oracle_media/ on the Manager. If not, generate one.

To prepare and apply quarterly patch packages

The following table describes the files you must download to prepare and apply BDA patch packages and Oracle quarterly patches and where you must place the contents.

Files (.zip) to DownloadExampleDescriptionRequired Location
BMC Database Automation patch package wrappersGIPSU-Oct2014- (0 KB archive) for corresponding Oracle patch mediaPatch Repository in BMC Database Automation GUI
Quarterly patch media from

Actual Oracle patch media. In the example file name, 18705901 is the patch ID.

Patch Repository in BMC Database Automation GUI

OPatch utility from Oracle/app/clarity/oracle_media/p6880880_102000_Linux-x86-64.zipOPatch utility. In the example file name, 6880880 is the patch ID./app/clarity/oracle_media directory on the Manager

  1. Download the quarterly BDA patch package wrappers. 


    • To obtain access to the package wrappers, you need to contact BMC Customer Support.
    • The actual Oracle patch media is not included in patch package wrappers.
    • Patch package wrappers named ‘GIPSU- DBMS are applicable only if you are running a version of BDA earlier than 8.5 (beginning with version 8.5, the ‘GIPSU- DBMS wrapper type is no longer necessary).
    • If Oracle releases additional OJVM patches, they can be applied (using a separate job) after applying the GIPSU. The BDA OJVM patch package wrappers are available here.
    • Starting with version 8.9.01, BDA supports applying the combo PSU / OJVM. Download the appropriate combo patch package wrapper available here.


  2. Download the quarterly patch media from Oracle.


    On the Oracle support site, perform a search of the patch ID or OPatch ID to locate the files more quickly. When you download the Oracle patch media, the latest OPatch utility is also downloaded with it.

  3. Import the patch package wrapper (downloaded in Step 1) into the Patch Repository.

    1. From the Management Console, select Patching > Patch Repository in the Context Frame.
    2. In the Patch Repository page, click Import Package.

    3. Click Browse to select a patch package file.

    4. Complete the Import Package page and click Import Package.
  4. Replace the imported zero-length placeholder file contained in the patch package with the actual Oracle media.

    1. From the Management Console, select Patching > Patch Repository in the Context Frame.

    2. In the Patch Repository page, select the imported patch package and select Edit from the list box for that row.

    3. In the Package Configuration page, click Remove in the Patch File row to remove the zero-length placeholder file.

    4. In the Package Configuration page, click Browse in the Patch File row and select the Oracle patch media downloaded from Step 2.
    5. In the Package Settings page, do the following:
      1. Verify that the Package Name is displayed.
      2. (Optional) Update the Container and Available To settings.
      3. Click Skip Ahead and complete the wizard.


After applying GIRU April 2019 patcc, the permission of $GRID_HOME/bin/sqlplus is changed to root:oinstall. You can use BDA custom action to change the permission manually.

The following patch management options are available for each patch package in the Patch Repository Listing page.

Actions Field



Displays patch package details.

NEW IN 8.9.02Pre-Stage

Allows you to copy and then extract a patch media on a candidate before you install or deploy the patch package.

Note: BMC Database Automation 8.9.02 and earlier versions do not support this option for the Oracle quarterly patch packages. For information about the pre-staging other patch packages, see Pre-staging an Oracle patch package. Starting with version 8.9.03, you can use this option for the Oracle quarterly patch packages as well.


See Installing an Oracle patch package.


See Rolling back a previously applied Oracle patch package.

VerificationDisplays the Oracle Patch Installation Verification page so that you can view patch candidates and selected options for patching.
ConflictsDisplays the Oracle Patch Conflicts Check page so that you can check for Oracle patch conflicts based on the patch package and candidates selected.


Displays the patch package settings and permits changes to be made.

Important: When you change the target OS of an existing Oracle patch package (for instance, from Microsoft Windows to Linux), any default pre-provisioning or post-provisioning script files associated with the existing package are not replaced. To replace them, use the Package Scripts step of the wizard.


Enables you to export a BMC Database Automation patch package from the patch repository. When you export a patch package, a .zip file is created and downloaded to the location that you specify.


Removes that patch package from BMC Database Automation.

The Patch Repository Listing page also contains the following buttons:

  • Create New Package: Use to create an Oracle patch package, where you can also granularly control the application and rollback of the patches.
  • Import Package: Use to import a patch package that was created on another Manager. Before importing packages into the patch repository, ensure that all the appropriate targets for the intended package are specified under Patching > Packaging Configuration.

Bypassing patch validation

The quarterly BMC Database Automation patch package wrappers provided by BMC include a checksum to validate that the actual Oracle patch media that you uploaded into the patch package wrapper (see Step 4 in the preceding section) is the exact Oracle patch media that was tested by BMC.

To disable (ignore) the checksum, use a patching .xml template and add the following custom field:


Then, when initiating an Apply Patch job, select the template, and select No from the Validate Patch custom field in the Custom Fields page of the wizard:

For more information about working with templates and custom fields, see Adding custom fields to a template.

Related topic
Was this page helpful? Yes No Submitting... Thank you