Troubleshooting
Problem
SQL agent collector is named differently on cluster nodes
Symptom
In the Windows Cluster Administrator, the SQL agent collector can sometimes fail to be added to the cluster services because the service name is different on both cluster nodes.
Cause
While upgrading the SQL agent from version 6.2.3 (or lower) to version 6.3.1, the collector service name will be renamed. The service name will no longer be called KOQCOLL0 but will now be KOQCOLL_<instance name>. In case the upgrade didn't finish as expected, for example an agent or collector process that refused to stop (APAR IV61191 could contribute to this), could prevent the collector service to be renamed, and the service name would still be called KOQCOLL0 instead of KOQCOLL_<instance name>.
Environment
SQL agent 6.3.1
Diagnosing The Problem
Check the Windows Services applet, and verify the service name of the SQL agent collector: is it KOQCOLL0 or KOQCOLL_<instance name>?
Resolving The Problem
Remove the SQL agent instance through 'Manage Tivoli Enterprise Monitoring Services':
1° double-click the 'Monitoring Agent for Microsoft SQL Server' agent template
2° move the monitored server instance from left ('Server to Monitor') to right ('Database Servers Available') by clicking on the >> button . Click on 'OK'.
3° double-click the 'Monitoring Agent for Microsoft SQL Server' agent template again
4° move the monitored server instance from right ('Database Servers Available') to left ('Server to Monitor') by clicking on the << button. Click on 'OK'.
You will be asked to enter the configuration parameters.
5° restart the SQL agent instance
After that, the collector service name will be renamed to KOQCOLL_<instance name>, in this case KOQCOLL_SQLEXPRESS
Product Synonym
itm itcam sql agent
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21696116