Configuring Oracle DB patching for your deployment
The BigFix Console offers a simple interface for configuring and deploying Oracle DB patches across your environment. To configure the download plugin for Oracle DB, refer to Using Middleware download plug-in.
Procedure
Complete the following steps to configure Oracle DB
patching for your deployment from the BigFix console license overview
dashboard:
-
In the BigFix console,
click the Updates for Linux Applications Middleware site
or the Updates for Windows Applications Middleware site
to open the required sites.


-
Click Fixlets and Tasks and choose the appropriate
Update Oracle DB Patch List and update scripts Fixlet
from your Oracle DB installation.
Note: If you are using Oracle ASM or Oracle RAC, select the ASM Fixlet version.Note: If you are running a standalone Oracle DB, choose the Non-ASM or plain Fixlet version.Note: If you want to use the independent Fixlet, make sure to use the PSU, OJVM, and OJDK.
-
Click a Update Oracle DB Patch List and update scripts
Fixlet and select Take Action.

-
Set the input fields in the Execution tab of the
Take Action window.
- End Date
- Leave the end date field empty or unspecified.
- Reapply Action
- Click While Relevant to enable this option to ensure the action is reapplied whenever it becomes relevant.
- Reapply Interval
- Set the reapply interval to
1 dayto wait one day between reapplications.
- Maximum Allowed Reapplications
- Choose
Unlimitedto accept unlimited reapplications.
- Action Name
- Update the action's name to clearly indicate that it is a policy action.
- By configuring the action on the Execution tab as described, you create a policy action that runs daily.
- When you finish editing, click OK to deploy the action.
-
After the policy action runs on the database servers, Oracle
DB patch actions can become relevant.
Note: The Fixlet detects only databases that are configured in /etc/oratab (or /var/opt/oracle/oratab on Solaris).