This section describes the steps for migrating from Mirror Replication Agent version 12.6 to Mirror Replication Agent version 15.0.
To migrate from Mirror Replication Agent 12.6 to 15.0
Sybase recommends that you back up the existing Mirror Replication Agent instances directory containing the instance configuration file. In addition, for Mirror Replication Agent for Oracle, back up the Mirror Replication Agent System Database (RASD).
Shut down all of the Mirror Replication Agent version 12.6 instances.
Use the ma_admin utility script from the Mirror Replication Agent 15.0 installation's bin directory to upgrade all of the verifiable Mirror Replication Agent version 12.6 instances. Execute the ma_admin utility script with the -u option:
ma_admin -u <src_directory>
where the src_directory is the full path name to the Mirror Replication Agent version 12.6 installation directory. For example:
For UNIX:
/sybase15/MA-15_0/bin/ma_admin.sh -u /sybase/MRO-12_6
For Windows:
d:\sybase15\MA-15_0\bin\ma_admin -u d:\sybase\MRO-12_6
This command will upgrade all valid Mirror Replication Agent instances.
For information about those instances that failed to upgrade, refer to the administration logs (…/MA-15_0/admin_logs). After you correct the problem, you can re-run this command. (This command will not upgrade again those Mirror Replication Agent instances that have already been successfully upgraded.)
Be sure that your CLASSPATH is set properly for the Mirror Replication Agent version 15.0 instances. For Mirror Replication Agent for Oracle, use ojdbc14.jar.
Start Mirror Replication Agent version 15.0.
Log in to each Mirror Replication Agent instance and run the ra_migrate command first.
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 Mirror Replication Agent instance. For example:
ra_config pdb_archive_path, <log path on the rep agent setup machine>
You can now resume replication.
