Upgrading compiled objects with dbcc upgrade_object
116 Adaptive Server Enterprise
Error reporting
To send all the output from dbcc upgrade_object to the window, a System
Administrator can execute
dbcc traceon(3604). Sybase recommends that you
use this command if you think the output of error messages might overflow the
error log.
Using database dumps in upgrades
Upgrading using dump and load
You can load pre-12.5 database dumps and transaction logs and upgrade the
databases.
Some issues of which you should be aware:
• Upgrading requires space for copying data and logging changes to the
system tables during the upgrade process. If the source database in the
dump was nearly full, the upgrade process might fail due to insufficient
space. While this is expected to be uncommon, you can use
alter database
to extend the free space in the event of insufficient-space errors.
• After reloading an older dump, run
sp_checkreswords from the new
installation on the loaded database to check for reserved words.
Upgrading compiled objects in database dumps
When you load a database dump that was created in an earlier version than the
current Adaptive Server, you are not required to perform the pre-upgrade tasks
before loading the dump. Therefore, you will not receive any notification if the
compiled objects in your database dump are missing their source text. After
loading a database dump, run
sp_checksource to verify the existence of the
source text for all compiled objects in the database. Then, you can allow the
compiled objects to be upgraded as they are executed, or you can run
dbcc
upgrade_object
to find potential problems and upgrade objects manually.
For information on using
sp_checksource, see the Reference Manual:
Procedures.