Problem with Datasourcer

[ReasonGirl]

Dear Genesys Pros,

thank you for your recent help with Reason settings for CCA. I did not test it yet but it looks very encouraging! I am still waiting for Genesys to answer the same question. Read about it in my previous post 

I have noticed the following problem with my datasourcer:

a). when I start it the log contains the following:

12:05:46.188 StatServer-ctiserver:3040[10] SEvevntError SRID=36217 URID=0 LongValue=16
12:05:46.189 StatServer-ctiokssh:3040[10] SEvevntError SRID=36222 URID=0 LongValue=16
12:05:46.189 StatServer-ctiokssh:3040[10] SEvevntError SRID=36223 URID=0 LongValue=16

what is it?

b). in my DMA data timestamps are not consistent:

[table]
[tr]
[td]Id[/td][td]Begin Time[/td][td]Update Time[/td][td]Receive Time[/td]
[/tr]
[tr]
[td]100[/td][td]2006/9/12 10:45[/td][td]2006/9/12 11:00[/td][td]2006/9/12 11:23[/td]
[/tr]
[tr]
[td]101[/td][td]2006/9/12 11:00[/td][td]2006/9/12 11:15[/td][td]2006/9/12 11:30[/td]
[/tr]
[tr]
[td]102[/td][td]2006/9/12 11:15[/td][td]2006/9/12 11:30[/td][td]2006/9/12 11:44[/td]
[/tr]
[tr]
[td]103[/td][td]2006/9/12 11:30[/td][td]2006/9/12 11:45[/td][td]2006/9/12 12:00[/td]
[/tr]
[/table]


Q1: Why is Receive time not right after Update time? I do not think that chunk 100 has the correct information because it as received at 11:23, thus, it would contain 11:00-11:15 data. What is wrong?

Q2: Why the intervals for receive data are not 15 minutes apart as set by my CollectorDefault (00:00+00:15)? The number of agents has not changed. Server load is stable.

We are using datasourcer 7.2. Please help 


[move][glow=yellow,2,300]*************************
*         Reason(able) Girl          *
*************************[/glow][/move]

[ReasonGirl]

To follow up on my question why receive time is more than 15 minutes behind Update Time in DMA I have noticed the following:

12:45:05.002 Chunk schedule #1 time [[color=Orange]1158117300,1158118200[/color]] received from 0, records 79856
12:45:05.761 Chunk schedule #1 time [1158117300,1158118200] LOG_ID 149 records 79856 submitted
12:45:20.496 Chunk schedule #1 time [1158117300,1158118200] LOG_ID 149 written
12:45:25.883 Chunk schedule #3 time [[color=Blue]1158118200,1158119100[/color]] received from 0, records 8736
12:45:26.676 Chunk schedule #3 time [1158118200,1158119100] LOG_ID 150 records 8736 submitted
12:45:27.657 Chunk schedule #4 time [1158118200,1158119100] received from 0, records 7909
12:45:28.110 Chunk schedule #3 time [1158118200,1158119100] LOG_ID 150 written
12:45:29.026 Chunk schedule #4 time [1158118200,1158119100] LOG_ID 151 records 7909 submitted
12:45:29.156 Chunk schedule #2 time [1158118200,1158119100] received from 0, records 4609
12:45:30.185 Chunk schedule #4 time [1158118200,1158119100] LOG_ID 151 written
12:45:30.989 Chunk schedule #2 time [1158118200,1158119100] LOG_ID 152 records 4609 submitted

notice that value for time[] for schedule #1 (marked in bright orange) is 15 minutes BEFORE the time for the other schedules (see blue).

Could it be because there are 70000 records?

Schedule #7 has 50000 records but its timestamp is fine:

12:45:36.269 Chunk schedule #7 time [1158118200,1158119100] received from 0, records 56028
12:45:36.284 Chunk schedule #7 time [1158118200,1158119100] LOG_ID 153 records 56028 submitted
12:45:41.158 Chunk schedule #7 time [1158118200,1158119100] LOG_ID 153 written

why is it only agent report that is affected?

[Kim]

RG

It is hard to say why datasourcer is getting data 15 minutes out of sync but you still should have the right values during the timespan. As long as s/s is aware of the timespan, d/s will get the right data.

We have the same problem with d/s 7.2 as well.

Did you notice that d/s does not reconnect to statserver after network failure? (and yes addp is up and running)