repserver

The Replication Server executable program.

Syntax

{repserver | repsrvr} [-C config_file] [-i id_server] 
[-S rs_name] [-I interfaces_file] 
[-E errorlog_file] [-M] [-v] [-K keytab_file]
[-k rs_principal_name]
[-upgr] [-Aerssd_release_dir] [-purgeq] 
[–nodb {all|dbid_1[,dbid_2[,dbid_3[,…]]]]} 
[-e]

Parameters

-C config_file – specifies the name and location of the Replication Server configuration file. The rs_init program creates a configuration file which, by default, is named Rep_Server_name.cfg, where Rep_Server_name is the name of the Replication Server. You can specify this file name by using the -C flag. If you do not use the -C flag, repserver looks for the configuration file named config.rs in the directory where you started the Replication Server.
-i id_server – specifies the name of the ID Server for the replication system. The ID Server must be the first Replication Server started. It must be running and accessible before you can start a new Replication Server. The name of the ID Server is stored in the configuration file. Use the -i option to specify a different ID Server.
-S rs_name – the name to use for the current Replication Server. If network-based security and unified login are enabled, specifies the name of the principal user.
-I interfaces_file – specifies the name and location of the interfaces file where the Replication Server is defined. The interfaces file must also have entries for the data servers and other Replication Servers that the current Replication Server communicates with. Interfaces files at replicate sites must have entries for the primary Replication Server and the primary data server. If you do not use the -I flag, Replication Server looks for the default interfaces file in the Sybase release directory.
Refer to the Replication Server installation and configuration guides for your platform for more information about the interfaces file, including the default interfaces file name for your platform.
-E errorlog_file – specifies the name and location of the Replication Server error log file, into which repserver writes error messages. If you do not use the -E flag, the default error log file name and location is repserver.log in the directory where you started the Replication Server.
-M – starts the Replication Server in standalone mode, which is used to initiate recovery actions. See the Replication Server Administration Guide Volume 2 for more information about running Replication Server in standalone mode.
-v – prints the version number of the Replication Server.
-K keytab_file – specifies the name and location of the DCE keytab file that contains the security credential for the user logging into the server. You can create keytab files with the DCE dcecp utility. See your DCE documentation for more information.
Note: Use the -K keytab_file option only for Windows platform and only with DCE network security.
-k rs_principal_name – specifies the Replication Server principal name that is authenticated with the Kerberos key distribution center (KDC).
Note: When you start Replication Server with the Kerberos security mechanism enabled, Replication Server first uses the principal name specified with the –k rs_principal_name option for Kerberos authentication. If the -k rs_principal_name option is not specified, Replication Server looks for the principal name set in the SYBASE_RS_PRINCIPAL environment variable. If neither is specified, Replication Server uses the server name for authentication.

See Specifying the Replication Server Principal Name in the Replication Server Administration Guide: Volume 1.
-upgr – instructs Replication Server to start in upgrade mode
-A erssd_release_directory – specifies the location of the release directory of the ERSSD that you are going to upgrade if Replication Server is using an ERSSD. For example, on:
- UNIX – /sybase/REP-15_5/ASA11
- Windows – c:\sybase\REP-15_5\ASA11
If you do not include the -A option, Replication Server obtains the release directory location from the Replication Server configuration file if the configuration file contains the information. Replication Server ignores the release directory location in the configuration file if you specify the -A option because what you specify manually in the repserver or repsrvr.exe command overrides the configuration file settings.
-purgeq – purges transactions from the inbound queue. You must use this option if you are upgrading from a version of Replication Server earlier than 15.5.
-nodb all – excludes all user databases from the upgrade process
-nodb dbid_1[,dbid_2[,dbid_3[,...]]] – excludes specific databases from the upgrade process. Separate multiple database IDs with a comma and do not include a space between the IDs. For example:
```
repserver –upgr . . .  -A . . .  -nodb 101,102,105
```
-e – records the SQL statements that Replication Server sends to data servers when you enter the -upgr parameter for upgrading. Without the -e option, there is no record of the SQL statements generated. With or without the -e option, the upgrade process uses the Replication Server error log file to record the current configuration parameter settings stored in the rs_config table before the upgrade starts, any errors that occur during the upgrade process, and why any user database was not upgraded. See the error log file to restore the former settings if you need to downgrade.

