Filter
Top Products
CHAPTER 5 Upgrading Adaptive Server
Installation Guide 65
sybsystemprocs
sybprocsdev is the default name for the device-holding database
sybsystemprocs. It is frequently referred to as the sybsystemprocs device in
Adaptive Server.
Verify that the
sybsystemprocs database is large enough. For an upgrade, the
default size for
sybsystemprocs is 124MB, or enough free space to
accommodate the existing
sybsystemprocs database, and the largest catalog
that is to be upgraded, plus an additional 10 percent for logging upgrade
changes. You may need more space if you are adding user-defined stored
procedures. 124MB accommodates additional internal data structures, but does
not account for the possibility of a larger number of user-defined system
procedures.
To assist with the upgrade process, Sybase recommends you set the
OLDSYBASE, OLDSYBASE_ASE, and OLDSYBASE_OCS environment
variables to point to the old installation of Adaptive Server. If you set these
environment variable to the old installation of the Adaptive Server, the upgrade
utility automatically populates input fields with the correct information as you
upgrade.
Set the OLDSYBASE_ASE variable to the SYBASE_ASE appropriate to your
older server. If you are upgrading from 12.0 for example, it should be
ASE-12_0. If your preupgrade version is earlier than 12.0, specify it as null:
setenv OLDSYBASE_ASE ""
This is required if you are using the sqlupgraderes utility to perform your
upgrade.
Use either of the following methods to upgrade Adaptive Server:
•
sqlupgrade – provides an X-Windows or Motif GUI for the upgrade
process. See “Using sqlupgrade” on page 65.
•
sqlupgraderes – provides a noninteractive, file-based interface for the
upgrade process.
sqlupgraderes allows you to upgrade Adaptive Server
using a resource file. This is useful for customer sites that want to upgrade
many similar servers. See “Using sqlupgraderes” on page 68.
Using sqlupgrade
sqlupgrade verifies that the server is eligible for the upgrade. Perform all
pre-upgrade tasks before running
sqlupgrade.