If you are rolling back after having used any of the 15.0.2 features, additional steps can be necessary. You should take steps before you downgrade to 15.0 or 15.0.1, and others should be performed immediately after downgrading. You need to read the documentation on the features below that may require manual changes.
To correct errors related to:
Encrypted columns – see Chapter 2” Encrypted Columns” in Adaptive Server 15.0.2 New Feature Guide
User passwords – see Chapter 10 “Supported Security Features” in Adaptive Server 15.0.2 New Feature Guide
instead of triggers – see Chapter 22, “Instead of Triggers” in Adaptive Server 15.0.2 New Feature Guide
SQL user-defined functions – see Chapter 17 “User Defined SQL Functions” in Adaptive Server 15.0.2 New Feature Guide
Archived databases – see Chapter 4 “Archived Database Access” in Adaptive Server 15.0.2 New Feature Guide
Hash built-ins – see Chapter 19 “Changes to System Procedures, Functions and Commands” in Adaptive Server 15.0.2 New Feature Guide
In general, no additional steps are required when you are returning to an Adaptive Server version in which the feature was already available.
Drop all stored procedures, views, and triggers that use the messaging built-ins for the Real-Time Messaging feature.
For more information about Real Time Messaging, see the Real Time Data Services Messaging Users Guide.
If a new nocase sortorder for Chinese or Japanese character sets is configured as Adaptive server's default sortorder. Before downgrading to a 15.0 or 15.0.1 release, switch to a sortorder that is compatible to that release. Switching a sortorder means all user indexes need to be reindexed. Please refer to System Administration Guide Chapter 9 “Configuring Character Sets, Sort Orders, and Languages” for details on how to change server's default sortorder. If sp_downgrade is called when the new nocase sortorder is in use, the error message “Cannot downgrade to ‘%1!’ server, which does not support server's current default sortorder” will be raised and the downgrade process will be aborted.
The XML Service feature of Adaptive Server includes the new xmltable function. If you create views or stored procedures using the xmltable function in 15.0.2, then return to 15.0 or 15.0.1, you will get an error.
Instead of Triggers are objects stored in the system catalogs. These objects should be removed before downgrading. When the 15.0 or 15.0.1 server is booted any Instead of Triggers that were not removed will remain in the system catalogs but will not execute.
SQL user defined functions are also objects stored in the system catalogs. If you do not remove them before downgrading, they remain in the catalogs after downgrade. Attempts to drop or execute a SQL user defined function from a 15.0 or 15.0.1 version will result in misleading error messages.
If you installed the 15.0.2 automatic database expansion procedures using installdbextend, and then applied the threshold procedure to one or more database segments, the thresholds might not work properly when applied to the log segment after a downgrade to 15.0 or 15.0.1.
To clear all auto-expansion thresholds that might exist on one or more segments before downgrading, use the command:
sp_dbextend 'clear', 'threshold'
Alternatively, before downgrading, you can disable the entire automatic expansion feature server-wide without changing any existing rules or clearing any thresholds. Execute the following commands using sa_role:
use master go sp_dbextend 'disable', 'database', 'server-wide' go
This prevents threshold procedures from doing any work even if they were fired at runtime.
Sybase recommends that you leave all the policies and thresholds in place, and simply disable the entire feature server-wide before the downgrade. This simplifies re-enabling automatic expansion if you return to 15.0.2 later.
When downgrading a server that has replication enabled on databases that contain encrypted data, perform one of the following before you start the downgrade procedure:
Ensure that all replicated data in the primary database transaction log has been successfully transferred to the standby or replicate database. The process for doing this is application dependent.
Using the following commands truncate the transaction log in the primary database, and zero the RS locator for that database in the Replication Server. In the primary database run:
sp_stop_rep_agent primary_dbname
dbcc settrunc ('ltm', 'ignore')
dump tran primary_dbname with truncate_only
dbcc settruc ('ltm', 'valid')
Shut down Replication Server. In the RSSD for the Replication Server run:
rs_zeroltm primary_servername, primary_dbname
If you are downgrading to Adaptive Server versions 15.0 or 15.0.1, run installjsdb script from the lower version anytime you downgrade Job Scheduler.
Disable Job Scheduler before you downgrade Adaptive Server:
sp_configure "enable job scheduler", 0
Downgrade Adaptive Server. See the installation guide for details.
Run the installjsdb script from the version you are downgrading to:
isql –Usa –Psa_password –Sservername –i $SYBASE_ASE/scripts/installjsdb
The directory with the location of the isql executable ($SYBASE_OCS/bin)
must be in your path.
Enable Job Scheduler:
sp_configure "enable job scheduler", 1
To start Job Scheduler, either restart the server, or enter:
use sybmgmtdb� go� sp_js_wakeup "start_js",1 go�
Downgrading Job Scheduler