Downgrading from Replication Agent for Oracle 12.6

This procedure assumes you have followed the migration instructions above and are using a Replication Agent for Oracle version 12.6 instance. If the Replication Agent for Oracle version 12.5 instance no longer exists, create one using the Replication Agent for Oracle version 12.5 ra_admin or administrator command, then follow the procedure described below, using the $SYBASE/RAX-12_6/bin/gen_RAO_migrate_with_parms.ksh script described above, instead of the $SYBASE/RAX-12_6/bin/gen_RAO_migrate.ksh script described below.

The difference between the two generation scripts is that the gen_RAO_migrate_with_parms.ksh script copies parameter values in addition to initializing the primary database and the Replication Agent, whereas the gen_RAO_migrate.ksh script assumes all parameters are already configured.

To downgrade from Replication Agent for Oracle version 12.6

1. Generate the downgrade script by running the $SYBASE/RAX-12_6/bin/gen_RAO_migrate.ksh file:

   cd $SYBASE/RAX-12_6/bin
   �./gen_RAO_migrate.ksh mySrcRao myuid mypwd /workdir
   

   where:

   • mySrcRao is the name of the interfaces or sql.ini file entry for the Replication Agent for Oracle version 12.6.

   • myuid is the user ID for logging in to the Replication Agent for Oracle version 12.6 instance.�

   • mypwd is the password for logging in to the Replication Agent for Oracle version 12.6 instance. If there is no password, then use two double-quotes with nothing in between (““ ).�

   • workdir is the path name of a directory to use as a work area and where the <src_instance>_migrate_<date>.cmds file will be created�.

   The script generates a file (/<workdir>/<src_instance>_migrate_<date>.cmds) of Replication Agent commands that you will later run against the Replication Agent for Oracle version 12.5 instance to initialize the primary database, to initialize the Replication Agent for Oracle version 12.5 (including incrementing the database generation id), and to re-mark all the tables, procedures, and LOB columns that were marked in the Replication Agent for Oracle version 12.6 instance.

   The script does not modify any of the Replication Agent for Oracle version 12.5 parameters except for pdb_auto_run_scripts, pdb_dflt_column_repl, and pdb_convert_datetime, which will all be set to the same values as configured in the Replication Agent for Oracle version 12.6 instance.�

   When running the Korn shell script on Windows, if the following message appears, you can ignore it:�

   tail: write error on standard output: The pipe is being closed.
   

   After the migration script is generated, do not mark, unmark, enable, or disable any of the tables, LOB columns, or procedures, nor modify any parameters in the Replication Agent for Oracle version 12.6 instance. If you do, these changes will not be applied to the Replication Agent for Oracle version 12.5 instance.

2. To see which objects will be marked and which LOB columns will be enabled, examine the generated file /<workdir>/<src_instance>_migrate_<date>.cmds.

   If you want to change what is marked or enabled, you can make changes to this file. For example, you can set pdb_convert_datetime to true for some tables and procedures and to false for others.

3. Be sure that the appropriate Oracle JDBC driver is in your CLASSPATH. The one required for Replication Agent for Oracle version 12.6 will not work for older versions of Replication Agent for Oracle.

   No other Oracle drivers are allowed in the CLASSPATH.

4. Start and log in to the Replication Agent for Oracle version 12.5 instance.

5. Test the primary database connection:

   test_connection PDS
   

6. Prevent users (other than the Replication Agent for Oracle version 12.6 user) from any further access to the primary database.

7. Verify that the Replication Agent for Oracle version 12.6 instance is in REPLICATING state and allow replication to finish. To verify that replication has completed:�

   1. Periodically issue the ra_statistics command, watching until the following statistics are zero:

      • Input queue size

      • Output queue size

   2. When they are both zero, make note of the Last QID Sent from the last set of statistics.

   3. Issue the ra_locator update command so that Replication Agent retrieves the truncation point from Replication Server.

   4. Wait, then issue the ra_locator command and compare the displayed locator with that of the Last QID Sent. If they are different, wait and repeat this step.�

8. Quiesce the Replication Agent for Oracle version 12.6 instance.

9. In the Replication Agent for Oracle version 12.6 instance, de-initialize the Replication Agent:

   pdb_xlog remove, force
   

10. Shut down the Replication Agent for Oracle version 12.6 instance.

11. Run the script that was generated in Step 1 above against the Replication Agent for Oracle version 12.5 instance. For example:

    isql –S <myTgtRAO> -Umyuid -Pmypwd -i /<workdir>/<mySrcRao>_migrate_<date>.cmds
    

    where:

    • myTgtRAO is the name of the path to the Replication Agent for Oracle version 12.5 instance.

    • workdir is the path name of the directory that was used as a work area and where the <src_instance>_migrate_<date>.cmds file was created.�

    • mySrcRao is the name of the interfaces or sql.ini file entry for the Replication Agent for Oracle version 12.6.

    The script initializes the primary database, the Replication Agent (including incrementing the database generation id), and re-marks all the tables, procedures, and LOB columns that were marked in the Replication Agent for Oracle version 12.6 instance.

12. Allow users access to the primary database.�

13. Log in to the RSSD and set the Replication Server’s locator to “0”:

    rs_zeroltm source_ds, source_db
    

    where source_ds and source_db match the Replication Agent for Oracle version 12.5 instance’s values for the rs_source_ds and rs_source_db parameters.

    The rs_source_ds and rs_source_db values were migrated from Replication Agent for Oracle version 12.6 and should not be changed.

14. In the Replication Agent for Oracle version 12.5 instance, resume replication.�

15. Log out of the Replication Agent for Oracle version 12.5 instance.�

16. If you created a new interfaces or sql.ini entry when you upgraded to Replication Agent for Oracle version 12.6, update entry so the Replication Agent for Oracle version 12.5 instance name is again associated with the old Replication Agent for Oracle version 12.5 instance machine and port number.

17. Revert the Oracle logging properties back to your desired setup in the primary database.

18. Revoke any additional privileges that were granted to the Replication Agent primary database user for the upgrade in the primary database.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF