The process that updates a secondary server with respect to the coordinator is called synchronization.
Synchronizing copies the coordinator's version of the database catalog to a single secondary server. The multiplex automatically makes committed changes, including global schema changes, changes to data in IQ tables visible on all servers in the multiplex. In general, Sybase IQ propagates DDL and DML changes to secondary servers, so you only need to synchronize a secondary server for these server management actions:
While creating a new secondary server
Restoring the coordinator from backup
Restarting a secondary server that has been excluded or shut down for an extended time period
After running the coordinator in single-node mode
After adding a file to the IQ_SYSTEM_MAIN dbspace
Synchronizing individual
secondary servers (Sybase Central)
Make sure that the coordinator is running, and connect to it with Sybase Central.
To synchronize a secondary server, right-click that server and choose Control > Synchronize. You can keep running queries on the other servers.
Sybase Central stops the secondary server that you right-clicked, replaces its catalog store, then restarts the server. The coordinator continues running throughout the operation.
Synchronizing multiple servers (Sybase Central)
To synchronize multiple servers:
Right-click the Multiplex folder to launch the synchronization wizard.
Select Control > Synchronize context menu item.
In the wizard page, select the servers to synchronize.
Synchronizing servers
(command line)
Perform the following steps on the computer where the secondary server runs.
If you checked “Generate Admin Scripts” when creating the multiplex server in Sybase Central, you can run the sync_server script instead of dbbackup.
Remove the .LOG transaction log file in the secondary server directory.
Back up the catalog store to the directory where the secondary server runs:
dbbackup -y -d -c "uid=dba;pwd=sql;links=tcpip{port=2763};eng=mpxnode_c" /host1/mpx/
Set the log file path:
dblog -r -t mpxtest.log mpxtest.db
Start the secondary node using the start_iq command.
Repeat the previous steps for each secondary server in the multiplex.
