We have done a complete install of CA UIM and we are seeing that the mon_config_service probe is not starting. We are seeing in the logs that the max restart time out is being reached. We need to get this running for proper alerting.
We have done a complete install of CA UIM and we are seeing that the mon_config_service probe is not starting. We are seeing in the mcs logs that the max restart time out is being reached.
With log_level=5 set, the following entry shows up in the mcs log:
Jan 17 11:17:29:901 [main, mon_config_service] Schema doesn't exist - creating with init file /legacy/sqlserver/Create_SSRV2_tables.sql
Jan 17 11:17:30:156 [main, mon_config_service] Error executing CREATE FUNCTION concat(@lhs varchar(max), @rhs varchar(max)) RETURNS varchar(max) AS
DECLARE @result varchar(max)
SET @result = @lhs + @rhs
Looking in the database, the concat function was given a bad name: "concat;0". The extra ';' is preventing the function from being dropped and recreated as needed. The mcs probe continues to try to configure itself, but this badly named function is preventing this.
Release : 9.0.2
Component : UIMMCS - UIM : mon_config_service
After making a backup of the functions in the UIM database, run the following command to remove the function:
drop function "dbo"."concat";
After the function is removed, re-activate the mcs probe. The probe should recreate the function and continue to start.
If there are issues with any of this process, please open a support case for assistance.