Recovering From a Failed Upgrade

Follow these steps after you have fixed the underlying problem that caused the failed upgrade.

1. Rerun the upgrade utility, $SYBASE/$SYBASE_ASE/upgrade/upgrade .
2. Reinstall system stored procedures using the scripts from the new version:

   isql -Usa -P<password> -i $SYBASE/$SYBASE_ASE/scripts/installmaster

   Note:

   When the server crashes during an upgrade, as it is restarting it attempts to upgrade the databases. After this finishes, and the installation is fully recovered, re-run the upgrade utility. This assures that all postupgrade configuration work is done. Then reinstall system stored procedures as previously described.

3. During the upgrade process, the log may become too full due to recorded catalog changes. If so, log in to the new server using isql, and issue:

   isql> dump tran dbname with truncate_only

   1. If truncate_only indicates that it could not truncate the log, retry the command as no_log instead.
   2. If this too does not truncate the log successfully, then use the alter database command to extend the database as explained below.
   This frees the log, and allows the upgrade process to continue.
4. In some cases, the pre-upgrade space estimations are insufficient for the data copy phase of upgrade. In this case, an error message says 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"

   alter database allows you to specify the size to alter the database with the unit-specifier ‘m’, or ‘M’.