Replication Server version 15.7.1 - Sybase ASE 15.5, how to change primary data server in RSSD?

Question

Recently, I am requested to migrate the current Sybase data server to a new Sybase data server (let's say, from pub1 to pub2). To do this, I need to rebuild all the RepAgents which have been set up previously in pub1. Is there any primary data server I would need to set in the RSSD? Because I could see when I run the command 'connect' without any option, it will connect to (pub1.repserver) instead of (pub2.repserver). Is there any configuration required on the RSSD to make it (pub2.repserver)? Also, I actually have setup one RepAgent (pub2.db_lotte), the setup process using rs_init was successful, but seems the RepAgent connection is down after the setup process (admin who_is_down), the connection couldn't bring up and no error is captured in the replication log.

Appreciate if anyone could help.

Thanks.

Answer 1

You're going to need to provide more details on what you mean by 'migrate the current Sybase data server', eg, are you moving the dataserver? are you copying the dataserver? something else?

Also, there's generally nothing to do directly in the RSSD. All commands should be issued either in the PDB, the PRS/RRS, and/or the RDB.

---

Generally speaking ...

If a database has been copied from elsewhere (eg, dump and load), you'll want to make sure the old repagent info is discarded and the old secondary trunc pt is removed, eg:

use new_db
go
-- in case repagent is running:
exec sp_stop_rep_agent 'new_db'
go
-- discard repagent config settings
exec sp_config_rep_agent 'new_db','disable'
go
-- in case sp_config_rep_agent didn't remove 2nd tp:
dbcc settrunc('ltm','ignore')
go

At this point you then use rs_init to add 'new_db' as a a new database/connection to the desired PRS.

NOTE: If 'new_db' is to be the active db in a WS setup, make sure the logical connection has been created before running rs_init.

Once you've added 'new_db' to the replication domain you'll need to continue with normal replication setup, eg:

• make sure RDB(s) is added to the replication domain (if not already a member)
• add route(s) to RRS (as needed)
• setup repdefs/subs
• assign any custom/modified classes to the DSI connections