You can perform various operations to alter servers from the server property sheet in Sybase Central or using Interactive SQL. The coordinator must be running. Although you can run the ALTER MULTIPLEX SERVER command from any server in the multiplex, it is recommended that, like all DDL, commands be run on the coordinator.In all cases except when altering role from reader to writer, the named server is automatically shut down once the change is committed.
Renaming servers (Sybase Central)
Open the server property sheet.
Change the server name on the Configuration tab.
Renaming servers (Interactive SQL)
Start the server, connect to it, and issue a command in the following format:
ALTER MULTIPLEX SERVER oldname RENAME newname
This command renames and shuts down the named server. For complete syntax, see “ALTER MULTIPLEX SERVER statement”.
Changing database file path (Sybase Central)
Open the server’s property sheet.
On the Configuration tab, change the database file path.
Changing database file path (Interactive SQL)
Start the server, connect to it, and issue a command in the following format:
ALTER MULTIPLEX SERVER server name DATABASE 'new db file path'
This command also shuts down the named server.
Changing server role (Sybase Central)
Open the server property sheet.
On the General tab, change the server role (reader/writer).
Changing server role (Interactive SQL)
Start the server, connect to it, and issue a command in the following format:
ALTER MULTIPLEX SERVER server name ROLE {WRITER|READER}
You cannot change the role of coordinator. Changing a write server to a reader automatically shuts down the server.
Changing host/port (Sybase Central)
Open the server’s property sheet.
On the Configuration tab, change the host/port information.
Changing host/port (Interactive SQL)
Start the server, connect to it, and issue a command in the following format:
ALTER MULTIPLEX SERVER server name HOST 'hostname' PORT portnumber
This command also shuts down the named server.
Including or excluding servers (Sybase Central)
If a multiplex secondary server will be shut down for an extended period of time, that server should be excluded. Excluding the server allows the coordinator to ignore this server when performing version cleanup. Otherwise, the coordinator will need to reserve all old versions of IQ objects since the secondary node was shut down. This takes up unnecessary disk space. A designated failover server cannot be excluded unless it is the last secondary node to be excluded in the multiplex. Include/exclude does not apply to the coordinator.
Open the server property sheet.
On the General tab, include or exclude the server.
An alternate method is to right-click the server and select context menu Control > Include/Exclude.
Including or excluding servers (Interactive SQL)
Start the server, connect to it, and issue a command in the following format:
ALTER MULTIPLEX SERVER server name STATUS {INCLUDED|EXCLUDED}
If the target server is running, it is strongly recommended that you shut it down before excluding it. In case you do not, it will eventually shut itself down, but it is better that you plan for and shut it down prior to excluding it. Excluding a server shuts it down. After including a server, the server must be synchronized and then started.
Designating failover node (Sybase Central)
Right-click the Multiplex Name in the Sybase Central tree view.
Choose Designate Failover.
Designating failover node (Interactive SQL)
Start the server, connect to it, and issue a command in the following format:
ALTER MULTIPLEX SERVER server name ASSIGN AS FAILOVER SERVER
The designated failover node defaults to the first multiplex server added to the multiplex.
See also “Failover”.