Replication error on Logger Side A in the purge cycling

[lee yongbeom]

what's happen?

At the replication process error,  the issue occures like below.

Seeing that the time, maybe It's occures in the purge cycle.

[Version Information]

ICM 8.5.3

00:30:00:925 la-rpl Trace: Server is returning a STARTING POINT for table t_Trunk_Group_Half_Hour with FromRecoveryKey = -1.0 and ToRecoveryKey = 6267243305987.0

00:30:02:784 la-rpl Trace: Server is returning a STARTING POINT for table t_Route_Call_Detail with FromRecoveryKey = -1.0 and ToRecoveryKey = 6267243500191.0

00:30:15:597 la-rpl Trace: No MATCHING Recovery Request for table t_Trunk_Group_Half_Hour, FromRecoveryKey = 6267243305987.0 and ToRecoveryKey = 6267243305987.0

00:30:19:784 la-rpl Trace: No MATCHING entry for table t_Route_Call_Detail, FromRecoveryKey = 6267243500191.0 and ToRecoveryKey = 6267243500191.0

00:30:36:784 la-rpl Trace: No MATCHING entry for table t_Route_Call_Detail, FromRecoveryKey = 6267243500191.0 and ToRecoveryKey = 6267243500191.0

00:30:53:784 la-rpl Trace: No MATCHING entry for table t_Route_Call_Detail, FromRecoveryKey = 6267243500191.0 and ToRecoveryKey = 6267243500191.0

00:31:10:784 la-rpl Trace: No MATCHING entry for table t_Route_Call_Detail, FromRecoveryKey = 6267243500191.0 and ToRecoveryKey = 6267243500191.0

00:31:27:784 la-rpl Trace: No MATCHING entry for table t_Route_Call_Detail, FromRecoveryKey = 6267243500191.0 and ToRecoveryKey = 6267243500191.0

00:31:44:784 la-rpl Trace: No MATCHING entry for table t_Route_Call_Detail, FromRecoveryKey = 6267243500191.0 and ToRecoveryKey = 6267243500191.0

[Gergely Szabo]

Hi,

it's kind of normal. The above messages mean that the Logger does not see some entries in the HDS tables, and it is copying those missing entries.

It's quite possible you are facing some replication issues. I've seen this before but it just got solved by itself.

G.

[lee yongbeom]

Hi,

Thanks for reply.

Because of replication issuses, the data not transfer into the DAW server.

so I'm recycle the logger process for resolving the issue.

Is this case bugs?

[Gergely Szabo]

Hi,

I guess so. Or a misconfiguration.

What I remember it started happening when I played around the purge schedule on the AW/HDS.

I did not feel the need to talk to Cisco because it happened twice only for the last year and it's something I can live with.

G.