After you have collected data about your current system, Sybase suggest that you write a migration plan. This chapter discusses migration methods and planning. In addition to choosing a migration method, you may need to bring your system resources to the level required by Adaptive Server version 15.0 and make changes needed in applications and system administration procedures.
Before beginning the upgrade process, consider these issues:
Before you run Adaptive Server, you must first implement your site licenses with the SySAM utility. See the Adaptive Server Installation Guide for your platform for pre-installation planning and SySAM installation information. See the Users guide: Software Asset Management 2.0 for information about SySAM. You can also see http://www.sybase.com/sysam for more information about SySAM and license issues.
For Adaptive Server installations 11.5.x and older, Sybase recommends that you first upgrade to Adaptive Server version 12.0, then upgrade to version 15.0.
Before you upgrade to the latest emergency bug fix (EBF) release and migrate your server, review the README file included with the EBF for general information, loading instructions, and specific fixes.
Some versions of Adaptive Server include system roles to control features. If you have modified the values of user or role IDs to resemble system accounts to control user IDs, login IDs, or roles, make sure these IDs do not conflict with users or roles added with the new version of Adaptive Server.
During a database upgrade, the upgrade process may add a new role to the database. If this role and ID pair already exists in the server, the new role cannot be added, causing the entire upgrade to fail. Before upgrading Adaptive Server, review sysusers and sysroles to make sure that any user or role IDs that you manually inserted are within the normal Sybase user range.
If you are using dump and load to upgrade to Adaptive Server 15.0, after the upgrade is complete, you must copy the existing login IDs and role information from the earlier version to the upgraded server before you load the first database to be upgraded.
You must repartitioned tables after you complete the upgrade. You can manually unpartition these tables before running the upgrade to save time and effort during the upgrade. This is particularly helpful for tables for which the partitioning scheme is changed. See “Partition changes” for more information partition changes.
