Post-downgrade Tasks

After you perform the basic downgrade steps, some changes from the 15.5 upgrade still persist.

1. If you have both a local and a remote server running on an Adaptive Server version 15.x and are upgrading both of them, upgrade the local server first. If one is to be upgraded but not the other, upgrade the local server first. Sybase does not certify that Component Integration Services running on earlier versions of Adaptive Server can connect to later versions. You may encounter errors if an earlier version of Adaptive Server maps a proxy table to a later version and the remote table uses functionality not available in the earlier release. Sybase certifies that each version of Adaptive Server connects to earlier releases through Component Integration Services. Component Integration Services is tested and certified to connect to earlier versions of Adaptive Server.
2. Installing system stored procedures of the old version drops auditing information about the system stored procedures. Reenable auditing for all system stored procedures for which auditing was enabled before the downgrade. Use the output of sp_displayaudit recorded during predowngrade to help determine the system stored procedures for which auditing was enabled. Reenter the audit options using sp_audit. For example, if you had enabled stored procedure auditing for sp_addlogin stored procedure in your server before upgrading, run the following sp_audit command to reenable auditing on sp_addlogin:

   sp_audit "exec_procedure", "all", "sp_addlogin", "on"

   After you run installmaster, installmodel, installcommit, installsecurity, installhasvss, installjsdb, and installmsgsvss on your downgraded server, return system stored procedures to their earlier form. New stored procedures introduced in releases subsequent to the downgraded server are not removed.

   Attention: Attempts to execute new stored procedures against an older binary have unpredictable results.
3. During upgrade to Adaptive Server 15.5 you should have created a restore_msgs.ebf file. Now you must run this script to restore your messages back to the version from which you upgraded.

   isql -Usa  -P <sa_password>  -S <server_name> -i <restore_msgs.ebf> 

   Note:

   If you upgraded from a 15.0 or 15.0.1 release and are reverting back to the 15.0 or 15.0.1 release, then you must only run instmsgs.ebf file from the relevant release.

4. The on-disk structures of stored procedures, triggers, and views may contain statement identity tokens, datatypes and object references that are not understood by the earlier Adaptive Server versions. You must drop all compiled objects that use features introduced into Adaptive Server subsequent to the release to which you are downgrading.
5. If during the upgrade process you ran the ‘update all statistics’ on syslogins then you must delete statistics for syslogins and recreate them. spt_values are dropped and re-created when you run installmaster from the release area you downgraded to. Any new types are eliminated from this table.
6. Running installmaster from the release area of the server to which you downgraded removes configuration parameters, that belong to 15.5, by deleting sysconfigures rows for configuration parameters that do not exist in syscurconfigs. After running installmaster the error messages no longer appear when you start the server. If a downgraded server is booted using the 15.5 configuration file, the new options cause the message ‘Unknown parameter’ the unknown options are reported the first time the server is booted. These messages can be ignored because the configuration file is rewritten without the unknown options.
7. If you used keywords in 15.5, see the Additional Steps Required if You Used New Features topic for more information.
8. If you disabled replication before the downgrade process, enable it again. Consult the Reenabling Replication Server After the Dataserver Upgrade topic for more information.