Troubleshooting patching problems


Sometimes, 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 though the patch is already installed on the instance or database.
  • You don't see an instance or a database in the roll back candidates list though the patch is successfully installed on the instance or database.

These issue occurs because of the 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:
    1. cmdb_trace.log
    2. .cmdb_trace.log.LCK
  4. If the permissions are not set as clarity:clarity or clarity:root, set them.
  5. Run the CMDB Collector.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Database Automation 8.5