The procedure for recovering from a failed upgrade is:
Fix the underlying problem
Rerun the upgrade utility, $SYBASE/$SYBASE_ASE/upgrade/upgrade
Reinstall system stored procedures using the scripts from the new version
isql -Usa -P<password> -i $SYBASE/$SYBASE_ASE/scripts/installmaster
If Adaptive Server crashes (e.g., if there's a power
failure) while upgrade is in progress, when it is restarted it will
attempt to upgrade databases while it is booting. Messages for this
upgrade will go to Adaptive Server's console (the terminal or window
where it was started). After this finishes, and the installation
is fully recovered, re-run the upgrade utility. This assures that
all post-upgrade configuration work is done. Then reinstall system
stored procedures as previously described
During the upgrade process, the log may get full due to the catalog changes that are made. If so, log in to the 15.0.2 server using isql, and issue:
isql> dump tran dbname with truncate_only
If “truncate_only” indicates that it could not truncate the log, try again using option "no_log" instead. If this too does not truncate the log successfully, then you will need to use "alter database" to extend the database as explained below.
This frees the log space, and allow the upgrade process to continue.
In some cases, the pre-upgrade space estimations might be insufficient for the data copy phase of upgrade. In this case, you may get an error that there is insufficient space in the system segment for the upgrade. The upgrade process hangs, waiting for space to be provided. You can log in to the new server using isql, and use alter database to increase the size of the database.
isql> alter database dbname on device_name = "2m"
In 15.0.2 Adaptive Server, alter database allows
you to specify the size to alter the database with the unit-specifier ‘m’,
or ‘M’.
