Why you are running analysis job before catalog is updated ?
Patch analysis is dependent on the patch catalog. You may not execute analysis until catalog update is completed.
Monoj Padhy the catalog updates are scheduled to update the catalog on a regular basis. It is not like BSA allows you to single thread similar workload, they run in parallel. In our case the triggering of any process is not just limited to business hours only. As i mentioned before analysis jobs are part of other automated provisioning process. As long as my process is not dependent upon the latest catalog, it should be using the most valid catalog from prior run.
it should be using the most valid catalog from prior run. >> this is not the way BSA patch analysis works.
if catalog update is in progress for (myWin2k8 say) then you cant run any patch analysis job using/refering the same catalog. until the catalog updation is finished.
and one more thing lets say you have created a catalog on day1 and updated and then executed the patch analysis job and then patch download,remediation etc...
on day2 you again updated the same catalog and now due to some reason it is failed to update the catalog successfully.
In this scenario you cant run analysis job until your catalog gets updated successfully.
so BSA always uses the latest catalog update run result during patch analysis process. Thats why you are failed to execute patch analysis job when catalog update is in progress.
Monoj Padhy I understand everything you explain, my question was how everyone avoids this situation or people have standard maintenance window where BSA is unavailable for use regularly because we decide to do housekeeping?
It kind of defeats an automation process that is supposed to support businesses process which doesn't have downtime.
Usually we do as follows.Lets assume we are planning to apply patches during weekends then we complete every other activity before hand. We may take couple of hours of downtime for the servers that needs patching to be deployed.
Mon- create patch catalog and update it
Tue- reserved to fix any issue that encountered during catalog update.
Wed- patch analysis
Thu- download the required patches
Friday- change approval process, if any
sat/sun- apply patches. You may like to have small small time windows during weekends and apply the required patches. This facilitates to apply patches with minimum maintenance window and thus ensuring high service availability.
This is just an idea. You may adjust as per your need.
If someone else have better solution to it, they may share it.
this actually has been a common issues. the patch users that run the analysis jobs don't know when the catalogs are being updated, so they just run their jobs on whatever schedule they must keep. that ends up conflicting w/ the cuj times and then you hit the error. so what is worse - having the patching job fail, or having the patching job run but only check for older patches (because the cuj is running concurrently to get newer patches) ?
It is almost the similar situation you are describing Bill Robinson. The admins have their weekly schedules to catch up to patching servers. I am okay with the check for older patches as my policy doesn't update them immediately on availability. The more i am thinking about it, I might have to reduce my catalog update schedules. I was hoping to keep the catalog current to capture updates to fixes even though i am not going to apply them immediately. I wasn't aware of the conflict until when one of my users complained :-).
create an idea for this, i know i've heard this complaint before.
Any updates to this topic? Is it going to work the same way in the upcoming 8.6?