Happy New Year!!
You may encounter a situation where you need to force deployment of a TrueSight Capacity Optimization patch.
This can happen when the patch is stuck in READY state in the Maintenance tab or if the patch is in ERROR state and can't be redeployed via the TrueSight Capacity Optimization Maintenance User Interface (UI). In this article we will cover these two situations and a procedure for how to resolve this.
Situation 1 - Patch is in READY state in the Maintenance tab
The most common source of a TrueSight Capacity Optimization patch deployment that remains in READY state occurs when the Scheduler on the target machine for the patch is no longer communicating properly with the Dataub's Remote Scheduler Supervisor.
So, the first thing to try, is to correct the communication channel between the TrueSight Capacity OptimizationDatahub Remote Scheduler Supervisor and the Scheduler by following the steps in the linked article below, Steps to recover BCO functionality when the BCO Schedulers are unable to properly communicate with the Datahub Remote Scheduling Supervisor service at:
In most cases, once the steps in the article have been followed, the patch stuck in READY state will be automatically deployed after the TrueSight Capacity OptimizationScheduler is restarted (which is part of the cleanup processs).
Situation 2 - Patch is in ERROR state and can't be redeployed via the TrueSight Capacity Optimization Maintenance UI
This situation is less common, but the TrueSight Capacity Optimization patch is in ERROR state and can't be redeployed for some reason (such as subsequent patches have been deployed that are blocking the re-deployment).
In this case, the patch deployment can be forced by copying the patch file to the $CPITBASE/scheduler/autodeploy on the target machine and restarting the TrueSight Capacity Optimization Scheduler (or waiting for the Auto Deployment task to execute which can take up to 10 minutes).
Here is an applicable scenario :
You have installed TrueSight Capacity Optimization 9.5 with a Datahub AS and a Web AS. The Datahub AS does not have the Web component installed.
Mistakenly, the $CPITBASE/repository directory has not been shared between the two environments.
You then deploy the TrueSight Capacity Optimization 9.5 SP2 patch using the Maintenance tab to both AS Schedulers.
In this case, the TrueSight Capacity Optimization 9.5.02 patch deployment will fail on the Datahub AS (and thus none of the database update DDL with run) and it will succeed on the Web AS.
This results in a mismatch between the datbase structure and what the patched Web binaries are expecting. One of the symptoms of this mismatch is that an attempt to redeploy the TrueSight Capacity Optimization 9.5.02 patch on the Datahub AS (even after the $CPITBASE/repository directory has been properly shared) via the GUI can't proceed because the 'Target Schedulers' screen will remain blank (due to the underlying SQL failing to execute).
To fix this copy the BCO_9.5.02.00_AS.zip file to the $CPITBASE/repository directory on the Datahub AS and then restart the TrueSight Capacity Optimization Scheduler on the machine.
We hope you found this article useful (actually we hope you never have to use it!). It is also available in our Knowledge Base as: In BCO, how can I force the deployment of a patch if it is in READY state in the Maintenance tab or in ERROR state and can't be redeployed via the BCO UI
Miss a blog? See BMC TrueSight Support Blogs