Synchronizing the Multiplex Nodes

Check the SQL Remote and multiplex server log files for synchronization problems.

1. Start the multiplex server.
2. Start SQL Remote on all multiplex nodes.

   Give the multiplex time to propagate any changes throughout the multiplex. To do this, look at the write server console log file and check that the events starting with ev_iqmpx have successfully executed. By default, the server console log file is created in $ASDIR/logfiles.

   For example:

   Now accepting requestsOS Available: 933096K, Working Set: 83988K, Cache Target: 11483K
   OS Available: 860680K, Working Set: 83996K, Cache Target: 11483K
   Next time for 'ev_iqmpxq2w' is 2008/11/23 22:03:00.000
   Next time for 'ev_iqmpxstatus' is 2008/11/23 22:03:00.000
   OS Available: 859232K, Working Set: 84112K, Cache Target: 11489K
   OS Available: 861052K, Working Set: 84424K, Cache Target: 11489K
   OS Available: 860972K, Working Set: 84428K, Cache Target: 11489K
   OS Available: 850248K, Working Set: 85540K, Cache Target: 11579K
   OS Available: 850104K, Working Set: 85568K, Cache Target: 11579K
   Next time for 'ev_iqmpxq2w' is 2008/11/23 22:04:00.000
   Next time for 'ev_iqmpxstatus' is 2008/11/23 22:04:00.000
   OS Available: 850120K, Working Set: 85600K, Cache Target: 11579K
   Next time for 'ev_iqmpxq2w' is 2008/11/23 22:05:00.000
   Next time for 'ev_iqmpxstatus' is 2008/11/23 22:05:00.000
   OS Available: 852668K, Working Set: 85604K, Cache Target: 11579K

3. Wait for SQL Remote to scan the log files, then view the logs.
   Wait for SQL Remote to process any messages:

   I. 11/23 22:06:10. Scanning logs starting at offset 0001787252
   I. 11/23 22:06:10. Hovering at end of active log

4. Shut down SQL Remote and multiplex servers.
   If you simply shut down the multiplex servers, the SQL Remote servers detect that the multiplex servers are no longer running and shut themselves down. By default, the SQL Remote servers should shut themselves down within 60 seconds.
5. Shut down query servers in the multiplex. They are no longer required.
6. If the logs report no errors, verify the database.