To install an Oracle patch package, you must have a role with patch capabilities.
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.
In the Oracle Patch Install Candidates page, populate the following fields, and click Next.
Patch candidate field
Specify how to install this patch.
Parallel: Apply patch package to all specified databases and hosts simultaneously.
Serial: Apply patch package to all specified databases and hosts one at a time.
Rolling (RAC only): Candidates are patched in an order that minimizes downtime. Only one instance of a database is offline when applying a patch at any time. Also, to minimize the job duration, multiple databases are patched at a specific time but not on the same node.
(Optional) Select this field to upgrade the version of OPatch that is installed on the target node as part of the patch package installation.
Fix Inventory Permissions
(Optional) Select this field to modify the inventory permissions for the specified Oinstall user and bypass associated verification checks. BMC Database Automation expects the Oracle user inventory directory permissions to be set to 770. If permissions are not set to 770, enable the Fix Inventory Permissions field to update the permission setting, thereby preventing a provisioning error.
Select a template. By default, The BMC Database Automation template that was selected from the Default Template field in the Edit Existing Package wizard is displayed. Optionally, you can select a template for this operation. For Oracle on Linux/UNIX, see Managing templates for Oracle on Linux and UNIX. For Oracle on Windows, see Managing templates for Oracle on Windows. If you select a template, you can click Skip Ahead to advance directly to the next step that requires input. An information message appears in the step, in green type, listing the fields that require entries before you advance to the next step.
Select the databases, hosts, and ASM instances that you want to patch with this patch package. You can select database or cluster homes. BMC Database Automation uses both database and cluster candidates by default, and when you apply the patch you define whether patches are applicable to a database, a cluster, or both.
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.
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.
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.
In the Job Options page, specify any of the following Job options, and click Next.
(Optional) Click Add Email to add email addresses to the notification list.
(Displayed when SNMP is configured) Select this option to send the results of this job to an SNMP destination. See Configuring SNMP.
Cleanup Agent Logs
(Optional) Select this option to automatically remove logs that are generated by BMC Database Automation on the Agent after the job is complete.
If the Change Control page appears, populate the following fields, and click Next.
Bypass Change Control
(Optional) Select this option to prevent BMC Remedy ITSM from controlling the change process. Selecting this option removes the rest of the fields from this page.
Change Control Options
Select whether to use an existing BMC Remedy ITSM change ticket or to open a new BMC Remedy ITSM change ticket to control the change process.
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
Assign the type of change for the new BMC Remedy ITSM change ticket.
Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.
Assign the urgency level for the new BMC Remedy ITSM change ticket.
Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.
Assign the change class for the new BMC Remedy ITSM change ticket.
Type a summary of the change process.
The Change Control page appears only when change control is configured for your environment. See Configuring change control.
To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.
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.