A minor change was made to the format of a log record in SAP ASE version 15.5 that introduces an unlikely possibility for the SAP ASE server to misinterpret this changed log record in cases where the upgraded server contains a database that is the primary database for replication. This change should not affect your upgrade process; however, it requires you to strictly follow some steps when you move from SAP ASE 15.0.x or earlier to SAP ASE 15.5.x and later (nonclustered editions). See the following table for all possible combinations of upgrades.
Current Version | Upgrading to | Special Upgrade Information |
---|---|---|
SAP ASE 15.0.x or earlier | SAP ASE 16.0 |
If you are using Replication Server to replicate one or more databases in the version to be upgraded, ensure that all transactions have been replicated before the polite shutdown is done, by draining the log. See Upgrading ASE in a Replication System and Upgrading Replication Server in the Replication Server Configuration Guide for your platform. |
SAP ASE Cluster Edition 15.5.x or later | SAP ASE 16.0 |
Upgrading any version of SAP ASE Cluster Edition to a nonclustered version is not supported. |
SAP ASE 15.5.x | SAP ASE 16.0 |
No special upgrade instructions. |
Current Version | Upgrading to | Special Upgrade Instructions |
---|---|---|
SAP ASE 15.0.x and earlier | SAP ASE 16.0 |
When you use online database to upgrade a single database in SAP ASE 16.0 (either the cluster or noncluster edition) after loading a database dump and transaction logs from SAP ASE 15.0.x or earlier, if the database you are upgrading is also replicated, make sure the database's transaction log is truncated before you turn replication back on. |
SAP ASE Cluster Edition 15.5.x or later | SAP ASE 16.0 |
Upgrading a database from any version of the Cluster Edition to a nonclustered version is not supported. |
SAP ASE 15.5.x | SAP ASE 16.0 |
No special upgrade instructions. |