SCI Alarm Wizard

[cavagnaro]

Hi guys,
I'm trying to create a reaction alarm on SCI based on this condition. Normally I do alarms based on standard conditions, but they don't provide something I could use, so trying to do this by using the codes 0234 or 16781 but no luck...I do run the Wizard and try to do 00-0234, but doesn't work. How am I supposed to do this if possible?

Thanks in advance

[quote]
+0062 Connection to multiserver created, host 'myhost', port '1234', socket '123'
+0062 MSG_STARTDB status='2'
ODBC: id='2.1' req='6' Protocols versions: dbclient='00010003' dbserver='00010003' dblib='00010003'
+0000 001242E5,hDBC=6322244,6322244
+0000 Open DB: username = 'user_name', database = 'my_db', dbserver = 'mydb'
+0234 Could not connect to SQL Server using SQL Native Client driver. Attemting default MS SQL Server driver...
+16781  odbcerr: [Microsoft][ODBC SQL Server Driver]Dialog failed
+16781  MSG_ERROR status='30' msg='[Microsoft][ODBC SQL Server Driver]Dialog failed '
[/quote]

[Kubig]

Try to look into the *.lms files,which you can find under install folder of DBServer.

[cavagnaro]

So I can only use the alarms shown on the lms files?
Can't find something related to the event I see on logs.

[Fra]

Cav,

I'm not sure I have quite understood what you're trying to achieve.. 
But if you're planning to implement custom alarm conditions, then you can't pick *any* code; for URS you should there's a dedicated range for custom conditions (22001 to 22020), you should verify whether the same applies to other app types.

Fra

[Kubig]

I think yes, you can use "only" the messages from the *.lms files.

[cavagnaro]

[quote author=Fra link=topic=8299.msg36541#msg36541 date=1397119426]
Cav,

I'm not sure I have quite understood what you're trying to achieve.. 
But if you're planning to implement custom alarm conditions, then you can't pick *any* code; for URS you should there's a dedicated range for custom conditions (22001 to 22020), you should verify whether the same applies to other app types.

Fra
[/quote]

Hey Fra, what I want to is to send an alarm when some DBServer losses connection to DB Server (Oracle, MSSQL, etc) due the fact that sometimes agents complain about not being able to login or strategies failing and Genesys support is actioned when they should be able to call DB guys first.
It is a business issue that as they have like 3 support areas and they don't share same level of components access I want that when something happens instead of calling us to check logs and see that DB engines are down or not accesible from Genesys logs, they receive the alarm as soon as it happens and we don't have to lose time with those tasks.

Thanks Kubig, will have to do some tests in order to be 100% sure, hard to do on live platform. Will have to do a small lab with some DB engine.

[mduran22]

Cav,

Have you taken a look at the log advanced search wizard?

[Fra]

[quote author=cavagnaro link=topic=8299.msg36545#msg36545 date=1397155046]
[quote author=Fra link=topic=8299.msg36541#msg36541 date=1397119426]
Cav,

I'm not sure I have quite understood what you're trying to achieve.. 
But if you're planning to implement custom alarm conditions, then you can't pick *any* code; for URS you should there's a dedicated range for custom conditions (22001 to 22020), you should verify whether the same applies to other app types.

Fra
[/quote]
Right..! I recall that in the past DBServer was throwing the event  Dbg 46-10734 Send message 'MSG_CONNLOST' to 'App X' when it disconnected from the DBMS; however, message ID 10734 is used not only for that..plus I can't find it in the latest Framework 8.1 Combined Log Events Help..

Fra


Hey Fra, what I want to is to send an alarm when some DBServer losses connection to DB Server (Oracle, MSSQL, etc) due the fact that sometimes agents complain about not being able to login or strategies failing and Genesys support is actioned when they should be able to call DB guys first.
It is a business issue that as they have like 3 support areas and they don't share same level of components access I want that when something happens instead of calling us to check logs and see that DB engines are down or not accesible from Genesys logs, they receive the alarm as soon as it happens and we don't have to lose time with those tasks.

Thanks Kubig, will have to do some tests in order to be 100% sure, hard to do on live platform. Will have to do a small lab with some DB engine.


[/quote]