There are scenarios where a particular MCS template has some kind of corruption and the configuration profiles based on that probe template are not displaying as expected.
An example could be that, despite we have upgraded a probe template to the latest version that should include an enhancement, we are not seeing the template displaying correctly (ie. missing option) even after that new version looks correctly installed.
With the below set of queries it is possible to clean the MCS tables from everything related to a particular probe's templates that are currently running on MCS.
The below procedure does NOT affect existing profiles, but it's only intended for completely removing certain probe's template from the database with the scope of redeploying it from scratch.
Release : 9.2.0
Component : UIM - MON_CONFIG_SERVICE
The following queries - executed on this order - will remove everything related to logmon MCS probe templates. After this a new deployment of logmon_mcs_template will need to be deployed on the MCS hub for the logmon template to be visible again in MCS:
delete from SSRV2ConfigValue where profile in(select profileID from SSRV2Profile where template in(select templateID from SSRV2Template where probe='logmon'));
delete from SSRV2Field where template in(select templateID from SSRV2Template where probe='logmon');
delete from SSRV2Profile where template in(select templateID from SSRV2Template where probe='logmon');
delete from SSRV2Removal where template in(select templateID from SSRV2Template where probe='logmon') ;
delete from SSRV2PackageTemplate where template in(select templateID from SSRV2Template where probe='logmon') ;
delete from SSRV2Template where probe='logmon';
delete from ssrv2probetemplatespackage where probe_name = 'logmon';
delete from ssrv2probetemplateupgrade where probe_name = 'logmon';