03-05-2015 12:34 PM - edited 03-14-2019 02:31 PM
Hello,
I would like to know how to verify that Primary and Secondary UCCX is synchronized (CLI, Web, etc..).
Thanks a lot for your help.
BR
Aubert
03-05-2015 04:07 PM
03-06-2015 12:56 AM
Hi Marcelo,
thank you for your email, I checked on UCCX HA via the commands follows:
admin:utils uccx dbreplication status
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_bafru904_uccx 2 Active Connected 851 Mar 5 11:01:18
g_bafru914_uccx 1 Active Local 0
Normaly the result should be at '0' for both UCCX but I have '851' in 'QUEUE' is it normal?
admin:show uccx dbreplication servers
This operation may take a few minutes to complete. Please wait...
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_bafru904_uccx 2 Active Connected 428 Mar 5 11:01:18
g_bafru914_uccx 1 Active Local 0
I have the same thing Queue '428'
Can you tell me that UCCX HA works fine (see HA commands below)?
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log
login as: admin
admin@145.140.0.4's password:
Command Line Interface is starting up, please wait ...
Welcome to the Platform Command Line Interface
VMware Installation:
2 vCPU: Intel(R) Xeon(R) CPU E5640 @ 2.67GHz
Disk 1: 146GB
Disk 2: 146GB
8192 Mbytes RAM
admin:show uccx dbreplication tables
This operation may take a few minutes to complete. Please wait...
CURRENTLY DEFINED REPLICATES
-------------------------------
REPLICATE: template_db_cra_bafru914_uccx_1_1_agentconnectiondetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 114
PARTICIPANT: db_cra:informix.agentconnectiondetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65538 / 0x10002
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_2_agentstatedetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 76
PARTICIPANT: db_cra:informix.agentstatedetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65539 / 0x10003
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_3_contactcalldetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 517
PARTICIPANT: db_cra:informix.contactcalldetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65540 / 0x10004
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_4_contactroutingdetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 89
PARTICIPANT: db_cra:informix.contactroutingdetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65541 / 0x10005
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_7_monitoredresourcedetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.monitoredresourcedetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65544 / 0x10008
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_8_latestsynchedtime
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.latestsynchedtime
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65545 / 0x10009
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_9_eememailstatusdescription
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eememailstatusdescription
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65546 / 0x1000a
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_10_eemreasoncodedescription
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eemreasoncodedescription
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65547 / 0x1000b
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_11_eemstatedescription
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eemstatedescription
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65548 / 0x1000c
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_12_eemactiveemail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eemactiveemail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65549 / 0x1000d
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_13_eemcontactemaildetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eemcontactemaildetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65550 / 0x1000e
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_14_eememailagentstatedetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eememailagentstatedetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65551 / 0x1000f
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_1_promptsfoldertbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.promptsfoldertbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65554 / 0x10012
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_3_grammarsfoldertbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.grammarsfoldertbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65556 / 0x10014
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_4_grammarsfiletbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.grammarsfiletbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65557 / 0x10015
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_5_documentsfoldertbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.documentsfoldertbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65558 / 0x10016
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_7_sysgrammarsfoldertbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.sysgrammarsfoldertbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65560 / 0x10018
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_8_sysgrammarsfiletbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.sysgrammarsfiletbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65561 / 0x10019
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_11_latestsynchedtime
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.latestsynchedtime
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65564 / 0x1001c
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_fcrassvr_bafru914_uccx_3_2_fcrascalllogtoday
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: fcrassvr:informix.fcrascalllogtoday
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65567 / 0x1001f
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_fcrassvr_bafru914_uccx_3_4_fcrasrecordlog
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: fcrassvr:informix.fcrasrecordlog
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65569 / 0x10021
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_fcrassvr_bafru914_uccx_3_5_latestsynchedtime
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: fcrassvr:informix.latestsynchedtime
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65570 / 0x10022
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_6_remotemonitoringdetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.remotemonitoringdetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65543 / 0x10007
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_15_eemqueueagentdetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra:informix.eemqueueagentdetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65552 / 0x10010
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_6_documentsfiletbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.documentsfiletbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65559 / 0x10017
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_9_scriptsfoldertbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.scriptsfoldertbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65562 / 0x1001a
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_fcrassvr_bafru914_uccx_3_1_fcrasstatelogtoday
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: fcrassvr:informix.fcrasstatelogtoday
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65566 / 0x1001e
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_fcrassvr_bafru914_uccx_3_3_fcrascalllogweek
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 500
PARTICIPANT: fcrassvr:informix.fcrascalllogweek
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65568 / 0x10020
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_bafru914_uccx_1_5_contactqueuedetail
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 89
PARTICIPANT: db_cra:informix.contactqueuedetail
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65542 / 0x10006
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_2_promptsfiletbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.promptsfiletbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65555 / 0x10013
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
REPLICATE: template_db_cra_repository_bafru914_uccx_2_10_scriptsfiletbl
STATE: Active ON:g_bafru914_uccx
CONFLICT: Timestamp
FREQUENCY: immediate
QUEUE SIZE: 0
PARTICIPANT: db_cra_repository:informix.scriptsfiletbl
OPTIONS: transaction,ris,ats,fullrow
REPLID: 65563 / 0x1001b
REPLMODE: PRIMARY ON:g_bafru914_uccx
APPLY-AS: INFORMIX ON:g_bafru914_uccx
REPLTYPE: Master
Command successful.
admin:show uccx dbrepl
admin:show uccx dbreplication server
admin:show uccx dbreplication servers
This operation may take a few minutes to complete. Please wait...
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_bafru904_uccx 2 Active Connected 428 Mar 5 11:01:18
g_bafru914_uccx 1 Active Local 0
Command successful.
admin:utils uccx dbre
admin:utils uccx dbreplication statu
admin:utils uccx dbreplication status
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_bafru904_uccx 2 Active Connected 851 Mar 5 11:01:18
g_bafru914_uccx 1 Active Local 0
------------------------------------------------------------------
REPLICATE STATE
------------------------------------------------------------------
db_cra:informix.agentconnectiondetail Active
db_cra:informix.agentstatedetail Active
db_cra:informix.contactcalldetail Active
db_cra:informix.contactroutingdetail Active
db_cra:informix.contactqueuedetail Active
db_cra:informix.monitoredresourcedetail Active
db_cra:informix.latestsynchedtime Active
db_cra:informix.eememailstatusdescription Active
db_cra:informix.eemreasoncodedescription Active
db_cra:informix.eemstatedescription Active
db_cra:informix.eemactiveemail Active
db_cra:informix.eemcontactemaildetail Active
db_cra_repository:informix.promptsfoldertbl Active
db_cra_repository:informix.promptsfiletbl Active
db_cra_repository:informix.grammarsfoldertbl Active
db_cra_repository:informix.grammarsfiletbl Active
db_cra_repository:informix.documentsfoldertbl Active
db_cra_repository:informix.scriptsfiletbl Active
db_cra_repository:informix.latestsynchedtime Active
fcrassvr:informix.fcrascalllogtoday Active
fcrassvr:informix.latestsynchedtime Active
db_cra:informix.remotemonitoringdetail Active
db_cra:informix.eemqueueagentdetail Active
db_cra_repository:informix.documentsfiletbl Active
db_cra_repository:informix.scriptsfoldertbl Active
fcrassvr:informix.fcrasstatelogtoday Active
fcrassvr:informix.fcrascalllogweek Active
db_cra:informix.eememailagentstatedetail Active
db_cra_repository:informix.sysgrammarsfoldertbl Active
db_cra_repository:informix.sysgrammarsfiletbl Active
fcrassvr:informix.fcrasrecordlog Active
------------------------------------------------------------------
admin:utils uccx dbreplic
admin:utils uccx dbreplication s
[K
[Kadmin:utils uccx dbreplication [0J[0Ktempla
admin:utils uccx dbreplication templatestatus
TEMPLATE DATABASE TABLES
==============================================
template_db_cra db_cra informix.agentconnectiondetail
db_cra informix.agentstatedetail
db_cra informix.contactcalldetail
db_cra informix.contactqueuedetail
db_cra informix.contactroutingdetail
db_cra informix.eemactiveemail
db_cra informix.eemcontactemaildetail
db_cra informix.eememailagentstatedetail
db_cra informix.eememailstatusdescription
db_cra informix.eemqueueagentdetail
db_cra informix.eemreasoncodedescription
db_cra informix.eemstatedescription
db_cra informix.latestsynchedtime
db_cra informix.monitoredresourcedetail
db_cra informix.remotemonitoringdetail
template_db_cra_repository db_cra_repository informix.documentsfiletbl
db_cra_repository informix.documentsfoldertbl
db_cra_repository informix.grammarsfiletbl
db_cra_repository informix.grammarsfoldertbl
db_cra_repository informix.latestsynchedtime
db_cra_repository informix.promptsfiletbl
db_cra_repository informix.promptsfoldertbl
db_cra_repository informix.scriptsfiletbl
db_cra_repository informix.scriptsfoldertbl
db_cra_repository informix.sysgrammarsfiletbl
db_cra_repository informix.sysgrammarsfoldertbl
template_fcrassvr fcrassvr informix.fcrascalllogtoday
fcrassvr informix.fcrascalllogweek
fcrassvr informix.fcrasrecordlog
fcrassvr informix.fcrasstatelogtoday
fcrassvr informix.latestsynchedtime
admin:
Thanks a lot for your help.
BR
Aubert
03-06-2015 05:13 AM
the 'Queue' should be '0' at the end of the database replication.
If you enter the command again, the 'Queue' number is incrementing or decrementing?
Regards.
03-06-2015 06:29 AM
Hi Marcelo,
admin:show uccx dbreplication servers
This operation may take a few minutes to complete. Please wait...
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_bafru904_uccx 2 Active Connected 0 Mar 5 11:01:18
g_bafru914_uccx 1 Active Local 0
admin:utils uccx dbreplication status
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_bafru904_uccx 2 Active Connected 425 Mar 5 11:01:18
g_bafru914_uccx 1 Active Local 0
Thanks a lot.
BR
Aubert
03-06-2015 06:40 AM
Hi Marcelo,
the 'Queue' number is decrementing.
BR
Aubert
03-06-2015 07:22 AM
Hi Aubert,
ok.
Keep an eye on the 'Queue' number until it reaches '0'.
It's possible that you had a connections problem in the past and now the database is in the process to synchronize.
Hope this helps.
03-06-2015 08:05 AM
Hi Marcelo,
the 'Queue' number is '0' at this moment but this value isn't '0' all the time because it changes all the days.
BR
Aubert
Aubert
03-06-2015 08:14 AM
it's sounds good to me ... after the end of the shift, you probably got a '0' for a long period.
Hope this helps. Regards.
03-06-2015 08:22 AM
Hi Marcelo,
The 'Queue' has changed again, it was '584' then after '0' and it is instable.
It never stay long time at '0'.
BR
aubert
03-06-2015 05:44 PM
Hi,
some tables, like 'contactcalldetail', has a lot of changes during the normal operation. The 'contactcalldetail' table, for example, creates a new record for each call or call leg processed by the system.
In your 'debug' the 'contactcalldetail' has a '517' 'Queue Size' ... probably because in this site, you have an active Contact Center, in other words, a lot of calls during a normal day.
Check this number at the end of the day ... when the Agents is not in a logging state.
Hope this helps.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide