Highlighted
Arunhclite Super Contributor.
Super Contributor.
202 views

MSSQL Metric 3218 not triggering alerts

Hi All,

We have HP OMi 10.12 Windows OS. We are already monitoring MSSQL with the management pack.

Recently deployed the 3218 policy for % of Database space used.

But it is not triggering alert, eventhough the alert condition matches.  Kindly suggest on the troubleshoot steps like whether the  policy is working and collecting  metrics.

Thanks,
Arunkumar.K

0 Likes
7 Replies
Acclaimed Contributor.. KAKA_2 Acclaimed Contributor..
Acclaimed Contributor..

Re: MSSQL Metric 3218 not triggering alerts

What is the output of command "dbspicam -vpm 218" ? -KAKA-

0 Likes
Arunhclite Super Contributor.
Super Contributor.

Re: MSSQL Metric 3218 not triggering alerts

Hi Kaka,

 

Thanks for the quick response.

Here is the output

 

2019-04-16T12:22:17 ERROR dbspicam(10) dbspicam [cola:../cola.c:2136]: MSSQLServ
er20-8: MSSQL Server MP collector 'dbspims9.exe -vpm 218 -i LWUKWVPTV17\INS3 ' i
s still running. MSSQL Server MP collector '218' causes an overlap in metric 'db
spims9.exe -m 58,230,218,57,242,240,241,243,97 -i LWUKWVPTV17\INS3 ' - terminati
ng this collector.

There are 3 instances in the DB server. I deployed that policy for only 1 server.

 

Thanks,

Arunkumar.K

0 Likes
Arunhclite Super Contributor.
Super Contributor.

Re: MSSQL Metric 3218 not triggering alerts

Hi Kaka,

Could you get the issue behind this error?  Kindly update on this.

Thanks,

Arunkumar.K

0 Likes
Acclaimed Contributor.. KAKA_2 Acclaimed Contributor..
Acclaimed Contributor..

Re: MSSQL Metric 3218 not triggering alerts

Basically it means previous collector command never ends. This could be due to different reasons.

Apply HF"OMi_MgmtPack_MSSQL_01_01_028" on top of MP version and probabaly that solve your issue with overlapping metrics.

If HF does not solve issue then you may kill all the running process and start tracing for DBSPI/MP and probabaly you see a reason there.

As a last sort of resort reach MF support.

-KAKA-

0 Likes
Arunhclite Super Contributor.
Super Contributor.

Re: MSSQL Metric 3218 not triggering alerts

Hi Kaka,

 

Raised a case with HP and they suggested to add the below syntax in the defaults file under dbspi fodler.

 'MSSQL_PROCESS_UNLIMITED ON'

Once added, alerts started triggering.

Thanks much for your help on this.

Thanks,

Arunkumar.K

0 Likes
Acclaimed Contributor.. KAKA_2 Acclaimed Contributor..
Acclaimed Contributor..

Re: MSSQL Metric 3218 not triggering alerts

Glad that your issue is solved and thanks for sharing detail. if your case is still open please check with them if this is for metric 3218 only or if it is for general purpose in case there is metric overlapping issue.

-KAKA-

 

0 Likes
Arunhclite Super Contributor.
Super Contributor.

Re: MSSQL Metric 3218 not triggering alerts

Hi Kaka,

 

The syntax is not for overlapping it is to 'ignore DB maxsize and autogrowth'

 

Overlapping seems o be a different issue.

 

Thanks,
Arunkumar.K

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.