db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: master and slave are not in synch for replicated database
Date Tue, 07 Apr 2009 20:57:10 GMT
Brian Spindler <bspindler@netuitive.com> writes:

> Guys/Gals,
>
>  
>
> I have taken the following procedure:
>
>  
>
> 1.       Using ij logged into my database
>
> 2.       Run CALL SYSCS_UTIL.SYSCS_FREEZE_DATABASE();

I saw in another thread you use embedded. Did you do a shutdown at
this point?
E.g. connect 'jdbc:derby:<db>;shutdown=true'

>
> 3.       Exit ij
>
> 4.       Copy database to slave
>
> 5.       Start slave
>
> 6.       Start master.
>
>  
>
> Then I get this error: 
>
>  
>
> Caused by: ERROR XRE05: The log files on the master and slave are not in
> synch for replicated database 'foo'. The master log instant is 1:104173,
> whereas the slave log instant is 1:103957. This is FATAL for replication
> - replication will be stopped.
>
>                 
>
>  
>
> I thought by freezing/copying etc... they would be in synch?
>
>  
>

-- 
Dag H. Wanvik, staff engineer
Sun Microsystems, Databases (JavaDB/Derby)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101

Mime
View raw message