Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 81656 invoked from network); 7 Apr 2009 20:56:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Apr 2009 20:56:00 -0000 Received: (qmail 73039 invoked by uid 500); 7 Apr 2009 20:56:00 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 72969 invoked by uid 500); 7 Apr 2009 20:56:00 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 72961 invoked by uid 99); 7 Apr 2009 20:56:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Apr 2009 20:56:00 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=FS_REPLICA,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-inf-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Apr 2009 20:55:50 +0000 Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n37KtTQW004638 for ; Tue, 7 Apr 2009 20:55:29 GMT MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KHR001000QL7F00@fe-emea-10.sun.com> for derby-user@db.apache.org; Tue, 07 Apr 2009 21:55:29 +0100 (BST) Received: from khepri23.norway.sun.com ([unknown] [129.159.112.235]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KHR009IS0SGOJ00@fe-emea-10.sun.com> for derby-user@db.apache.org; Tue, 07 Apr 2009 21:55:29 +0100 (BST) Date: Tue, 07 Apr 2009 22:55:28 +0200 From: Dag.Wanvik@Sun.COM (Dag H. Wanvik) Subject: Re: master and slave are not in synch for replicated database In-reply-to: <8CE9C7FC34485B41B9A6B7459DFED80802B9BD1A@MI8NYCMAIL03.Mi8.com> Sender: Dag.Wanvik@Sun.COM To: Derby Discussion Message-id: References: <8CE9C7FC34485B41B9A6B7459DFED80802B9BD1A@MI8NYCMAIL03.Mi8.com> User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.1 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Brian Spindler writes: > Guys/Gals, > > > > I have taken the following procedure: > > > > 1. Using ij logged into my database > > 2. Run CALL SYSCS_UTIL.SYSCS_FREEZE_DATABASE(); Do you run embedded or client server? Are there any other live connections at this point? > > 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? >