Examples

Example 1 – Starts the Replication Server named TOKYO_RS, using the configuration file TOKYO_RS.cfg.
```
repserver -STOKYO_RS -CTOKYO_RS.cfg
```
Example 2 – Starts the Replication Server named SYDNEY_RS, using the configuration file SYDNEY_RS.cfg. TOKYO_RS is the ID Server for the replication system.
```
repserver -SSYDNEY_RS -CSYDNEY_RS.cfg -iTOKYO_RS
```
Example 3 – Starts Replication Server and specifies an interfaces file, my_newinterfaces, that overrides a default interfaces file or LDAP directory service.
```
repserver -STOKYO_RS _CTOKYO_RS.cfg 
	-I$SYBASE/SYBASE_RS/my_newinterfaces
```
Example 4 – Starts the NY_RS Replication Server, and upgrades it using the /sybase/REP-15_5/ASA11 ERSSD release directory location, RSSD ny_rs.cfg configuration file, my_newinterfaces interfaces file, and ny_rs_errorlog error log file:
```
repserver –upgr –SNY_RS –A/sybase/REP-15_5/ASA11 –Cny_rs.cfg –Imy_newinterfaces –E ny_rs_errorlog 
```

Usage

Use repserver in UNIX or repsrvr.exe in Windows to start the Replication Server executable program. Normally, you start Replication Server by executing the run file created by rs_init. For convenience, repserver refers to the command on both platforms.
The repserver executable program is located in the bin subdirectory of the Sybase release directory. Refer to the Replication Server installation and configuration guides for your platform for more information.
The repserver command should be executed by the “sybase” user so that the Replication Server can access its disk partitions.
The interfaces file must contain definitions of the other Replication Servers and data servers that the current Replication Server communicates with. Interfaces files at replicate sites must have entries for the primary Replication Server and the primary data server.
If a password is stored in encrypted form, you cannot edit it directly by editing the Replication Server configuration file. To change an encrypted password in this file, use the rs_init program. Refer to the Replication Server installation and configuration guides for your platform for more information.
The RSSD_primary_user and the RSSD_maint_user are automatically assigned to the rs_systabgroup group by rs_init at Replication Server configuration time. This enables these users to modify the system tables. You can add other user login names to this group with the Adaptive Server system procedure sp_changegroup. See the Adaptive Server Enterprise System Administration Guide for more information.
If any of the network-based security parameters for the RSSD are present, the use_security_services parameter is set “on” and network-based security is initiated automatically.
Use the -upgr parameter when you are upgrading Replication Server. You can only use the -A, -purgeq, -nodb, and -e options when you use -upgr. See Upgrading RSSD or ERSSD and User Databases with repserver in the Replication Server Configuration Guide.
Use the -k rs_principal_name option to specify the Replication Server principal name.

