Patch Oracle databases
Oracle Database Patch Fixlets are specific to OS, Oracle version, and specific patch level such as "OracleDB 19c on Linux - 2023-10 Patch". (There are also Patch Fixlet variants specific to ASM and RAC.) When a Patch Fixlet is deployed to a database server, it attempts to patch all the targeted databases on that server; for example, "OracleDB 19c on Linux - 2023-10 Patch" will patch all 19c databases listed in the server's oratab file to 2023-10.
- Downloads the PSU and OJVM combination patch file and the current OPatch file from the BigFix server, if you haven't downloaded them already during a precheck action or a previous failed patch action.
- Reruns all the same prechecks as the corresponding precheck Fixlet.
- Applies the PSU and OJVM binary patches and verifies that they were successfully applied.
- Applies the PSU and OJVM database patches and verifies that they were successfully applied for grid/ASM/RAC patches. This action runs during the binary patch phase by the Oracle autopatch tool.
- Runs some basic post-patch database consistency checks, such as verifying that the run didn't result in invalid dba_objects or dba_registry rows.
- Removes the patch downloads if the patch was successful.
A successful patch action reports a Completed status. If any
of the preceding activities fails, the patch action reports a
Failed status. If you activated the Oracle patching
results analysis, the Oracle Patching Failed
property reports a summary
of the patching activities that failed.
The /var/opt/BESClient/ORACLE folder contains files that can help you troubleshoot an unsuccessful patch, including the PATCH-<OracleVersion>.log (e.g. PATCH-19.0.0.0.log) file, which is a detailed log of the latest patch action.
The corresponding rollback Fixlet becomes applicable after the patch Fixlet deployment.