Managing patching

The BMC Database Automation patch repository provides an easy method for creating a patch package and automatically applying patches to multiple nodes, one at a time or simultaneously. A patch package consists of the patch itself (from either Oracle, Microsoft or Sybase) and any pre-provisioning or post-provisioning scripts to be run. After a patch package is created, it can be applied to the hosts and databases you specify, and it can be exported to another Manager. In addition to applying interim software patches, you can roll back, where applicable, a previously applied patch, when necessary. Patches can be applied to nodes that have been provisioned outside of BMC Database Automation in addition to nodes that have been provisioned by BMC Database Automation.

Starting from version 8.9.02, you can divide the patch application process in the following phases to optimize the patch application process: 

• Pre-stage the patch: This step copies the patch media to nodes and extracts it.
• Apply the patch: Compares if the patch media is already present on the node. If the media exists, it is compared with the patch media to be copied using checksum. If the checksum matches, then the patch is applied to the node. If the media is not present or checksum does not match, the media is first copied and then patch is applied to the node.

You can pre-stage a patch outside the patch window, which typically has bandwidth and time constraints. After pre-staging, you can apply the patch in patch window.

The following topics provide instructions for managing patching by using BMC Database Automation:

• Managing patch packages for Oracle quarterly packages
• Creating a patch package
• Patching a database
• Rolling back a patch package
• Pre-staging a patch package