-- start slave using database name in subprotocol, default slave host
-- and port, authorization
jdbc:derby:myDB;startslave=true;user=mary;password=little88lamb

-- start slave using databaseName attribute, non-default slave host
-- and port, no security
jdbc:derby:;databaseName=myDB;startSlave=true;slaveHost=localhost;
slavePort=4852

stopMaster=true attribute

Function

Stops database replication on the master system. This attribute sends a stop-slave
message to the slave system if the network connection is working. Then it shuts down all
replication-related functionality, without shutting down the specified database.

The Derby instance where this attribute is specified must be the replication master for the
specified database.

For more information, see the topics under "Replicating databases" in the Derby Server
and Administration Guide.

Combining with other attributes

You must specify a database name in the connection URL, either in the subprotocol or by
using the

databaseName=nameofDatabase

attribute.

If authentication is turned on, you must also specify this attribute in conjunction with the

user=userName

and

password=userPassword

attributes. If both authentication and SQL

authorization are turned on, the user must be the database owner.

You may not specify this attribute in conjunction with any attributes not mentioned in this
section.

Examples

-- stop master using database name in subprotocol, authorization
jdbc:derby:myDB;stopMaster=true;user=mary;password=little88lamb

-- stop master using databaseName attribute, no security
jdbc:derby:;databaseName=myDB;stopMaster=true;

stopSlave=true attribute

Function

Stops database replication on the slave system.