Update the software of the database servers in a mirroring system by installing the software, stopping each server, and starting the database on the new server. All database servers in a database mirroring system must use the same minor release.
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.
Test the following steps in non-production environment with your application before performing the steps in a production environment.
Context and remarks
The mirroring system stops temporarily during the update.
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.
Stop the servers in the following order:
For example, run the Stop utility (dbstop):
dbstop -y -c "UID=DBA;PWD=sql;Server=myserver"
Install the new software on the primary, mirror, and arbiter servers.
Start the servers in the following order:
If the mirroring system is involved in read-only scale-out, install the software on the copy nodes, and then restart the copy nodes
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|