Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

DB Read step always goes to "Connection Not Available" branch

UCCX 8.5.1.11002-22, HA

I have a DB Read step in a CCX script that has worked successfully in the past, but I noticed today it always goes to the Connection Not Available branch, and I don't know why.  If I open the DB Read step in the editor I can successfully test the query.  I can also successfully test the connection from the UCCX Administrator > Subsystems > DataSource page.  When I step through the script using reactive debug, I see it always goes to Connection Not Available.  What is the best way to troubleshoot this?  For example, which log file on the CCX server might have additional information about the failed connection?

Everyone's tags (4)
2 REPLIES
Community Member

DB Read step always goes to "Connection Not Available" branch

Hi Craig,

first of all please check that any service related to database is not " out of service" eg , CCX database service

then make sure that your DSN connections are fine,

then you can collect the CCX database logs( Through RTMT)  and MEDT logs ( located on the PC from which you are running the reactive debug. )

have you made any recent changes to the script related to DB read step lately ?

Community Member

Re: DB Read step always goes to "Connection Not Available" branc

Hi,

I've the same simptoms running 1 node of the same UCCX version.

I've went through MIVR logs and find that the UCCX is not releasing the DB connections. Therefore, always a new call that want to connect to DB gets the Connection Not Available.

Anyone knows if it is a bug and it is solved on 8.5SU3?

MIVR Logs:

107323875: Nov 20 10:23:50.201 WET %MIVR-STEPS_DB-7-UNK:Task:42000158117 DB Read Step Execution

107323876: Nov 20 10:23:50.202 WET %MIVR-STEPS_DB-7-UNK:Task:42000158117 DB Resource: CONTACTOS

107323877: Nov 20 10:23:50.202 WET %MIVR-STEPS_DB-7-UNK:Task:42000158117 Data Source Name: DSN

107323878: Nov 20 10:23:50.202 WET %MIVR-STEPS_DB-7-UNK:Task:42000158117 SQL Command: select * from XXXXXX where Numero=$callingNumber

107323879: Nov 20 10:23:50.202 WET %MIVR-SS_DB-7-UNK:EDBS Subsystem is initialized properly......

107323880: Nov 20 10:23:50.202 WET %MIVR-SS_DB-7-UNK:EDBS_DS:MaxActive cnxs: 5

107323881: Nov 20 10:23:50.202 WET %MIVR-SS_DB-7-UNK:EDBS_DS:NumActive cnxs: 5

107323882: Nov 20 10:23:50.202 WET %MIVR-SS_DB-7-UNK:EDBS_DS:Connection request IN {

107323883: Nov 20 10:23:50.202 WET %MIVR-SS_DB-7-UNK:EDBS_DS:Connection request OUT } - No connections available

107323884: Nov 20 10:23:50.202 WET %MIVR-STEPS_DB-7-UNK:Task:42000158117 Database Connection not Available for DSN

107323885: Nov 20 10:23:50.202 WET %MIVR-STEPS_DB-3-DB_CONNECTION_NOT_AVAILABLE:DB_CONNECTION_NOT_AVAILABLE

A restart to the CCX ENGINE solved the issue for now:

Antes Chamada de Teste:

13205: Nov 20 10:45:22.368 WET %MIVR-SS_DB-7-UNK:EDBS_DS:MaxActive cnxs: 5

13206: Nov 20 10:45:22.368 WET %MIVR-SS_DB-7-UNK:EDBS_DS:NumActive cnxs: 0

Durante chamada de teste:

13957: Nov 20 10:47:07.414 WET %MIVR-SS_DB-7-UNK:SS_EDBS::checking connectivity for the DSN: DSN

13958: Nov 20 10:47:07.414 WET %MIVR-SS_DB-7-UNK:SS_EDBS::checkConnectivityForDSN: DSN

13959: Nov 20 10:47:07.414 WET %MIVR-SS_DB-7-UNK:EDBS Subsystem is initialized properly......

13960: Nov 20 10:47:07.414 WET %MIVR-SS_DB-7-UNK:EDBS_DS:MaxActive cnxs: 5

13961: Nov 20 10:47:07.414 WET %MIVR-SS_DB-7-UNK:EDBS_DS:NumActive cnxs: 1

Após ligação:

14243: Nov 20 10:47:12.902 WET %MIVR-SS_DB-7-UNK: Task:43000000017 Database connections being cleared

14378: Nov 20 10:47:22.425 WET %MIVR-SS_DB-7-UNK:EDBS Subsystem is initialized properly......

14379: Nov 20 10:47:22.425 WET %MIVR-SS_DB-7-UNK:EDBS_DS:MaxActive cnxs: 5

14380: Nov 20 10:47:22.425 WET %MIVR-SS_DB-7-UNK:EDBS_DS:NumActive cnxs: 0

Thx,

A mensagem foi editada por: Rui Martins

778
Views
0
Helpful
2
Replies
CreatePlease to create content