Moving a Replication Agent Instance to the Same Platform

Move a Replication Agent instance to another host machine that uses the same operating system and hardware.

1. Install Replication Agent on host2. Sybase recommends that you use the same installation directory structure as on host1.
   Note: The version string of the Replication Agent that you install on host2 must be exactly the same as the version string of the Replication Agent on host1 .
2. On host2, install one of the following as appropriate for your primary database:
   • JDBC driver (Oracle or Microsoft SQL Server)
   • IBM DB2 client

   Update the CLASSPATH environment variable.
3. If you are moving an instance of Replication Agent for UDB (any version), Replication Agent for Oracle 15.7.1, or Replication Agent for Microsoft SQL Server 15.0, skip this step.
   • (Linux or UNIX) Mount the drive containing the online and archive logs for the primary Oracle database.
   • (Windows) For Replication Agent for Oracle version 15.6 and earlier, or Replication Agent for Microsoft SQL Server version 15.1 and later, map a network drive to the location containing the primary database transaction and archive logs.
4. Shut down inst1 on host1.
5. Copy the inst1 instance directory to host2 from host1:
   • (Linux or UNIX) $SYBASE/RAX-15_n
   • (Windows) %SYBASE%\RAX-15_n
6. Update any interfaces (Linux or UNIX) or sql.ini (Windows) files that refer to the inst1 instance. Change the host name of the entries to host2 from host1.
   If you use Sybase Control Center (SCC) to monitor the Replication Agent instance, update the host name for the inst1 instance in SCC.
7. If you chose to install Replication Agent on host2 in the same installation directory as on host1, skip this step.
   If the installation directory on host2 is different from that used on host1, edit these properties in the $SYBASE/RAX-15_n/inst1/inst1.cfg (Linux or UNIX) or %SYBASE%\RAX-15_n\inst1\inst1.cfg (Windows) configuration file:

   • asa_install_dir
   • lob_cache_directory
   • log_directory
   • rasd_backup_dir
   • rasd_database
   • rasd_trace_log_dir
   • rasd_tran_log
   • rasd_tran_log_mirror

   Note: Not all Replication Agent versions or types use all of these properties.

   For example, to edit log_directory on Linux or UNIX, change:

   log_directory=<host1_install_dir>/RAX-15_n/inst1/log

   to:

   log_directory=<host2_install_dir>/RAX-15_n/inst1/log

   where <host1_install_dir> and <host2_install_dir> are the installation paths for Replication Agent on host1 and host2.
   On Windows, use double backslashes in path names. For example, change:

   log_directory=C\:\\sybase\\RAX-15_5\\inst1\\log 

   to:

    log_directory=C\:\\software\\syb\\RAX-15_5\\inst1\\log

8. On host2, start inst1 in the Admin state.
9. If you are moving an instance of Replication Agent for UDB (any version), Replication Agent for Oracle 15.7.1, or Replication Agent for Microsoft SQL Server 15.0 skip this step.
   For Replication Agent for Oracle version 15.6 and earlier, or Replication Agent for Microsoft SQL Server version 15.1 and later, adjust the device paths.
10. Resume inst1 instance on host2.