Filter
Top Products
CHAPTER 5 Upgrading Adaptive Server
Installation Guide 87
5 Copy the 32-bit $SYBASE/$SYBASE_ASE/install/RUN_<server> file to
the equivalent 64-bit $SYBASE/$SYBASE_ASE/install directory.
6 Edit the RUN_server file to reflect the new location of the interfaces,
configuration, and log files.
7 Remove all references to the 32-bit $SYBASE directories from your
$PATH definition.
8 Change to the 64-bit $SYBASE directory and source the ASE150.[csh, sh]
script (Bourne shell).
9 Change to the 64-bit $SYBASE/install directory and execute:
startserver -f RUN_server
10 After the 64-bit server starts, run installmaster, installmodel, and
installmsg.ebf.
11 If you used
dbccdb for dbcc checkstorage, run installdbccdb. This
re-creates some tables in the
dbccdb, and you may lose history data.
12 Drop and re-create all your compiled objects, such as stored procedures,
triggers, views, and defaults.
13 If you have partitioned tables, update partition statistics.
14 Run
dbcc again on all databases to verify that they run cleanly.
Warning! If you originally created your user passwords on an Adaptive 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.
To ensure that your passwords will work in the new system, you must either be
running version 12.0.0.3/esd#1, or you must drop and re-create 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.
Recovering from a failed upgrade
• During the upgrade process, the log may get full due to the catalog changes
that are made. If so, log in to the new server using
isql, and issue: