If you specify the failover=true attribute on the master, the attribute sends the remaining log records to the slave instance and then sends a failover message to the slave. The replication functionality and the database are then shut down on the master system. If failover is successful, an exception with the error code XRE20 is thrown. Hence, when issued on the master, the failover=true attribute does not return a valid connection.
You may specify this attribute on the slave only if the network connection between the master and the slave is down.
When you specify this attribute on the slave, or when a failover message is sent as part of the execution of the failover=true attribute on the master, all transaction log chunks that have been received from the master are written to disk. The slave replication functionality is shut down, and the boot process of the database is allowed to complete. The database is now in a transaction consistent state, reflecting all transactions whose commit log records were received from the master. When issued on the slave, the failover=true command returns a valid connection.
The
For more information, see the topics under "Replicating databases" in the
You must specify a database name in the connection URL, either in the
subprotocol or by using the
If authentication is turned on, you must also specify
this attribute in conjunction with the
You may not specify this attribute in conjunction with any attributes not mentioned in this section.