db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Spindler" <bspind...@netuitive.com>
Subject RE: master and slave are not in synch for replicated database
Date Wed, 08 Apr 2009 02:23:25 GMT
I've tried both:

connect 'jdbc:derby:<db>;shutdown=true';

and

exit; 

both seem to simply hang and I'm forced to do Ctrl+C to get back my command prompt.  Does
that sound right? 

regardless; both result in the same error.


-----Original Message-----
From: Dag H. Wanvik [mailto:Dag.Wanvik@Sun.COM]
Sent: Tue 4/7/2009 4:57 PM
To: Derby Discussion
Subject: Re: master and slave are not in synch for replicated database
 
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