Sybase Adaptive Server Enterprise 15.0.2 Installation Manual page 125

Reserved word errors
Missing, truncated, or corrupted source text
Quoted identifier errors
Installation Guide
After reviewing the errors and potential problem areas, and fixing those that
need to be changed, you can use
objects manually instead of waiting for the server to upgrade the objects
automatically. For details, see "Using dbcc upgrade_object" on page 113.
If
dbcc upgrade_object
compiled object, it returns an error, and that object is not upgraded. To fix the
error, either manually change the object name or use quotes around the object
name, and issue the command
the compiled object.
For example, suppose you load a database dump from Adaptive Server 11.5
into Adaptive Server 15.0 and the dump contains a stored procedure that uses
the word "lock." When you run
the command returns an error because, although "lock" was not reserved in
version 11.5, it became a reserved word in version 11.9.2. With this advance
notice, you can change the stored procedure and any related tables before they
are used in a production environment.
If the source text in
syscomments
corrupted,
dbcc upgrade_object
not hidden, you can use
text. If truncation or other corruption has occurred, drop and re-create the
compiled object.
returns a quoted identifier error if:
dbcc upgrade_object
• The compiled object was created in a pre-11.9.2 version with quoted
identifiers active (
• Quoted identifiers are not active (
session.
To avoid this error, activate quoted identifiers before running
. When quoted identifiers are active, you must use single quotes
upgrade_object
instead of double quotes around quoted
dbcc upgrade_object
finds a reserved word used as an object name in a
set quoted identifiers on
dbcc upgrade_object
was deleted, truncated, or otherwise
may report syntax errors. If the source text was
to verify the completeness of the source
sp_helptext
set quoted identifiers on
set quoted identifiers off
dbcc upgrade_object
CHAPTER 7 Troubleshooting
to upgrade compiled
. Then drop and re-create
on that stored procedure,
).
) in the current
dbcc
keywords.
111