Adding the Primary Database to Replication Server

Add the Replication Server instance to the interfaces file of the data server that hosts the primary database.

Note: Restart the Adaptive Server instance if the interfaces file has changed.

Go to $SYBASE/$SYBASE_REP/init/rs.

Make a copy of the setupdb.rs file and rename it as myprimary.rs.

Edit the myprimary.rs file.

Note: Modify the parameters described in this table.

Sample Values for the myprimary.rs File
Parameter	Description	Value
sybinit.release_directory	Valid path of the Replication Server software ($SYBASE).	/opt/software
rs.rs_name	Name of the Replication Server.	SAMPLE_RS
rs.rs_rs_sa_user	User ID that has “sa” privileges on Replication Server.	sa
rs.rs_rs_sa_pass	Password of the “sa” user.	sa_pass
rs.rs_ds_name	Name of the data server that hosts the primary database.	sunak1502i
rs.rs_ds_sa_user	User ID that has “sa” privileges on data server.	sa
rs.rs_ds_sa_password	Password of the “sa” user for the data server.	password
rs.rs_db_name	Name of the primary database.	pubs2
rs.rs_needs_repagent	Specifies whether you plan to replicate from specified primary database.	yes
rs.rs_db_maint_user	User ID whose work is not replicated when logged on the primary database. The user is called maintenance user.	<`database`>_maint Note: If the user ID does not exist, the script creates the user ID on the database. The user ID cannot be the name of an alias.
rs.rs_db_maint_password	Password for the maintenance user.	<`database`>_maint_ps
rs.rs_ltm_rs_user	User that the Replication Agent will use to log into the Replication Server. The name must exist. This name typically comes from values that were set up during Replication Server creation time: rs.rs_ltm_rs_user.	`SAMPLE_RS_ra`
rs.rs_ltm_rs_pass	Password of the rs.rs_ltm_rs_user.	sa_pass
rs.rs_db_physical_for_logical	Specifies whether this is a warm standby database.	no

Save the file.

Go to $SYBASE/$SYBASE_REP/install.

Create the connection from the primary database to the Replication Server by running the resource file:

./rs_init -r ../init/rs/myprimary.rs

If the rs_init command fails, check the log file in $SYBASE/$SYBASE_REP/init/logs, correct the issue, then disable the RepAgent as follows:

Log in to the primary Adaptive Server using an “sa” user role and access the primary database.
Disable the RepAgent thread in the primary database:
```
sp_config_rep_agent pubs2,'disable'
go
```

Re-run rs_init command

Validate the primary connection:

isql -Usa -Psa_pass -SSAMPLE_RS

Enter:

admin who
go

The output from the command looks similar to:

Spid     Name       State              Info
------   -------    ------------       -----------
48       DSI EXEC   Awaiting Command   102(1)sunak1502i.pubs2
33       DSI        Awaiting Message   102 sunak1502i.pubs2
35       DIST       Awaiting Wakeup    102 sunak1502i.pubs2
36       SQT        Awaiting Wakeup    102:1 DIST sunak1502i.
pubs2
34       SQM        Awaiting Message   102:1 sunak1502i.pubs2
32       SQM        Awaiting Message   102:0 sunak1502i.pubs2
37       REP AGENT  Awaiting Command   sunak1502i.pubs2
39       NRM        Awaiting Message   sunak1502i.pubs2
27       DSI EXEC   Awaiting Command   101(1)SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
20       DSI        Awaiting Message   101 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
26       SQM        Awaiting Message   101:0 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
21       dSUB       Sleeping
15       dCM        Awaiting Message
18       dAIO       Awaiting Message
23       dREC       Sleeping           dREC
9        dDELSEG    Awaiting Message
49       USER       Active             sa
14       dALARM     Awaiting Wakeup
24       dSYSAM     Sleeping

Exit the isql session.