Replication Server Configuration Guide UNIX en

PUBLIC
SAP Replication Server 16.0 SP03

Document Version: 1.0 – 2019-06-06
Replication Server Configuration Guide for UNIX

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 Plan the Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Primary and Replicate Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Required Replication Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Replication Server System Database Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Initial Disk Partition for Each Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
ID Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Databases that Require Replication Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Databases that Require Warm Standby. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Complete the Replication Server Installation Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Replication Server Installation Worksheet Sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Release Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Replication Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Replication Server Security Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Replication Server Interfaces Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ID Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Replication Server System Database Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
SAP ASE Server RSSD Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Disk Partition Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Remote Site Connections Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Database Replication Agent Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3 Complete the Database Setup Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Database Setup Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Replication Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Replication Server Interfaces Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Database Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Logical Connection Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Database RepAgent Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3 Configure SAP Replication Server and Add Databases Using rs_init . . . . . . . . . . . . . . . . . . . . .35
3.1 rs_init in Interactive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Starting rs_init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2 rs_init With a Resource File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Using a Resource File for rs_init. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
3.3 rs_init Command Line Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

2 PUBLIC Content
3.4 Configuring a New Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Entering Replication Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Editing the Interfaces File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Entering ID Server Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Selecting the RSSD Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Entering Embedded Replication Server System Database Information. . . . . . . . . . . . . . . . . . . . 52
Entering Replication Server System Database Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Entering RSSD Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Entering RSSD RepAgent Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Entering Disk Partition Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Entering Remote Site Connections Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.5 Adding a Database to the Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Completing Database Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Completing Logical Connection Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Completing the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4 Upgrade or Downgrade SAP Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.1 Prerequisites When Using Kerberos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.2 Requirements for Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.3 Preparing to Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.4 Upgrading Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Backing Up the RSSD or ERSSD Before Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Stopping Replication Agent and Quiescing Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . 65
Deciding the Upgrade Method to Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Upgrading RSSD or ERSSD and User Databases with repserver. . . . . . . . . . . . . . . . . . . . . . . . . 66
Upgrading RSSD or ERSSD with rs_init. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Fixing a Failed Replication Server Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Upgrades to User Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Commit a Local Site to a New Version Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Backing Up the RSSD or ERSSD After Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
4.5 Upgrading SAP ASE in a Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Suspending Replication and Transaction Activity in the Database. . . . . . . . . . . . . . . . . . . . . . . . 86
Draining Transaction Logs for Primary Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Draining the RSSD Transaction Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Disabling the Secondary Truncation Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Upgrading SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Updating the SAP ASE System Catalog to Support Quoted Identifiers. . . . . . . . . . . . . . . . . . . . 90
Restoring Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6 Downgrading Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Downgrade Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.7 Migrating Between 32-Bit and 64-Bit Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Content PUBLIC 3
5 Upgrade and Downgrade Using Existing Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.1 Upgrading Using Existing Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.2 Downgrading to an Earlier Version in Existing Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6 Password Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

6.1 Enabling Password Encryption for a Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.2 Altering an Encrypted Password for a Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7 Secure Sockets Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7.1 Setting Up SSL Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Include Trusted CA certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Obtain a Certificate for Each SSL-Enabled Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating an Identity File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Adding an Encrypted Password to the Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating SSL Entries in the Directory Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Enabling or Disabling SSL on Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Set the Value of ssl_protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Restarting Replication Server After SSL Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
8 Start or Stop a Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

8.1 Start-up Sequence for Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
8.2 Runserver File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.3 Starting a Replication Server Using the Runserver File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.4 Starting Replication Server with Sufficient Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.5 Stopping a Replication Server Using isql. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
9 Install and Implement Non-SAP ASE Support Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

9.1 Components for Non-SAP ASE Support Installed with Replication Server. . . . . . . . . . . . . . . . . . . . 114
9.2 Setting Up and Configuring Non-SAP ASE Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
10 Sample Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

10.1 Setting Up the Sample Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
10.2 Establishing the Sample Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
10.3 Troubleshooting and Testing the Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

4 PUBLIC Content
1 Conventions
These style and syntax conventions are used in SAP documentation.
Style Conventions
Key Definition
Monospaced (fixed-width) ● SQL and program code

● Commands to be entered exactly as shown
● File names
● Directory names
Monospaced, surrounded by angle In SQL or program code snippets, placeholders for user-specified values (see ex
ample below).
brackets
Surrounded by angle brackets ● File and variable names

● Cross-references to other topics or documents
● In text, placeholders for user-specified values (see example below)
● Glossary terms in text
Bold san serif ● Command, function, stored procedure, utility, class, and method names
● Glossary entries (in the Glossary)
● Menu option paths
● In numbered task or procedure steps, user-interface (UI) elements that you
click, such as buttons, check boxes, icons, and so on
An explanation for a placeholder (system- or setup-specific values) follows in text. For example:
Run the following, where <installation directory> is the location where the program is installed:
<installation directory>/start.bat
Syntax Conventions
Key Definition
{} Curly braces indicate that you must choose at least one of the enclosed options. Do not type the
braces when you enter the command.

Conventions PUBLIC 5
Key Definition
[] Brackets mean that choosing one or more of the enclosed options is optional. Do not type the brack
ets when you enter the command.
() Enter parentheses as part of the command.
| The vertical bar means you choose only one of the options shown.
, The comma means you choose as many of the options shown as you like, separating your choices
with commas that you type as part of the command.
... An ellipsis (three dots) means you may repeat the last unit as many times as you need. Do not in
clude ellipses in the command.
<> Angle brackets are not part of the syntax. Rather, they denote variables within the syntax. For exam
ple, if the syntax calls for a variable such as a password, this is denoted as <password>. However,
when using the syntax in a command or query, omit the angled brackets. So, instead of using <My
Password> use MyPassword.
Case-sensitivity
● All command syntax and command examples are shown in lowercase. However, replication command
names are not case-sensitive. For example, RA_CONFIG, Ra_Config, and ra_config are equivalent.
● Names of configuration parameters are case-sensitive. For example, Scan_Sleep_Max is not the same as
scan_sleep_max, and the former would be interpreted as an invalid parameter name.
● Database object names are not case-sensitive in replication commands. However, to use a mixed-case
object name in a replication command (to match a mixed-case object name in the primary database),
delimit the object name with quote characters. For example: pdb_get_tables "<TableName>"
● Identifiers and character data may be case-sensitive, depending on the sort order that is in effect.
○ If you are using a case-sensitive sort order, such as “binary,” you must enter identifiers and character
data with the correct combination of uppercase and lowercase letters.
○ If you are using a sort order that is not case-sensitive, such as “nocase,” you may enter identifiers and
character data with any combination of uppercase or lowercase letters.
Terminology
SAP Replication Server works with various components to enable replication between supported database,
such as SAP Adaptive Server Enterprise (SAP ASE), SAP HANA, SAP IQ, Oracle, IBM DB2 UDB, and Microsoft
SQL Server. SAP Replication Server uses SAP ASE for its Replication Server System Database (RSSD) or it uses
SAP SQL Anywhere for its embedded Replication Server System Database (ERSSD).
Replication Agent is a generic term used to describe the Replication Agents for SAP ASE, Oracle, IBM DB2
UDB, and Microsoft SQL Server. The specific names are:
● RepAgent – Replication Agent thread for SAP ASE

● Replication Agent for Oracle
● Replication Agent for Microsoft SQL Server

6 PUBLIC Conventions
● Replication Agent for UDB – for IBM DB2 on Linux, Unix, and Windows
● Replication Agent for DB2 for z/OS

Conventions PUBLIC 7
2 Overview
To successfully install and configure SAP Replication Server, use the configuration guide along with the
installation guide.
The installation guide explains how to unload the software from the distribution media to your hard disk.
The configuration guide explains how to:
● Gather the information you need to prepare your system for your configuration.
● Configure SAP Replication Servers and add databases to your replication system.
● Upgrade existing SAP Replication Server System Databases (RSSDs).
● Downgrade existing RSSDs and then reinstall an earlier version of the software.
● Enable password encryption for an SAP Replication Server or a RepAgent.
● Start and stop an SAP Replication Server or a RepAgent.
Before you begin:
1. Plan your replication system.

2. Use the Replication Server Installation and Database Setup worksheets to collect and record the
information you need to install and configure a Replication Server, and to add a database to your
replication system.
3. Use the worksheets and the installation guide for your platform to install Replication Server and the
included sample Replication Server.
Related Information
Plan the Replication System [page 8]

Complete the Replication Server Installation Worksheet [page 13]
Complete the Database Setup Worksheet [page 29]
2.1 Plan the Replication System
Answer the following questions to plan your replication system.
In your planning, you need to know:
● Where will the primary and replicate data reside?

● What Replication Servers will you need?
● Where will the SAP Replication Server System Database (RSSD) be for each Replication Server?
● Where is the initial disk partition for each Replication Server?
● Which Replication Server is the ID Server?

8 PUBLIC Overview
● Which databases require Replication Agents?
● Which databases require warm standby?
Related Information
Primary and Replicate Data [page 9]

Required Replication Servers [page 9]
Replication Server System Database Location [page 10]
Initial Disk Partition for Each Replication Server [page 10]
ID Server [page 11]
Databases that Require Replication Agents [page 12]
Databases that Require Warm Standby [page 13]
2.1.1 Primary and Replicate Data
Primary data is a set of data that is replicated from a source (the primary database) to another database (the
replicate database) through the replication system. Replicate data is the set of data that is replicated (copied)
from the primary database to the replicate (target) database. The primary database is known to all Replication
Servers subscribed to the data.
When planning your replication system, decide on the following:
● Identify which databases will contain the primary data to replicate to other databases.
 Note
This document refers to SAP Adaptive Server Enterprise (SAP ASE) databases, but Replication Server
can also work with other databases.
● Identify those databases in which Replication Server maintains copies of the data.
Related Information
Install and Implement Non-SAP ASE Support Features [page 114]
2.1.2 Required Replication Servers
When designing a replication system, decide how many Replication Servers to install, which databases they will
manage, and on which machine they will execute.
A Replication Server can manage one or more databases. A replication system may only need one Replication
Server, another may require a Replication Server at each geographic site to manage all of the databases at that

Overview PUBLIC 9
site, while others may require multiple Replication Servers at each site to handle many databases or heavy
transaction volumes.
When you upgrade Replication Servers, you can phase in the upgrades and install newer versions of Replication
Servers initially only at certain sites. Consider the timing of such upgrades with care, and assess the need at
each site for the new Replication Server features.
Related Information
Upgrade or Downgrade SAP Replication Server [page 59]
2.1.3 Replication Server System Database Location
Replication system data is stored in a dedicated SAP ASE database called the Replication Server System
Database (RSSD), or in an embedded Replication Server System Database (ERSSD) using SAP SQL Anywhere.
RSSD is actively managed, while ERSSD is automatically created, configured, and maintained by Replication
Server. If you choose to use RSSD, it is created when the Replication Server is installed.
Before you begin the installation, decide which SAP ASE server is storing the RSSD for the Replication Server
and the devices on which the database and its log will be stored. You can create the SAP ASE database devices
during installation, but identify their physical disk location before you install the Replication Servers.
If you use ERSSD, decide the directory paths for the ERSSD database file, transaction log, and backup. For
better performance and recoverability, place the database file, transaction log, and backup directory on
different disk devices.
Related Information
Replication Server System Database Information [page 24]
2.1.4 Initial Disk Partition for Each Replication Server
Replication Server stores messages, such as replicated transactions, on disk in stable queues. Disk space for
the queues is allocated from disk partitions you create. A disk partition can be a raw disk partition or an
operating system file.
Allocate a disk partition of at least 20 MB for each Replication Server you install. You may add more partitions
later. Check each partition to verify its availability and that the “sybase” user can write to it. To use an operating
system file for a partition, create an empty file. Verify that there is enough space on the file system for
Replication Server to extend the file to full partition size.
See System Requirements in the installation guide for your platform.

10 PUBLIC Overview
2.1.5 ID Server
The ID Server is an SAP Replication Server that registers all SAP Replication Servers and databases in the
replication system.
An ID Server is like any SAP Replication Server and performs the usual SAP Replication Server tasks. In
addition, it also assigns a unique identification number to every SAP Replication Server and database in the
replication system. The ID Server also maintains version information for the replication system.
To allow a new SAP Replication Server, or the SAP Replication Server that manages a new database, to log in
and retrieve an ID number, the ID Server must be running whenever any of the following occurs:
● SAP Replication Server is installed

● A route is created
● A database connection is created or dropped
This means that the ID Server is the first SAP Replication Server you install and start when you install a
replication system. If you have only one SAP Replication Server, or are installing SAP Replication Server for the
first time, that SAP Replication Server is also the ID Server. If you are adding a SAP Replication Server to an
existing replication system, make sure you know the name of the ID Server.
The ID Server requires its own login name for SAP Replication Servers to use when they connect to it. The login
name is recorded in the configuration files of all SAP Replication Servers in the replication system by the
rs_init configuration program when you are setting up and managing the replication system.
You may have two ID Servers in the replication system, to serve as the primary and backup ID Servers. Only the
primary ID Server may interact with other SAP Replication Servers for ID management in the same domain.
The backup ID Server syncs through a Remote Procedure Call (RPC) whenever there is any change in the
primary ID Server. When the primary ID Server fails or becomes unavailable, you can repair the primary ID
Server, or promote the backup ID Server to be the primary.
 Note
The ID Server is critical to your replication environment, and is difficult to move once it has been installed.
To change the primary ID Server to a different SAP Replication Server, configure the new primary ID Server
on each SAP Replication Server in the same system, including the ID Servers.
Use the sysadmin idserver command to configure and manage primary and backup ID Servers. See the
Replication Server Reference Manual for details.
Related Information
Replication System Domain [page 12]

Replication Server Information [page 18]

Overview PUBLIC 11
2.1.5.1 Replication System Domain
All replication system components that use the same ID Server fall under the same replication system domain.
Some organizations have multiple independent replication systems. Since the ID Server determines member
SAP Replication Servers and databases in a replication system, one replication system in an organization with
multiple replication systems is also called an ID Server domain.
No special steps are required to set up multiple ID Server domains. Every SAP Replication Server or database
belongs to one replication system and has a unique ID number in that ID Server domain.
You can set up multiple replication system domains, with the following restrictions:
● SAP Replication Servers in different domains cannot exchange data. Each domain is treated as a separate
replication system with no cross-communication between them. You cannot create a route between SAP
Replication Servers in different domains.
● A database can be managed by only one SAP Replication Server in one domain. Any given database is in
the domain of a single ID Server. You cannot create multiple connections to the same database from
different domains.
2.1.6 Databases that Require Replication Agents
A Replication Agent retrieves transactions from a database log and passes them to the replication system
through the Replication Server that manages the database.
You can configure multiple replication paths from SAP ASE with an Adaptive Server Replication Agent for each
replication path. See Multi-Path Replication in the Administration Guide Volume 2. For non-SAP databases,
there is only one Replication Agent per database. Because you configure the Replication Agent when you set up
a database for replication, you must know whether the database requires a Replication Agent before you add
the database to the replication system.
A user database requires a Replication Agent:
● If the database holds primary data that is replicated to other databases managed by the same or different
Replication Servers.
● If the Replication Server manages a database that is a source of replicated stored procedure execution.
● If you plan to replicate a stored procedure execution from a primary to replicate databases or from a
replicate to a primary database. Replication Agent retrieves the procedure call information from the
database transaction log. See the Administration Guide Volume 1.
● If the database is the active or standby database in a warm standby application. Replication Agent for a
standby database is needed only when you switch to the standby database. See the Administration Guide
Volume 1.
An RSSD requires a Replication Agent if the Replication Server using that RSSD has a route to another
Replication Server; for example:
● The Replication Server manages primary data that is replicated to databases managed by other
● The Replication Server manages a database that is a source of replicated stored procedure execution.
● The Replication Server is an intermediate site in an indirect route.

12 PUBLIC Overview
An RSSD does not require a Replication Agent if the replication system has only one Replication Server.
Replication Agent for ERSSD is managed by Replication Server. It is automatically started when a route is
created. You need not decide the ERSSD Replication Agent requirements while you install or configure
Replication Server.
Related Information
Database Replication Agent Information [page 29]
2.1.7 Databases that Require Warm Standby
Replication Server can maintain a warm standby database for an SAP ASE or Oracle database. If the active
database fails, clients can switch to the standby database with little interruption.
To set up a warm standby application, perform some tasks in Replication Server before and after you add
databases to the replication system.
Before you install Replication Server, see Manage Warm Standby Applications in the Administration Guide
Volume 2.
To configure warm standby for Oracle databases, see Heterogeneous Warm Standby for Oracle in the
Heterogeneous Replication Guide.
2.2 Complete the Replication Server Installation Worksheet
Use the worksheet to record configuration information you need during the Replication Server installation.
The rs_init program is used to configure Replication Server software. The sections in the Replication Server
Installation Worksheet correspond to the rs_init menus; enter information from the worksheet directly into
rs_init.
rs_init supplies default values for most items in the Replication Server Installation Worksheet and Database
Setup Worksheet based on the values you enter. For example, if you enter “TOKYO_RS” for the Replication
Server name, rs_init names the log file TOKYO_RS.log. Accept the displayed value or enter a different
value.
 Note
Do not use names that begin with “rs_” for SAP ASE servers, Replication Servers, database objects, or login
names, as these are reserved for Replication Server. See the Reference Manual for other restrictions.

Overview PUBLIC 13
Related Information
Replication Server Installation Worksheet Sample [page 14]

Release Directory [page 16]
Replication Server Security Information [page 21]
Replication Server Interfaces Information [page 22]
ID Server Information [page 22]
SAP ASE Server RSSD Device Information [page 26]
Disk Partition Information [page 27]
Remote Site Connections Information [page 29]
Database Replication Agent Information [page 29]
2.2.1 Replication Server Installation Worksheet Sample
Make a copy of this worksheet for each Replication Server you install, and complete each section as you
prepare to install and configure Replication Server.
Keep the worksheet copy to use if you reconfigure your replication system.
Required fields are marked with an asterisk (*). rs_init has default values for items that are not marked.
To use a default value, leave the unmarked fields blank and fill it in on the worksheet when you run rs_init.
Release Directory
Release directory:
Release Server Information
Replication Server name:*
Is this Replication Server the ID Server?* Yes No
Replication Server error log:
Replication Server configuration file:
Replication Server password encryption: Yes No
Replication Server character set:
Replication Server language:
Replication Server sort order:
Replication Server Security Information
(Solaris only) Yes No
Enable network security?*

14 PUBLIC Overview
Replication Server Security Information
If Yes, security system: dce csfkrb5
If Yes, login name:
If Yes, keytab file name:
(All platforms) Yes No
Use Secure Sockets Layer (SSL) security?
If Yes, SSL identity file:
If Yes, SSL private key password:
Replication Server Interfaces Information
Host name/address:*
Port:*
Name alias:*
ID Server Information
ID Server name:*
ID Server user:
ID Server password:
Starting Replication Server ID:
Starting database ID:
Replication Server System Database Choice
Will RSSD be embedded? Yes No (default)
SQL Anywhere Embedded Replication Server System Database Information
Complete if you selected ERSSD name:*
Yes for “Will RSSD be ERSSD database file directory:*

embedded?”
ERSSD transaction log directory:*
ERSSD backup directory:*
ERSSD error log directory:*
Adaptive Server Enterprise Replication Server System Database Information
Complete if you selected RSSD Adaptive Server name:*
No for “Will RSSD be em RSSD name:

bedded?”
Will RSSD be replicated?* Yes No
Allow HA failover for RSSD connections? Yes No
Create RSSD:* Yes No
SA user:

Overview PUBLIC 15
Adaptive Server Enterprise Replication Server System Database Information
SA password:*
Primary user:
Primary password:
Maintenance login:
Maintenance password:
Adaptive Server Enterprise RSSD Device Information
Complete if you selected Size of the RSSD database:
No for “Will RSSD be em RSSD device name:*

bedded?”
Create the RSSD device:* Yes No
RSSD device physical name:
RSSD device size:
Size of the RSSD log:
RSSD log device name:*
Create the RSSD log device:* Yes No
RSSD log device physical name:
RSSD log device size:
Disk Partition Information
Disk partition path:*
Logical identifier for disk partition:*
Size of disk partition:
Start value for partition:
Remote Site Connections Information
Replication Server login name:
Replication Server password:
RSSD RepAgent Information
Complete if you selected RS user:
Yes for “Will RSSD be re RS password:

plicated?”
2.2.2 Release Directory

The release directory is the installation directory where you install Replication Server.
Replication Server creates a new directory structure that allows you to use multiple versions of some
components.

16 PUBLIC Overview
See Installation Directory Structure in the installation guide for your platform.
Related Information
Verifying Permissions [page 17]
2.2.2.1 Verifying Permissions
Verify the “sybase” user has write permission for the release directory.
Context
See the installation guide for your platform for more information about the “sybase” user.
Procedure
1. In the .cshrc or .profile file of the “sybase” user, set the environment variable to the full path of the
release directory. In these examples, your path is /work/sybase:
○ C shell – add this line to the .cshrc file:
setenv SYBASE /work/sybase
At the shell prompt, enter:
source .cshrc
○ Bourne shell – add this line to the .profile file:
SYBASE="/work/sybase"; export SYBASE
At the shell prompt, enter:
. .profile
2. Record the release directory on the worksheet.
 Note
In addition to $SYBASE, Replication Server uses environment variables for Replication Server—
$SYBASE_REP, and SAP Open Client/SAP Open Server — $SYBASE_OCS. See Postinstallation Tasks in
the Installation Guide.

Overview PUBLIC 17
2.2.3 Replication Server Information
Replication Server information used to complete in the corresponding section in the worksheet.
Field Description
Replication Server name (Required) A name for the Replication Server that is unique in the replication system.
Is this Replication Server the ID (Required) Select Yes if you are installing the ID Server.
Server?
Replication Server error log The path for the Replication Server error log file. Replication Server writes informa
tional and error messages to this text file.
Replication Server configuration file The path for the Replication Server configuration file, which contains parameters that
Replication Server reads at start-up. See Manage a Replication System in the Admin
istration Guide Volume 1.
Replication Server password en Select Yes for passwords to be encrypted in the Replication Server configuration file
cryption and in the RSSD.
 Caution
