Synchronization failed

Unanswered Question
Nov 2nd, 2008

"Synchronization failed because the LastUpdateKey on sideB is not present in the sideA Config Message Log.

The sideB Logger cannot come online duplexed because its database is out of date."

Please help we are not getting any reports and still logger is not writting

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
david.macias Sun, 11/02/2008 - 05:51

You've lost synchronization between both sides. Assuming you just didn't upgrade one side and forgot to upgrade the other, just do a database backup and restore the other side and you should be good to go.

david

rbua Tue, 01/20/2009 - 08:41

Hola Claudio,

you need to use ICMDBA select the working logger as a source and the failing as the receiver and do a synch.

Regards,

Riccardo

blackz88mobile Tue, 01/20/2009 - 08:19

Having not far from same problem - logger says that dbnextrow failed :-( any suggestions?

(Distributor process configlogger) -

connecting to database is okay then

Logger waiting for AW init to initialize the AW database... then

dbnextrow failed 5 times

...

db init procedure also failed if manual operation selected...

rbua Tue, 01/20/2009 - 08:42

Hi,

this is most likely a DB corruption, select the AWDB in ICMDBA, do a recreate, once the recreate is completed do a manual AW init, this should fix it.

Regards,

Riccardo

Actions

This Discussion