db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oskar Zinger <oska...@yahoo.com>
Subject Re: Upgrade from to
Date Tue, 05 Nov 2013 17:32:50 GMT
Hi Kathey,

Nope that does not seem to help.


On Tuesday, November 5, 2013 11:54 AM, Katherine Marsden <kmarsdenderby@sbcglobal.net>
On 11/5/2013 8:46 AM, Oskar Zinger wrote:

>I'm in the process of upgrading to
>Once I did the upgrade, the Derby replication no longer works. It now complains about
the Databases being not in synch.
>This same code was working just fine in, but does not work in
>Anyone experienced this?
>This is the error I'm getting:
>java.sql.SQLNonTransientConnectionException: DERBY SQL error: ERRORCODE: 40000, SQLSTATE:
XRE05, SQLERRMC: The log files on the master and slave are not in synch for replicated database
'ImpactDB'. The master log instant is 1:980936, whereas the slave log instant is 1:846980.
This is fatal for replication - replication will be stopped.
I am not familiar with replication, but wonder if it is a
    requirement of upgrade to do a clean shutdown of the database before
    upgrading the jars or if that would at least help you work around
    the problem.  I couldn't find anything in the documentation though
    requiring special procedures for upgrade with replication.  

View raw message