Replication Server Configuration File Parameters
Configuration parameter	Description
`CONFIG_charset`	The character set used to write the Replication Server configuration file. Use this parameter only if this character set differs from the Replication Server’s character set. It can be any character set that is compatible with the Replication Server’s character set.
`erssd_backup_dir`	ERSSD backup directory.
`erssd_dbfile`	ERSSD database file.
`erssd_errorlog`	ERSSD error log.
`erssd_logmirror`	ERSSD transaction log mirror file.
`erssd_ping_cmd`	Allows user to specify a different command to ping ERSSD. For debug purposes only.
`erssd_port`	ERSSD port number for network listener. The port number is obtained from the interface file.
`erssd_release_dir`	Allows user to specify a different release directory. For debug purposes only. The default is $SYBASE/$SYBASE_REP/ASA11.
`erssd_ra_release_dir`	Allows a user to specify a different release directory for ERSSD Replication Agent. For debug purposes only.
`erssd_ra_start_cmd`	Allows user to specify a different command to start ERSSD Replication Agent. For debug purposes only.
`erssd_start_cmd`	Allows user to specify a different command to start ERSSD. For debug purposes only.
`erssd_translog`	ERSSD transaction log file.
`ID_pw`	The password for the ID Server user (`ID_user`).
`ID_pw_enc`	The encrypted password for the ID Server user (`ID_user`).
`ID_server`	The name of the Replication Server that is the designated ID Server for the replication system.
`ID_user`	The login name on the ID Server for other Replication Servers to use.
`RS_charset`	The character set for the Replication Server to use. You can specify any Sybase-supported character set. In setting up a replication system, it is highly recommended, though not required, that all servers at a given Replication Server site use the same character set. It is also recommended that all of the Replication Servers in your replication system use compatible character sets. Refer to the Replication Server Design Guide for details.
`RS_language`	The language used by the Replication Server to print its messages to the error log file and to its clients. You can specify any language to which the Replication Server has been localized that is compatible with the character set chosen.
`RS_send_enc_pw`	Ensures that all Replication Server client connections are made with encrypted passwords except for the first connection to the RSSD. Values are on and off. Default: off
`RS_sortorder`	The sort order that Replication Server uses. The sort order controls what rows of a table belong in a subscription that has a where clause involving character data. It also controls how identifiers you enter are recognized. You can specify any Sybase-supported sort order that is compatible with the character set chosen. All sort orders in your replication system should be the same.
`RS_unicode_sort_order`	The Unicode sort order Replication uses. You can specify any Sybase-supported Unicode sort order. Default: binary
`RSSD_database`	The name of the RSSD.
`RSSD_embedded`	Indicates whether RSSD is embedded or not.
`RSSD_ha_failover`	Specifies whether HA failover is allowed or not. Default: No.
`RSSD_maint_pw`	The password for the RSSD maintenance user.
`RSSD_maint_pw_enc`	The encrypted password for the RSSD maintenance user.
`RSSD_maint_user`	The login name for the RSSD maintenance user. This login name is automatically assigned to the `rs_systabgroup` group, whose users can modify the system tables. You can add other user login names to this group with the Adaptive Server system procedure sp_changegroup. See the Adaptive Server Enterprise System Administration Guide for more information.
`RSSD_msg_confidentiality`	Specifies whether Replication Server sends and receives encrypted data. If set to “required”, outgoing and incoming data must be encrypted. If set to “not_required”, outgoing data is not encrypted and incoming data may be encrypted or not encrypted. This option is not implemented. Default: not_required
`RSSD_msg_integrity`	Specifies whether data are checked for tampering. Valid entries are “required” and “not_required”. This option is not implemented. Default: not_required
`RSSD_msg_origin_check`	Specifies whether the origin of data should be checked. Valid entries are “required” and “not_required”. This option is not implemented. Default: not_required
`RSSD_msg_replay_detection`	Specifies whether data should be checked to make sure they have not been read or intercepted. Valid entries are “required” and “not_required”. This option is not implemented. Default: not_required
`RSSD_msg_sequence_check`	Specifies whether data should be checked to make sure the sequence hasn’t changed. Valid entries are “required” and “not_required”. This option is not implemented. Default: not_required
`RSSD_mutual_auth`	Specifies whether the RSSD must provide proof of identity before Replication Server establishes a connection. Valid entries are “required” and “not_required”. This option is not implemented. Default: not_required
`RSSD_primary_user`	The login name for the RSSD primary user. rs_init automatically assigns this user to the `rs_systabgroup` group during installation. You can add other user login names to this group using the Adaptive Server system procedure sp_changegroup. See the Adaptive Server Enterprise System Administration Guide for more information.
`RSSD_primary_pw`	The password for the RSSD primary user.
`RSSD_primary_pw_enc`	The encrypted password for the RSSD primary user.
`RSSD_sec_mechanism`	The security mechanism Replication Server uses for initial contact with the RSSD at startup. Thereafter, network security information for contact with the RSSD is read from the rs_config file. This option is not implemented.
`RSSD_server`	The name of the Adaptive Server with the RSSD.
`RS_ssl_identity`	SSL identity file.
`RS_ssl_pw`	Password for the SSL private key
`RS_ssl_pw_enc`	The encrypted password for the SSL private key.
`RSSD_unified_login`	Specifies whether Replication Server seeks to connect to the RSSD with a credential at startup. Thereafter, network security information for contact with the RSSD is read from the rs_config file. Valid entries are “required” and “not_required”. This option is not implemented. Default: not_required
`trace`	Turns on a Replication Server trace. You can use multiple instances of this parameter to set the different traces available. Spaces are not allowed. For example: trace=DSI,DSI_BUF_DUMP trace=DIST,DIST_TRACE_COMMANDS
`trace_file`	Indicates the name of the Replication Server log file.