Troubleshooting patching problems

You might encounter the following issues when installing or rolling back a patch:

• You see an instance or a database in the list of patch candidates, but the patch is already installed on the instance or database.
• You do not see an instance or a database in the rollback candidates list, but the patch is successfully installed on the instance or database.

These issues occur because of insufficient permissions on the CMDB log files. 

Resolution: Follow these steps to resolve the issue:

1. Navigate to the following directory: /app/clarity/dmanager/var/log.
2. Run the following command: ls -latr
3. Check the permissions on the following files:
   • cmdb_trace.log
   • .cmdb_trace.log.LCK
4. If the permissions are not set as clarity:clarity or clarity:root, set them.
5. Run the CMDB Collector.

Sometimes, when BDA runs an Oracle patch under root user instead of Oracle user, the patch job fails. This is because of change of ownership of the sqlplus file at the location /app/oracle/rac/Home/product/19000/bin/sqlplus.

Resolution: On the Oracle home location, change the ownership of sqlplus to testcl:oinstall.