If you do not encrypt passwords, anyone with the required permissions can view
the passwords in the configuration files and in the RSSD rs_users system ta
ble.
Replication Server character set The character set that the Replication Server will use. Specify any SAP-supported
character set that is available for your language.
Replication Server language The language Replication Server will use to print messages to the error log and to cli
ents. It can be any language that is compatible with the character set you install.
Additional information about character sets is available in the SAP Adaptive Server
Enterprise Configuration Guide.
Replication Server sort order The sort order for the Replication Server.
Related Information
Replication Server Character Sets [page 19]

Replication Server Language [page 20]
Replication Server Sort Order [page 21]
ID Server [page 11]

18 PUBLIC Overview
2.2.3.1 Replication Server Character Sets
For replication to work correctly, make sure Replication Server, the data servers, and the Replication Agents it
controls for replication all use the same character sets.
The character set must be compatible with the character sets of the other Replication Servers in the system.
By default, rs_init configures Replication Server with the native character set for your platform.
When you create a subscription, Replication Server copies the requested data from the primary database to
the replicate database in a process known as subscription materialization. During subscription materialization,
the primary data server converts character data to the replicate Replication Server character set. Install the
replicate Replication Server character set at the primary data server if it differs from the primary data server
character set.
Similarly, when you create a route, install the character set of the destination Replication Server at the data
server of the source Replication Server RSSD.
Related Information
Supported Character Sets [page 19]
2.2.3.1.1 Supported Character Sets
Character sets that Replication Server supports.
Supported character sets in the English language version of Replication Server include:
Charset Description
cp437 (Code Page 437) character set used by IBM PCs
cp850 (Code Page 850) IBM/Microsoft Multilingual Character Set, usedi n IBM PCs
deckanji DEC Kanji Code for JIS-X0208
eucgb EUC GB encoding for Simplified Chinese character sets
eucji extended UNIX Code for JIS-X0201 and JIZ-X0208
eucksc (Code Page 949) EUC KSC Korean encoding
gb18030 GB 18030-2000 standard for Chinese characters,

established by the government of the People's Republic of
China
iso15 similar to iso_1

Overview PUBLIC 19
Charset Description
iso_1 (ISO-8859/1) 8-bit character set for many system. This is the default for
SAP ASE with Solaris and IBM RISC System 6000 AIX
mac default Macintosh character set
roman 8 Hewlett-Packard character set
roman 9 the same as roman 8, except for codepoint 0xBA,

previously treated as the universal currency symbol, now
representing the euro currency symbol
sjis (Shift-JIS) IBM/Microsoft Code for JIS-X0201 and JIX-X02081
utf8 an ASCII-preserving encoding method for Unicode
Language Charsets
Chinese ● eucgb
● gb18030
● utf8
Japanese ● deckanji
● eucjis
● sjis
● utf8
Korean ● eucksc
● utf8
French, German, and Spanish ● cp437

● cp850
● iso15
● iso_1
● mac
● roman8
● roman9
● utf8
2.2.3.2 Replication Server Language
By default, rs_init configures Replication Server to print messages in U.S. English.
Other available languages are Chinese, French, German, Japanese, Korean, and Spanish. rs_init uses the
same identifiers for language names as SAP ASE. You can select any language when you install Replication
Server as long as the language is compatible with the character set you install.

20 PUBLIC Overview
If the language for the Replication Server and the language for its connected data servers differ, install the
language for the Replication Server at the data servers. This lets the data servers return messages to
Replication Server in the configured language, and recognize and format dates for the configured language.
For example, the date format “01/02/99” is equivalent to “January 2, 1999” in us_english but “February 1,
1999” in french. Data servers can format the date correctly only if the Replication Server configured language
is installed.
2.2.3.3 Replication Server Sort Order
The sort order controls which rows of a table belong in a subscription that has a where clause involving
character data.
The sort order also controls how things such as case-sensitivity and accents are recognized in the identifiers
you enter.
You may specify any SAP-supported sort order that is compatible with your character set. For replication to
work, all sort orders in your replication system should be the same.
By default, rs_init configures Replication Server with the binary sort order. Available sort orders vary,
depending on the character set you plan to install. Sort orders are located in the release directory in the
directory charsets/<charset_name>, where <charset_name> is the name of the character set.
See the Design Guide for guidelines on configuring languages, character sets, and sort orders in your
replication system.
2.2.4 Replication Server Security Information
(Solaris only) Security information used to complete the corresponding section in the worksheet.
Field Description
Enable network security (Required) Select Yes to enable external network security.
Type of security system If you are enabling network security, select DCE or Kerberos.
Login name The name of the primary user who will make secure connections. You should use
the name of the Replication Server as the principle user name.
Keytab file name The full path to the location of the keytab file.
Use SSL security Select Yes if you are using Secure Sockets Layer (SSL) security.
SSL identity file The full path to the location of the SSL identity file.
SSL private key password The private key password. The default password is password.
See Manage Replication Server Security in the Administration Guide Volume 1 for more information on security.

Overview PUBLIC 21
Related Information
Secure Sockets Layer [page 104]
2.2.5 Replication Server Interfaces Information
Use the Replication Server interfaces information of the worksheet to record information that defines the
network port where Replication Server listens for connections. Each entry in the interfaces file is called a
listener service.
 Note
If you are using network-based security, available with version 11.5 or later, use the directory services of
your network security mechanism to register Replication Servers, SAP ASE, and gateway software. See the
documentation that comes with your network-security mechanism for details.
Field Description
Hostname/address (Required) The name of the machine running Replication Server. If the machine has
more than one host name or IP address, enter the name or address associated with
the network you plan to use.
Port (Required) Choose an unused port number between 1025 and 65535 not used by the
machine. To identify which port numbers are in use, check the /etc/services
directory or use the netstat command.
Name alias (Required) On networks that allow multiple protocols, you can use a name alias to
distinguish listener services. An alias is a nickname for a Replication Server. You can
not use the alias for any other server on the network.
2.2.6 ID Server Information
ID Server information used to complete its corresponding section in the worksheet.
These are the worksheet fields:
Field Description
ID Server name (Required) If the Replication Server you are installing is the ID Server, rs_init as
signs an ID Server name identical to this Replication Server name.
If you are installing a new Replication Server in an existing Replication Server domain,
enter the name of the Replication Server that is acting as the ID Server.

22 PUBLIC Overview
Field Description
ID Server user If the Replication Server you are installing is the ID Server, enter the login name that
other Replication Servers will use to connect to this ID Server.
If you are installing a new Replication Server to an existing Replication Server domain,
copy the ID Server user name from the worksheet you completed when you created
the ID Server.
ID Server password If the Replication Server you are installing is the ID Server, enter the password for the
ID Server user.
If you are adding a new Replication Server to an existing Replication Server domain,
copy the ID Server password from the worksheet you completed when you created the
ID Server.
Starting Replication Server ID and (Optional) These two configuration parameters specify separate ranges of Replication
Starting Database ID Server ID numbers and database ID numbers that an ID Server will assign. Doing so
makes merging replication systems easier.
 Note
“Starting Replication Server ID” and “Starting Database ID” in the worksheet apply
only to the ID Server. If you are not installing the ID Server, skip to “Replication
Server System Database Information”.
Related Information
Default ID Number Ranges and ID Number Allocation for ID Server Domains [page 23]
ID Server [page 11]
2.2.6.1 Default ID Number Ranges and ID Number

Allocation for ID Server Domains
An ID Server assigns ID numbers sequentially. Separate value ranges are maintained for databases and
Table 1: Database and Replication Server Default ID Number Ranges

Object Type Minimum ID Number Maximum ID Number
Database 101 16777215
Replication Server 16777317 33554431
Make sure the minimum values for each ID Server are within the ranges specified. For example, if your
organization has three separate ID Server domains, set the minimum ID numbers as shown in "Example ID
Number Allocation for ID Server Domains."

Overview PUBLIC 23
Table 2: Example ID Number Allocation for ID Server Domains
ID Server Domain Starting Database ID Starting Replication Server ID
Finance division 101 16777317
Manufacturing division 100101 16877317
Sales division 200101 16977317
This arrangement provides the ID Server in each domain with at least 100,000 ID numbers for databases and
100,000 ID numbers for Replication Servers. You need not set a maximum value, since you are unlikely to
install more than 100,000 Replication Servers or add more than 100,000 databases to a replication system.
See Manage a Replication System in the Administration Guide Volume 1 for more information about adding
replication system domains.
2.2.7 Replication Server System Database Information
Replication Server maintains its system tables in its system database. You can set up either a Replication
Server System Database (RSSD) in an SAP ASE database, or an Embedded Replication Server System
Database (ERSSD) in a SQL Anywhere (SA) database.
Related Information
SAP Adaptive Server Enterprise RSSD Information [page 24]

SQL Anywhere ERSSD Information [page 25]
2.2.7.1 SAP Adaptive Server Enterprise RSSD Information
The worksheet fields list RSSD information for the SAP Adaptive Server Enterprise (SAP ASE) server if you
want an RSSD.
Field Description
RSSD Adaptive Server name (Required) The name of the SAP ASE server that will hold the system database
for the Replication Server.
RSSD name The name of the database where the Replication Server system tables will be
stored.
Will RSSD be replicated? (Required) Select Yes if the RSSD for the Replication Server requires a Replica
tion Agent.
Allow HA failover for RSSD connections? Select Yes if the SAP ASE managing the RSSD supports HA failover and you want
RSSD connections to fail over to an alternative server.

24 PUBLIC Overview
Field Description
Create RSSD (Required) Select Yes for rs_init to create the system database.
Select No if the system database already exists or if you plan to create it man
ually.
If the database already exists, it should be dedicated to this Replication Server.

See the Installation Guide for disk space and system requirements.
SA user The login name for the “sa” user for the SAP ASE server that will hold the RSSD.
The default is “sa.”
rs_init uses the “sa” login name to create user login names and the system
tables in the RSSD.
SA password (Required) The “sa” password for the SAP ASE server that will hold the RSSD.
Primary user The login name for the RSSD primary user. Replication Server uses this login
name for system table updates. rs_init creates the primary user.
Primary password The password for the RSSD primary user.
Maintenance login The name of the maintenance user for the RSSD. Replication Server uses this
login name to perform operations on the system tables that are replicated from
other sites. rs_init creates the maintenance user and adds the maintenance
user to the RSSD.
Maintenance password The password for the RSSD maintenance user.
2.2.7.2 SQL Anywhere ERSSD Information
SQL Anywhere information that you need if you plan to have an ERSSD.
Field Description
ERSSD name The name of the SQL Anywhere server that will hold the system database for the
Replication Server.
ERSSD database file directory The directory for the SQL Anywhere server database file.
ERSSD transaction log directory The directory for the SA server transaction log.
ERSSD backup directory The directory for the SQL Anywhere server backup files.
ERSSD error log directory The directory for the SQL Anywhere server error log file.
 Note
Although rs_init specifies the same device when filling these fields with default values, you should place
the ERSSD database directory, ERSSD transaction log directory, and ERSSD backup directory on separate
devices for better performance and recoverability.
See Manage a Replication System in the Administration Guide Volume 1.

Overview PUBLIC 25
2.2.8 SAP ASE Server RSSD Device Information
Complete this section for rs_init to create the RSSD.
If you selected No for "Create RSSD" and you do not want rs_init to create an RSSD, skip this section and
proceed to “Disk partition information”.
Field Description
Size of the RSSD database The size, in megabytes, of the data portion.
RSSD device name (Required) The name of the SAP ASE logical device where you create the RSSD.
If the device already exists, it needs enough space to create the new database.
Create the RSSD device (Required) Select Yes to create the RSSD data device on the SAP ASE database
device.
Select No if the RSSD data device already exists, or if you plan to create it before
you run rs_init.
RSSD device physical name Enter the physical device name for the database device on which you store the
RSSD.
RSSD device size Enter the capacity of the physical device, in megabytes, that is at least the size
you specified for the data portion of the RSSD database.
Size of the RSSD log The size, in megabytes, for the RSSD database log.
 Note
Store the RSSD log on a device other than the master device, and on a differ-
ent device from the RSSD data.
RSSD log device name (Required) The logical name for the device to use for the RSSD log.
Create the RSSD log device (Required) Select Yes to create the RSSD log device in SAP ASE.
Select No if the device already exists or if you plan to create it before you run
rs_init.
RSSD log device physical name Enter the physical device name for the device that will server as the RSSD log de
vice.
Leave this blank if you do not want an RSSD log device, or if you are using a single
device for both the RSSD and its log. The latter option is not recommended.
RSSD log device size Enter the capacity of the physical device, in megabytes, that is at least ithe size
you specified for the RSSD log.
Leave this blank if you do not want an RSSD log device, or if you are using a single
device for both the RSSD and its log. The latter option is not recommended.
Related Information
RSSD Device [page 27]

26 PUBLIC Overview
2.2.8.1 RSSD Device
The RSSD device is the SAP ASE database device where rs_init creates the Replication Server RSSD.
Avoid use the default master device as the RSSD device, making sure the database device meets minimum
space requirements of the 40 MB for the database, and the 16 MB for the RSSD log. Use sp_helpdevice to
list the available devices.
Select one of the following if the SAP ASE does not have a device available for the RSSD:
● Add a device and record the information on your worksheet

● Have rs_init create the device when it installs Replication Server
 Note
If the SAP ASE server is not on the local machine, create the device yourself. Otherwise, rs_init
incorrectly evaluates the local machine’s file system instead of the remote machine’s file system when
it validates the path name and disk space requirements of the device.
For rs_init to create the device, verify that the disk file or raw partition exists and has the proper
permissions . Execute sp_configure devices in SAP ASE to verify that the value for devices is high enough to
allow you to add a new device. See the SAP Adaptive Server Enterprise System Administration Guide for
information about device requirements.
2.2.9 Disk Partition Information
Disk partition information to complete the corresponding section in the worksheet.
Replication Server uses disk partitions for stable queues, to temporarily store the data it receives and sends.
Replication Server can use raw partitions, if they are available on your platform, or operating system files. Raw
partitions provide improved recovery capability because the operating system does not buffer its I/O.
The minimum partition size is 20 MB. You can add more partitions after the Replication Server is installed.
Field Description
Disk partition path (Required) The name of the physical disk device or the full path name of a file to
use for the disk partition. Any operating system file you specify must already ex
ist, and have enough space on the file system for Replication Server to extend the
file to the size you specify.
Logical identifier for disk partition (Required) A logical identifier for the partition. This name is used in commands
and in Replication Server messages to identify the disk partition.
See Replication Server Reference Manual > Topics > Identifiers.

Overview PUBLIC 27
Field Description
Size of disk partition The size of the disk partition, in megabytes. The minimum size is 20 MB.
See Replication Server Administration Guide Volume 1 > Replication Server Tech
nical Overview > Transaction Handling with Replication Server > Stable Queues >
Partitions for Stable Queues and Replication Server Design Guide > Capacity Plan
ning.
Start value for partition This value prevents Replication Server from using the beginning of a raw disk
partition. It is required if your operating system stores information, such as con
figuration maps, at the beginning of the disk partition. Enter the number of meg
abytes Replication Server should ignore.
For example, if you enter 1, Replication Server does not use the first megabyte of
the raw disk partition.
Related Information
Creating a Disk Partition [page 28]
2.2.9.1 Creating a Disk Partition
Create raw partitions in Replication Server if they are available on your platform or operating system files. Raw
partitions provide improved recovery capability because the operating system does not buffer its I/O.
Prerequisites
Verify that the operating system file you plan to use for a partition exists before you specify it in rs_init.
Procedure
1. Log in as the "sybase" user.

2. Use a text editor or the UNIX touch command to create an empty file for the partition:
To use touch, use the following, where <path> is the full path to the disk file:
touch <path>
3. Grant read and write permission to the "sybase" user:
chmod 600 <path>

28 PUBLIC Overview
4. Verify that there is enough free space on the file system for this new file to grow to the size you specify;
Replication Server extends this file to the full partition size during installation.
2.2.10 Remote Site Connections Information
The information defines a login name for other Replication Servers to use when logging in to this Replication
Server.
Field Description
Replication Server login name The login name that other Replication Servers uses to connect to this Replication
Server.
Replication Server password Replication Server password
2.2.11 Database Replication Agent Information
The Replication Agent information to complete the corresponding section in the worksheet.
Field Description
RS user The login name that the RSSD Replication Agent uses to connect to the Replica
tion Server
RS password The password for the RS user login name.
Related Information
2.3 Complete the Database Setup Worksheet
Use the worksheet to record configuration information for each database you add to the replication system.
Refer to the information on the worksheet when you use rs_init to add the database to your replication
system.
Each primary or replicate database in your replication system is managed by a Replication Server. The
database may also require a Replication Agent.
See the Design Guide for guidelines on configuring character sets, languages, and sort orders in your
replication system.

Overview PUBLIC 29
Related Information
Database Setup Worksheet [page 30]

Replication Server Interfaces Information [page 31]
Database Information [page 32]
Logical Connection Information [page 33]
Database RepAgent Information [page 34]
2.3.1 Database Setup Worksheet
Make a copy of this worksheet for each database you add to the replication system, and complete each section
as you prepare to install and configure Replication Server.
Keep the worksheet copy to use if you reconfigure your replication system.
rs_init has default values for items that are not marked. To use the default values, leave the unmarked field
blank and fill it on the worksheet when you run rs_init.
Required fields are marked with an asterisk (*).
Replication Server Information
Replication Server name:*
RS SA user:*
RS SA password:*
Replication Server Interfaces Information
Host name/address:*
Port:*
Name alias:*
Database Information
SAP ASE name:*
SA user:
SA password:
Database name:
Will the database be replicated?* Yes No
Maintenance user:
Maintenance password:
Is this a physical connection for an existing logical Yes No

connection?

30 PUBLIC Overview
Logical Connection Information
Complete if you chose Yes for “Is this a physical connection for an existing logical connection?”
Is this an active connection or a standby connec Active Standby

tion?*
Logical DS name:*
Logical DB name:*
Enter these values if you select Standby for “Is this an active connection or standby connection?”
Active DS name:*
Active DB name:*
Active DB SA user:*
Active DB SA password:*
Initialize standby using dump and load?* Yes No
Use dump marker to start replicating to standby?* Yes No
Database RepAgent Information
Enter these values if you selected Yes for “Will the database be replicated?”
RS user:
RS password:
2.3.2 Replication Server Information
The Database Setup Worksheet includes Replication Server information needed to identify the Replication
Server that manages the database.
Make sure the installed Replication Server is running before you add the database to the replication system.
These are the worksheet fields:
Field Description
Replication Server name (Required) The name of the Replication Server that manages the database.
RS SA user (Required) The Replication Server System Administrator (RS SA) login name (usu
ally “sa”).
RS SA password (Required) The password for the Replication Server SA user.
2.3.3 Replication Server Interfaces Information
Copy the information you have provided in the "Replication Server interfaces information" section of the
Replication Server Installation Worksheet for the Replication Server that manages this database. Since the

Overview PUBLIC 31
Replication Server is already installed, you need not enter this information again unless you start rs_init in a
release directory that uses a different interfaces file.
 Note
If you are using network-based security, available with version 11.5 or later, use the directory services of
your network security mechanism to register Replication Servers, SAP ASE, and gateway software. See the
documentation that comes with your network-security mechanism for details.
Field Description
Hostname/address (Required) The name of the machine running Replication Server. If the machine has
more than one host name or IP address, enter the name or address associated with
the network you plan to use.
Port (Required) Choose an unused port number between 1025 and 65535 not used by the
machine. To identify which port numbers are in use, check the /etc/services
directory or use the netstat command.
Name alias (Required) On networks that allow multiple protocols, you can use a name alias to
distinguish listener services. An alias is a nickname for a Replication Server. You can
not use the alias for any other server on the network.
2.3.4 Database Information
The Database Setup Worksheet includes database information that identifies the database you are adding to
the replication system.
Field Description
Adaptive Server name (Required) The name of the SAP ASE where the database resides.
SA user The “sa” login name for the SAP ASE managing the database.
SA password The password for the SA user login name.
Database name The name of the database.
Will the database be replicated? (Required) Select Yes if the database requires a Replication Agent.
Maintenance user A login name for Replication Server to use when updating replicated data. Grant
this user all permissions needed to maintain the replicated data. rs_init cre
ates this login, if it does not already exist, and grants the necessary permissions.
See the Administration Guide Volume 1 for more information about login names
for replication system components.
Maintenance password The password for the maintenance user.
Is this a physical connection for an ex Select Yes if you are adding an active or standby database for a warm standby ap
isting logical connection? plication.
See the instructions for setting up warm standby databases in Managing Warm
Standby Applications in the Administration Guide Volume 2.

32 PUBLIC Overview
Related Information
2.3.5 Logical Connection Information
The Database Setup Worksheet includes logical connection information for adding a database that is part of a
warm standby database application.
Setting up a warm standby application requires additional tasks in the Replication Server before and after you
use rs_init to add the databases to the replication system.
To configure warm standby for Adaptive Server databases, see Manage Warm Standby Applications in the
Administration Guide Volume 2. To configure warm standby for Oracle databases, see Heterogeneous Warm
Standby for Oracle in the Heterogeneous Replication Guide.
Field Description
Is this an active connection or standby (Required) Select Active if you are adding the active database for the warm
connection? standby application.
Select Standby if you are adding the standby database for the warm standby ap
plication.
Logical DS name (Required) The name of the logical data server for the logical connection, cre
ated in advance using create logical connection.
Logical DB name (Required) the name of the logical database for the logical connection, created in
advance using create logical connection.
Complete the rest of the items in this section only if you have selected a standby connection over an active
connection.
Field Description
Active DS name (Required) The name of the data server with the active database. Enter the ac
tual data server name, not the logical data server name defined for the warm
standby database pair.
Active DB name (Required) The name of the active database. Enter the actual database name,
not the logical database name defined for the warm standby database pair.
Active DB SA user (Required) The login name of the system administrator for the data server of the
active database. Replication Server uses this login name to set up warm standby
applications.
Active DB SA password (Required) The password for the system administrator login name of the data
server of the active database.
Initialize standby using dump and load? (Required) Select Yes if you plan to initialize the standby database with the con
tents of the active database with the dump and load commands.
Select No if you plan to initialize the standby database with the bcp utility, or if
you do not need to initialize the standby database.

