ALTER MULTIPLEX SERVER server-name server-option
server-option:{ RENAME new-server-name | DATABASE 'dbfile' | ROLE { WRITER | READER | COORDINATOR } | STATUS { INCLUDED | EXCLUDED } | ASSIGN AS FAILOVER SERVER | host-port-list }
host-port-list: { HOST ' hostname ' PORT port number }
RENAME Changes the name of the given server. The server automatically shuts down. The next restart requires the new name.
DATABASE Changes the catalog file path for the given server. The server will automatically shutdown and next time it should be started using new catalog path. Its user's responsibility (Sybase central might hide it) to relocate the catalog file itself.
ROLE Changes the role of the given server. Users are not allowed to change the role of coordinator or role to coordinator. If the writer node's role is changed to reader, the server shuts down.
STATUS Changes the status of the given server. A failover node cannot be excluded unless it is the last node to be excluded. The server automatically shuts down after exclusion. After including a node, you must be synchronize and restart it.
ASSIGN Designates the given server as the new failover server. The node should not be in the excluded state. The ASSIGN AS FAILOVER clause is a standalone clause that cannot be used with any other ALTER MULTIPLEX SERVER clause.
The coordinator must be running, but you can run the ALTER MULTIPLEX SERVER command from any server in the multiplex. (Sybase recommends that all DDL statements be run on the coordinator.) In all cases except when altering role from reader to writer, the named server is automatically shut down.
Exclude secondary server mpx_writer1:
ALTER MULTIPLEX SERVER mpx_writer1 STATUS EXCLUDED
It is recommended that the target server be shutdown
before you exclude it. If you do not, an excluded server will automatically
shut down and requires ALTER MULTIPLEX SERVER server-name STATUS INCLUDED and
a synchronize to rejoin the multiplex.
Must have DBA authority.
