Synchronize and shutdown multiplex query nodes

When you migrate a multiplex database, check the SQL Remote and multiplex server log files for synchronization problems.

StepsCorrecting synchronization problems

  1. Start the multiplex server.

  2. If it is not already, start SQL Remote on all nodes in the multiplex. These are normally started by Sybase Central when starting servers.

  3. 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
    
  4. Wait for SQL Remote to scan its log files a few times and view the logs. To view these log files from Sybase Central, right-click the multiplex server and select SQL Remote | View SQL Remote Log.

    The console indicates that SQL Remote is hovering at the end of the active log. Wait for SQL Remote to process any messages. For example:

    I. 11/23 22:06:10. Scanning logs starting at offset 0001787252
    I. 11/23 22:06:10. Hovering at end of active log
    
  5. Shut down SQL Remote and multiplex servers. If you simply shut down the multiplex servers, the SQL Remote servers will hover, then 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.

  6. Shut down query servers in the multiplex. They are no longer required.

  7. If the logs report no errors, verify the database. See “Verify the 12.x databases before migration”.