Adaptive Server sqlupgrade only upgrades Adaptive Server from one version to another. This section describes how to upgrade a 32-bit version of Adaptive Server to a 64-bit version of Adaptive Server.
To migrate Adaptive Server from the 32-bit to the 64-bit version, you must first install and configure the 64-bit operating system.
Run dbcc checks on all databases in the 32-bit Adaptive Server and make sure they run cleanly.
Create a 64-bit Adaptive Server in a new directory
Create devices and databases to match those in the 32-bit server. Make sure that the sysusages mapping is correct. See document ID #1324 http://my.sybase.com/detail?id=1324.
Allow 10 percent more space for the sybsystemprocs database.
Dump the databases on the 32-bit server.
Load the databases to the 64-bit server.
If you have partitioned tables, update partition statistics.
Run dbcc checks on the 64-bit server and make sure they run cleanly.
If you have DDL scripts to create devices, databases, tables, rules, stored procedures, triggers, and views you can use bcp to move data out of the old database and into the new.
If you do not have DDL scripts, use the ddlgen utility to re-create the schema for the Adaptive Server you are about to upgrade. See the Utility Guide.
Run dbcc checks on databases to verify data integrity.
Use bcp to extract all the data from all the tables in the databases.
Create a new 64-bit Adaptive Server in a new directory.
Create devices, databases, and tables.
bcp data into tables.
Recreate all views, triggers, stored procedures.
Run dbcc checks on the 64-bit server and make sure they run cleanly.
The third method requires you to modify some key files, recreate stored procedures, then replace the binary.
Run dbcc checks on all databases in the 32-bit Adaptive Server and make sure the dbcc's run cleanly. (checkdb, checkalloc, checkcatalog and checkstorage)
In a new directory, copy the files for the 64-bit Adaptive Server.
Shut down the 32-bit server.
Copy the interfaces file and the configuration file from the 32-bit $SYBASE directory to the 64-bit $SYBASE directory.
Copy the 32-bit $SYBASE/install RUN_server file to the equivalent 64-bit $SYBASE/install directory.
Edit the RUN_server file to reflect the new location of the interfaces, configuration, and log files.
Remove all references to the 32-bit $SYBASE directories from your $PATH definition.
cd to the 64-bit $SYBASE and source the SYBASE.csh script (c shell) or SYBASE.sh script (korn shell).
cd to the 64-bit $SYBASE/install and execute:
startserver -f RUN_server
After the 64-bit server starts, run installmaster, installmodel, and installmsg.ebf.
If you used dbccdb for dbcc checkstorage, run the installdbccdb. This recreates some tables in the dbccdb, and you may loose history data.
Drop and recreate all your compiled objects, such as stored procedures, triggers, views, and defaults.
If you have partitioned tables, update partition statistics.
Run dbcc again on all databases to verify that they run cleanly.
WARNING! If you originally created your user passwords on a SQL Server running on a SunOS system and are now running on 32-bit Solaris, you could experience a problem related to passwords due to Sun encryption changes in recent releases.
In order to ensure that your passwords will work in the new system, you must either be running version 12.0.0.3/esd#1, or drop and recreate all user passwords on the 32-bit system before migrating to the 64-bit server. You can use the same passwords or create a new set.
