Normally, you need to restart Replication Server only if you are reconfiguring system files or if your system experienced a failure that brought down Replication Server. Initially, the installation process starts the replication system for you.
To bring up a Replication Server site, start system components in this sequence:
Start the data server containing the databases that Replication Server manages.
If Replication Server uses Adaptive Server Enterprise for the RSSD, start the RSSD. For more details, see the Replication Server Installation Guide.
Start Replication Server by executing the repserver command on UNIX systems, or the repsrvr.exe command on Windows 2000 or 2003 systems, or by executing the Replication Server run file.
Start RepAgent for the data server and for the RSSD if RepAgent has not been configured to start automatically at server startup.
If you are using the LTM as the replication agent, start the LTM by executing the ltm command or by executing the LTM run file after starting Replication Server. For details, see
To ensure that Replication Server started with no errors:
Check the repserver.log file for error messages (indicated with the letter “E” on the left), as described in .
Use Sybase Central to check Replication Server status.
RSM – You can use the topology view in Sybase Central to check the status of Replication Server components. See “Viewing the status of a server or folder” in Replication Server’s plug-in help.
Use isql to log in to each Replication Server, or use a script that logs in to each server. See .
