Check servers for Oracle DB patch readiness by using the precheck tasks

For each Oracle DB patch Fixlet a corresponding precheck tasks are available. The precheck tasks verify that your Oracle DB servers are capable of being patched to the specified Oracle patch level.

Before performing prechecks on PSU and OJVM integrated or independent patch Fixlets, make sure that the Patch List tasks is deployed for each endpoint.

Each precheck tasks performs the following activities:

  1. Downloads the PSU and OJVM combination patch file and the current OPatch file from the BigFix server.
  2. Verifies dependencies, such as (Perl is installed, Oracle home permissions permit patching, and so on.
  3. Verifies at least one listener is running.
  4. Verifies all databases that are defined in the /etc/oratab (or /var/opt/oracle/oratab on Solaris) folder are running.
  5. Verifies all databases are online if you are patching grid/ASM/RAC.
  6. Verifies that each Oracle home has enough space to install the patches.
  7. Verifies there are no invalid dba_objects or dba_registry rows. (The ORACLE_ALLOW_INVALIDS client setting disables this check.)
  8. Indicates whether the PSU binary patch or the OJVM binary patch or both pactches are required.
  9. Indicates whether the PSU database patch or the OJVM database patch or both patches are required.
  10. The Fixlet supports the latest versions of Opatch, ensuring the required minimum version is met.
  11. Verifies that no installed interim patches conflict with the installation of PSU or OJVM patches. The ORACLE_ALLOW_CONFLICTS client setting disables this check.
  12. Removes inactive patches to minimize the time required for actual patching. Inactive patches are patches that have already been superseded by another patch installed on the system, as identified by the Oracle opatch tool.

A successful precheck action reports a Completed status. If any of the preceding activities fails, the precheck action reports a Failed status. If the Oracle patching results analysis is activated, the Oracle Prechecks Failed property reports a summary of the checks that failed.

The <client installed folder>/BESClient/ORACLE folder contains files that can help you troubleshoot an failed precheck, including PRECHECK-<OracleVersion>.log (e.g. PRECHECK-19.0.0.0.log) , which is a detailed log of the latest precheck action.

Patch files are downloaded to the ORACLE HOME/PATCHING folder. With the ORACLE_PATCH_FOLDER client setting you can override this placement by specifying a different folder for the downloads.

Important: The patch downloads are not removed at the end of the precheck action. A subsequent precheck and patch actions re-use the downloaded files. The downloads are removed after a successful patch action.
Important: Even though the system uses a combo patch (PSU + OJVM), it will only patch the required components and delete the unnecessary patch. This ensures that the patching process is efficient and minimizes any excess or redundant updates. For example, <PATCHTYPE>-<oracleversion>.log (e.g. PSU-PATCH-19.0.0.0.log).
Important: There will be no seperate precheck tasks for OJDK, as these are just binaries. Instead, prechecks are included directly within the patch Fixlet itself.

You can run a precheck tasks as many times as required to prepare to run a patch action.