Overview PUBLIC 33
Field Description
Use dump marker to start replicating to (Required) Select Yes if transactions will be executed in the active database
standby? while the standby database is initialized.
2.3.6 Database RepAgent Information
The Database Setup Worksheet includes database RepAgent information needed if the database requires a
Replication Agent and you have selected to replicate the database.
Field Description
RS user The Replication Server login name that the Replication Agent will use to connect
to the Replication Server.
The default Replication Server user login name and password for this Replication
Agent is the default login name and password for the Replication Server user for
the RSSD RepAgent, which you supplied in the “RSSD RepAgent” section of the
Replication Server Installation Worksheet. For this user to use a different login
name and password, create the user in the Replication Server, then grant con
nect source permission to the user.
RS password The password for the RS user login name.

34 PUBLIC Overview
3 Configure SAP Replication Server and
Add Databases Using rs_init
Use rs_init, either interactively or with a resource file, to configure SAP Replication Server and to add
databases to your replication system.
Related Information
rs_init in Interactive Mode [page 35]

rs_init With a Resource File [page 37]
rs_init Command Line Options [page 46]
Configuring a New Replication Server [page 48]
Adding a Database to the Replication System [page 55]
3.1 rs_init in Interactive Mode
The interactive mode of rs_init is easy to use and catches mistakes that might be missed when using
rs_init with a resource file.
rs_init in interactive mode provides command keys and menu prompts to help you make selections and
move between windows. It also rejects invalid entries and displays warnings or error messages when you make
improper selections. If you make a mistake, change your entry and continue with the installation session.
Related Information
Starting rs_init [page 36]

Configure SAP Replication Server and Add Databases Using rs_init PUBLIC 35
3.1.1 Starting rs_init
Run rs_init and provide the information from the Replication Server Installation Worksheet.
Prerequisites
Set the SYBASE environment variable to the path of the release directory, as described in the Installation Guide.
Context
Each section of the worksheet corresponds to a window or a menu in rs_init. You can also start rs_init
with other command line options for your replication environment.
Run rs_init on the machine on which the Replication Server will run.
Procedure
1. Log in to your machine as the “sybase” user.

2. Change to the release directory:
cd $SYBASE/$SYBASE_REP
3. Enter:
$SYBASE/$SYBASE_REP/install/rs_init
4. Choose Configure a Server Product Replication Server .

From the Configure Replication System menu, you can:
○ Configure a new Replication Server.
○ Add a database to the replication System.
○ Upgrade or downgrade Replication Server.
○ Enable password encryption for a Replication Server or alter passwords in configuration files.
Related Information
rs_init Interactive Command Keys [page 37]

Password Encryption [page 100]
Configuring a New Replication Server [page 48]

36 PUBLIC Configure SAP Replication Server and Add Databases Using rs_init
Adding a Database to the Replication System [page 55]
3.1.1.1 rs_init Interactive Command Keys
rs_init has several command keys that you can use in interactive mode.
Keys Command Action
Ctrl + A Accept Accept the values currently listed in the menu and move to the next menu.
Ctrl + B Backward Scroll backward one page. Use this command key when a menu or list does not fit on
a single screen.
Ctrl + C Quit Quit rs_init and return to the shell prompt. Your terminal may use a key mapping
other than Ctrl + C . Use the key sequence that is mapped to the SIGINT signal.
Ctrl + F Forward Scroll forward one page. Use this command key when a menu or list does not fit on a
single screen.
Ctrl + R Refresh Refresh the screen.
Ctrl + X Exit Exit the current menu or prompt.

or Esc
Ctrl + W Write to Generate a file containing the values specified during the current rs_init session.
resource file The default file name is $SYBASE/$SYBASE_REP/init/logs/
resource.dmp. rs_init prompts you to enter an alternative file name. You can
copy information from this generated file into one of the resource file templates.
? Help Display an online help screen.
3.2 rs_init With a Resource File
Using rs_init with resource files to install, configure, upgrade, or downgrade may save time if you plan to
install multiple Replication Servers and many of the rs_init values are similar.
A resource file is an ASCII-formatted file that contains configuration information for rs_init. Instead of
entering configuration variables during an interactive rs_init session, use a text editor to edit the resource
file to specify the variables, then specify the resource file name on the rs_init command line.
Related Information
Using a Resource File for rs_init [page 38]

3.2.1 Using a Resource File for rs_init
Prepare and use a resource file for rs_init.
Context
SAP supplies several resource file templates for Replication Server. Each template contains the attributes that
are valid for a certain rs_init operation. Copy and edit a template file, which is supplied with the Replication
Server software.
Procedure
1. Select the resource file template to use.

2. Make a copy of the template and rename it to distinguish it from the original. For example:
cp install.rs install.rsx
 Note
You need read and write permissions on the copy of the resource file template to edit it. You may need
to grant write permission to yourself as the file owner.
3. Use a text editor to edit the new resource file.

To use the vi editor, for example, enter:
vi install.rsx
4. When you have finished editing the resource file, start rs_init from the operating system prompt, using
the -r flag to specify your resource file. For example:
$SYBASE/$SYBASE_REP/install/rs_init -r install.rsx
 Caution
If you try to start a resource file session with an input file that is not an edited copy of one of the
resource file templates, rs_init fails upon validation of the input file.
You can also start rs_init using a resource file with other command line options for your replication
environment.
Related Information
Replication Server Resource File Templates [page 39]

Syntax and Parameters for a Resource File [page 39]
Sample Replication Server Resource File [page 41]
3.2.1.1 Replication Server Resource File Templates
The resource file templates for Replication Server are located in subdirectories under the init subdirectory of
the installation directory.
Template Name Description
install.rs Configures a new Replication Server.
setupdb.rs Adds a database to the replication system.
upgr.rs Upgrades an RSSD for a Replication Server. Use this template after installing
new Replication Server software.
upgrdb.rs Upgrades a user database that is already part of a replication system.
downgr.rs Downgrades an RSSD for a Replication Server. Use this template before rein
stalling the previous Replication Server software release.
eers.rs Enables password encryption for a Replication Server.
updrscf.rs Alters a password in a Replication Server configuration file.
3.2.1.2 Syntax and Parameters for a Resource File
Resource files list the attributes and their values to be defined during an rs_init session.
Syntax
Attribute entries are in this format:
<product_name>.<attribute>:<value>
Parameters
<product_name >
Either sybinit or rs.
<attribute>

