Upgrading RSSD or ERSSD with rs_init

(Optional) Use rs_init to upgrade the RSSDs or ERSSDs so they are compatible with the executable programs.

1. Log in as the “sybase” user and change to the directory where you installed Replication Server—$SYBASE.
2. Set SYBASE environment variables to the directory where Replication Server 15.7 is installed by using the SYBASE.sh or SYBASE.csh shell scripts.
3. Verify that the RSSD and Replication Servers that you are upgrading are running.
4. If the Replication Server uses Adaptive Server 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 must have 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.
5. If the Replication Server uses an ERSSD, edit the rs_name.cfg file, where rs_name is your Replication Server:
   1. Add the erssd_release_dir parameter to specify the location of the SQL Anywhere ERSSD database that you are going to upgrade. For example:

      erssd_release_dir=/sybase/REP-15_5/ASA11

   2. 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”. At the entry for "ERSSD start command", you see for example:

      ERSSD start command: /sybase/REP-15_5/ASA11/bin/dbspawn
      -f -q /sybase/REP-15_5/ASA11/bin/dbsrv11
      -s none -ti 0 -x "tcpip(PORT=15501;DOBROAD=NO;BLISTENER=NO)"
      -o /sybase/REP-15_5/errorlog/rs155_prs_ERSSD.out
      /sybase/REP-15_5/dbfile/rs155_prs_ERSSD.db 

   3. 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:
   1. Add the erssd_ra_release_dir parameter to specify the location of the SQL Anywhere ERSSD database that you are going to upgrade. For example:

      erssd_ra_release_dir=/sybase/REP-15_5/ASA11

   2. 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.” For example:

      erssd_ra_start_cmd=/sybase/REP-15_5/ASA11/bin/dbltm
      -ud -S SAMP_RS_ERSSD_ra
      -C /sybase/REP-15_5/samp_repserver/SAMP_RS_ERSSD_ra.cfg
      -ot /sybase/REP-15_5/samp_repserver/SAMP_RS_ERSSD_ra.out
      -I /sybase/interfaces

7. If you are upgrading from Replication Server version 12.6 to version 15.7.1 SP100 and if 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/RS126/REP-12_6/ASA8/lib
   export LD_LIBRARY_PATH

8. Start rs_init:
   $SYBASE/$SYBASE_REP/install/rs_init
   You see the RS_INIT menu.
9. Select Configure a Server Product. Choose 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.
    1. Enter the name of the Replication Server with the RSSD you are upgrading.
    2. Enter the login name for the Replication Server “sa” user. The default value is “sa."
    3. Enter the password for the “sa” user on the Replication Server.
    4. Enter the path name of the Replication Server configuration file.
    5. 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 that they use the programs in the new version directory.
15. Restart Replication Server using the appropriate executables for the new version.
    Warning!  Some Replication Server configuration options with newer versions may have a wider valid range. If you increase any of these configuration options after upgrading, you must 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.
    1. 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-15_5/bin/repserver and start Replication Server from $SYBASE/REP-15_5/bin/repserver.
       
    2. If you are using Adaptive Server as the RSSD, restart the RepAgent for the RSSD:

       sp_start_rep_agent RSSD_name

    3. Resume log transfer to Replication Server from all Replication Agents for primary databases, and RSSD or eRSSD:

       resume log transfer from all

    4. 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

16. If you have more Replication Servers to upgrade, repeat the upgrade procedures.