If you ran the pre-upgrade option in preupgrade,
the utility scanned the system catalogs and calculated how much
additional space needed to perform the upgrade.
Note:
Sybase recommends that you use preupgrade to
determine how much free space is required for the upgrade.
-
If you ran the pre-upgrade option in preupgrade,
the utility scanned the system catalogs and calculated how much
additional space needed to perform the upgrade.
-
If you did not run the pre-upgrade check, you must manually
calculate how much free space you must add to your system catalogs
and databases.
As a general rule, you must double the size of the
largest catalog that you are going to upgrade, and add approximately
10 percent more to calculate the free space required for the upgrade
to succeed. For example, if you have a large number of stored procedures
or compiled object in any database, the syscomments and sysprocedures catalogs require additional
space.
-
If you do not have a sybsystemdb, and are
not using two-phase commit or DTM applications, create a sybsystemdb with
a minimum of 4MB. If you are using two-phase commit or DTM, you can either:
- Create a minimum-sized sybsystemdb for
upgrade and expand it later, or
- Create a sybsystemdb of 5 to
20MB, depending on your expected usage. Approximately 25 percent
of the database should be data storage, and 75 percent should be
log storage.
Adaptive Server uses this database for tracking transactions and
during recovery. In addition, it is used for applications using two-phase
commit and Distributed Transaction Management (DTM).
-
If you do not have a sybsystemdb database:
1> use sybsystemdb
2> go
1> sp_create_syscoordinations
2> go
-
If you have a sybsystemdb and the database
is at least 4MB, you do not need to make any changes. If the database
is smaller than 4MB, increase the size with alter database.
-
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.
-
If you are using the Java in the database feature you must enable PCI and
configure sybpcidb database. For sqlupgrade[res],
the enable java setting in the old server is detected.
If it is set at 1, then preupgrade asks you to
create a sybpcidb device and database before
you run upgrade.
-
Increasing the default database size. See the Increasing Default Database Sizes topic for instructions on how to do this.