An item for which you are supplying information, such as a server name or network
protocol.
<value>
The value to assign to the attribute.
Usage
● Resource file entries can be only one line long (80 characters).
● rs_init ignores blank lines and lines that begin with a pound sign (#).
● If you do not enter a valid value for every required attribute, rs_init returns an error when you use the
resource file.
● If an SAP-defined default value exists for an attribute, you can specify the default with the special value
USE_DEFAULT.
● Some resource file attributes can take lists of values. Attributes that can accept lists of values end with
_list. Use commas to separate values. For example:
rs.rs_rs_network_protocol_list:tcp,ipx
● If you use a resource file to upgrade or modify a Replication Server, use the UNCHANGED value to indicate
that a particular attribute should remain unchanged.
● Do not use the USE_DEFAULT or the UNCHANGED value for required attributes with a null default value. Do
not enter USE_DEFAULT or UNCHANGED for the passwords that you specify with these attributes:
Password Attribute User ID
rs.rs_idserver_pass ID Server user
rs.rs_rs_sa_pass Replication Server sa login
rs.rs_rssd_prim_pass RSSD primary user
rs.rs_db_maint_password Database maintenance user
rs.rs_rssd_maint_pass RSSD maintenance user
rs.rs_ltm_rs_pass Log transfer manager login ID
rs.rs_rs_pass Replication Server login name
Passwords are required for these attributes. If the attribute has no value or is not in the resource file, you
see a message in the stdout. For example, if you do not provide a value for the rs_db_maint_password
attribute in the setupdb.rs resource file, you see:
Attribute 'rs_db_maint_password' could not be set because '' is an invalid value
To ensure security, enter a password that complies with the password security requirements, such as a
minimum password length that administrator has enforced. See Replication Server Administration Guide
Volume 1 > Manage Replication Server Security > Managing Replication Server User Security > Manage
Replication Server Login Names and Passwords > Password Configuration Options for All Users.
● If you are rebuilding an existing Replication Server, drop the RSSD or ERSSD before you start rs_init.

3.2.1.3 Sample Replication Server Resource File
The values in your resource file may differ from those in this sample resource file.
######################################################
# RESOURCE TEMPLATE
#
# This file contains a list of configuration attributes
# for Replication Server. This is the template
# for configuring a new Replication Server. DO NOT EDIT
# THIS FILE.
# Copy the template to another file and edit that.
#
# Syntax of the resource file is:
#
# product_name.attribute:value
#
# Attributes with a value of USE_DEFAULT will use the
# Sybase defaults for this platform.
#
#NOTES:
# Generic attributes are prefaced by "sybinit." The
# only generic attributes are "release_directory" and
# "product."
#
######################################################
######################################################
# RELEASE LOCATION
#
sybinit.release_directory: /usr/u/sybase
# The product that you wish to configure. Possible
values are:
# rs
#
sybinit.product: rs
######################################################
# REPLICATION SERVER ATTRIBUTES
#
# This operation installs a new Replication Server.
rs.rs_operation: rs_install
######################################################
# ID SERVER INFORMATION
#
# Name of the ID Server
rs.rs_idserver_name: IDRS
# Is the ID Server the same as the Replication Server
that is being installed ? Default is no
rs.rs_id_server_is_rs_server: yes
# Login that other Replication Servers will use to
# connect with the ID Server. Default is
#<rs_idserver_name>_id_user.
rs.rs_idserver_user: USE_DEFAULT
# Password for the ID Server user. This is a required field.
rs.rs_idserver_pass:
# The next two attributes should be set only when
#installing an ID Server and there are multiple ID
#Server domains
# First ID used for Replication Servers in this ID
#Server domain
rs.rs_start_rs_id: USE_DEFAULT
# First ID used for databases in this ID Server domain
rs.rs_start_db_id: USE_DEFAULT
######################################################
# REPLICATION SERVER INFORMATION
#
# Replication Server name

rs.rs_name: NYRS
# Replication Server sa password. This is a required field.
rs.rs_rs_sa_pass:
# Name of the Replication Server run file. This file will
# start Replication Server with any configured arguments.
# Default is RUN_<rs_name>.
rs.rs_rs_run_file: USE_DEFAULT
# Will the Replication Server manage databases with
# primary data, submit asynchronous transactions, or
#serve as an intermediate site in an indirect route ?
#Default is no
rs.rs_requires_ltm: no
# Will the Replication Server manage databases with primary data,
# submit asynchronous transactions, or serve as an intermediate
# site in an indirect route and the RSSD is an eRSSD? Default is no
rs.rs_erssd_requires_ltm: no
# Will the Replication Server(11.0 or higher) manage
#databases with primary data, submit asynchronous
#transactions, or serve as an intermediate site in an
#indirect route ? Default is yes
rs.rs_needs_repagent: yes
# Locations of the errorlog and config file for the
# Replication Server.
# The default names of these files are <rs_name>.log and
#<rs_name>.cfg respectively.
# The default directory in which these files are located
#is the current working directory on Unix platforms, and
#in %SYBASE%\install on PC platforms.
rs.rs_rs_errorlog: USE_DEFAULT
rs.rs_rs_cfg_file: USE_DEFAULT
# Character set to be used by this Replication Server
#(and the RSSD LTM if needed)
rs.rs_charset: USE_DEFAULT
# Language to be used by this Replication Server (and
#the RSSD LTM if needed)
rs.rs_language: USE_DEFAULT
# Sort order to be used by this Replication Server (and
#the RSSD LTM if needed)
rs.rs_sortorder: USE_DEFAULT
######################################################
# REPLICATION SERVER SYSTEM DATABASE CHOICE
#
# Is this an embedded rssd
rs.rs_rssd_embedded: no
######################################################
# EMBEDDED REPLICATION SERVER SYSTEM DATABASE
#INFORMATION
# The following only applies if embedded RSSD is chosen
#
# erssd name
rs.rs_erssd_name: rep_erssd
# embedded rssd database directory
rs.rs_erssd_database_dir: /work/database
# embedded rssd transaction log directory
rs.rs_erssd_translog_dir: /work/translog
# embedded rssd backup directory
rs.rs_erssd_backup_dir: /work/backup
# embedded rssd error log directory
rs.rs_erssd_errorlog_dir: /work/errorlog
######################################################
# REPLICATION SERVER SYSTEM DATABASE INFORMATION
# The following only applies if embedded RSSD is not
#chosen
# Name of the Adaptive Server that will manage the
# Replication Server's system database.
rs.rs_rssd_sqlsrvr: NYDS
# Name of the database where the Replication Server
#system tables will be stored. Default is <rs_name>_RSSD

rs.rs_rssd_db: USE_DEFAULT
# Do you want the RSSD connections to allow HA failover?
#Default is no
rs.rs_rssd_ha_failover: no
# Do you want rs_init to create the system database ?
#Default is no
rs.rs_create_rssd: no
# sa login for the system Adaptive Server - default is sa
rs.rs_rssd_sa_login: USE_DEFAULT
# sa password for the system Adaptive Server
rs.rs_rssd_sa_pass:
# Name of the RSSD primary user. Default is
#<rs_rssd_db>_prim
rs.rs_rssd_prim_user: USE_DEFAULT
# Password for the RSSD primary user. This is a required field.
rs.rs_rssd_prim_pass:
# Name of the RSSD maintenance user. Default is
#<rs_rssd_db>_maint
rs.rs_rssd_maint_user: USE_DEFAULT
# Password for the RSSD maintenance user. This is a required field.
rs.rs_rssd_maint_pass:
# The dbo_user and dbo_password attributes are not used
#by default. They should be used only if the RSSD
#requires an LTM and the log should be scanned by
#someone other than rs_rssd_sa_login. This user should
already exist in the database.
# Name of the Database Owner for the RSSD
rs.rs_rssd_dbo_user: USE_DEFAULT
# Password for the database owner
rs.rs_rssd_dbo_pass:
######################################################
# REPLICATION SERVER SYSTEM DATABASE DEVICE INFORMAITON
# The following only applies if embedded RSSD is not
# chosen (USED ONLY IF RS_INIT IS TO CREATE THE RSSD)
# Size of the system database in MB. Default and minimum
# is 40
rs.rs_rsdddb_size: 40
# Size of the log for the system database in MB. Default
#and minimum is 32
rs.rs_rssd_log_size:32
# Name of the device on which the system database is to
#be created Default is master
rs.rs_rssd_db_device_name: dbdev
# Do you want rs_init to create this device for the
#system database ?
# Default is no
rs.rs_create_rssd_database_dev: no
# Physical pathname of the device for the system
#database
rs.rs_rssd_db_device_path: /work/dev1
# Size of the device for the system database
rs.rs_rssddb_device_size: 40
# Name of the device on which the log for the system
#database is to be created
rs.rs_rssd_log_device_name: logdev
# Do you want rs_init to create this device for the log
# for the system database ? Default is no
rs.rs_create_rssd_log_dev: no
# Physical pathname of the device for the log for the
# system database
rs.rs_rssd_log_device_path: /work/dev2
# Size of the device for the log for the system database
rs.rs_rssd_log_device_size:32
######################################################
# DISK PARTITION INFORMATION
#
# Full path name of a raw disk partition for the
# Replication Server

rs.rs_diskp_name: /work/dev3
# Logical identifier name for the raw disk partition for
# the Replication Server
rs.rs_diskp_lname: part1
# Size, in megabytes, of the raw disk partition.Default
# is 20.
rs.rs_diskp_size: 20
# The offset, in megabytes, at which the Replication
#Server should begin writing in the raw disk partition.
#Default is 0
rs.rs_diskp_vstart: 0
######################################################
# REMOTE SITE CONNECTION INFORMATION
#
# Replication Server login name that other Replication
# Servers will use to connect with this Replication
# Server Default is <rs_name>_rsi
rs.rs_rs_user: USE_DEFAULT
# Password for the Replication Server login name. This is a required field.
rs.rs_rs_pass:
######################################################
# SYSTEM DATABASE LOG TRANSFER MANAGER INFORMATION
#
# (IF RSSD NEEDS LTM)
# Name of the RSSD LTM. Default is
# <rs_rssd_sqlsrvr>_<rs_name>_RSSD_ltm.
rs.ltm_name: NY_LTM
# Replication Server login name that the log transfer
# manager will use when connecting to the Replication
# Server
# Default is <rs_name>_ltm
rs.rs_ltm_rs_user: USE_DEFAULT
# Password for the login name for the log transfer
# manager.
# This is a required field.
rs.rs_ltm_rs_pass:
# Login name for the user who will start and shutdown
#the log
# transfer manager for the Replication Server system
# database
# Default is sa
rs.rs_ltm_admin_user: USE_DEFAULT
# Password for the admin user.This is a required field.
rs.rs_ltm_admin_pass:
######################################################
# ID SERVER INTERFACES INFORMATION
# These attributes are valid only for Unix platforms.
# On PC platforms, adding interface file entries through
# resource files is not supported.
# rs.do_add_id_server must be no on these platforms.
#
# Add ID Server to interfaces file? Default is no
rs.do_add_id_server: USE_DEFAULT
# Connect retry count; number of times client tries to
# connect to ID Server before giving up
rs.rs_id_server_connect_retry_count: USE_DEFAULT
# Connect retry delay time (in seconds); amount of time
# client waits between each connection attempt
rs.rs_id_server_connect_retry_delay_time: USE_DEFAULT
# Notes associated with ID Server interfaces file entry
rs.rs_id_server_notes: Default Sybase Configuration
# Protocol for ID Server network listener
rs.rs_id_server_network_protocol_list: tcp
# Name of host for ID Server
rs.rs_idserver_hostname: herbie
# Port numbers for network listener
rs.rs_idserver_port: 5002
######################################################

# REPLICATION SERVER INTERFACES INFORMATION
# On PC platforms,adding interface file entries through
# rs.do_add_replication_server must be no on these
# platforms.
#
# Add Replication Server to interfaces file?
rs.do_add_replication_server: no
# connect
# to Replication Server before giving up
rs.rs_rs_connect_retry_count: USE_DEFAULT
# client waits between each connection attempt
rs.rs_rs_connect_retry_delay_time: USE_DEFAULT
# Notes associated with Replication Server interfaces
# file entry
rs.rs_rs_notes: Default Sybase Configuration
# Protocol for Replication Server network listener
rs.rs_rs_network_protocol_list: tcp
# Name of host for Replication Server
rs.rs_rs_hostname: herbie
rs.rs_rs_port: 5005
#####################################################
# LOG TRANSFER MANAGER INTERFACES INFORMATION - IF RSSD
# HAS LTM
# On PC platforms,adding interface file entries through
# rs.do_add_ltm must be no on these platforms.
# Add Log Transfer Manager to interfaces file?
rs.do_add_ltm: no
# connect to Log Transfer Manager before giving up
rs.rs_ltm_connect_retry_count: USE_DEFAULT
#client waits between each connection attempt
rs.rs_ltm_connect_retry_delay_time: USE_DEFAULT
# Notes associated with Log Transfer Manager interfaces
# file entry
rs.rs_ltm_notes: Default Sybase Configuration
# Protocol for Log Transfer Manager network listener
rs.rs_ltm_network_protocol_list: tcp
# Name of host for Log Transfer Manager
rs.rs_ltm_hostname: herbie
rs.rs_ltm_port: 5000
######################################################
# REPLICATION SERVER SECURITY INFORMATION
# These attributes apply to the security features
# available for the replication server. This option is
# only available on Solaris and NT.
# Enable external network security
rs.rs_network_security_enable: no
# Type of network security for the Replication Server,
# choices are "dce" or "csfkrb5",
rs.rs_network_security_system: USE_DEFAULT
# Login name for the user who will principle user, this
# login name will be used for all secure connections,
# SAP recommends the name of the Replication Server
# as the principle user name.
rs.rs_principal_user_name: USE_DEFAULT
# Full path to the location of keytab file
rs.rs_keytab_file: USE_DEFAULT
# Use Secure Socket Layer(ssl) security
rs.rs_use_ssl: no

# Full path to the location of the ssl identity file
rs.rs_ssl_identity_file: USE_DEFAULT
# Password for the ssl private key
rs.rs_ssl_pkey_password:
# end of resource file
3.3 rs_init Command Line Options
Familiarize yourself with the available rs_init command line options for a resource file. You can use some of
these options in an interactive rs_init session.
You can also start rs_init with other command line options for your replication environment:
rs_init -r <resource_file_name> [-<option>] [<parameter>]
where:
● <option> – is the letter specifying a command line option.

● <parameter> – is any valid parameter for that option.
You can specify more than one command line option. The -r option <resource_file_name> are required to
use rs_init in a resource file session.
Flags Parameters Explanation
-a none Validates the resource file and exits without performing

the configuration task. Without the -a flag, rs_init
validates the resource file and continues the product
configuration. The -r flag is required when using with
the -a flag.
-c See the list of supported char Specifies the character set used for all messages and
acter sets. prompts. The -c flag forces rs_init to use a particular
character set. Otherwise, rs_init uses your system’s
default character set.
-e none Records information about the user’s environment, then

exits. Information is written to the log file. Without the -
e flag, rs_init records user environment information
and continues the product configuration.
-h none Prints out usage message (help) and exits.
-I none Allows you to specify the interfaces file that rs_init

should use instead of using the default file located in
$SYBASE directory.
For example, rs_init -I /tmp/interfaces
If you do not specify the interfaces file, rs_init uses

the default file located in $SYBASE.

Flags Parameters Explanation
-l French, German, Japanese, Specifies the language used for all messages and
Spanish, Chinese, Korean prompts. The -l flag forces rs_init to use a particular
language. Without this option, rs_init uses U.S. Eng
lish.
-log Path and file name of log file Lets the user specify location of the session log file.
Without the -log flag, rs_init uses the default log lo
cation ($SYBASE/init/log).
-r Path and file name of resource Tells rs_init to take input from the listed resource
file file. Use this flag in noninteractive sessions to configure
new server products, upgrade existing server products,
or modify existing server products.
-s Path of the release directory Specifies the release directory. If you do not use the -s
flag, rs_init assumes that the release directory is the
current directory.
-T IGNORE_WARNINGS none Entering certain values for some attributes causes

rs_init to exit with a warning. (For example,
rs_init exits if you specify an operating system file
for the location of the master device.) Invoking an
rs_init resource file session with the -T
IGNORE_WARNINGS flag allows the rs_init session
to continue.
-v none Prints the rs_init version string and exits.
-w display_width (Linux only) Set the display_width to change the

maximum length of characters displayed in one line in
rs_init interactive mode.
Value: 80 to 200 characters
If not set, the maximum number of characters allowed is

80; any additional characters are truncated.
To view the full message of long characters, you may

need to manually enlarge the window size of rs_init
interactive mode.
Related Information
Supported Character Sets [page 19]

3.4 Configuring a New Replication Server
Configure a new Replication Server in your replication environment using rs_init.
Prerequisites
Complete the Replication Server Installation Worksheet.
Procedure
1. From the rs_init menu, select Configure a Server Product to see a list of the SAP products installed in
the release directory.
2. Select Replication Server Install a New Replication Server .

You see a list of tasks needed to install a new Replication Server.
 Note
The Install a New Replication Server option only lets you configure a new Replication Server; it does not
allow you to install additional software.
Select each task and complete the windows until the status of each task is “Complete.”
Related Information
Entering Replication Server Information [page 49]

Editing the Interfaces File [page 49]
Entering ID Server Information [page 50]
Selecting the RSSD Type [page 51]
Entering Embedded Replication Server System Database Information [page 52]
Entering Replication Server System Database Information [page 52]
Entering RSSD Device Information [page 53]
Entering RSSD RepAgent Information [page 54]
Entering Disk Partition Information [page 54]
Entering Remote Site Connections Information [page 55]

3.4.1 Entering Replication Server Information
Enter the configuration information for the Replication Server using rs_init.
Procedure
1. In the New Replication Server window, select Replication Server Information.

You see the Replication Server Name window.
2. Enter the name you recorded in the “Replication Server information” section of your worksheet, then press
Return. Press Ctrl + A to accept the name.
3. Select each item on the Replication Server Information screen and enter the value you recorded on your
worksheet. If you use a default value, record it on your worksheet.
 Note
For character sets, language and sort order, enter the appropriate number for the value to select from
the list displayed.
See Customizing Localization for Adaptive Server in the SAP Adaptive Server Enterprise Configuration Guide
for more information on the character sets and sort orders.
In some configurations, if you set Replication Server language before you set its character set, you receive
an error message. To avoid this, set the character set before you set the language.
4. Press Ctrl + A to accept the information and return to the New Replication Server window.
3.4.2 Editing the Interfaces File
Modify the interfaces file. The interfaces file contains network address information for each SAP ASE server
and Replication Server in your replication system.
Procedure
1. To reach the interfaces file window, select Replication Server Interfaces Information from the
Replication Server Information window.
2. Select dsedit to edit the interfaces file if you are using an xterm window or, if xterm is unavailable,
execute the dscp utility from the command line to edit the interfaces file. dscp is in $SYBASE/
$SYBASE_OCS/bin.
 Note
If you are using Replication Server with network-based security, use the directory services of your
network security mechanism to register Replication Servers, SAP ASE servers, and gateway software.
See the documentation that comes with your network security mechanism for details.

See the Open Client and Open Server Configuration Guide for more information on dsedit.
3.4.3 Entering ID Server Information
Complete the ID Server Information dialog box.
Prerequisites
● Have the login name and password (ID Server User/Password) that all Replication Servers use to log in to
the ID Server when you configure the ID Server.
● When you install a Replication Server that is not the ID Server, copy the ID Server Name, ID Server User,
and ID Server Password from the “ID server" section of the worksheet.
Procedure
1. From the New Replication Server window, select ID Server Information. If the Replication Server you are
configuring is the ID Server, you see the ID Server Information window.
If the Replication Server you are installing is not the ID Server, you see the ID Server Name window. Select
ID Server Name and type the name of the ID Server for the replication system from the worksheet you
completed for the ID Server, then press Ctrl + A to accept your changes.
The Starting Replication Server ID and Starting Database ID appear only when you configure the ID Server.
2. Complete the ID Server Information window with the information from the “ID Server” section of your
worksheet.
If you do not make entries for the starting Replication Server ID and starting database ID, the default
ranges are used, as shown in "Default ID Number Ranges and ID Number Allocation for ID Server Domains"
section.
3. Press Ctrl + A to accept your changes and return to the New Replication Server window.
Related Information
ID Server [page 11]

Default ID Number Ranges and ID Number Allocation for ID Server Domains [page 23]

3.4.4 Selecting the RSSD Type
Determine the RSSD type for your replication system.
Context
Before you enter your Replication Server System Database (RSSD) information, decide whether you want an
RSSD or an embedded Replication Server System Database (ERSSD).
Procedure
In the Replication Server System Database Choice window, select:

○ Yes – for an ERSSD using SQL Anywhere. The text on the second line changes to:
2. Embedded Replication Server System
Database INCOMPLETE
Select the Embedded Replication Server System Database option to go to the ERSSD Name window,
then follow the steps to enter information for your ERSSD.
○ No – (default) if you do not want an ERSSD. This assumes you are creating a regular Replication Server
System Database with SAP ASE. The second line on the window appears as:
2. Replication Server Database on ASE INCOMPLETE
Select the Replication Server System Database on ASE option, to go to the Replication Server System
Database window, then follow the steps to enter information for your RSSD.
Related Information
Entering Embedded Replication Server System Database Information [page 52]

Entering Replication Server System Database Information [page 52]

3.4.5 Entering Embedded Replication Server System
Database Information
Complete the ERSSD information dialog box.
Procedure
1. If you selected an ERRSD in Selecting RSSD Type, enter the name of your SQL Anywhere server in the
ERSSD window, and press Ctrl + A to accept the name. The Embedded Replication Server System
Database window appears.
 Note
If you are configuring an existing Replication Server, delete the previous ERSSD database (*.db), the
previous transaction log file (*.log), and the previous transaction log mirror file (*.mlg) before you
start rs_init.
2. You see the following options, each filled with a default value:
○ ERSSD Database Directory
○ ERSSD Transaction Log Directory
○ ERSSD Backup Directory
○ ERSSD Error Log Directory
○ ERSSD Interface Information
Select each item to change the default value to the value you recorded in the Replication Server Installation
Worksheet. See Manage a Replication System in the Administration Guide Volume 1 for more information on
value requirements for ERSSDs.
3. Press Ctrl + A to accept the values and return to the Replication Server System Database Choice
window.
4. Press Ctrl + A to return to the New Replication Server window.
3.4.6 Entering Replication Server System Database

Information
Complete the Replication Server System Database Information dialog box.
Procedure
1. In the New Replication Server window, select Replication Server System Database.

 Note
If you are configuring an existing Replication Server, delete the previous RSSD before you start
rs_init.
2. Select each item on the window and enter the value recorded on your worksheet. If you use a default value,
copy it from the dialog box to your worksheet.
For “RSSD will be replicated,” select Yes if you will have more than one Replication Server in your
environment.
3. Press Ctrl + A to accept the values. You see the New Replication Server window.
3.4.7 Entering RSSD Device Information
If you selected Yes for "Create RSSD" in the Replication Server System Database window, the "RSSD Device
Information" option appears in the New Replication Server window. Fill in the values in this window.
Context
 Caution
Skip this section and go to "Entering Disk Partition Information" if you selected No for Create RSSD in the
Replication Server System Database window, and you already created the RSSD.
Procedure
1. From the New Replication Server window, select RSSD Device Information, then choose Continue.
2. Complete the window using information from your worksheet. If you use a default value, record this on your
worksheet.
3. Press Ctrl + A to accept your entries and return to the New Replication Server window.

3.4.8 Entering RSSD RepAgent Information
Complete the RSSD RepAgent information dialog box.
Context
If you selected Yes for the “RSSD will be replicated” option in the Replication Server System database window,
the “Database Replication Agent” option appears in the New Replication Server window.
Procedure
1. Select Database Replication Agent. Enter the RSSD Replication Server user name, and the Replication
Server password from your worksheet.
 Note
Where necessary, rs_init uses the settings established for the Replication Server when configuring
an RSSD RepAgent.
2. Press Ctrl + A to accept this information.
3.4.9 Entering Disk Partition Information
Complete the disk partition information dialog box.
Prerequisites
If the Replication Server disk partition is a raw device, make sure the disk partition existst before you can start
working on the Disk Partition Information window. However, if the disk partition is an operating system file,
Replication Server automatically creates the disk partition if the partition does already not exist.
Procedure
1. From the New Replication Server window, select Disk Partition.

2. Complete the window using the information you recorded on your worksheet.
You can add more partitions after Replication Server is installed. See the Design Guide for help in
determining how much space you need.

3. Press Ctrl + A to accept the values and return to the New Replication Server window.
3.4.10 Entering Remote Site Connections Information
Modify the default values in the Remote Site Connections window, which rs_init provided based on the
Replication Server name you entered.
Procedure
1. From the New Replication Server window, select Remote Site Connections.
2. Complete the window using the information on your worksheet. If you use a default value, copy it to the
“Remote site connections” section of the worksheet.
3. Press Ctrl + A to accept your changes and return to the New Replication Server screen.
3.5 Adding a Database to the Replication System
Add a database to the replication system. Each primary or replicate database in a replication system is
managed by a Replication Server.
Prerequisites
Complete the Database Setup Worksheet.
Procedure
1. From the RS_INIT menu, select Configure a Server Product.

2. Select Replication Server. You see the Configure Replication System window.
3. Select Add a Database to the Replication System.
rs_init indicates the status of each part of the installation with “Incomplete” or “Complete.”
4. Select Replication Server Information, then click Continue.
5. Select Replication Server Name. Enter the name of the Replication Server from your worksheet. Press
Ctrl + A to accept your changes.
6. Complete the window using the information you recorded on your worksheet.
If the status of Replication Server Interfaces Information is “Incomplete,” add an entry to the interfaces file
for the Replication Server.

7. Press Ctrl + A to accept your changes and return to the Add Database to Replication System window.
Related Information
Completing Database Information [page 56]

Completing Logical Connection Information [page 57]
Completing the Configuration [page 57]
Editing the Interfaces File [page 49]
3.5.1 Completing Database Information
Finalize the database information.
Procedure
1. In the Add Database to Replication System window, select Database Information, then click Continue.
2. Complete the window using the information you recorded on the worksheet. If you use a default value,
record this information on to your worksheet. The label refers to SAP ASE server as “SQL Server.”
 Note
The password you specify in this step must be valid to log in to SAP ASE as “sa”. You cannot change the
password in rs_init by specifying a different password in this window. To change the SAP ASE server
“sa” password, log in to the SAP ASE server after installation and change the password using the
alter user command.
3. Choose Yes for “Will the Database Be Replicated?” if:
○ It contains primary data.

○ It is part of a warm standby application.
○ Applications execute replicated stored procedures in it.
4. If you are adding the active or standby database for a warm standby application:
a. Choose Yes for “Is This a Physical Connection for Existing Logical Connection?”
b. Specify the additional information in the Logical DB Setup window.
5. Press Ctrl + A to accept your changes, then go to “Completing the Configuration” section.

3.5.2 Completing Logical Connection Information
Finalize the information you entered in the Logical Connection information window.
Prerequisites
● Set up a warm standby application between Adaptive Server databases. See Manage Warm Standby
Applications in the Administration Guide Volume 2.
● Set up a warm standby application between Oracle databases. See Heterogeneous Warm Standby for
Oracle in the Heterogeneous Replication Guide.
 Note
Create the logical connection in the Replication Server before you add a database for a warm standby
application.
Procedure
1. If you selected Yes to “Is This a Physical Connection for Existing Logical Connection?” in the Database
Information window, Logical Database Setup selections appear. Specify logical connection parameters.
In the Database Information window, select Logical DB Setup.
The Logical Connection Information window appears. When you choose “active” for the first item, only
these options appear:
○ Logical DS Name
○ Logical DB Name
2. Complete the Logical Connection Information window using the information on your worksheet. If you use
a default value, record this information on your worksheet.
3. Press Ctrl + A to accept your changes, and rs_init returns you to the Database Information window.
3.5.3 Completing the Configuration
Complete the replication system configuration.
Procedure
1. If the Database Information window indicates incomplete tasks on the Add Database to Replication System
window, select each one and complete the required information.
When all tasks show as “Complete,” press Ctrl+A Ctrl + A . A message asks whether to execute the
configuration.

2. Enter y to continue with the configuration.
Messages appear on the window as the configuration progresses; these messages require no action.
Do not interrupt the configuration. Most configurations require at least several minutes to complete.
When the configuration is complete, rs_init displays “Configuration completed successfully.”

3. Click OK to return to the Configure Replication System window.
 Note
To add other databases to the replication system, go to “Adding a database to the replication system”
section, and repeat the procedure for each database.
4. Press Ctrl + X to navigate through the screens and exit the program. rs_init displays the path to the
log file for the session before you return to the command prompt.
Results
Find out more about the progress of the installation by looking at the current rs_init log file. rs_init log
files are stored in the init/logs subdirectory of the $SYBASE_REP directory.

4 Upgrade or Downgrade SAP Replication
Server
Upgrade or downgrade SAP Replication Server, or migrate to 64-bit platforms.
 Caution
Do not modify the secondary truncation point of Replication Agent, truncate the transaction log, or
increase the generation number while upgrading.
Related Information
Prerequisites When Using Kerberos [page 59]

Requirements for Upgrading [page 60]
Preparing to Upgrade [page 61]
Upgrading Replication Server [page 63]
Upgrading SAP ASE in a Replication System [page 85]
Downgrading Replication Server [page 91]
Migrating Between 32-Bit and 64-Bit Platforms [page 94]
Required Replication Servers [page 9]
4.1 Prerequisites When Using Kerberos
If you are using Kerberos authentication, disable it before you upgrade or downgrade SAP Replication Server.
Here is a simple way to disable Kerberos authentication:
● In SAP ASE, set unified login required to 0.
sp_configure "unified login required", 0
● In SAP Replication Server, set use_security_services to off.
config replication server set use_security_services to 'off'
After the upgrade or downgrade is complete, revert these settings back to their previous values to enable
Kerberos authentication.
For more information about enabling and disabling Kerberos, see the Replication Server Administration Guide
Volume 1.

Upgrade or Downgrade SAP Replication Server PUBLIC 59
4.2 Requirements for Upgrading
There are several requirements for the site, route, and system versions, mixed-version environments, and
different platforms, when you upgrade Replication Server.
Site, Route, and System Version
If a replication system domain has Replication Server 16.0 SP03 PL07 and later, then the system and route
versions in the replication system domain requires version 12.6 and later.
If the Replication Server version, the site version, and the route version are earlier than 12.6, upgrade
Replication Server to version 12.6 or later, set site version to 12.6 or later, and upgrade routes to 12.6 or later,
before you can install Replication Server 16.0 SP03 PL07.
Mixed-Version Environments
Replication Server 16.0 SP03 PL07 (and later) does not support mixed-version environments containing
versions earlier than 12.6. You can upgrade directly to Replication Server 16.0 SP03 PL07 from versions 12.6
and later, including any ESDs for versions 12.6 and later.
 Note
To create a database subscription from a primary Replication Server with version 16.0 SP03 PL07, use a
15.7.1 SP303 (or later) version replicate Replication Server.
SQL Anywhere Version for ERSSD
ERSSD requires SQL Anywhere. SAP Replication Server 16.0 SP03 PL07 includes SQL Anywhere version 16.0
on 64-bit Linux, Solaris SPARC, Solaris x64, HP-UX Itanium, and IBM AIX.
Version 16.0 SP03 PL07 also includes SQL Anywhere version 12 for upgrading an ERSSD database format if
you have installed an earlier version of SQL Anywhere.
File Permission
Change OpenLDAP file permissions to 755 if you are upgrading SAP Replication Server versions 16.0 SP03
PL03 or 16.0 SP02 PL07 to a later version in these operating systems:
● HP-UX Itanium (64-bit)

● IBM AIX (64-bit)

60 PUBLIC Upgrade or Downgrade SAP Replication Server
● Solaris x86-64 (64-bit)
● Solaris SPARC (64-bit)
Execute the following:
chmod 755 $SYBASE/REP-16_0/lib64/COPYRIGHT.openldap

chmod 755 $SYBASE/REP-16_0/lib64/LICENSE.openldap
Related Information
Commit a Local Site to a New Version Level [page 79]

Replication Server Site Version [page 81]
Replication Server Route Version [page 82]
4.3 Preparing to Upgrade
Prepare the Replication Server for upgrade.
Procedure
1. Back up the RSSD or ERSSD. The upgrade process makes changes to the RSSD or ERSSD that you cannot
roll back if the upgrade fails. Restore the RSSD or ERSSD from the backup if the upgrade fails.
2. When you upgrade from a pre-15.7 version of SAP Replication Server using a customized
rs_sqlserver_function_class in your connection, you may lose some customized function-string-
class scope functions.
SAP recommends that you back up these function strings before upgrading:
○ rs_commit
○ rs_get_lastcommit
○ rs_get_thread_seq
○ rs_get_thread_seq_noholdlock
○ rs_initialize_threads
○ rs_ticket_report
○ rs_update_threads
3. Determine where to install Replication Server.
If you plan to install the Replication Server software in a directory that:
○ Does not contain your existing Replication Server installation – verify that the interfaces file is
accessible and see Upgrading Replication Server [page 63]
○ Contains your existing Replication Server installation – see Upgrade and Downgrade Using Existing
Directories [page 97]

4. Use rs_helpsub and rs_helpdbsub to check that all subscriptions are valid. The upgrade fails if there
are subscriptions that are not in a valid state before upgrading.
5. Install Replication Server, following the instructions in the installation guide for your platform.
6. Verify the system-wide and route versions and upgrade to version 12.6 if necessary:
Task Descrption Actions
Check System version Execute sysadmin ○ If the system version is 1260, you
system_version on the current are ready to upgrade to SAP
SAP Replication Server: Replication Server 16.0 SP03
PL07. Proceed to "Upgrading
sysadmin system_version Replication Server" in the next
go
section.
An example of the output is: ○ If the system version is earlier or

later than 12.6, go to "Set ID
The current system Server system version."
version is 1102.
Set ID Server system version ○ If the system version is earlier ○ If successful, go to "Recheck
than 12.6, set the system version system version."
on the ID server to 1260,
○ If unsuccessful, go to "Upgrade
otherwise some features are
Replication Server to 12.6."
disabled after upgrading:
sysadmin
system_version, 1260
go
If setting the system version is

unsuccessful, you see this
message: The system
version could not be
set. The specified
version '1260' is
higher than the lowest
Replication Server
version in the system
'1250'
If setting the system version is
successful, you see this
message: The system
version has been reset
from 1102 to 1260
○ If the system version is larger
than 12.6, use the traceflag
RSFEATURE_SYSVER_UPDAT
E to set the system version on
the ID server to 1260, otherwise
when you create table replication

Task Descrption Actions
definition, table level functions

and function strings will not be
created for this replication
definition:
RSFEATURE_SYSVER_UPD
ATE, 1260
go
Upgrade Replication Server to 12.6 Upgrade Replication Server to 12.6 Go to "Set ID Server system version."
and set the site version to 12.6 for any
Replication Server in the domain that
has a version earlier than 12.6.
Recheck system version Execute sysadmin ○ If the system version is 12.6, go

system_version again on the to "Verify route version."
current Replication Server. ○ If the system version is not 12.6,
go to "Set ID Server system
version."
Verify route version Execute admin ○ If the route version is lower than
show_route_versions to verify 12.6, upgrade them to 12.6. See
all route versions are 1260 or later. Upgrade Routes in the
Administration Guide Volume 1.
○ If the route version is 12.6 or
later, you can upgrade to SAP
Replication Server 16.0 SP03
PL07.
4.4 Upgrading Replication Server
Upgrade Replication Server from version 12.6 and later.
1. Backing Up the RSSD or ERSSD Before Upgrade [page 64]

Back up the RSSD or ERSSD before you upgrade Replication Server. The upgrade process makes
changes to the RSSD or ERSSD that you cannot roll back if the upgrade fails. Restore the RSSD or
ERSSD from the backup if the upgrade fails.
2. Stopping Replication Agent and Quiescing Replication Server [page 65]
Stop Replication Agent and quiesce Replication Server to purge all inbound queues.
3. Deciding the Upgrade Method to Use [page 66]
Decide whether to upgrade Replication Server and associated databases using the simplified upgrade
method with repserver or continue to upgrade with rs_init.
4. Upgrading RSSD or ERSSD and User Databases with repserver [page 66]
Use the utility to upgrade the Replication Server RSSD or ERSSD, and user databases in one step.

5. Upgrading RSSD or ERSSD with rs_init [page 70]
(Optional) Use rs_init to upgrade the RSSDs or ERSSDs to be compatible with the executable
programs in the Replication Server version to which you are upgrading.
6. Fixing a Failed Replication Server Upgrade [page 74]
Retry the upgrade process if it fails.
7. Upgrades to User Databases [page 74]
After you upgrade the Replication Server RSSD or ERSSD, apply upgrades to a primary, replicate, or
standby database in the replication system to accommodate changes, such as installing new stored
procedures, that support the new version of Replication Server to which you are upgrading, and
features such as Multi-Path Replication.
8. Commit a Local Site to a New Version Level [page 79]
After you upgrade a Replication Server and its user databases, decide whether to commit to the new
Replication Server version level, set the replication site version to the new version, and upgrade the
route version to the new version.
9. Backing Up the RSSD or ERSSD After Upgrade [page 84]
Back up the RSSD or ERSSD after upgrading Replication Server, setting its site version, and performing
route upgrades to the relevant routes.
Related Information
Backing Up the RSSD or ERSSD Before Upgrade [page 64]

Stopping Replication Agent and Quiescing Replication Server [page 65]
Deciding the Upgrade Method to Use [page 66]
Upgrading RSSD or ERSSD and User Databases with repserver [page 66]
Upgrading RSSD or ERSSD with rs_init [page 70]
Fixing a Failed Replication Server Upgrade [page 74]
Upgrades to User Databases [page 74]
Commit a Local Site to a New Version Level [page 79]
Backing Up the RSSD or ERSSD After Upgrade [page 84]
4.4.1 Backing Up the RSSD or ERSSD Before Upgrade
Back up the RSSD or ERSSD before you upgrade Replication Server. The upgrade process makes changes to
the RSSD or ERSSD that you cannot roll back if the upgrade fails. Restore the RSSD or ERSSD from the backup
if the upgrade fails.
Procedure
1. Back up the RSSD using the SAP ASE dump database or dump transaction commands, or the ERSSD
using the Replication Server sysadmin erssd, backup command.

2. (Optional) Restore the RSSD using the SAP ASE commands load database or load transaction
command, or restore the ERSSD using the ERSSD recovery procedure.
See the Administration Guide Volume 1 > Manage a Replication System > > Manage the Embedded
Replication Server System Database for information on recovery procedures.
Task overview: Upgrading Replication Server [page 63]
Next task: Stopping Replication Agent and Quiescing Replication Server [page 65]
4.4.2 Stopping Replication Agent and Quiescing Replication

Server
Stop Replication Agent and quiesce Replication Server to purge all inbound queues.
Procedure
1. On Replication Server, stop Replication Agent for all primary databases and system databases:
suspend log transfer from all
2. If you are using an SAP ASE server as the RSSD, stop RepAgent for the RSSD:
sp_stop_rep_agent <RSSD_name>
3. If there are incoming routes to the Replication Server you are upgrading, log in to the source Replication
Server and suspend all routes to the Replication Server (<dest_rs>) you are upgrading:
suspend route to <dest_rs>
4. Execute the admin command on the Replication Server to verify that the Replication Server queues have
been drained out and that the Replication Server you are upgrading has been quiesced:
admin quiesce_check
If Replication Server is not yet quiesced, retry with admin quiesce_force_rsi.
 Caution
If Replication Server is not quiesced, you may lose data if you proceed with the upgrade process.
Previous task: Backing Up the RSSD or ERSSD Before Upgrade [page 64]
Next task: Deciding the Upgrade Method to Use [page 66]

4.4.3 Deciding the Upgrade Method to Use
Decide whether to upgrade Replication Server and associated databases using the simplified upgrade method
with repserver or continue to upgrade with rs_init.
Procedure
1. Use the repserver utility to upgrade the Replication Server RSSD or ERSSD, and user databases in one
step.
Optionally, continue to use rs_init to upgrade the Replication Server RSSD or ERSSD, and user
databases in several steps.
2. Upgrade user databases in the replication system only if they failed to upgrade during seamless upgrade or
if you excluded them from the upgrade process.
To upgrade the user databases, use one of:
○ Fixing User Database Upgrades with sysadmin upgrade, "database" [page 75]
○ Upgrading an SAP ASE User Database with rs_init [page 76]
You can use sysadmin upgrade, "database" or rs_init to upgrade the user databases.
Previous task: Stopping Replication Agent and Quiescing Replication Server [page 65]
Next task: Upgrading RSSD or ERSSD and User Databases with repserver [page 66]
4.4.4 Upgrading RSSD or ERSSD and User Databases with

repserver
Use the utility to upgrade the Replication Server RSSD or ERSSD, and user databases in one step.
Prerequisites
● Back up the RSSD or ERSSD.

● Stop Replication Agent and quiesce Replication Server.
Context
Repeat the steps in this task for every Replication Server you want to have.

ERSSD requires SAP SQL Anywhere, which is compatible with 64-bit versions operating system. If you are
upgrading to SAP Replication Server 16.0 SP03 PL07 on Solaris SPARC, Solaris 10 x64, or IBM AIX, and using
ERSSD, platforms must be 64-bit for the upgrade to function properly. For these operating systems, ERSSD
can only be run on 64-bit machines. This is a restriction of the underlying SAP SQL Anywhere database.
Procedure
1. If the Replication Server uses SAP ASE for the RSSD, grant sa_role to the primary user at the RSSD:
sp_role 'grant', sa_role, <primary_user>
You can revoke the “sa” role after the upgrade process is finished by executing:
sp_role 'revoke', sa_role, <primary_user>
 Note
The <RSSD_primary_user> in the .cfg file requires a replication role or “sa” role. The
<RSSD_primary_user> may not necessarily be the sa user ID or the user that has been entered in the
rs_init pane.
2. Grant sa_role to the maintenance user for each user database.

3. Shut down the preupgrade version of Replication Server.
a. Use isql to log in to the Replication Server as the system administrator:
isql -Usa -P<sa _password> - S<rs_name>

go
b. Enter:
shutdown
go
4. Log in as the "sybase" user and change to the $SYBASE directory where you installed the new Replication
Server.
5. Use the SYBASE.sh or SYBASE.csh shell script to set SYBASE environment variables to the directory in
which you installed the new Replication Server.
6. Start the new version of Replication Server in upgrade mode:
repserver –upgr –S <rs_name> –A < erssd_release_dir>

–C <config_file> –I <interfaces_file> –E <errorlog_file>
In upgrade mode, Replication Server upgrades the ERSSD or RSSD it is using, automatically connects to
each user database to which it has maintenance user access, and where a connection exists, applies the
upgrade scripts to the database.
The full syntax is:
repserver [-C <config_file>] [-i <id_server>]

[-S <rs_name>] [-I <interfaces_file>]
[-E <errorlog_file>] [-M] [-v] [-K <keytab_file>]
[-upgr] [-A< erssd_release_dir>] [-purgeq]

[–nodb {all|<dbid_1>[,<dbid_2>[,<dbid_3>[,…]]]]}
[-e]
where:
○ -upgr – instructs Replication Server to start the upgrade
○ -A <erssd_release_directory> – specifies the location of the release directory of the ERSSD you
are going to upgrade if Replication Server is using an ERSSD, for example:
/sybase/REP-16_0/ASA17
Two new configuration file items erssd_release_dir_generated and
erssd_start_cmd_generated are generated by seamless upgrade when using the -A option.
 Note
These two configuration file items are generated by Replication Server internally. Do not manually
change them. The rs_init command ignore ths -A option when performing upgrades and
downgrades because it uses the erssd_start_cmd and erssd_release_dir parameters
specified in the configuration file.
If you do not include the -A option, Replication Server obtains the release directory location from the
configuration file if it 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 command overrides configuration file settings.
○ -purgeq – purges transactions from the inbound queue. 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, no record of the SQL statements is generated.
With or without the -e option, the upgrade process uses the Replication Server error log file to record
any errors that occur during the upgrade process, and why any user database was not upgraded.
You can use only the -A, -purgeq, -nodb, and -e options when you use -upgr. See repserver in the
Reference Manual for descriptions of the other repserver parameters.
For example, the NY_RS Replication Server is using the /sybase/REP-16_0/ASA11 ERSSD release
directory location, the <ny_rs.cfg> configuration file, the interfaces file, and the ny_rs_errorlog
error log file, and ou are upgrading it, enter:
repserver –upgr –SNY_RS –A/sybase/REP-16_0/ASA17 –Cny_rs.cfg –Iinterfaces –E

ny_rs_errorlog
If the upgrade is successful, the upgrade mode shuts down Replication Server and you do not see any
warning or error messages.
7. Restart Replication Server using the appropriate executables for the new version.

 Caution
Some Replication Server configuration options with newer versions may have a wider valid range. If you
increase any of these configuration options after upgrading, reinstate the old values before
downgrading. Otherwise, the Replication Server may not start or may behave incorrectly.
8. If you installed the new Replication Server software in a different directory than the earlier version, modify
the runserver files for the Replication Server to replace the old binary with new binary in the new version
directory.
9. If you are using SAP ASE as the RSSD, and it has a RepAgent, restart the RepAgent for the RSSD:
sp_start_rep_agent <RSSD_name>
10. Resume log transfer to Replication Server from all Replication Agents for primary databases, and RSSD or
ERSSD:
resume log transfer from all
11. If there are incoming routes to <dest_rs> (the Replication Server you upgraded and now restarted), log in
to the source Replication Server and resume all routes to <dest_rs> to allow the source Replication
Server to begin sending queued messages to <dest_rs>. At the source Replication Server, execute:
resume route to <dest_rs>
12. Check the upgraded Replication Server:

a. Verify that the RSSD or ERSSD version of the upgraded Replication Server is correct.
You can check one of:
○ Replication Server error log – you see:
Upgraded RSSD successfully. The current RSSD version is '1600003'.
○ rs_config table – log in to isql and enter:
select * from rs_config where optionname='current_rssd_version'
b. Check that the Replication Server modules are running by executing admin who with the relevant
options.
Previous task: Deciding the Upgrade Method to Use [page 66]
Next task: Upgrading RSSD or ERSSD with rs_init [page 70]

4.4.5 Upgrading RSSD or ERSSD with rs_init
(Optional) Use rs_init to upgrade the RSSDs or ERSSDs to be compatible with the executable programs in
the Replication Server version to which you are upgrading.
Prerequisites
● Back up the RSSD or ERSSD.

● Stop Replication Agent and quiesce Replication Server.
Context
Upgrading an RSSD or ERSSD may add new Replication Server system tables, add new rows or columns to
existing tables, or install new stored procedures. Upgrade an RSSD based on the information from the
Replication Server Installation Worksheet for the Replication Server you are upgrading. Use rs_init to
individually upgrade any primary, replicate, or standby user databases in the replication system to
accommodate such changes as installing new stored procedures, that support the new version of Replication
Server to which you are upgrading.
SAP Replication Server Version to Upgrade From Supported SAP SQL Anywhere and dbsrv Binary Version
12.6 and pre12.6 8
15.0 – 15.1 9
15.2 – 15.6 11
15.7 – 15.7.1 SP120 12
15.7.1 SP200 16
15.7.1 SP300 16
16.0 SP03 17
Repeat the steps in this task for every Replication Server you want to upgrade.
ERSSD requires SAP SQL Anywhere, which is compatible with 64-bit versions operating system. If you are
upgrading to SAP Replication Server 16.0 SP03 PL07 on Solaris SPARC, Solaris 10 x64, or IBM AIX, and using
ERSSD, platforms must be 64-bit for the upgrade to function properly. For these operating systems, ERSSD
can only be run on 64-bit machines. This is a restriction of the underlying SAP SQL Anywhere database.
Procedure
1. Log in as the “sybase” user and change to the $SYBASE directory where you installed Replication Server.

2. Use the SYBASE.sh or SYBASE.csh shell script to set SYBASE environment variables to the directory in
which you installed the new Replication Server.
3. Verify that the RSSD and Replication Servers that you are upgrading are running.
4. If the Replication Server uses SAP ASE for the RSSD, grant sa_role to the primary user at the RSSD:
sp_role 'grant', sa_role, <primary_user>
You can revoke sa_role after the upgrade process is finished by executing:
sp_role 'revoke', sa_role, <primary_user>
 Note
The <RSSD_primary_user> in the .cfg file needs a replication or sa role. The

<RSSD_primary_user> may not necessarily be the sa user ID or the user who has been entered in the
rs_init pane.
5. If the Replication Server uses an ERSSD, edit the <rs_name>.cfg file, where <rs_name> is your
Replication Server:
a. Add the erssd_release_dir parameter to specify the location of the SQL Anywhere ERSSD
database you are going to upgrade, such as the following, where <xx> is the version of SQL Anywhere
being upgraded:
erssd_release_dir=/sybase/REP-16_0/ASA<xx>
b. Add the erssd_start_cmd parameter to specify the command to start the previous version of
ERSSD.
You can find an example of the parameter in the Replication Server error log by searching for “ERSSD
start command”. You see an entry similar to the following, where <xx> is the version of SQL Anywhere
and dbsrb being upgraded:
ERSSD start command: /sybase/REP-16_0/ASA<xx>/bin/dbspawn

-f -q /sybase/REP-16_0/ASA<xx>/bin/dbsrv<xx>-s none -ti 0 -x
"tcpip(PORT=15501;DOBROAD=NO;BLISTENER=NO)"
-o /sybase/REP-16_0/errorlog/rs160_prs_ERSSD.out
/sybase/REP-16_0/dbfile/rs160_prs_ERSSD.db
c. From the interfaces file, obtain the name and location of the Replication Server you are upgrading,
and the port number of the Replication Server RSSD.
6. If the Replication Server uses an ERSSD, and is performing routing, edit the <rs_name>.cfg file, where
<rs_name> is your Replication Server:
a. Add the erssd_ra_release_dir parameter to specify the location of the SQL Anywhere ERSSD
database you are going to upgrade, such as the following, where <xx> is the version of SQL Anywhere
being upgraded:
erssd_ra_release_dir=/sybase/REP-16_0/ASA<xx>
b. Add the erssd_ra_start_cmd parameter to specify the command to start the previous version of
ERSSD.
Obtain the name of the ERSSD Replication Agent and the location of the interfaces file from the
Replication Server log file by searching for “Starting embedded RSSD Replication Agent” and using the

same command format from the next line: “Executing command.” In this example, <xx> is the version
of SQL Anywhere and dbsrv being upgraded:
erssd_ra_start_cmd=/sybase/REP-16_0/ASA<xx>/bin/dbltm
-ud -S SAMP_RS_ERSSD_ra
-C /sybase/REP-16_0/samp_repserver/SAMP_RS_ERSSD_ra.cfg
-ot /sybase/REP-16_0/samp_repserver/SAMP_RS_ERSSD_ra.out
-I /sybase/interfaces
7. If you are upgrading from Replication Server version 12.6 to version 16.0 SP03 PL07 and the Replication
Server uses an ERSSD, include the lib subdirectory of the ASA directory in the LD_LIBRARY_PATH
environment variable:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/work/RS160/REP-16_0/ASA17/lib
export LD_LIBRARY_PATH
8. Start rs_init:
9. Select Configure a Server Product, then Continue.
10. Select Replication Server.
11. Select Upgrade an Existing Replication Server.
12. Complete the Upgrade Existing Replication Server window with the information from the Replication
Server Installation Worksheet for the Replication Server you are upgrading.
a. Enter the name of the Replication Server with the RSSD you are upgrading.
b. Enter the login name for the Replication Server sa user. The default value is “sa”
c. Enter the password for the sa user on the Replication Server.
d. Enter the path name of the Replication Server configuration file.
e. Press Ctrl + A to save your changes. You see:
Execute the Replication Server tasks now?
13. Enter “y” to continue the RSSD upgrade.
rs_init displays informational messages as it loads the upgrade script into the RSSD. When the upgrade
is complete, you see:
RSSD successfully upgraded from <old_rel_no> to <new_rel_no>. Replication Server
'<rs_name>' can now be restarted. Task to upgrade the RSSD succeeded.
Configuration completed successfully.
where:
○ <old_rel_no> – is the Replication Server version from which you are upgrading.
○ <new_rel_no> – is the new Replication Server version.
○ <rs_name> – is the name of the Replication Server.
14. If you installed the new Replication Server software in a different directory than the earlier version, modify
the runserver files for the Replication Servers so they use the programs in the new version directory.
15. Restart Replication Server using the appropriate executables for the new version.
 Caution
Some Replication Server configuration options with newer versions may have a wider range of valid
value. If you increase any of these configuration options after upgrading, reinstate the old values before
downgrading, or the Replication Server may not start or may behave incorrectly. The Replication

Server upgrade process prints all the current configuration option values in the rs_config to the
rs_init log, so that you can restore the former settings before downgrading.
a. Modify the old runserver file, run_<servername>, where <servername> is your Replication Server
name, to replace the old binary with the new binary in $SYBASE/REP-16_0/bin/repserver, and
start Replication Server from $SYBASE/REP-16_0/bin/repserver.
b. If you are using SAP ASE as the RSSD, restart the RepAgent for the RSSD:
c. Resume log transfer to Replication Server from all Replication Agents for primary databases, and the
RSSD or ERSSD:
resume log transfer from all
d. If there are incoming routes to <dest_rs> (the Replication Server you upgraded and have now
restarted) log in to the source Replication Server and resume all routes to <dest_rs> to allow the
source Replication Server to begin sending queued messages to <dest_rs>. At the source Replication
Server, execute:
resume route to <dest_rs>
Previous task: Upgrading RSSD or ERSSD and User Databases with repserver [page 66]
Next task: Fixing a Failed Replication Server Upgrade [page 74]
Related Information
Suggested Usage for Replication Server Upgrade Using Embedded RSSD [page 73]
4.4.5.1 Suggested Usage for Replication Server Upgrade

Using Embedded RSSD
Suggested usage for Replication Server upgrade when using embedded RSSD.
● While using the seamless upgrade function to upgrade eRSSD using repserver -upgr command, always
use the -A option to specify your ASA release directory.
● While using rs_init to upgrade eRSSD, specify the correct erssd_start_cmd and
erssd_release_dir values manually in the configuration file.

4.4.6 Fixing a Failed Replication Server Upgrade
Retry the upgrade process if it fails.
Procedure
1. Restart the old Replication Server against the RSSD and fix any problem that may have caused the error.
2. Re-run the upgrade process after you fix the error.
Repeat the process until the upgrade succeeds.
 Note
You cannot start a new Replication Server against a partially upgraded RSSD if you used rs_init.
However, you can start a new Replication Server in upgrade mode as many times as needed, using the
-upgr option with repserver, against a partially upgraded RSSD to continue the upgrade process or
to fix upgrade problems.
Previous task: Upgrading RSSD or ERSSD with rs_init [page 70]
Next: Upgrades to User Databases [page 74]
4.4.7 Upgrades to User Databases
After you upgrade the Replication Server RSSD or ERSSD, apply upgrades to a primary, replicate, or standby
database in the replication system to accommodate changes, such as installing new stored procedures, that
support the new version of Replication Server to which you are upgrading, and features such as Multi-Path
Replication.
Upgrading an RSSD or ERSSD may add new Replication Server system tables, add new rows or columns to
existing tables, or install new stored procedures. To accommodate changes that support the new version of
Replication Server to which you are upgrading, repserver or rs_init applies upgrades to user databases
such as a primary, replicate, or standby database in the replication system.
Not applying upgrades to replicate databases results in the following:
● SAP ASE – you cannot use Multi-Path Replication for replication to SAP ASE databases after you upgrade
Replication Server to 15.7 and later.
● SAP IQ – Replication Server suspends replicate connections to the SAP IQ replicate databases after you
upgrade Replication Server to 15.7.1 or later, and you see a "Awaiting Upgr" status if you use admin who.
You can upgrade the SAP IQ database using one of:
○ repserver -upgr – upgrades Replication Server at the same time

○ sysadmin upgrade,'database' – after upgrading Replication Server with rs_init or repserver
with the -nodb option
● Oracle – Replication Server suspends replicate connections to the Oracle replicate databases after you
upgrade Replication Server to 15.7.1 SP101 or later, and you see a "Awaiting Upgr" status if you use admin
who. You can upgrade the Oracle database using one of:
○ repserver -upgr – upgrades Replication Server at the same time
○ sysadmin upgrade,'database' – after upgrading Replication Server with rs_init or repserver
with the -nodb option
Parent topic: Upgrading Replication Server [page 63]
Previous task: Fixing a Failed Replication Server Upgrade [page 74]
Next: Commit a Local Site to a New Version Level [page 79]
Related Information
Fixing User Database Upgrades with sysadmin upgrade, "database" [page 75]
Upgrading an SAP ASE User Database with rs_init [page 76]
Upgrading Non-SAP ASE User Databases and User Databases Not Supported by sysadmin upgrade [page 77]
Upgrading Oracle User Databases Manually [page 78]
4.4.7.1 Fixing User Database Upgrades with sysadmin

upgrade, "database"
Apply upgrades to SAP ASE, Oracle, or SAP IQ, primary, replicate, or standby databases in the replication
system that failed to upgrade during the automatic upgrade process, or to databases that you excluded from
the automatic upgrade process.
Context
The upgrades are required to accommodate changes, such as installing new stored procedures that support
the new version of Replication Server to which you are upgrading.
Procedure
1. Enter admin version, “connection” at the upgraded Replication Server to identify the user
databases that you need to upgrade.

You see a list of the user databases and data servers, the database IDs, the corresponding Replication
Server, and the status of the database. For example:
dbid Name Controller RS Status

------ ---------- -------------- ------------------
101 pds.pdb01 rs_12 Database needs upgrade
102 pds.pdb02 rs_12 Database is not accessible
103 rds.rdb01 rs_12 Database has been upgraded
The “Not accessible” status means that Replication Server cannot connect to this user database because
the database is unavailable, or because the maintenance user ID that Replication Server uses to connect to
the database has insufficient privileges to connect.
2. Enter sysadmin upgrade, "database" at the upgraded Replication Server to upgrade the user
databases served by the Replication Server:
sysadmin upgrade, "database" {,<data_server>, <database> | all}, force
where:
○ <dataserver>, <database> – specifies a database to upgrade. Enter a separate command for each
database.
○ all – upgrades all databases served by the Replication Server. Replication Server displays error
messages if a database does not meet the conditions for upgrade.
○ force – upgrades the specified user database regardless of the upgrade status. Use this option to
force the upgrade of a user database even if you have already upgraded it.
For example, to upgrade the pdb01 database in the pds data server, enter:
sysadmin upgrade, database, pds, pdb01
If any of the databases fail to upgrade, see the Replication Server error log for the reasons, such as:
Database <data_server.database> is not accessible.
Fail to upgrade <data_server>.<database>.
4.4.7.2 Upgrading an SAP ASE User Database with rs_init

If you use rs_init to upgrade SAP Replication Server and the RSSD or ERSSD, apply upgrades to a primary,
replicate, or standby database in the replication system to accommodate changes, such as installing new
stored procedures, that support the new version of SAP Replication Server to which you are upgrading, and
features such as Multi-Path Replication.
Context
Not applying upgrades to replicate databases results in the following:
● SAP ASE – you cannot use Multi-Path Replication for replication to SAP ASE databases after you upgrade
SAP Replication Server to 15.7 and later.
● SAP IQ – SAP Replication Server suspends replicate connections to the SAP IQ replicates after you
upgraded SAP Replication Server to version 15.7.1 or later, and you see a "Awaiting Upgr" status if you use
admin who.

Procedure
1. Start rs_init.
2. Select Upgrade an existing database in the replication system from the Configure Replication System
window, then choose Continue.
3. Enter the information from the Database Setup Worksheet for the upgraded Replication Server:
○ Name of the Adaptive Server that manages the database you are upgrading.
○ Name of the database you are upgrading.
○ Login name for the “sa” user on the Adaptive Server that manages the database that you are
upgrading. The default value is “sa.”
○ Adaptive Server “sa” user password.
○ Login name for the maintenance user on the Adaptive Server that manages the database that you are
upgrading. The default is <database_maint>, where <database> is the name of the database you
are upgrading.
4. Select Continue. rs_init performs the upgrade.
5. If you have more Replication Servers or databases to upgrade, repeat the procedures to stop Replication
Agent and quiesce Replication Server, upgrade RSSD or ERSSD, and upgrade Adaptive Server databases.
4.4.7.3 Upgrading Non-SAP ASE User Databases and User

Databases Not Supported by sysadmin upgrade
Use the corresponding upgrade scripts for databases such as IBM DB2 UDB and Microsoft SQL Server that are
not supported by the sysadmin upgrade, database command and rs_init.
Procedure
1. Use the maintenance user login ID to connect to the user database.

See the SAP Replication Server Options documentation to configure a connection to a non-SAP ASE
database.
2. Find the relevant script in the scripts subdirectory of your SAP Replication Server installation directory.
The scripts are named hds_<dataserver_make>_upgradedb.sql, where <dataserver_make> is the
replicate data server type.
3. Run the script to upgrade the user database.
Modify or run the script unchanged depending on the way SAP Replication Server connects to the user
database.
If the connection is through, Enterprise Connect Data Access (ECDA) runs the script unchanged. For
example, to upgrade an IBM DB2 UDB user database, use ECDA for ODBC with the isql -i option to run
the hds_db2_upgradedb.sql script on the user database.

Related Information
Upgrading Oracle User Databases Manually [page 78]
4.4.7.3.1 Upgrading Oracle User Databases Manually
Use hds_oracle_upgradedb.sql to upgrade an Oracle user database manually or if the database upgrade
with sysadmin upgrade fails.
Procedure
1. Use the maintenance user login ID to connect to the user database.

See the SAP Replication Server Options documentation to configure a connection to a non-SAP ASE
database.
2. Locate the hds_oracle_upgradedb.sql in the scripts subdirectory of your SAP Replication Server
installation directory.
3. Run the script to upgrade the user database.
4. Check the status of the upgrade with admin who.
If you see "Awaiting Upgr", reset the connection to the database.
5. To reset the connection, log in to the RSSD and execute:
set replication off

go
set triggers off
go
update rs_databases set dist_status = dist_status & ~hextoint("0x400")
where ltype=’P’
and connid=<connection_id>
go
set replication on
go
set triggers on
go
 Note
Your <connection_id> can be found using the admin who command.
6. Restart SAP Replication Server.

4.4.8 Commit a Local Site to a New Version Level
After you upgrade a Replication Server and its user databases, decide whether to commit to the new
Replication Server version level, set the replication site version to the new version, and upgrade the route
version to the new version.
The system version is the version of the replication system and is set to 1260 by default starting from 16.0
SP03 PL04 release.
In a replication system that includes Replication Server versions 12.6 through 16.0 SP03 PL07, and for which
the site version is set to its software release level and the system version is 1260, each Replication Server can
use all the features of its release. Such a system is called a mixed-version system.
However, in a mixed-version system, interaction between Replication Servers of different version levels is
limited, and information associated with new features may not be available to Replication Servers of earlier
versions. Replication Servers of the same version can exchange full information about the software features
they support.
If, for example, you are upgrading to version 16.0 SP03 PL07, you can use new Replication Server features that
interact with other Replication Servers only if all these conditions are true:
● The system version is 1260.

● The site version for both Replication Servers has been set to the current site version.
● The routes between the Replication Servers have been upgraded.
See sysadmin system_version in the Reference Manual.
Previous: Upgrades to User Databases [page 74]
Next: Backing Up the RSSD or ERSSD After Upgrade [page 84]
Related Information
System Version and Software Version Relationship [page 80]

Replication Server Site Version [page 81]
Preparing to Upgrade [page 61]

4.4.8.1 System Version and Software Version Relationship
System version does not restrict your software capacities and is set at 1260 by default. You can use the full
capabilities of software version 16.0 SP03 PL07 and later as long as the site version is set properly.
SAP Replication Server Software Version System Version 1260
16.0 SP03 PL07 Full capability when site version is set to 1600305
16.0 SP03 Full capability when site version is set to 1600003
15.7.1 SP306 Full capability when site version is set to 1571306
15.7.1 SP300 to 15.7.1 SP301 Full capability when site version is set to 1571300
15.7.1 Full capability when site version is set to 1571
15.7 Full capability when site version is set to 1570
15.6 and 15.5 Full capability when site version is set to 1550
15.0 and 15.0.1 Full capability when site version is set to 1500
For example, new features of version 16.0 SP03 PL02 are available only when the system version is at least
1260 and the site version is set to 1600302.
If a software version is supported with full capability at a given system version, you can install new SAP
Replication Servers of that software version.

4.4.8.2 Replication Server Site Version
The site version determines which Replication Server features you can use.
If, for example, you have Replication Servers with a site version set to version 15.0, you can create replication
definitions for tables containing the bigint datatype. Such replication definitions are distributed to other
Replication Servers with site versions that are at the same version level or higher. Replication Servers of earlier
versions do not receive information about these replication definitions.
After you upgrade Replication Server and its user databases, set the Replication Server site version to the new
software version level before you use the new Replication Server features.
Set the site version for all Replication Servers that require it, and upgrade the routes. Information needed for
the new features cannot be propagated to other sites until the corresponding routes are upgraded.
 Caution
You cannot downgrade after you set the site version.
Related Information
Setting the Replication Server Site Version to the New Version [page 81]
4.4.8.2.1 Setting the Replication Server Site Version to the

New Version
Set the Replication Server site version to the new version to use the new features of Replication Server.
Procedure
1. Log in to the current Replication Server and execute sysadmin site_version, <new_site_version>
to complete the upgrade.
For example, to set the site version to 1570:
sysadmin site_version, 1570
See sysadmin site_version in the Reference Manual.

2. If the Replication Server uses an ERSSD, remove the erssd_release_dir and erssd_start_cmd
parameters, and all options and values you entered earlier for these parameters from the <rs_name>.cfg
file of the new version of Replication Server.

4.4.8.3 Replication Server Route Version
The route version is the earlier of the two site version numbers of the source and destination Replication
Servers of the route. Upgrade the route after you upgrade the source and destination Replication Servers on
either end of a route and also set their site versions to a higher Replication Server version.
Upgrading the route, which allows the Replication Servers to exchange information about newer software
features, rematerializes the data in the system tables in the RSSD and makes information associated with new
features available to a newly upgraded Replication Server. After upgrading, new types of information that were
not previously allowed can be exchanged.
Replication Server version 11.5 and later uses route version information to determine which feature set you can
use with the route and which data to propagate to other sites. If the route version is lower than the earliest site
version, perform a route upgrade. For example, information necessary for version 16.0 SP03 PL07 features is
not propagated to other sites until the corresponding route versions are upgraded to 1600305.
After you upgrade to Replication Server 16.0 SP03 PL07 and set the site version to 1600305, upgrade each
route for which this Replication Server is a source or destination, and the site versions of the source and
destination are at 1600305 or later. Set the new site version and upgrade the routes only to use new features
across multiple Replication Servers that support the new features.
How you upgrade routes depends on how you use Replication Server, and whether you are using a mixed-
version system.
If the source Replication Server is version 15.7 or later, you can use sysadmin upgrade, "route" to
upgrade a route regardless of the destination Replication Server version.
Related Information
Upgrading Routes [page 82]
4.4.8.3.1 Upgrading Routes
Set the route version to the new version.
Procedure
1. Execute admin version, "route" to report the routes to upgrade that start from and go to the
Replication Server you are upgrading. An example of the report:
Source Destination Route Proposed Status

Version Version
------ ----------- ------- -------- ------------------
NY_RS LON_RS 1500 1571200 Need route upgrade

2. Stop the log transfer for each primary database:

3. Set the proper site version number:
sysadmin site_version [, version]

4. Execute sysadmin upgrade, "route", <dest_rs_name> on the Replication Server that originates the
route to upgrade, where <dest_rs_name> is the destination Replication Server of the route you are
upgrading.
The destination Replication Server and the RSSD of the destination Replication Server both need the user
ID and password you use to execute the command. This user ID needs sa permission at the destination
Replication Server and dbo permission at the RSSD of the destination Replication Server.
For example, to upgrade the route from NY_RS to LON_RS in the example replication system in the
previous step, execute:
sysadmin upgrade, "route", LON_RS
When you execute the command, you see:

Route upgrade for route 'NY_RS.LON_RS' is in progress in the background"
In the background, NY_RS starts a routing thread that performs these procedures:
○ NY_RS determines if the route upgrade requires RSSD materialization. If it does, NY_RS proceeds to
the next step. Otherwise, NY_RS places a commit marker in the RSSD of LON_RS to alter the route
version and completes the route upgrade.
○ NY_RS places a begin marker in the RSSD of NY_RS.
○ Every two seconds, NY_RS checks for the arrival of the begin marker at the RSSD of LON_RS. If the
begin marker does not arrive at the RSSD of LON_RS within the defined threshold of one minute,
NY_RS terminates the upgrade process.
○ When the begin marker arrives at the RSSD of LON_RS, NY_RS instructs LON_RS to enter hibernation
mode.
○ The command instructs NY_RS to process the set of route upgrade scripts.
○ NY_RS places a commit marker in the RSSD of LON_RS to alter the route version, then completes the
route upgrade
○ NY_RS instructs LON_RS to leave the hibernation mode.
5. Execute admin version, "route" to check the status of the route upgrade:
○ If the route upgrade succeeds, the route should not be listed in the output.
○ If the route upgrade fails and you need to recover the route from the upgrade, you see something
similar to:
Version Version
------ ----------- ------- -------- ----------------
NY_RS LON_RS 1500 1571200 need route
upgrade recovery
○ If the route upgrade did not proceed and there are still routes to upgrade, you see something similar to:
Version Version
------ ----------- ------- -------- ----------------
NY_RS ROM_RS 1500 1571200 need route
upgrade

You can also check the error log of <source_rs_name> (the Replication Server where the route starts) for
the status of the route upgrade:
○ In a successful route upgrade that includes materialization to make information associated with new
features available to a newly upgraded Replication Server:
Upgrade for route '<source_rs_name.dest_rs_name>' is complete.
○ In a successful route upgrade that does not need rematerialization:
Upgrade for route '<source_rs_name.dest_rs_name>' is complete. no copying of
RSSD information is necessary.
○ In a failed route upgrade:
Route upgrade/upgrade recovery fails due to error. The upgrade procedure is
not completed. This routing thread will in turn exit.
6. To recover the route upgrade if the route upgrade fails:
a. Execute sysadmin upgrade,"route", <dest_rs>, "recovery" at the source Replication Server.
For example, at NY_RS, execute:
sysadmin upgrade, "route", LON_RS, "recovery"
b. Execute admin version,"route" at NY_RS to verify that the route upgrade is completed.
7. Restart the primary Replication Server distributor thread connection from the primary database after you
upgrade the route to support the replication of features included with the new version of Replication
Server.
For example, to restart the thread from the pdb primary database in the PDS primary data server, enter:
suspend distributor PDS.pdb

go
resume distributor PDS.pdb
go
4.4.9 Backing Up the RSSD or ERSSD After Upgrade
Back up the RSSD or ERSSD after upgrading Replication Server, setting its site version, and performing route
upgrades to the relevant routes.
If you have a new backup, you can avoid potential problems if you load an RSSD that corresponds to an earlier
version level. After you load the backup, this Replication Server and RSSD can recognize all queued messages
from other Replication Servers. If you restore the RSSD from a backup performed before you set the site
version, Replication Server may receive messages that the RSSD cannot accept.
See Backing Up the RSSD or ERSSD Before Upgrade [page 64] for detailed information about performing the
backup.
Previous: Commit a Local Site to a New Version Level [page 79]

4.5 Upgrading SAP ASE in a Replication System
You can separately upgrade SAP ASE in your replication system.
Prerequisites
Perform a dump database and dump transaction before upgrading SAP ASE.
1. Suspending Replication and Transaction Activity in the Database [page 86]

Suspend replication and transaction activity in the database. Replication activity includes creating and
dropping both routes and subscriptions.
2. Draining Transaction Logs for Primary Databases [page 86]
Ensure that the Replication Server completely processes the preupgrade log for each primary database
you are upgrading.
3. Draining the RSSD Transaction Log [page 88]
Create a replication definition to manually drain the RSSD transaction log. This ensures that
Replication Server processes all transactions in the RSSD log before you upgrade databases if
Replication Server has routes to other Replication Servers.
4. Disabling the Secondary Truncation Point [page 89]
Turn off the secondary truncation point for the duration of the upgrade; the Replication Agent cannot
be running when you upgrade a primary database.
5. Upgrading SAP ASE [page 89]
See the SAP Adaptive Server Enterprise Installation Guide for upgrade instructions.
6. Updating the SAP ASE System Catalog to Support Quoted Identifiers [page 90]
To ensure that replication proceeds correctly for objects with quoted identifiers created in versions of
Adaptive Server earlier than 15.7, update the SAP ASE system catalog after you upgrade SAP ASE, but
before you restore replication.
7. Restoring Replication [page 91]
Restore replication after you perform the upgrade procedure.
Related Information

4.5.1 Suspending Replication and Transaction Activity in the
Database
Suspend replication and transaction activity in the database. Replication activity includes creating and
dropping both routes and subscriptions.
Procedure
1. Verify that the subscriptions you created with primary data in the databases being upgraded have reached
a “valid” state at the primary Replication Server.
Do not upgrade while the subscriptions are being created.
Make sure no users create subscriptions for the data in the database you are upgrading until the upgrade
procedure is finished.
2. Run rs_helproute in each RSSD being upgraded to determine status.
The status of all routes should be “Active.” See Managing Routes in the Administration Guide Volume 1 to
resolve route problems.
3. Shut down the applications that are using the databases you are upgrading.
4. Use the admin who command in Replication Server to identify the existing Data Server Interface (DSI)
connections to the data server being upgraded.
5. Suspend all DSI connections to databases you are upgrading. For each database, issue:
suspend connection to <dataserver.database>
Task overview: Upgrading SAP ASE in a Replication System [page 85]
Next task: Draining Transaction Logs for Primary Databases [page 86]
4.5.2 Draining Transaction Logs for Primary Databases
Ensure that the Replication Server completely processes the preupgrade log for each primary database you are
upgrading.
Procedure
1. Wait for all remaining transactions to be replicated.

2. Execute:
admin who, sqm

Find the entry that corresponds to the inbound queue for this database by looking in the Info field for the
<queue_number> and <queue_type> entry. For an inbound queue, the <queue_type> is 1. Note the last
segment block entry for the queue.
3. Open the queue dump file, where <file_name> is the file to which you are dumping:
sysadmin dump_file, "<file_name>"
4. Create a dummy table to check that the Replication Server has received the latest log record written in the
log. You can drop this table later:
create table dummy (c1 int, c2 char(255))

go
sp_setreptable dummy, true
go
begin tran
go
insert dummy values (1,'hello')
go 10
commit tran
go
5. In the primary Replication Server, execute the admin who, sqm command until the last segment:block
entry for the inbound queue changes.
6. In Replication Server, dump the last block of the inbound queue to the dump file you just opened:
sysadmin dump_queue, <queue_number>, <queue_type>,

<last_seg>, <block>, 1
Use the <queue_number>, <queue_type>, <last_seg>, and <block> values found in the output of the
admin who, sqm command you just performed.
7. Use a text editor to examine the dump file to make sure it contains the transaction corresponding to the
inserts you performed in with the create table dummy command.
8. Repeat the last three steps until the transaction corresponding to the update is in the dump file. After
draining the transaction logs, do not allow any other activity in the databases. If activity does occur, redrain
the transaction logs.
Previous task: Suspending Replication and Transaction Activity in the Database [page 86]
Next task: Draining the RSSD Transaction Log [page 88]

4.5.3 Draining the RSSD Transaction Log
Create a replication definition to manually drain the RSSD transaction log. This ensures that Replication Server
processes all transactions in the RSSD log before you upgrade databases if Replication Server has routes to
other Replication Servers.
Context
To make sure the transaction log is completely processed, create a replication definition in the primary
Replication Server and verify that it appears in the replicate Replication Server RSSD. When the replication
definition is in the replicate RSSD, the log is fully processed.
Procedure
1. Log in to the primary Replication Server.

2. Create a temporary replication definition:
create replication definition <rep_def_name>

with primary at <dataserver.database>
with all tables named '<table_name>'(<column_name> <datatype>)
primary key (<column_name>)
Provide the names for the data server, database, table, and column, and the datatype of the column. See
the Replication Server Reference Manual for the complete syntax.
3. Log in to the replicate RSSD.
4. See whether the replication definition has arrived from the primary RSSD:
rs_helprep <rep_def_name>
Results
When the replication definition has arrived in the replicate RSSD, the RSSD transaction log has been drained.
Previous task: Draining Transaction Logs for Primary Databases [page 86]
Next task: Disabling the Secondary Truncation Point [page 89]

4.5.4 Disabling the Secondary Truncation Point
Turn off the secondary truncation point for the duration of the upgrade; the Replication Agent cannot be
running when you upgrade a primary database.
Procedure
1. Shut down the Replication Agents, or make sure that dbcc logtransfer is not running for the databases
that are being upgraded.
2. Shut down Replication Servers for the RSSDs you are upgrading.
3. In each primary database including RSSDs, turn off the secondary truncation point:
use <database>
go
dbcc settrunc ("ltm", "ignore")
go
Repeat this for each primary database and each primary RSSD.
Previous task: Draining the RSSD Transaction Log [page 88]
Next: Upgrading SAP ASE [page 89]
4.5.5 Upgrading SAP ASE
See the SAP Adaptive Server Enterprise Installation Guide for upgrade instructions.
Parent topic: Upgrading SAP ASE in a Replication System [page 85]
Previous task: Disabling the Secondary Truncation Point [page 89]
Next task: Updating the SAP ASE System Catalog to Support Quoted Identifiers [page 90]

4.5.6 Updating the SAP ASE System Catalog to Support
Quoted Identifiers
To ensure that replication proceeds correctly for objects with quoted identifiers created in versions of Adaptive
Server earlier than 15.7, update the SAP ASE system catalog after you upgrade SAP ASE, but before you restore
replication.
Procedure
1. Log in to isql at the primary SAP ASE server database.

2. Update the system catalog:
set nocount on
declare @cmd varchar(200)
,@cmdstat int
,@count int
,@dbid int
,@dbname varchar(30)
,@total int
select @cmdstat = config_admin(1, 102, 1, 1, NULL, NULL)
select @dbid = 1, @count = 0, @total = 0
while @dbid is not null
begin
select @dbname = db_name(@dbid)
select @cmd = 'select @count = count(1) from '+ @dbname
+ '.dbo.sysobjects'
+ 'where (sysstat2 & 134217728) = 0 '
+ 'and type = ''U'''
exec (@cmd)
if @count > 0
begin
print 'Object count in %1! is %2!', @dbname, @count
select @total = @total + @count
select @cmd = 'update ' + @dbname + '.dbo.sysobjects '
+ 'set sysstat2 = sysstat2 | 134217728 '
+ 'where (sysstat2 & 134217728) = 0 '
+ ' and type = ''U'''
exec (@cmd)
end
select @dbid = min(dbid) from sysdatabases where dbid > @dbid
end
if @total > 0
print 'You must restart ASE for changes to take effect.'
select @cmdstat = config_admin(1, 102, 0, 1, NULL, NULL)
Previous: Upgrading SAP ASE [page 89]
Next task: Restoring Replication [page 91]

4.5.7 Restoring Replication
Restore replication after you perform the upgrade procedure.
Procedure
1. Zero out the locator in the RSSD for each replicated primary.
Use isql to connect to the RSSD and execute:
use RSSD
go
rs_zeroltm <dataserver>, <database_name>
go
2. Set the secondary truncation point to “valid” in each primary database. Use isql to connect to the
replicated primary database and execute:
use database
go
dump tran database with truncate_only
go
dbcc settrunc("ltm","valid")
go
Previous task: Updating the SAP ASE System Catalog to Support Quoted Identifiers [page 90]
4.6 Downgrading Replication Server
Revert to an earlier version of the software. You cannot downgrade an RSSD to a version below the site version.
Prerequisites
● Find out if an RSSD downgrade is required to return to the earlier version. When you downgrade to an
earlier software version, you must install the earlier software. Read the installation guide for the earlier
version of Replication Server, then refer to the installation or configuration guide for that version for
installation instructions.
 Note
If an RSSD downgrade is not required, you need not perform these steps. Reinstall the earlier software
version following the instructions in the installation guide.

● Back up your system.
If you are downgrading to a directory other than the existing version directory, verify that the appropriate
interfaces file is accessible.
● Back up the RSSD for the Replication Server you plan to downgrade.
 Caution
Some Replication Server configuration options with newer versions may have a wider valid range. If you
increase any of these configuration options after upgrading, reinstate the old values before
downgrading. Otherwise, the Replication Server may not start or may behave incorrectly. The
Replication Server upgrade process prints all the current configuration option values in rs_config to
rs_init log, so that you can restore the former settings before downgrading.
Procedure
1. Stop Replication Agent for all primary databases and system databases by executing this command on
Replication Server:
2. If you are using SAP ASE as your RSSD, stop RepAgent for the RSSD:
3. If you are going to downgrade a replicate Replication Server, log in to the primary Replication Server and
suspend all the routes to the replicate Replication Server:
suspend route to <replicate_Replication_Server>
4. Verify that the Replication Server queues have been drained and that Replication Server has been
quiesced:
admin quiesce_check
Retry with admin quiesce_force_rsi if Replication Server is not yet quiesced.
 Caution
You may lose data if you proceed with the downgrade process without quiescing Replication Server.
5. Log in as the “sybase” user, and change to the $SYBASE_REP directory.

6. Verify that the RSSDs and the Replication Servers you plan to downgrade are running.
 Note
The downgrade process purges all the Replication Server inbound queues.
7. Start rs_init:
The RS_INIT menu appears.
8. Select Configure a Server Product.

10. Select Downgrade RSSD for an Existing Replication Server.
11. Enter information from the Replication Server Installation Worksheet for the Replication Server you are
downgrading:
○ Name of the Replication Server for which you are downgrading the RSSD.
○ Login name for the Replication Server “sa” user. The default value is “sa.”
○ Password for the Replication Server “sa” user.
○ Path name of the Replication Server configuration file.
12. Press Ctrl + A to save your changes. You see:
13. Enter “y” to continue.
Informational messages appear as rs_init loads the downgrade script into the RSSD. When the
downgrade is complete, you see these messages:
RSSD successfully downgraded to <rel_no>. Replication Server '<rs_name>' can now

be restarted. Task to downgrade the RSSD succeeded. Configuration completed
successfully.
where:
○ <rel_no> – is the Replication Server version from which you are downgrading.
○ <rs_name> – is the name of your Replication Server.
Press Return after each message. You see the Configure Replication System screen.
14. Press Ctrl + C and enter “y” to exit rs_init.
15. Shut down all Replication Servers and Replication Agents on this machine.
16. Restart the Replication Servers and Replication Agents.
17. If you are using SAP ASE as the RSSD, restart the RepAgent for the RSSD:
Related Information
Downgrade Restrictions [page 93]
4.6.1 Downgrade Restrictions

After you set the replication site version to a new level, you cannot downgrade any Replication Servers in the
replication system below that version level, or install a Replication Server below that version level.
For example, if you upgrade to version 16.0 SP03 PL07, Replication Server may write some version 16.0 SP03
PL07 commands to the inbound queue after the upgrade. Versions of Replication Server earlier than 16.0 SP03
PL07 cannot recognize the version 16.0 SP03 PL07 commands.
To return to an earlier software version, reinstall all Replication Servers and re-create your replication
applications.

If you do not want to use new features that depend on the site version, do not set the Replication Server site
version after the upgrade. You can then downgrade to an earlier version if needed.
If you plan to downgrade in a directory other than the existing version directory, verify that the interfaces file
is accessible.
If necessary, downgrade the RSSD for each Replication Server you are downgrading. Downgrade the RSSD
using the predowngrade— that is, the most recent—version of rs_init.
If the Replication Server uses an ERSSD, verify that the Replication Server configuration file contains the
erssd_release_dir and erssd_start_cmd parameters. Ensure the values for these parameters are the
same as the values before upgrading.
4.7 Migrating Between 32-Bit and 64-Bit Platforms
Replication Server is available only on 64-bit platforms for all supported UNIX and Linux operating systems.
Prerequisites
● Back up your replication system. The migration process makes changes to the system databases that you
cannot roll back if the migration fails. Restore the system databases if the migration fails.
● If you plan to install the software in a directory other than an existing version directory, verify that the
interfaces file is accessible.
Context
Replication Server versions 16.0 and later are available only on 64-bit platforms for all UNIX and Linux
operating systems. Therefore, upgrading to versions 16.0 and later may include upgrading from a 32-bit
platform.
 Note
This migration procedure applies only for migration in the same RSSD version and platform. If you have
migrated to a Replication Server version that is available only on 64-bit platforms, you cannot migrate back
to a 32-bit platform.

Procedure
1. Stop Replication Agent for all primary databases and system databases by executing this command on
Replication Server:
2. If you are using SAP ASE as your RSSD, stop RepAgent for the RSSD:
3. If you are migrating a Replication Server, log in to each upstream Replication Server and suspend all the
routes to the Replication Server you are migrating:
suspend route to <replicate_Replication_Server>
4. Verify that the Replication Server queues are drained and that Replication Server is quiesced:
admin quiesce_check
If Replication Server has not yet quiesced, use admin quiesce_force_rsi .
 Caution
You may lose data if you proceed with the migration process without quiescing Replication Server.
5. Stop Replication Server.

a. Log in to the Replication Server as the system administrator:
isql -Usa -Psa_password -Sservername
b. Enter:
shutdown
go
6. If you are using an ERSSD, restart it manually:

a. Set the LD_LIBRARY_PATH environment variable:
$ export
LD_LIBRARY_PATH=$SYBASE/REP-16_0/ASA17/
lib:$SYBASE/REP-16_0/lib64:$SYBASE/REP-16_0/
lib:$SYBASE/REP-16_0/lib3p64/log4cxx/lib:$SYBASE/
OCS-16_0/lib:$SYBASE/OCS-16_0/lib3p64:$SYBASE/OCS-16_0/
lib3p
b. Start the ERSSD:
-o $SYBASE/REP-16_0/samp_repserver/SAMPLE_RS.log
$SYBASE/REP-16_0/samp_repserver/dbfile/SAMPLE_RS_ERSSD.db &
In your Replication Server log file, search for “LD_LIBARY_PATH” and “ERSSD start command" to see
the actual commands for setting LD_LIBRARY_PATH, and for starting the ERSSD:
7. Load the migration script file into the ERSSD or RSSD. For example:
○ ERSSD – load $SYBASE/REP-16_0/scripts/rs_migration_asa.sql into the ERSSD.

○ RSSD – load $SYBASE/REP-16_0/scripts/rs_migration_ase.sql into the RSSD.

8. Start Replication Server from the new Replication Server executable.
Related Information
Start or Stop a Replication Server [page 111]

5 Upgrade and Downgrade Using Existing
Directories
You can upgrade and downgrade SAP Replication Server if you install the software into existing directories.
By default, the installation process installs versions 15.5 to 15.7.1 in the REP-15_5 diretory, and version 16.0
SP03 PL07 in REP-16_0 directory. Do not install and upgrade versions 15.5 to 16.0 SP03 PL07 using existing
directories that contain any preupgrade versions between 15.5 and 16.0 SP03 PL07. Back up the files and
directories of the preupgrade version of SAP Replication Server before you install the newer version in the same
directories.
The Upgrading Using Existing Directories [page 98] procedure applies only between these Replication Server
versions:
15.7.1 15.7.1 15.7.1

From ↓ To→ 15.5 15.6 15.7 15.7.1 SP100 SP200 SP300 16.0 SP03
15.5 NA NA Yes Yes Yes Yes Yes Yes
15.6 NA NA Yes Yes Yes Yes Yes Yes
15.7 NA NA NA Yes Yes Yes Yes Yes
15.7.1 NA NA NA NA Yes Yes Yes Yes
15.7.1 NA NA NA NA NA Yes Yes Yes

SP100
15.7.1 NA NA NA NA NA NA Yes Yes

SP200
15.7.1 NA NA NA NA NA NA NA Yes
SP300
Related Information
Upgrading Using Existing Directories [page 98]

Downgrading to an Earlier Version in Existing Directories [page 99]

Upgrade and Downgrade Using Existing Directories PUBLIC 97
5.1 Upgrading Using Existing Directories
Upgrade using the existing directories.
Procedure
1. Shut down the preupgrade version of Replication Server.

See Start or Stop a Replication Server [page 111].
2. Back up the entire set of files and directories under $SYBASE.
 Note
Keep this backup in case you need to downgrade from Replication Server version 16.0 SP03 PL07 to an
earlier version.
3. Use the relevant version of the installation guide to install your new version of Replication Server into the
existing version directories under $SYBASE.
 Note
Do not install the SAMPLE_RS sample Replication Server from the new version if you are using the
SAMPLE_RS from the earlier version.
The installation process:

○ Updates all subdirectories of $SYBASE that share directory names in both versions.
○ Backs up existing SYBASE.* files, where * can be .env, .sh, or .csh, by adding a "save" suffix to the
file. For example, Sybase.env is backed up as Sybase.env.save
4. Set the relevant environment variables in the SYBASE.env file in the Replication Server 16.0 SP03 PL07
installation directory.
See Environment Variables on UNIX in the installation guide for your platform.
5. Use the repserver or rs_init utilities to upgrade Replication Server from versions 15.5 and later to
version 16.0 SP03 PL07.
When upgrading from versions 15.5, 15.6 and later to version 15.7, you can only use rs_init.
For example, to upgrade the tokyo_rs Replication Server from version 15.6 to 16.0 SP03 PL07 using
repserver, enter:
/sybase/rs16sp03/REP-16_0/bin/repserver -upgr -Stokyo_rs

-C/sybase/rs16sp03/REP-16_0/install/tokyo_rs.cfg
-E/sybase/rs16sp03/REP-16_0/install/tokyo_rs.log
-I/sybase/rs16sp03/interfaces
-A /sybase/rs16sp03/REP-16_0/ASA17
After the upgrade, you see a new entry in the configuration file. For example after upgrading tokyo_rs, you
see:
erssd_release_dir=/sybase/rs16sp03/REP-16_0/ASA17
erssd_start_cmd=/sybase/rs16sp03/REP-16_0/ASA17/bin/dbspawn
-f -q /sybase/rs16sp03/REP-16_0/ASA17/bin/dbsrv17

98 PUBLIC Upgrade and Downgrade Using Existing Directories
-ti 0 -x "tcpip(PORT=11753;DOBROAD=NO;BLISTENER=NO)"
-o /sybase/rs16sp03/REP-16_0/errorlog/tokyo_rs_erssd.out
/sybase/rs16sp03/REP-16_0/dbfile/tokyo_rs_erssd.db
RS_random=b6BAdgNj4GOgnJ47vYwkgcPoQflYvQOxidNOsgnrqCgIk6tmrvYrWmF20hcV/SnPRH
 Note
You see the RS_random encryption attribute only if you upgrade to version 15.7.1 and later using either
repserver or rs_init. Because earlier versions of Replication Server cannot use the attribute, you
can leave it in the configuration file or delete it if you downgrade from versions 15.7.1 and later.
6. Change the runserver file you copied from the backup to use the upgraded Replication Server executable,
then start Replication Server.
See Starting a Replication Server Using the Runserver File in the Configuration Guide.
5.2 Downgrading to an Earlier Version in Existing

Directories
You can revert to an earlier Replication Server version in the existing directories if you backed up your earlier
version before upgrading to the same directories.
Procedure
1. Back up the entire set of files and directories under $SYBASE.

These contain the current Replication Server version files.
2. Downgrade Replication Server using the procedure in Downgrading Replication Server [page 91].
3. Back up the Replication Server ERSSD or RSSD after completing the downgrade procedure in the previous
step.
4. Restore the files and directories from the backup you made before you upgraded to the current Replication
Server version to overwrite the dicrectory structure under $SYBASE.
5. Verify that the .cfg, interfaces, and run_<repservername> runserver files are configured to run the
version of Replication Server you are downgrading to.
6. If there was replication activity on the upgraded version of Replication Server prior to the downgrade
process, verify that you are using the downgraded version of RSSD files, otherwise restore the ERSSD or
RSSD from the backup you have made in step 3.
If you use an ERSSD, copy the dbfile, translog, errorlog, and backup directories to the
corresponding locations. If you use SAMPLE_RS, copy all files and directories under $SYBASE/REP-16_0/
samp_repserver to the corresponding locations.
7. Set the relevant environment variables in the SYBASE.env file.
See Environment Variables on UNIX in the installation guide for your platform.
8. Start the downgraded Replication Server version with the runserver file.
See Starting a Replication Server Using the Runserver File in the Configuration Guide for UNIX.

Upgrade and Downgrade Using Existing Directories PUBLIC 99
6 Password Encryption
Replication Server encrypts all passwords, and stores and transmits passwords in encrypted format.
Replication Server uses password encryption instead of clear text when storing all passwords for new
Replication Server installations.
Set the site version to 1571 or later before you use rs_init to change existing encrypted passwords when you
are upgrading Replication Server. To change the passwords if you do not set the site version to 1571 or later, use
rs_init from the version of Replication Server that you are upgrading from. Manually remove the RS_random
attribute in the configuration file if you downgrade Replication Server.
To regenerate the password encryption key, see Password Encryption in the Administration Guide Volume 1.
Related Information
Enabling Password Encryption for a Replication Server [page 100]

Altering an Encrypted Password for a Replication Server [page 102]
6.1 Enabling Password Encryption for a Replication Server
Enable password encryption for a Replication Server using rs_init.
Context
rs_init creates a new configuration file that contains encrypted passwords for the Replication Server, and
encrypts the passwords in the rs_users and rs_maintusers system tables.
Procedure
1. Log in as the “sybase” user and change to the installation directory.

2. Start rs_init:
You see the RS_INIT menu.

100 PUBLIC Password Encryption
5. Select Enable Password Encryption for a Replication Server.
6. Enter:
○ Name of the Replication Server for which to enable password encryption.
○ Login name for the Replication Server with “sa” user.
○ Password for the Replication Server “sa” user.
○ Full path for the Replication Server configuration file.
7. Press Ctrl + A to save your changes. rs_init displays:
8. Enter “y” to enable encryption.
rs_init shuts down the Replication Server and encrypts the passwords in the Replication Server
configuration file and in the rs_users and rs_maintusers system tables.
Replication Server 'rs_name' can now be restarted.

9. Press Return. rs_init displays:
Configuration tasks completed successfully.
10. Press Return. You see the Configure Replication System screen.
11. Press Ctrl + C and enter “y” to exit rs_init.
12. Restart the Replication Server and any connected Replication Agents.
13. Delete the backup of the Replication Server configuration file.
Results
 Note
The backup file contains unencrypted passwords; remove that file to protect your replication system
security. However, you may first want to make a hard copy or offline backup of the file and store it in a safe
place.
The backup file has the same name as the Replication Server configuration file, but the extension is changed to
a three-digit number such as “001.” The file with the highest extension number is the most recent backup file.

Password Encryption PUBLIC 101
6.2 Altering an Encrypted Password for a Replication
Server
Change an encrypted password in a Replication Server configuration file using rs_init.
Context
Do not use rs_init to change the passwords stored in the RSSD. Instead use the alter user command to
change the Replication Server password, and alter connection or alter route to change the
maintenance user password..
Procedure
1. Log in as the “sybase” user and change to the installation directory.

2. Start rs_init:
You see the RS_INIT menu.
5. Select Alter a Replication Server Configuration File Password.
6. Enter:
○ Name of the Replication Server that has the configuration file to update.
○ Login name for the Replication Server “sa” user.
○ Password for the Replication Server “sa” account.
○ Full path name for the Replication Server configuration file.
○ Parameter for the password to alter:
○ <RSSD_primary_pw_enc> – for the RSSD primary user.
○ <RSSD_maint_pw_enc> – for the RSSD maintenance user.
○ <ID_pw_enc> – for the ID Server user name.
○ New password to use.
7. Press Ctrl + A to save your changes. rs_init displays:
8. Enter “y”.
rs_init shuts down the Replication Server, then records the new password in the Replication Server
configuration file. When that process is complete, rs_init shows:
Configuration completed successfully.
Press Return to continue.

102 PUBLIC Password Encryption
9. Press Return. You see the Configure Replication System screen.
10. Press Ctrl + C and type “y” to exit rs_init.
11. Restart the Replication Server.

Password Encryption PUBLIC 103
7 Secure Sockets Layer
Secure Sockets Layer (SSL) is an industry standard for sending wire- or socket-level encrypted data over
secure network connections.
See Manage Replication Server Security in the Administration Guide Volume 1 for detailed information on the
SSL security option.
Related Information
Replication Server Security Information [page 21]
7.1 Setting Up SSL Services
Set up SSL services on Replication Server.
Prerequisites
Review the SSL Plus user documentation and documentation for any third-party SSL security software you are
using.
1. Include Trusted CA certificates [page 105]

Modify the Open Client/Server trusted roots file to include trusted certificate authority (CA)
certificates.
2. Obtain a Certificate for Each SSL-Enabled Replication Server [page 105]
Obtain a certificate from a trusted certificate authority (CA) for each Replication Server accepting SSL
connections.
3. Create an Identity File [page 106]
Create the identity file that contains the concatenation of a certificate and its corresponding encrypted
private key, and that is understood by the SSL Plus software.
4. Add an Encrypted Password to the Configuration File [page 107]
Use rs_init to enable SSL on Replication Server and to add or change an encrypted SSL password.
5. Create SSL Entries in the Directory Service [page 107]
Create SSL entries in the Replication Server directory service—such as the interfaces file or an
LDAP server—which defines the server address and port numbers, and determines security protocols
that are enforced for client connections.
6. Enable or Disable SSL on Replication Server [page 109]
You can enable SSL using Replication Server commands or rs_init.

104 PUBLIC Secure Sockets Layer
7. Restart Replication Server After SSL Changes [page 110]
Stop and start Replication Server for SSL configuration changes to take effect.
Related Information
7.1.1 Include Trusted CA certificates
Modify the Open Client/Server trusted roots file to include trusted certificate authority (CA) certificates.
The list of known and trusted CAs is maintained in the trusted roots file: $SYBASE/config/trusted.txt
The system administrator adds and deletes CAs using a standard ASCII-text editor. The trusted roots file is
similar in format to a certificate file.
By default, Replication Server recognizes these third-party CAs:
● Thawte
● Entrust
● Baltimore
● VeriSign
● RSA
Parent topic: Setting Up SSL Services [page 104]
Next: Obtain a Certificate for Each SSL-Enabled Replication Server [page 105]
7.1.2 Obtain a Certificate for Each SSL-Enabled Replication

Server
Obtain a certificate from a trusted certificate authority (CA) for each Replication Server accepting SSL
connections.
The system administrator installs server certificates and private keys for the Replication Server installation.
The system administrator can get a server certificate using third-party tools provided with an existing public-
key infrastructure (PKI) already in use in the customer environment. Each Replication Server acting as a server
in an SSL-enabled connection needs a certificate issued by a trusted CA.
Most third-party PKI vendors have utilities to generate certificates and private keys.
SAP Replication Server uses OpenSSL to request, authorize, and convert third-party certificates. OpenSSL is
an open source toolkit that implements SSL and TLS protocols as well as a cryptography library. See the
OpenSSL website for more information.

Secure Sockets Layer PUBLIC 105
Parent topic: Setting Up SSL Services [page 104]
Previous: Include Trusted CA certificates [page 105]
Next task: Create an Identity File [page 106]
7.1.3 Creating an Identity File
Create the identity file that contains the concatenation of a certificate and its corresponding encrypted private
key, and that is understood by the SSL Plus software.
Prerequisites
Verify that you have sa role before performing this task.
Context
The name and default location of the identity file is the following, where <servername> is the name of the
server as specified at start-up:
$SYBASE/$SYBASE_REP/certificates/servername.crt
Procedure
1. Specify the alternate location in the RS_ssl_identity entry in the configuration file to place the identity
file in a different location.
2. Confirm the common name in the certificate matches the Replication Server name in the directory service.
Client certificates are not supported.
Task overview: Setting Up SSL Services [page 104]
Previous: Obtain a Certificate for Each SSL-Enabled Replication Server [page 105]
Next task: Add an Encrypted Password to the Configuration File [page 107]

7.1.4 Adding an Encrypted Password to the Configuration File
Use rs_init to enable SSL on Replication Server and to add or change an encrypted SSL password.
Context
The SSL password decodes the identity file private keys. This password is stored as the RS_ssl_pw entry in
the Replication Server configuration file where it is not sent over the network.
You can use the sysadmin ssl, checkcert command to check if the SSL password can decode the private
keys of the identity file that were configured in the Replication Server configuration file. For more information,
refer to the sysadmin ssl, checkcert topic under the SAP Replication Server Commands chapter in the
Replication Server Reference Manual.
 Note
Enable and disable SSL on Replication Server by using the configure replication server and
use_ssl options.
Previous task: Create an Identity File [page 106]
Next task: Create SSL Entries in the Directory Service [page 107]
7.1.5 Creating SSL Entries in the Directory Service
Create SSL entries in the Replication Server directory service—such as the interfaces file or an LDAP server
—which defines the server address and port numbers, and determines security protocols that are enforced for
client connections.
Context
Replication Server implements the SSL protocol as a filter that is appended to master and query lines in the
directory service.

Procedure
1. Verify that all attempts to connect to a master or query entry in a directory service with an SSL filter
supports the SSL protocol.
For example, if a primary Replication Server (SYBSRV1) and a replicate Replication Server (SYBSRV2) were
to use the Transmission Control Protocol (TCP) and the SSL protocol for communication, entries in the
interfaces file might look like this:
SYBSRV1
query tcp myserver sybasehost1 5001 ssl
master tcp myserver sybasehost1 5001 ssl
SYBSRV2
2. You can also configure Replication Server to accept SSL connections and, at the same time, have other
connections that accept clear text or use security mechanisms such as DCE and Kerberos.
To support both SSL and other connection protocols, use multiple interfaces files.
For example, a typical interfaces file entry that supports the TCP and both SSL and clear text
connections looks like this:
SYBSRV1
master tcp myserver sybasehost1 5001
3. The interfaces file master line entries allow SYBSRV1 to listen for both SSL and clear text connections.
To make sure that SYBSRV1 sends queries to SYBSRV2 using SSL, the interfaces file needs a single
query entry for SYBSRV1.
To allow SYBSRV1 to send queries to other servers using a different protocol, use a separate interfaces
file.
Previous task: Add an Encrypted Password to the Configuration File [page 107]
Next task: Enable or Disable SSL on Replication Server [page 109]

7.1.6 Enabling or Disabling SSL on Replication Server
You can enable SSL using Replication Server commands or rs_init.
Context
 Note
Replication Server does not need the REP_SSL license, since SSL comes as a part of the basic
REP_SERVER license.
Procedure
1. Enable or disable SSL using configure replication server with the use_ssl option.
To use configure replication server, enter:
configure replication server

set use_ssl to 'on'
Set use_ssl to off to disable SSL. By default, SSL is not enabled on Replication Server. When use_ssl is
off, Replication Server does not accept SSL connections.
use_ssl is a static option; restart Replication Server after you change its value.
2. Edit the LIBPATH environment variable in SYBASE.csh or SYBASE.sh to log in to Replication Server
running on IBM AIX 64-bit platforms:
File Execute
SYBASE.csh source SYBASE.csh

setenv LIBPATH $SYBASE/$SYBASE_OCS/lib3p:$LIBPATH
SYBASE.sh source SYBASE.sh

export LIBPATH=$SYBASE/SYBASE_OCS/lib3p:$LIBPATH
Previous task: Create SSL Entries in the Directory Service [page 107]
Next task: Restart Replication Server After SSL Changes [page 110]

7.1.7 Set the Value of ssl_protocol
Use the ssl_protocol parameter with the configure replication server command to set the protocol
that Replication Server utilizes to accept client connections.
To check the protocol that Replication Server is currently using, use this parameter with the admin config
command. The default value of the parameter is TLSv1.
The valid value list (available protocol versions) for the ssl_protocol parameter is as under:
● TLSv1(Default value)
● TLSv1.1
● TLSv1.2
General rules:
● When you set the value of ssl_protocol to a particular protocol and version, Replication Server only
accepts client connections that have a protocol version either equal to or higher than what you have set.
For example: If you have set the value of ssl_protocol to TSLv1.1, Replication Server only accepts
TLSv1.1 or TLSv1.2 client connections, and so on.
● SSL does not support connections to ERSSD (Embedded Replication Server System Database) and
DBLTM (Log Transfer Manager utility).
Syntax and usage examples:
● Set the value of ssl_protocol to <TLSv1>:
configure replication server set ssl_protocol to 'TLSv1'

go
● Check the current value of ssl_protocol:
admin config, 'ssl_protocol'

go
7.1.8 Restarting Replication Server After SSL Changes
Stop and start Replication Server for SSL configuration changes to take effect.
Previous task: Enable or Disable SSL on Replication Server [page 109]
Related Information
Start or Stop a Replication Server [page 111]

8 Start or Stop a Replication Server
You can start a Replication Server using the runserver file created by rs_init and connect using isql, then
executing shutdown to stop.
Related Information
Start-up Sequence for Servers [page 111]

Runserver File [page 111]
Starting a Replication Server Using the Runserver File [page 112]
Starting Replication Server with Sufficient Memory [page 112]
Stopping a Replication Server Using isql [page 113]
8.1 Start-up Sequence for Servers
In a production system, start SAP ASE and Replication Servers whenever your machine restarts. See your
system administrator to do this.
Start servers in this order:
1. SAP ASE servers, if the Replication Server uses RSSD SAP ASE.
2. Replication Servers.
8.2 Runserver File
The executable runserver file contains the command line to start SAP Replication Server. When you install a
new SAP Replication Server to your replication system, rs_init creates a runserver file in the installation
directory.
Your runserver file name includes the name of the server. For example, the runserver file for an SAP Replication
Server named ROME_RS is RUN_ROME_RS.

Start or Stop a Replication Server PUBLIC 111
8.3 Starting a Replication Server Using the Runserver File
Use the runserver file created by rs_init to start a Replication Server.
Procedure
1. Log in to your system as the “sybase” user.

2. Set the $SYBASE_REP and $SYBASE_OCS environment variables to the path of the installation directory,
as described in the installation guide for your platform.
3. From the shell prompt, execute the runserver file as a background process.
For example, enter this command to start the TOKYO_RS Replication Server:
$SYBASE/$SYBASE_REP/RUN_TOKYO_RS &
As the servers start, you see diagnostic messages, which are recorded in the server log.
8.4 Starting Replication Server with Sufficient Memory
Avoid failures when there is heavy memory consumption by Replication Server caches and buffers by
configuring Replication Server or the operating system to provide sufficient memory when Replication Server
starts up.
Procedure
1. Modify the ulimit option settings in the runserver file to:
ulimit -d 'unlimited'
ulimit -c 'unlimited'
ulimit -m 'unlimited
2. (Optional) Modify the operating system memory limits.
For example, on IBM AIX, change the default settings in the /etc/security/limits file:
○ fsize – 1
○ core – 2097151
○ cpu – 1
○ data – 1
○ rss – 1
○ stack – 65536
○ nofiles – 2000
See your operating system documentation for similar implementations

112 PUBLIC Start or Stop a Replication Server
8.5 Stopping a Replication Server Using isql
Stop a Replication Server using the isql utility.
Context
When you shut down a Replication Server, it refuses additional connections, terminates threads, and exits.
Procedure
1. Use isql to log in to the Replication Server as the system administrator:
isql -Usa -P<sa_password> -S<servername>
2. Enter:
shutdown
go

Start or Stop a Replication Server PUBLIC 113
9 Install and Implement Non-SAP ASE
Support Features
Replication Server support for replication into a non-SAP ASE replicate database has some requirements.
● Replication Server system tables—rs_lastcommit and rs_info— created in the non-SAP ASE database,
and Replication Server support functions such as rs_get_lastcommit and rs_get_charset.
● Function strings that:
○ Replace certain language command and stored procedure invocations from the replicate Replication
Server, then,
○ Produce operations in the replicate database that emulate the behavior of the commands and stored
procedures that would exist in a SAP ASE replicate database.
● Heterogeneous datatype support for non-SAP ASE datatypes that do not map directly to Replication
Server datatypes (or SAP ASE datatypes), which must be translated to the appropriate datatypes for
replication into the replicate database.
Related Information
Components for Non-SAP ASE Support Installed with Replication Server [page 114]
Setting Up and Configuring Non-SAP ASE Support [page 115]
9.1 Components for Non-SAP ASE Support Installed with

Replication Server
The components included in a Replication Server default installation are connection profiles that contain
function-string classes and error classes for each actively supported database, datatypes class, Replication
Server native datatype literal descriptor row in the RSSD rs_datatype table, and Replication Server datatype
translation engine.
Replication Server includes connection profiles that you use to connect to non-SAP ASE data servers.
Connection profiles contain or install these components:
● Datatype definitions – assign a unique datatype ID to each datatype, and describe the attributes of each
non-SAP ASE datatype, such as delimiters, length, scale, precision, minimum and maximum values, how it
is represented using native Replication Server datatypes. Replication Server uses datatype definitions to:
○ Identify datatypes
○ Convert datatypes into native datatypes for internal handling (if necessary)
○ Translate datatypes

114 PUBLIC Install and Implement Non-SAP ASE Support Features
● Replication Server support objects in the replicate database – Replication Server relies on a replicate
database to maintain some of the operational data that Replication Server needs to replicate to that
database.
Non-SAP ASE support accommodates the Replication Server replicate database requirements by creating
two tables in the replicate database:
○ rs_info – stores the character set and sort order used by the database. The Replication Server
maintenance user ID must have select permission on this table.
○ rs_lastcommit – is used by the replicate Replication Server to record information about the most
recent replicated operations committed in the replicate database. Because this table is both read and
updated by the replicate Replication Server, the Replication Server maintenance user ID needs both
insert and update permission on this table.
● Replication Server function strings – allow users to customize the database operations sent by the
replicate Replication Server to the replicate database. Non-SAP ASE support uses function strings to
replace invocations of stored procedures and certain database commands that the replicate Replication
Server sends to the replicate database.
The function strings required to support connections to non-SAP ASE data servers are installed in the
RSSD of the replicate Replication Server.
For functions-string classes, see Customize Database Operations in the Administration Guide Volume 2 and
for datatype classes, see Topics in the Reference Manual.
● Class-level translations for non-SAP ASE datatypes – default datatype-to-datatype mappings, provided by
connection profiles.
Connection profiles provide a function-string class for each supported database server. The class-level
translations are specific to each function-string class that supports a non-SAP replicate database.
9.2 Setting Up and Configuring Non-SAP ASE Support
Set up and configure non-SAP ASE support in Replication Server.
Procedure
1. Create a replicate database connection – use the using profile clause with the create connection
command to create a connection to a non-SAP ASE replicate database. See create connection using
profile in the Reference Manual.
2. Create replicate definitions – see Create Replication Definitions in the Administration Guide Volume 1.
3. Mark tables for replication – see Mark Tables for Replication in the Administration Guide Volume 1.
4. Create subscriptions – see Manage Subscriptions in the Administration Guide Volume 1.

Install and Implement Non-SAP ASE Support Features PUBLIC 115
Results
When you complete all these steps, you can begin replicating transactions to a non-SAP ASE replicate
database. See the Heterogeneous Replication Guide for information specific to supported non-SAP ASE
databases.

116 PUBLIC Install and Implement Non-SAP ASE Support Features
10 Sample Replication System
The sample replication system replicates the changes made to two tables in the pubs2 database from one SAP
ASE to another SAP ASE.
You can set up this example as an introduction to using Replication Server or to test your replication system
installation.
 Note
The application architecture for this example is similar to the decision-support model described in the
Design Guide.
The goal of this replication system is to replicate all changes made to the authors and titles tables in the
pubs2 database in one SAP ASE to the same tables in the pubs2 database in another SAP ASE.
The replication system has two SAP ASE servers:
● A primary SAP ASE, named TOKYO_DS, holds the RSSD for the primary Replication Server and the
primary pubs2 database.
● The replicate SAP ASE, named SYDNEY_DS, holds the RSSD for the replicate Replication Server and the
replicate pubs2 database.
The replication system has two Replication Servers:
● A primary Replication Server named TOKYO_RS manages the primary pubs2 database.
● A replicate Replication Server named SYDNEY_RS manages the replicate pubs2 database.
The replication system has two RepAgents, which are the Replication Agents for SAP ASE:
● A RepAgent for the primary RSSD runs in the ASE TOKYO_RSSD and transfers the RSSD log to the primary
Replication Server.
● A RepAgent for the primary pubs2 database runs in the ASE TOKYO_PUBS2 and transfers the pubs2 log
to the primary Replication Server.
Related Information
Setting Up the Sample Replication System [page 118]

Establishing the Sample Replication [page 119]
Troubleshooting and Testing the Replication System [page 121]

Sample Replication System PUBLIC 117
10.1 Setting Up the Sample Replication System
Use the SAP ASE servers or Replication Servers that you have already installed to set up the sample replication
system. Substitute the names of your servers throughout the instructions.
Prerequisites
Choose the machines where each server will execute and locate disk space for SAP ASE database devices and
Replication Server partitions. See the installation guide for your platform for disk space and system
requirements.
Procedure
1. Install the primary SAP ASE, TOKYO_DS.

2. Install the replicate SAP ASE, SYDNEY_DS.
3. Install the pubs2 database in the primary SAP ASE:
isql -Usa -Psa_passwd -STOKYO_DS < \

$SYBASE/$SYBASE_ASE/scripts/installpubs2
4. Install the pubs2 database in the replicate SAP ASE:
isql -Usa -Psa_passwd -SSYDNEY_DS < \

$SYBASE/$SYBASE_ASE/scripts/installpubs2
5. Complete the Replication Server Installation Worksheet for the primary Replication Server (TOKYO_RS).
○ Create the RSSD for TOKYO_RS in the TOKYO_DS SAP ASE server.
○ The RSSD requires a RepAgent.
6. Complete the Replication Server Installation Worksheet for the replicate Replication Server (SYDNEY_RS).
○ Create the RSSD for SYDNEY_RS in the SYDNEY_DS SAP ASE server.
○ The RSSD does not require a RepAgent.
7. Complete the Database Setup Worksheet for the primary pubs2 database.
○ The database is in TOKYO_DS SAP ASE server.
○ The database is managed by the TOKYO_RS Replication Server.
○ The database requires a RepAgent.
8. Complete the Database Setup Worksheet for the replicate pubs2 database.
○ The database is in SYDNEY_DS SAP ASE server.
○ The database is managed by the SYDNEY_RS Replication Server.
○ The database does not require a RepAgent.
9. Log in to the machine where the primary Replication Server executes. Run rs_init and install Replication
Server TOKYO_RS using the installation worksheet you completed for TOKYO_RS.

118 PUBLIC Sample Replication System
10. Log in to the machine where you installed the primary Replication Server. Run rs_init and add the
primary pubs2 database to the replication system using the Database Setup Worksheet for the primary
pubs2 database.
11. Log in to the machine where the replicate Replication Server executes. Run rs_init and install Replication
Server SYDNEY_RS using the installation worksheet you completed for SYDNEY_RS.
12. Log in to the machine where you installed the replicate Replication Server. Run rs_init and add the
replicate pubs2 database to the Database Setup Worksheet for the replicate pubs2 database.
Related Information
Replication Server Installation Worksheet Sample [page 14]

10.2 Establishing the Sample Replication
Create a route from the primary Replication Server to the replicate Replication Server to establish a sample
replication.
Procedure
1. Log in to the primary Replication Server as “sa”:
isql -Usa -STOKYO_RS
2. Enter the create route command:
create route to SYDNEY_RS

set username SYDNEY_RS_rsi
set password SYDNEY_RS_rsi_ps
go
 Note
Find the user name and password for the create route command in the “Remote site connections”
section of the Replication Server Installation Worksheet for the replicate Replication Server.
3. Create a login account in the primary SAP ASE for the user who creates the replication definitions and
subscriptions. In this example, the login name is “repsys.” Add the user to the pubs2 database and grant
the user select permission for the tables to replicate:
isql -Usa -STOKYO_DS

sp_addlogin repsys, repsys_ps
go
use pubs2

go
sp_adduser repsys
go
grant select on authors to repsys
grant select on titles to repsys
go
quit
4. Add the “repsys” user to the two Replication Servers and grant create object permission to the user.
The “repsys” user needs the same login name and password in the two Replication Servers and the
primary SAP ASE:
isql -Usa -STOKYO_RS

create user repsys
set password repsys_ps
go
grant create object to repsys
go
quit
isql -Usa -SSYDNEY_RS
create user repsys
set password repsys_ps
go
grant create object to repsys
go
quit
5. Create replication definitions for the authors and titles tables:
isql -Urepsys -Prepsys_ps -STOKYO_RS

create replication definition authors
with primary at TOKYO_DS.pubs2
with all tables named 'authors'
(
au_id varchar(11),
au_lname varchar(40),
au_fname varchar(20),
phone char(12),
address varchar(40),
city varchar(20),
state char(2),
country varchar(12),
postalcode char(10)
)
primary key (au_id)
searchable columns (state, postalcode)
go
create replication definition titles
with primary at TOKYO_DS.pubs2
with all tables named 'titles'
(
title_id varchar(6),
title varchar(80),
type char(12),
pub_id char(4),
price money,
advance money,
total_sales int,
notes varchar(200),
pubdate datetime,
contract bit
)
primary key (title_id)
searchable columns (type, pub_id)
go

6. Set replication to on for the authors and titles tables in the primary pubs2 database:
isql -Usa -STOKYO_DS

use pubs2
go
sp_setreptable authors, true
go
sp_setreptable titles, true
go
7. In the replicate pubs2 database, grant permissions on the authors and titles tables to the
maintenance user:
isql -Usa -SSYDNEY_DS

use pubs2
go
grant select, insert, delete, update
on authors to pubs2_maint
grant select, insert, delete, update
on titles to pubs2_maint
go
 Note
You can find the maintenance user in the “Database information” section of the Database Setup
Worksheet you completed for the replicate pubs2 database.
8. In the replicate Replication Server, create subscriptions for the authors and titles tables:
isql -Urepsys -Prepsys_ps -SSYDNEY_RS

create subscription authors_sub
for authors
with replicate at SYDNEY_DS.pubs2
without materialization
go
create subscription titles_sub
for titles
without materialization
go
 Note
Since there is already data at the replicate database, this example uses create subscription with
the without materialization option. For other methods, see Replication Server Commands in the
Reference Manual .
10.3 Troubleshooting and Testing the Replication System

Troubleshoot and test replication for the authors and titles tables when replication is established.
If you created a subscription with materialization, log in to the replicate pubs2 database and select the data
from the titles and authors tables:
● If the rows exist in the replicate tables – it indicates that the subscriptions were created and materialized
successfully.

● If the rows do not appear in the replicate tables – execute check subscription in each of the
Replication Servers:
check subscription authors_sub

for authors
check subscription reports the status of the subscription. If the status is not “valid” in both the
primary and replicate Replication Servers, then either the subscription has not finished materializing or an
error has occurred.
The authors and titles tables are very small. If there are no configuration problems, they should not take
more than a few seconds to materialize. If you do not see the results quickly, you can assume that an error has
occurred.
If you created a subscription without materialization or the subscription has completed materializing, log in to
the primary pubs2 database and execute some insert, update, and delete SQL commands against the
authors and titles tables. Then log in to the replicate pubs2 database and verify that your modifications
appear in the replicate tables. If the rows do not appear in the replicate tables:
● Execute check subscription in each of the Replication Servers.

● Check the error logs for the primary and replicate Replication Servers for error messages. The most
common problems are:
○ Failure to log in to the primary SAP ASE. The user who creates the subscription in the replicate
Replication Server needs the same login name and password in the primary SAP ASE and the primary
Replication Server.
○ Missing permissions in the primary database. The user who creates the subscription has to be a user
in the primary database and also have select permission in the primary table.
○ Missing permissions in the replicate database. The maintenance user needs select, insert,
update, and delete permissions on the tables in the replicate database.
○ A Replication Server or SAP ASE has stopped running. Try logging in to each of the servers. Restart any
servers that are not running.

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Important Disclaimers and Legal Information PUBLIC 123
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Replication Server Configuration Guide UNIX en

Uploaded by

Copyright:

Available Formats

Replication Server Configuration Guide UNIX en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Replication Server Configuration Guide UNIX en

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Replication Server 16.0 SP03

Replication Server Configuration Guide for UNIX

THE BEST RUN

Replication Server Configuration Guide for UNIX

4 Upgrade or Downgrade SAP Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Replication Server Configuration Guide for UNIX

6 Password Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7 Secure Sockets Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8 Start or Stop a Replication Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

9 Install and Implement Non-SAP ASE Support Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

10 Sample Replication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Replication Server Configuration Guide for UNIX

These style and syntax conventions are used in SAP documentation.

Monospaced (fixed-width) ● SQL and program code

Surrounded by angle brackets ● File and variable names

Replication Server Configuration Guide for UNIX

() Enter parentheses as part of the command.

● RepAgent – Replication Agent thread for SAP ASE

Replication Server Configuration Guide for UNIX

Replication Server Configuration Guide for UNIX

The configuration guide explains how to:

Before you begin:

1. Plan your replication system.

Plan the Replication System [page 8]

2.1 Plan the Replication System

Answer the following questions to plan your replication system.

In your planning, you need to know:

● Where will the primary and replicate data reside?

Replication Server Configuration Guide for UNIX

Primary and Replicate Data [page 9]

2.1.1 Primary and Replicate Data

When planning your replication system, decide on the following:

Install and Implement Non-SAP ASE Support Features [page 114]

2.1.2 Required Replication Servers

Replication Server Configuration Guide for UNIX

Upgrade or Downgrade SAP Replication Server [page 59]

2.1.3 Replication Server System Database Location

Replication Server System Database Information [page 24]

2.1.4 Initial Disk Partition for Each Replication Server

See System Requirements in the installation guide for your platform.

Replication Server Configuration Guide for UNIX

● SAP Replication Server is installed

Replication System Domain [page 12]

Replication Server Configuration Guide for UNIX

2.1.6 Databases that Require Replication Agents

A user database requires a Replication Agent:

Replication Server Configuration Guide for UNIX

Database Replication Agent Information [page 29]

2.1.7 Databases that Require Warm Standby

2.2 Complete the Replication Server Installation Worksheet

Replication Server Configuration Guide for UNIX

Replication Server Installation Worksheet Sample [page 14]

2.2.1 Replication Server Installation Worksheet Sample

Release Server Information

Replication Server name:*

Is this Replication Server the ID Server?* Yes No

Replication Server error log:

Replication Server configuration file:

No for “Will RSSD be em RSSD name:

No for “Will RSSD be em RSSD device name:*

Yes for “Will RSSD be re RS password: