Synchronization failed

[ishaqkhan77]

"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

[david.macias]

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

[geoff]

This can be fixed. Contact TAC and they will provide the instructions.

Regards,

Geoff

[ishaqkhan77]

Thanks for all support of TAC its resloved.

[claudio_rivas]

Hi,

I'm currently on the same issue, both nodes are on same version... i think this is a time sinc problem, maybe a timezone change.

What was the solution with TAC on your case.

Regards,

Claudio.

[Riccardo Bua]

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

[claudio_rivas]

Hi Riccardo!

Thank you, your suggestions are the solution to the issue i was on. I think this is a time issue where time zones or clocks of both sides are not syncronized, and if you change the system timezone or clock causes the database from the loggers to be desyncronized.

Again thank you and regards.,

Claudio.

[eslam rizk]

I faced same error message ,
15:41:20:517 la-clgr Trace: LastUpdateKey for A Configuration is 8522334824045.0
15:41:20:517 la-clgr Trace: LastUpdateKey for B Configuration is 8523209299696.0
15:41:20:517 la-clgr The sideA Logger cannot come online in duplexed mode because its database is out of date
and issue solved by sync Side B to Side A Logger Database using ICMDBA Tool
Thanks alot

[blackz88mobile]

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...

[Riccardo Bua]

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

[blackz88mobile]

Many thanks! :-) It was a great idea!!! :-)

[joesnyde]

More than likely TAC had them resynch the loggers

http://www.cisco.com/en/US/products/sw/custcosw/ps1001/products_tech_note09186a00803ec363.shtml