db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r644015 - in /db/derby/docs/trunk/src: adminguide/cadminreplicstartrun.dita ref/rrefattribstartmaster.dita
Date Wed, 02 Apr 2008 19:36:47 GMT
Author: chaase3
Date: Wed Apr  2 12:36:45 2008
New Revision: 644015

URL: http://svn.apache.org/viewvc?rev=644015&view=rev
Log:
DERBY-3169: Add documentation for replication

Added information about unlogged operations described in DERBY-3551 and 
information about installed jar files described in DERBY-3552 to 
rrefattribstartmaster.dita and cadminreplicstartrun.dita topics.

Patch: DERBY-3169-7.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=644015&r1=644014&r2=644015&view=diff
==============================================================================
--- db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita (original)
+++ db/derby/docs/trunk/src/adminguide/cadminreplicstartrun.dita Wed Apr  2 12:36:45 2008
@@ -69,7 +69,12 @@
 jdbc:derby:wombat;startMaster=true;slaveHost=myremotesystem
 </codeblock>
 A successful use of the <i>startMaster=true</i> attribute will also unfreeze
the
-database.</li>
+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>
 </ol>
 <p>See the <ph conref="../conrefs.dita#pub/citref"></ph> for details about
these
 attributes.</p>
@@ -88,5 +93,19 @@
 either the slave or the master database. There is one exception to this rule:
 if the entire system is shut down, the peer that is shut down notifies the other
 replication peer that replication is stopped.</p>
+<p>If you install jar files on the master system while replication is running,
+the same jars are not automatically installed on the slave. But because the
+transaction log information sent to the slave system includes the jar file
+installation, the slave database has a record of the jar files, even though they
+are not actually there. Therefore, you must install the jar files on the former
+slave after a failover by calling either <codeph>SQLJ.remove_jar</codeph>
+followed by <codeph>SQLJ.install_jar</codeph>, or
+<codeph>SQLJ.replace_jar</codeph>. (For information on installing jar files,
see
+"Storing jar files in a database" in the
+<ph conref="../conrefs.dita#pub/citutilities"></ph>.)</p>
+<p>If the jar files must be available to clients immediately after a failover,
+you must stop replication and then start replication over again from the
+beginning, so that the slave database will have the same jar files as the
+master.</p>
 </conbody>
 </concept>

Modified: db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita?rev=644015&r1=644014&r2=644015&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefattribstartmaster.dita Wed Apr  2 12:36:45 2008
@@ -31,10 +31,21 @@
 </metadata></prolog>
 <refbody>
 <section><title>Function</title>
-<p>Starts replication of a database in master mode. The specified database must
-have been created before you specify this attribute.</p>
-<p>For more information, see the topics under "Replicating databases" in the
-<ph conref="../conrefs.dita#pub/citadmin"></ph>.</p>
+<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
+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>For more information on replication, see the other topics under
+"Replicating databases" in the <ph conref="../conrefs.dita#pub/citadmin"></ph>.</p>
 </section>
 <section><title>Combining with other attributes</title>
 <p>You must specify a database name in the connection URL, either in the



Mime
View raw message