Use oakcli to check for any problems before you start the patch upgrade.
Before installing the patch, use the oakcli validate command on Node 0 to identify any possible problems in your environment, such as missing dependencies or other conflicts that can cause issues with patch installation. Conflicts can be introduced if you customize the standard configuration. The oakcli validate command shows a report that lists the components that require patching. If a component is listed as Up-to-date for the supported version that you indicate with the -ver flag, then that component does not require patching.
Run the oakcli validate command using the following syntax to validate your system, where patch_version is the patch version for which you want to validate your system:
oakcli validate -c ospatch -ver patch_version
Example 1-1 Validating Readiness for Oracle Database Appliance Patch Set 12.1.2.7
Use the following commands to check for any problems on your system before installing the 12.1.2.7 patch bundle:
Run the patch validation check for the 12.1.2.7 patch set:
# oakcli validate -c ospatch -ver 12.1.2.7.0
The output of these commands inform you if the patch can be installed on your environment. If the output from the command indicates that there is a problem (for example, if there are missing RPM dependencies on the server), then address the issue, and run oakcli validate again.
Note:
These commands run only on the local node. run the commands on both nodes to check both Oracle Database Appliance nodes.