Finding compiled object errors before production – Sybase ADAPTIVE 15.0.2 User Manual

Page 126

Advertising
background image

Upgrading compiled objects with dbcc upgrade_object

110

Adaptive Server Enterprise

Compiled objects for which the source text was hidden using

sp_hidetext

are

upgraded in the same manner as objects for which the source text is not hidden.
For information on

sp_hidetext

, see the Reference Manual:Procedures.

Note

If you are upgrading from 32-bit installations to use a 64-bit Adaptive

Server, the size of each 64-bit compiled object in the

sysprocedures

table in

each database increases by approximately 55 percent when the object is
upgraded. The pre-upgrade process calculates the exact size. Increase your
upgraded database size accordingly.

To ensure that compiled objects have been upgraded successfully before they
are invoked, you can upgrade them manually using the

dbcc upgrade_object

command. For details, see “Finding compiled object errors before production”
on page 110.

Finding compiled object errors before production

Changes made in earlier versions of Adaptive Server may cause compiled
objects to work differently in version 12.5.x and later. You can use

dbcc

upgrade_object

to find the following errors and potential problem areas that

may require manual changes to achieve the correct behavior:

Reserved word errors

Missing, truncated, or corrupted source text

Quoted identifier errors

Temporary table references

select * potential problem areas

After reviewing the errors and potential problem areas, and fixing those that
need to be changed, you can use

dbcc upgrade_object

to upgrade compiled

objects manually instead of waiting for the server to upgrade the objects
automatically. For details, see “Using dbcc upgrade_object” on page 113.

Advertising