@@@@Platform-“OnPrem”
@@@@Product-“Database”
@@@@ReleaseVersion-“26.11”
@@@@info-map-label-“Other Error Messages in orachk_error.log or exachk_error.log”
Other Error Messages in orachk_error.log or exachk_error.log
Description:
When examining the orachk_error.log , some messages are expected and they are not indicative of problems. These errors are redirected and absorbed into the error.log to keep them from being reported on the screen.
For example, an error similar to the following is reported numerous times, once for each Oracle software home for each node:
/bin/sh: /u01/app/11.2.0/grid/OPatch/opatch: Permission denied
chmod: changing permissions of `/u01/app/oracle_ebs/product/11.2.0.2/VIS_RAC/.patch_storage': Operation not permitted
OPatch could not open log file, logging will not be possible
Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
These types of errors occur in role-separated environments when the tool runs as the Oracle Database software owner uses Opatch to list the patch inventories of homes that are owned by Oracle Grid Infrastructure or other Oracle Database home owners. When you run Opatch to list the patch inventories for other users, Opatch fails because the current user does not have permissions on the other homes. In these cases, the Opatch error is ignored and the patch inventories for those homes are gathered by other means. To avoid such errors, Oracle recommends that you run Oracle Orachk and Oracle Exachk as root in role-separated environments.
Action:
You do not need to report these types of errors to Oracle Support.
Also, ignore the errors similar to the following:
orachk: line [N]: [: : integer expression expected
The line number changes over time. However, the error indicates that the tool was expecting an integer return value and no value was found. The value was null that the shell was not able to compare the return values. The error is repeated many times for the same command, once for each node.