Oracle Cloud Infrastructure Documentation

Use Case: Patching Oracle-Defined Products

As an application owner, I want to patch the Oracle Clusterware and Oracle Base Database Service products that Fleet Application Management supports.

This use case describes an example in which you want to patch Oracle-defined products. It provides two scenarios and the steps needed to complete them. You can extrapolate the steps to apply to other types of Oracle-defined products in Fleet Application Management.

Define Oracle Database as a Product Stack and Patch It

To select Oracle Database as a product stack, follow these steps:

  1. Create a fleet by selecting the Oracle Database product stack that Fleet Application Management supports.
  2. Validate the fleet and wait for Fleet Application Management to complete the software inventory discovery.
  3. Confirm all required targets to verify the compliance status of the resources and targets.
  4. Check the compliance state of the fleet.
  5. If the fleet is noncomplaint, fix compliance issues by selecting the Oracle Database runbook provided by Fleet Application Management for patching. Also, you can fix compliance by creating a schedule for a later time from the Schedules page.

The patching process starts and the resources move into a compliant state.

Create a Product Stack and Patch It

To create a product stack that includes more than one product, and patch it, follow these steps:

  1. Create a product stack (for example, Oracle Clusterware DB) and include products such as Oracle Clusterware and Oracle Base Database Service.
  2. Create a fleet by selecting the product stack created in the previous step.
  3. Create a runbook for patching by using one of the following options:
    • Clone the Oracle Database runbook provided by Fleet Application Management and edit it to accommodate your specific discovery and patch requirements. For example, remove irrelevant tasks and keep the ones pertinent to the Oracle Base Database Service and Oracle Clusterware.
    • Create a custom runbook and add the runbook library tasks that Fleet Application Management supports.
  4. Validate the fleet and wait for Fleet Application Management to complete the software inventory discovery.
  5. Confirm all required targets to verify the compliance status of the resources and targets.
  6. If the fleet is noncompliant, fix compliance issues by selecting the runbook you created or cloned in step 3.

The patching process starts and the resources move into a compliant state.