db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r793902 - in /db/derby/docs/trunk/src: adminguide/cadminreplicstartrun.dita ref/rrefattribstartmaster.dita
Date Tue, 14 Jul 2009 13:52:21 GMT
Author: chaase3
Date: Tue Jul 14 13:52:21 2009
New Revision: 793902

URL: http://svn.apache.org/viewvc?rev=793902&view=rev
Log:
DERBY-4196: Document initiation of replication from cleanly shut down database

Corrected instructions in two topics.

Patch: DERBY-4196.diff

Modified:
    db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita
    db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita

Modified: db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita?rev=793902&r1=793901&r2=793902&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita Tue Jul 14 13:52:21 2009
@@ -32,24 +32,12 @@
 immediately after the database is created; it can be initiated at any time after
 the database is created.
 </p>
-<p>Before you start replication, you must boot the master database and then
-copy the database to the slave location. To ensure that the master database
-is not modified between the time you start the file-system copy and the time
-you start replication, you must freeze the master database. Follow these
+<p>Before you start replication, you must shut down the master database and then
+copy the database to the slave location. Follow these
 steps to start replication:
 </p>
 <ol>
-<li>Boot the database on the master system.</li>
-<li>When you are ready to start replication, freeze the master database by
-calling the <codeph>SYSCS_UTIL.SYSCS_FREEZE_DATABASE</codeph> procedure, as
-shown in the following example:
-<codeblock>CallableStatement cs = conn.prepareCall
-("CALL SYSCS_UTIL.SYSCS_FREEZE_DATABASE()");
-cs.execute();
-cs.close();</codeblock>
-This procedure ensures that all data pages and the log are written to disk,
-and blocks modifications to the database until replication has successfully
-started.</li>
+<li>Make sure that the database on the master system is shut down cleanly.</li>
 <li>Copy the database to the slave location.</li>
 <li>Start slave replication mode on the Derby instance that is acting
 as the slave for the database. To start slave replication, use the
@@ -68,13 +56,9 @@
 <codeblock>
 jdbc:derby:wombat;startMaster=true;slaveHost=myremotesystem
 </codeblock>
-A successful use of the <i>startMaster=true</i> attribute will also unfreeze
the
+A successful use of the <i>startMaster=true</i> attribute will also start the
 database.
-<p>If any unlogged operations are running when the user specifies
-<i>startMaster=true</i>, the attempt to start the master fails and an error
-message appears. The message instructs the user to unfreeze the database to
-allow the operations to complete, and then to specify <i>startMaster=true</i>
-again.</p></li>
+</li>
 </ol>
 <p>See the <ph conref="../conrefs.dita#pub/citref"></ph> for details about
these
 attributes.</p>

Modified: db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita?rev=793902&r1=793901&r2=793902&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita Tue Jul 14 13:52:21 2009
@@ -32,18 +32,16 @@
 <refbody>
 <section><title>Function</title>
 <p>Starts replication of a database in master mode. Before you specify this
-attribute, you must boot the database on the master system, freeze it, perform a
+attribute, you must cleanly shut down the database on the master system, perform a
 file system copy of the database to the slave system, and specify the
 <i><xref
 href="rrefattribstartslave.dita#rrefattribstartslave">startSlave=true</xref></i>
 attribute. For details, see the topic "Starting and running replication" under
 "Replicating databases" in the <ph conref="../conrefs.dita#pub/citadmin"></ph>.
 </p>
-<p>If any unlogged operations are running when the user specifies
-<i>startMaster=true</i>, the attempt to start the master fails and an error
-message appears. The message instructs the user to unfreeze the database to
-allow the operations to complete, and then to specify <i>startMaster=true</i>
-again.</p>
+<p>If the master database is already booted and any unlogged operations are
+running when the user specifies <i>startMaster=true</i>, the attempt to start
+the master fails and an error message appears.</p>
 <p>For more information on replication, see the other topics under
 "Replicating databases" in the <ph conref="../conrefs.dita#pub/citadmin"></ph>.</p>
 </section>



Mime
View raw message