Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere 16 - Changes and Upgrading » How to upgrade to SQL Anywhere 16 » Upgrades and rebuilds in a database mirroring system


Updating the database server software to a Support Package for database mirroring system without rebuilding the database

Update the software of the database servers in a mirroring system by stopping each server, installing the software, and then restarting the database on the new server.


You must have the BACKUP DATABASE system privilege. You must be the owner of the database, or have the VALIDATE ANY OBJECT system privilege.

By default, you must have the SERVER OPERATOR system privilege to stop network database servers.

Context and remarks

Because you can stop servers in the system one at a time, the mirroring system can continue to run during a Support Package update of the server software. A failover from the primary server to the mirror server occurs at least once during the update process. Connections to the primary and mirror server drop during any failover.

Test the following steps in non-production environment with your applications before performing the steps in a production environment.

 Apply a Support Package to a database mirroring system
  1. Make a backup of the primary database, copy the backup, and validate the copy of the backup.

    For example, run the following command to back up a database named mydb.db:

    dbbackup -c "DBN=mydb;ENG=myserver;UID=DBA;PWD=sql" backup-dir

    Create a copy of the backup:

    xcopy backup-dir\*.db validatebackup-dir\backupmydb.db

    Validate the backup copy:

    dbvalid -c "DBF=validatebackup-dir\backupmydb.db;UID=DBA;PWD=sql"

    If the copy of the backup does not validate, then fix the problems that cause the validation to fail before proceeding. Otherwise, you risk losing data.

  2. If the mirroring system is part of a read-only scale-out system, then for each copy node:

    1. Stop the copy node server.

    2. Install the software.

    3. Start the copy node.

  3. Stop the mirror server.

  4. Install the software on the mirror server.

  5. Start the mirror server and ensure that it is in a synchronized state.

  6. Stop the arbiter server.

  7. Install the software on the arbiter.

  8. Start the arbiter server.

  9. Initiate a fail over by connecting to the primary database and executing the following statement:


    Connections to the primary and mirror drop during the failover. The current primary becomes the mirror.

  10. Stop the mirror server.

  11. Install the software on the mirror server.

  12. Start the mirror server and ensure that it is synchronized.


The databases in the mirroring system run on the new version of the software.


Examine the database mirroring system to confirm that the upgrade completed properly, and test the database mirroring system with your application.

 See also