dbsrv16 [ server-options ] database-file -sm alternate-server-name

• All operating systems
• Network server only.

The alternate-server-name is only active when the database server is acting as mirror for the database. By using the -sm and -sn command-line options, an application can always connect to the database on the primary or the mirror server, without knowing which physical server is acting as primary or mirror.

The -sm database option must be specified after the database-file, and applies only to that database.

• CREATE MIRROR SERVER statement
• Connecting to a database in a mirroring system
• -xa database server option
• -xf database server option
• -xp database option
• START DATABASE statement
• Database mirroring
• Server Enumeration utility (dblocate)
• ReadOnly database property

The following command starts the databases satest.db and sample.db on a database server named myserver. The -sn option instructs the database server to use mysampleprimary as an alternate server name when connecting to sample.db, while the -sm option instructs the database server to use mysamplemirror as an alternate server name to connect to sample.db, running on the mirror server.

dbsrv16 -n myserver satest.db sample.db -sn mysampleprimary 
-sm mysamplemirror -xp "partner=( Server=server2;LINKS=TCPIP( PORT=2637;TIMEOUT=1 ) );
auth=abc;arbiter=( Server=arbiter;LINKS=TCPIP( PORT=2639;TIMEOUT=1 ) );mode=sync" 
-xf "c:\arbiter\arbiter.state"

You can connect to sample.db while it is running on the primary server using any of the following connection parameters:

• Server=myserver;DBN=sample
• Server=mysampleprimary
• Server=mysampleprimary;DBN=sample

You cannot connect to satest.db using Server=mysampleprimary.

You can connect to sample.db while it is running on the mirror server using any of the following connection parameters:

• Server=myserver;DBN=sample
• Server=mysamplemirror
• Server=mysamplemirror;DBN=sample

You cannot connect to satest.db using Server=mysamplemirror.