Getting false alerts during sybase probe monitoring

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

Receiving false alerts for some of the sybase DB servers that have been configured for DB monitoring.

Getting alert "Profile xxxx, instance abcdxxxx, cannot connect to database: [When defining parameters, names must be supplied for either all of the parameters or none of the parameters.]"

However when checked the DB is up and running and there is nothing found in DB logs. 

 

 

 

Environment

Release : 20.3

Component : UIM - SYBASE 4.32

Sybase server  and client are ASE 16

SLES 11.1/Adaptive Server Enterprise/16.0 SP03 

Resolution

Can see below messages in sybase logs during time of error /alerts getting generated

Dec 31 00:00:05:384 [140015514408704] sybase: Open Client Message:
Dec 31 00:00:05:384 [140015514408704] sybase: Message number: LAYER = (4) ORIGIN = (2) SEVERITY = (6) NUMBER = (47)
Dec 31 00:00:05:384 [140015514408704] sybase: Message String: ct_connect(): protocol specific layer: internal Client Library error: There is a tds login error. The installed encryption handler returned a status that was not CS_SUCCEED.
Dec 31 00:00:05:384 [140015514408704] sybase: Profile: TxxxF/check_dbalive, CheckTimeouts starting
Dec 31 00:00:05:384 [140015514408704] sybase: Profile Txxxx/check_dbalive, is not connected to TOK_DEV_MCWF, err: 
When defining parameters, names must be supplied for either all of the parameters or none of the parameters.
Dec 31 00:00:05:384 [140015514408704] sybase: Profile Txxx, dropping connection
Dec 31 00:00:05:384 [140015514408704] sybase: Profile: TxxxxF/check_dbalive, fwSendQoSValue - 

Errors were observed occurring during particular time of the day same time for specific instances 

This is most likely a environment /network issue 

Suggested workaround is to use the sybase probe scheduling option to exclude probe operation around the time of the error/alert till the environment issue is isolated /rectified on the the check_dbalive checkpoint in the profile

This can be set on profile/instance level 

Configure Schedules

The sybase probe functionality will also be enhanced to handle these type of errors in upcoming probe releases