This section describes the steps for migrating from Replication Agent version 12.6 to Replication Agent version 15.0, for both Oracle and Microsoft SQL Server.
To migrate from Replication Agent 12.6 to 15.0
Sybase recommends that you back up the existing Replication Agent instances directory containing the instance configuration file. In addition, for Replication Agent for Oracle, back up the Replication Agent System Database (RASD).
Shut down all of the Replication Agent version 12.6 instances.
Use the ra_admin utility script from the Replication Agent 15.0 installation's bin directory to upgrade all the verifiable 12.6 Replication Agent instances. Execute the ra_admin utility script with the -u option:
ra_admin -u <src_directory>
where the src_directory is the full path name to the Replication Agent version 12.6 installation directory. For example:
For UNIX:
/sybase15/RAX-15_0/bin/ra_admin.sh -u /sybase/RAX-12_6
For Windows:
d:\sybase15\RAX-15_0\bin\ra_admin -u d:\sybase\RAX-12_6
This command will upgrade all valid Replication Agent instances.
For information about those instances that failed to upgrade, refer to the administration logs (…/RAX-15_0/admin_logs). After you correct the problem, you can re-run this command. (This command will not upgrade again those Replication Agent instances that have already been successfully upgraded.)
Please make sure your CLASSPATH is set properly for the Replication Agent 15_0 instances. For Replication Agent for Oracle, use ojdbc14.jar.
Start Replication Agent version 15.0.
Log in to each Replication Agent instance and run the ra_migrate command first.
For Oracle only: If you do not want to have automatic archiving turned on (a version 12.6 default), then pdb_include_archives in version 15.0 needs to be set to false. If automatic archiving is true (a version 15.0 default), then pdb_archive_path needs to be set and the pdb_archive_remove needs to be false (a version 15.0 default) for each Replication Agent instance. For example:
using isql to "ra_config pdb_archive_path, <log path on the rep agent setup machine>
You can now resume replication.
