Sybase 11 9 X 12 5 Users Manual Svrtsg3

11.9.x-12.5 to the manual dd2798e9-0b5e-4118-adc4-f4726b2f3afb

2015-02-02

: Sybase Sybase-11-9-X-12-5-Users-Manual-490623 sybase-11-9-x-12-5-users-manual-490623 sybase pdf

Open the PDF directly: View PDF PDF.
Page Count: 588 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Sybase® Adaptive ServerTM
Enterprise Troubleshooting and
Error Messages Guide
Volume 3
Sybase Adaptive Server Enterprise
11.9.x-12.5
DOCUMENT ID: 39994-01-1250-01
LAST REVISED: May 2002
Copyright © 1989-2002 by Sybase, Inc. All rights reserved.
This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes.
Information in this document is subject to change without notice. The software described herein is furnished under a license agreement,
and it may be used or copied only in accordance with the terms of that agreement.
To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845.
Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other
international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled
software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic,
mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc.
Sybase, the Sybase logo, AccelaTrade, ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture,
Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server
Enterprise Replication, Adaptive Server Everywhere, Adaptive Server IQ, Adaptive Warehouse, Anywhere Studio, Application
Manager, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute, APT-FORMS, APT-Translator, APT-Library, Backup
Server, BizTracker, ClearConnect, Client-Library, Client Services, Convoy/DM, Copernicus, Data Pipeline, Data Workbench,
DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DB-Library, dbQueue, Developers Workbench, Direct
Connect Anywhere, DirectConnect, Distribution Director, e-ADK, E-Anywhere, e-Biz Integrator, E-Whatever, EC-GATEWAY,
ECMAP, ECRTP, eFulfillment Accelerator, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/Server, Enterprise
Connect, Enterprise Data Studio, Enterprise Manager, Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work
Designer, Enterprise Work Modeler, eProcurement Accelerator, EWA, Financial Fusion, Financial Fusion Server, Gateway Manager,
ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect,
InternetBuilder, iScript, Jaguar CTS, jConnect for JDBC, MainframeConnect, Maintenance Express, MDI Access Server, MDI Database
Gateway, media.splash, MetaWorks, MySupport, Net-Gateway, Net-Library, New Era of Networks, ObjectConnect, ObjectCycle,
OmniConnect, OmniSQL Access Module, OmniSQL Toolkit, Open Biz, Open Client, Open ClientConnect, Open Client/Server, Open
Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, PB-Gen, PC APT Execute, PC
Net Library, Power++, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner,
PowerDimensions, PowerDynamo, PowerJ, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips,
Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, Rapport, Report Workbench,
Report-Execute, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, Resource
Manager, RW-DisplayLib, S-Designor, SDF, Secure SQL Server, Secure SQL Toolset, Security Guardian, SKILS, smart.partners,
smart.parts, smart.script, SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL
Edit/TPU, SQL Everywhere, SQL Modeler, SQL Remote, SQL Server, SQL Server Manager, SQL SMART, SQL Toolset, SQL Server/
CFT, SQL Server/DBM, SQL Server SNMP SubAgent, SQL Station, SQLJ, STEP, SupportNow, S.W.I.F.T. Message Format Libraries,
Sybase Central, Sybase Client/Server Interfaces, Sybase Financial Server, Sybase Gateways, Sybase MPP, Sybase SQL Desktop, Sybase
SQL Lifecycle, Sybase SQL Workgroup, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SyBooks, System 10,
System 11, System XI (logo), SystemTools, Tabular Data Stream, TradeForce, Transact-SQL, Translation Toolkit, UNIBOM, Unilib,
Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, Viewer, Visual Components, VisualSpeller, VisualWriter, VQL,
WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server,
Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server and XP Server are
trademarks of Sybase, Inc. 04/02
Unicode and the Unicode Logo are registered trademarks of Unicode, Inc.
All other company and product names used herein may be trademarks or registered trademarks of their respective companies.
Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-
7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.
Sybase, Inc., 5000 Hacienda Drive, Dublin, CA 94568.
Contents
iii
About This Book .......................................................................................................................... vii
CHAPTER 4 Backup Server Error Messages................................................. 683
Commonly Encountered Errors.................................................... 683
“No language handler installed” Message............................. 683
LOGCONN Errors in Adaptive Server After Using Backup Server
684
load {database | transaction} with listonly Locks Database.. 684
Some Messages from Backup Server Are Lost .................... 684
dump database on Digital OpenVMS Alpha/Digital UNIX Raises
Error................................................................................ 684
Error 5704 in the OpenVMS Backup Server error log ........... 685
Unable to use Async IO when dumping to disk on HP-UX.... 686
Maximum Number of DBPROCESSes Already Allocated..... 687
Error Conditions Without Messages............................................. 687
Errors in Backup Server Error Log ............................................... 688
Net-Library routine net_dict_open failed in srv__open_dictionary
688
Net-Library routine net_listen failed in srv_start_net ............ 688
Net-Library routine net_init failed in srv__init_net ................ 688
No driver of the requested protocol class is available ........... 689
Net-lib protocol driver call to connect two endpoints failed ... 689
Open Server Error Messages Related to Backup Server............. 689
Error 5704.10.0 ..................................................................... 689
Error 16240.20.0 ................................................................... 690
A Listing of All Backup Server Error Messages............................ 690
Error Number Format ............................................................ 690
List of Error Messages .......................................................... 691
Backup Server Error Messages 1.1.2 - 1.63.2 ............................ 692
Backup Server Error Messages 2.1.2 - 3.55.2 ............................. 702
Backup Server Error Messages 4.1.2 - 4.75.3 ............................. 712
Backup Server Error Messages 4.76.3 - 4.147.2 ......................... 721
Backup Server Error Messages 5.1.2 - 6.89.2 ............................. 732
Backup Server Error Messages 7.1.2 - 8.17.2 ............................. 740
Contents
iv
CHAPTER 5 Component Integration Services Error Messages ................... 745
Component Integration Services Error Messages ...................... 745
CHAPTER 6 Adaptive Server Error Messages ............................................... 755
Working with Error Messages ...................................................... 755
Server Error Messages 1 - 199 .................................................... 757
Server Error Messages 200 - 299 ................................................ 765
Server Error Messages 300 - 399 ................................................ 773
Server Error Messages 400 - 499 ................................................ 776
Server Error Messages 500 - 599 ................................................ 780
Server Error Messages 600 - 699 ................................................ 789
Server Error Messages 700 - 799 ................................................ 797
Server Error Messages 800 - 899 ................................................ 799
Server Error Messages 900 - 999 ................................................ 807
Server Error Messages 1000-1099 .............................................. 813
Server Error Messages 1100-1199 .............................................. 816
Server Error Messages 1200-1299 .............................................. 821
Server Error Messages 1300-1399 .............................................. 828
Server Error Messages 1500-1599 .............................................. 830
Server Error Messages 1600-1699 .............................................. 839
Server Error Messages 1700-1799 .............................................. 841
Server Error Messages 1800-1899 .............................................. 848
Server Error Messages 1900-1999 .............................................. 851
Server Error Messages 2000–2099 ............................................. 855
Server Error Messages 2100–2199 ............................................. 856
Server Error Messages 2200–2299 ............................................. 857
Server Error Messages 2300–2399 ............................................. 864
Server Error Messages 2400–2499 ............................................. 871
Server Error Messages 2500–2599 ............................................. 874
Server Error Messages 2600–2699 ............................................. 883
Server Error Messages 2700–2799 ............................................. 885
Server Error Messages 2800–2899 ............................................. 892
Server Error Messages 2900–2999 ............................................. 896
Server Error Messages 3000 - 3099 ............................................ 897
Server Error Messages 3100 - 3199 ............................................ 898
Server Error Messages 3200 - 3299 ............................................ 902
Server Error Messages 3300 - 3399 ............................................ 907
Server Error Messages 3400 - 3499 ............................................ 909
Server Error Messages 3500 - 3599 ............................................ 918
Server Error Messages 3600 - 3699 ............................................ 918
Server Error Messages 3700 - 3799 ............................................ 921
Server Error Messages 3800 - 3899 ............................................ 924
Server Error Messages 3900 – 3999 ........................................... 926
Server Error Messages 4000 – 4099 ........................................... 931
Contents
v
Server Error Messages 4200 - 4299 ............................................ 935
Server Error Messages 4300 - 4399 ............................................ 938
Server Error Messages 4400 - 4499 ............................................ 941
Server Error Messages 4500 - 4599 ............................................ 943
Server Error Messages 4600 - 4699 ............................................ 944
Server Error Messages 4700 - 4799 ............................................ 948
Server Error Messages 4800 - 4899 ............................................ 949
Server Error Messages 4900 - 4999 ............................................ 953
Server Error Messages 5000 - 5099 ............................................ 962
Server Error Messages 5100 - 5199 ............................................ 965
Server Error Messages 5200 - 5299 ............................................ 971
Server Error Messages 5600 - 5699 ............................................ 972
Server Error Messages 5700 - 5799 ............................................ 976
Server Error Messages 5800 - 5899 ............................................ 977
Server Error Messages 5900 - 5999 ............................................ 985
Server Error Messages 6000 - 6099 ............................................ 986
Server Error Messages 6100 - 6199 ............................................ 987
Server Error Messages 6200 - 6299 ............................................ 988
Server Error Messages 6400 - 6499 ............................................ 995
Server Error Messages 6500 - 6599 ............................................ 996
Server Error Messages 6700 - 6799 ............................................ 999
Server Error Messages 6900 - 6999 .......................................... 1000
Server Error Messages 7000 - 7099 .......................................... 1002
Server Error Messages 7100 - 7199 .......................................... 1004
Server Error Messages 7200 - 7299 .......................................... 1008
Server Error Messages 7300 - 7399 .......................................... 1012
Server Error Messages 7400 - 7499 .......................................... 1020
Server Error Messages 7600 - 7699 .......................................... 1023
Server Error Messages 7700 - 7799 .......................................... 1026
Server Error Messages 7900 - 7999 .......................................... 1035
Server Error Messages 8000 - 8099 .......................................... 1046
Server Error Messages 8200 - 8299 .......................................... 1047
Server Error Messages 8400 - 8499 .......................................... 1050
Server Error Messages 8500 - 8599 .......................................... 1053
Server Error Messages 8600 - 8699 .......................................... 1054
Server Error Messages 8700 - 8799 .......................................... 1055
Server Error Messages 8800 - 8899 .......................................... 1055
Server Error Messages 8900 - 8999 .......................................... 1056
Server Error Messages 9000 - 9099 .......................................... 1057
Server Error Messages 9100 - 9199 .......................................... 1058
Server Error Messages 9200 - 9299 .......................................... 1063
Server Error Messages 9300 - 9399 .......................................... 1070
Server Error Messages 9500 – 9599 ......................................... 1074
Server Error Messages 9600 - 9699 .......................................... 1080
Contents
vi
Server Error Messages 9700 - 9799 .......................................... 1080
Server Error Messages 9800 - 9899 .......................................... 1083
Server Error Messages 9900 - 9999 .......................................... 1085
Server Error Messages 10100 - 10199 ...................................... 1095
Server Error Messages 10200 - 10299 ...................................... 1096
Server Error Messages 10300 - 10399 ...................................... 1100
Server Error Messages 10400 - 10499 ...................................... 1107
Server Error Messages 10500 - 10599 ...................................... 1116
Server Error Messages 10600 - 10699 ...................................... 1117
Server Error Messages 10700 - 10799 ...................................... 1127
Server Error Messages 10800 - 10899 ...................................... 1135
Server Error Messages 10900 - 10999 ...................................... 1140
Server Error Messages 11000 - 11099 ...................................... 1141
Server Error Messages 11100 - 11199 ...................................... 1146
Server Error Messages 11200 - 11299 ...................................... 1153
Server Error Messages 11300 - 11399 ...................................... 1153
Server Error Messages 11400 - 11499 ...................................... 1155
Server Error Messages 11500 - 11599 ...................................... 1163
Server Error Messages 11600 - 11699 ...................................... 1168
Server Error Messages 11700 - 11799 ...................................... 1169
Server Error Messages 11900 - 11999 ...................................... 1173
Server Error Messages 12000 - 12099 ...................................... 1176
Server Error Messages 12100 - 12199 ...................................... 1179
Server Error Messages 12200 - 12299 ...................................... 1180
Server Error Messages 12300 - 12399 ...................................... 1181
Server Error Messages 12400 - 12499 ...................................... 1184
Server Error Messages 12500 - 12599 ...................................... 1184
Server Error Messages 12700 - 12799 ...................................... 1189
Server Error Messages 12800 - 12899 ...................................... 1197
Server Error Messages 12900 - 12999 ...................................... 1199
Server Error Messages 13000 - 13099 ...................................... 1205
Server Error Messages 13100 - 13199 ...................................... 1213
Server Error Messages 13200 - 13299 ...................................... 1216
Server Error Messages 13900 - 13999 ...................................... 1217
Server Error Messages 14000 - 14099 ...................................... 1222
Server Error Messages 14100 - 14199 ...................................... 1225
Server Error Messages 14200 - 14299 ...................................... 1226
Server Error Messages 14300 - 14399 ...................................... 1228
Server Error Messages 14400 - 14499 ...................................... 1229
Server Error Messages 17000 - 18999 ...................................... 1229
Glossary ................................................................................................................................... 1231
Index ......................................................................................................................................... 1235
vii
About This Book
The Sybase Adaptive Server Enterprise Troubleshooting and Error
Messages Guide is a three-volume set. The first volume contains
guidelines for system database recovery and other troubleshooting
procedures. The second volume contains detailed error message
descriptions. This third volume includes the text of all Component
Integration Services, Backup Server, and Adaptive Server error messages,
along with a glossary and index.
For information about the intended audience of this guide, related
documents, other sources of information, conventions used in this manual,
and how to obtain help, please refer to “About This Book” in Volume 1.
viii
683
CHAPTER 4 Backup Server Error Messages
This chapter discusses Backup Server errors and Open Server errors
related to Backup Server, including:
• “Commonly Encountered Errors”
• “Error Conditions Without Messages”
• “Errors in Backup Server Error Log”
• “Open Server Error Messages Related to Backup Server”
• “A Listing of All Backup Server Error Messages”
Commonly Encountered Errors
Following are descriptions of some problems that commonly occur when
you use Backup Server.
“No language handler installed” Message
If you connect directly to the Backup Server with isql and attempt to issue
a command, you will get messages like the following:
1> dump database master to tapedump1
2> go
No language handler installed.
Language cmd: dump database master to tapedump1
This is expected behavior because Backup Server is not a stand-alone
Adaptive Server. It is an Open Server application, is not intended to accept
direct commands, and, therefore, has no way of parsing them. All
commands to the Backup Server, such as shutdown or dump and load, can
be issued only from a running Adaptive Server.
Commonly Encountered Errors
684
LOGCONN Errors in Adaptive Server After Using Backup Server
The Adaptive Server site handler reports this error when the server has
unexpectedly lost contact with another site. If the other site is a Backup Server,
then a dump or load session has prematurely completed. This error message
appears in the Adaptive Server error log:
site_hdlr: No LOGCONN for packet from site 1, channel 2
When the error is reported because a dump or load session was aborted by a
user interrupt (such as Ctrl-c), the message should be treated as an
informational message.
This error can also be reported if the Adaptive Server unexpectedly loses
contact with the Backup Server. In this case, the error should be investigated.
load {database | transaction} with listonly Locks Database
A database being loaded into is locked so that no other users can use it, even
though no actual data may be loaded, as in the case of a load with listonly. To
work around load with listonly locking an active database, create a dummy
database and do the load with listonly into that database instead of the database
you do not want to have locked.
Some Messages from Backup Server Are Lost
Messages initiated by a threshold procedure may be lost if the boot window is
not present. Adaptive Server has no mechanism for intercepting a Tabular Data
Stream (TDS) received from other servers; the TDS is merely passed on to the
client. Threshold procedures have no “client,” so messages from Backup
Server to these tasks will not appear unless you specify otherwise.
You must specify notify=operator_console if the dump is invoked by a stored
procedure, including sp_thresholdaction; this is an issue for volume change
prompts, for example, to which you cannot respond if you never see them.
dump database on Digital OpenVMS Alpha/Digital UNIX Raises
Error
Attempting to use dump database when your database devices are on raw
partitions (DEC HSC [mscp] devices) raises the following error:
CHAPTER 4 Backup Server Error Messages
685
Backup Server: 4.80.2.1: Server, device /dev/44a0e: You
must use the no-rewind-on-close tape device.
This is not a raw device problem in general, but a DEC HSC (mscp) device
issue. Digital UNIX has a known problem on its HSC device driver that causes
Backup Server to fail to identify the HSC device type. Digitals's CLD #00266
states that such devices return 0 when queried with “MTIOCGET ioctl.”
Warning! Sybase currently supports only SCSI devices on Digital UNIX.
Error 5704 in the OpenVMS Backup Server error log
Error 5704: "Changed client character set setting to '%.*s'” appears in the
System 11 Backup Server error log on OpenVMS, even when the character sets
and language of the Backup Server and the Adaptive Server appear the same.
The errors are written every time a dump or load command is issued. Logging
in to the Backup Server and immediately exiting generates this error as well.
The Adaptive Server error log reports the following:
00:97/02/14 15:40:50.59 server SQL Server's default sort order is:
00:97/02/14 15:40:50.69 server 'bin_iso_1' (ID = 50)
00:97/02/14 15:40:50.79 server on top of default character set:
00:97/02/14 15:40:50.89 server 'iso_1' (ID = 1).
The runserver file for the Backup Server appears as follows:
$ define sybase_system DISK$TECH_SUPPORT:[REL1002.]
$ define sybase sybase_system:[sybase]
$ backup_server:==$DISK$TECH_SUPPORT:[REL1002.SYBASE.bin]backup-server.exe
$ backup_server /SERVER_NAME="BCK_RAPIDF" -
/ERRORLOG=DISK$TECH_SUPPORT:[REL1002.SYBASE.install]log.BCK_RAPIDF -
/INTERFACES_FILE=DISK$TECH_SUPPORT:[REL1002.SYBASE]interfaces.-
/LANGUAGE=us_english -
/CHARACTER_SET=iso_1
Even though the character sets for the Backup Server and the Adaptive Server
appear to be identical, they are not so to the backupserver.exe program.
OpenVMS DCL Command Language Interpreter converts command string
tokens, except the strings enclosed in double quotes, to uppercase before
returning the parsed commands to the calling programs.
Consequently, to log into the Adaptive Server you must specify your user name
in quotes as in the following command:
Commonly Encountered Errors
686
isql/user_name="sa".
Similarly, the strings 'us_english' and 'iso_1' seen above in single quotes are
converted to uppercase. This causes backupserver.exe to interpret these strings
in an unexpected manner.
Note The runserver file is created in this manner by the sybinit.exe program.
To correct this problem, edit the Backup Server runserver file, enclosing the
two strings in double quotes as follows:
/LANGUAGE="us_english" -
/CHARACTER_SET="iso_1"
Unable to use Async IO when dumping to disk on HP-UX
When trying to dump a database to disk on HP the following error occurs:
Backup Server 4.86.2.1: Unable to use Async IO on
the database device 'disk device specified'.
Backup Server must use Async IO on a block special devices
because SQL Server is doing the same. Refer to the server
release notes.
Backup Server 4.27.2.1: Volume validation error:
attempt to close 'disk device specified' returned Bad file number.
This error occurs even though Async IO is configured correctly. It occurs
because of a problem in locking shared memory.
Adaptive Server, when using Async IO on HP, needs to lock its shared memory
into physical memory so that processing an Async IO request will never have
to wait for memory areas to be moved from swapspace to physical memory.
As the above error message says, Backup Server needs to do the same.
However it cannot do so because there is not enough lockable physical memory
left for the Backup Server.
On HP, lockable physical memory defaults to 75% of physical memory, not
75% of total shared memory.
To correct this problem try these options:
• Increase physical memory.
• Decrease the memory parameter for the Adaptive Server.
CHAPTER 4 Backup Server Error Messages
687
• Change the HP-UX kernel parameter UNLOCKABLE_MEM. By default,
this is 0 which signifies the aforementioned 75% - 25% ratio. Consult HP
technical support before changing this parameter.
Maximum Number of DBPROCESSes Already Allocated
Two scenarios could result in this error. They are summarized in the following
table:
Error Conditions Without Messages
A programming error may occur that causes the Backup Server to hang without
issuing a message. Follow these steps:
• Determine whether the entire Adaptive Server is hung or just a single
session.
• Terminate the hung session with keyboard interrupt or quit.
At this point, on a UNIX machine, it is necessary to check for I/O subprocesses
that remain alive, holding open dump devices. Perform this check with the ps
command and use kill (default signal) to kill the sybmultbuf processes whose
command lines contain device names used by the terminated session. Be
careful to kill only those processes that use the devices involved.
Each device is controlled by a pair of processes, and each pair of processes
controls just one device. Therefore, the presence of a device name in a
command line is sufficient to identify the subprocess to kill. dump and load data
from an aborted session or Server are not usable.
The Backup Server can exit abnormally without killing its subprocesses. In this
case, use kill to clean up the sybmultbuf processes before restarting the Backup
Server; otherwise, the devices involved may not be usable.
Scenario Action
The Backup Server runserver file, the interfaces file,
and the sysservers table in the master database do not
have a consistent name for the Backup Server.
Verify that all three locations contain the same Backup
Server name. Pay attention to case sensitivity.
You have hit a network limit for the Backup Server
process. Typically, this limit is set to 25.
Start Backup Server with the -Nnn flag to change the
network limit. For example, -N30 increases the limit to
30.
Errors in Backup Server Error Log
688
Errors in Backup Server Error Log
The following error messages may appear in the Backup Server error log.
Net-Library routine net_dict_open failed in srv__open_dictionary
Net-library routine net_dict_open() failed in
srv__open_dictionary()
Network error: status = 11 - Could not find addressing dictionary.
No server log file open; Using stderr for log.
The interfaces file does not exist or cannot be opened. Check to be sure the file
exists and the permissions are set correctly.
Net-Library routine net_listen failed in srv_start_net
Net-Library routine net_listen() failed in srv__start_net.
Network error: status = 12 - Net-lib protocol driver call to
register a listener failed
This is the Open Server equivalent of “Network port already in use.”
If your system is Digital OpenVMS using DECnet:
• The SYSNAM privilege is required to start a DECnet listener, just as with
Adaptive Server. Check to be sure this privilege is set appropriately.
• If this fails to help, try using DECnet object names instead of object
numbers. If this works, then report to Sybase Technical Support that you
have encountered bug 51237.
Net-Library routine net_init failed in srv__init_net
Net-Library routine net_init() failed in srv__init_net()
Network error: status = 162 - Unable to determine Net-Library error.
No server log file open; Using stderr for log.
Localization information is not as expected, possibly the result of loading an
incompatible Sybase product release into the same $SYBASE directory as the
Backup Server. Be sure the entire release directory is up to date and that you
have not accidentally renamed or deleted localization files.
CHAPTER 4 Backup Server Error Messages
689
No driver of the requested protocol class is available
No driver of the requested protocol class is available.
This message indicates that the entry in the interfaces file for the requested
Backup Server is wrong. Refer to the System Administration Guide Supplement
for your platform to find out the correct interfaces file entries.
Net-lib protocol driver call to connect two endpoints failed
Net-lib protocol driver call to connect two endpoints
failed.
An error occurred while trying to connect to the specified Backup Server. Make
sure the device name in the interfaces file is correct and that the Adaptive
Server's network address is correct in the interfaces file.
Open Server Error Messages Related to Backup Server
Following are some Open Server error messages that can appear when you are
using Backup Server.
Error 5704.10.0
Open Server Error: 5704.10.0: Changed client character set
setting to 'cp850'
Open Server Session Fatal Error: 16227.15.0: Unknown token TDS stream
received by spid 5
This message can appear if a user, who succeeds in executing a local dump
database, tries to dump to a remote Backup Server.
Check your default character set. If the default character sets for the remote
Backup Server and Adaptive Server are different, change the Backup Server's
default character set, restart the Backup Server, and rerun the dump.
A Listing of All Backup Server Error Messages
690
Error 16240.20.0
Many error conditions are associated with this Open Server error, differentiated
by the accompanying messages. The following errors begin with the phrase
“Open Server Fatal Error 16240.20.0”:
Net-Library routine net_address_get() failed in srv__start_net
Network error: status = 12 - Specified server name attribute could not be found
Backup Server: 1.29.2.1: Unable to start the Backup Server.
See Backup Server error log for additional information.
This is the Open Server equivalent of “Server name not found in interfaces
file.” The Backup Server will not start. Check to be sure the name of the server
you are trying to start is in the interfaces file, and remember that server names
are case-sensitive.
SYB_BACKUP is the logical name of the Backup Server. It may also be the
physical name, but it need not be.
Under normal circumstances, sybinit sets up the Backup Server, but if your
Backup Server name has been edited or deleted from the interfaces file, add it
again with sp_addserver, as follows:
1> sp_addserver SYB_BACKUP, NULL, physical-name
2> go
The specified physical-name is the name to use, both in the interfaces file and
when you do a dump or load with the at option.
A Listing of All Backup Server Error Messages
This section lists the text and gives a brief explanation for Backup Server
errors.
Error Number Format
A Backup Server error number has four components:
major.minor.severity.state
major numbers map to functional areas as follows:
Major
Number
Description
CHAPTER 4 Backup Server Error Messages
691
minor numbers order the errors within a major category. There is no special
meaning to these numbers; they serve only to distinguish between errors.
severity codes are as follows:
state codes have a one-to-one mapping to instances of the error reported within
the code.
List of Error Messages
Note Any “shortage of memory” message may indicate that both swap and
physical memory are in short supply. Increasing either may avert this error.
Make sure that you have enough physical memory so that Adaptive Server and
Backup Server can run without being swapped.
1 Critical errors
2 Open Server event errors
3 Backup Server RPC API errors
4 I/O service layer errors (that is, operating system I/O calls)
5 Network data transfer errors
6 Archive volume manipulation errors
7 Parser errors (errors in the dump or load command options)
8 Tape auto configuration errors
Severity Code Description
0 Internal informational message, usually a component of another message.
No user action necessary.
1 Information, no user action necessary.
2,3 An unexpected condition, possibly fatal to the session, has occurred. Error
may have occurred with any or all of usage, environment, or internal logic.
This severity consists of two levels, which indicate whether or not the
session must exit. 2 indicates the session must exit. 3 indicates the session
may or may not exit.
4 An unexpected condition, fatal to the execution of the Backup Server, has
occurred. The session must exit immediately.
Backup Server Error Messages 1.1.2 - 1.63.2
692
Backup Server Error Messages 1.1.2 - 1.63.2
Number Severity Text and Explanation
1.1.2 2 Memory allocation failed in %1! for a %2! allocation.
This DUMP or LOAD session must exit.
Explanation: Indicates shortage of virtual memory
on the machine running Backup Server. User should
terminate unnecessary processes.
1.2.0 0 WAIT
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.3.0 0 NOWAIT
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.4.0 0 PROCEED
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.5.4 4 Failed to install CS-Library message callback routine.
Explanation: Backup Server's attempt to install an
event handler failed. Backup Server cannot run.
1.6.0 0 RETRY
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.7.1 1 Cannot allocate the locale info of the task. Use the
Backup Server default language `%1!' instead.
Explanation: The local structure for the client
connection to Backup Server could not be allocated,
and the thread property for the local information could
not be captured. Refer to the Backup Server error log
for more information.
1.8.0 0 ABORT
Explanation: This informational text may be a
component of another message. No action is
necessary.
CHAPTER 4 Backup Server Error Messages
693
1.9.0 0 Backup Server
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.10.0 0 DUMP
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.11.0 0 LOAD
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.12.0 0 volume
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.13.0 0 OPERATOR
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.14.2 2 Unrecoverable I/O or volume error. This DUMP or
LOAD session must exit.
Explanation: This message is usually preceded by a
more specific message describing a fault encountered
in the lower I/O layers. One exception: this message is
the only error indication when the Backup Server fails
to start the multi-buffering subprocess that it uses to
perform backup I/O.Reasons for this failure are the
non-existence of the sybmultbuf program in the
standard locations (-M option argument, Backup
Server's current directory or $SYBASE/bin). User
should check the installation. If the sybmultbuf
program can be installed in the current directory or
$SYBASE/bin, it is not necessary to restart the Backup
Server.
1.15.4 4 UNRECOVERABLE CONDITION: ALL SESSIONS
WILL TERMINATE ABNORMALLY. THE
BACKUP SERVER MUST EXIT.
Explanation: This message is preceded by other
messages describing the failure.
Number Severity Text and Explanation
Backup Server Error Messages 1.1.2 - 1.63.2
694
1.16.2 2 Error (major = %1!, minor = %2!) raised with
unknown severity %3!.n
Explanation: Indicates a programming bug in an
instance of error reporting.
1.17.2 2 Major = %1!, Minor = %2!, Severity = %3!, state =
%4!: error text is missing.
Explanation: Indicates that localization files are out-
of-date with the code. Check installation with Sybase
Technical Support.
1.18.1 1 WARNING: Requested %1! file descriptors, was
allocated %2!; Backup Server will run out of file
descriptors if this number is less than the number of
database devices plus twice the number of stripes in
concurrent use.
Explanation: The Backup Server attempts to obtain
the highest number of file descriptors allowed to a user
program. This message indicates that the Backup
Server found a lower quota. Concurrent activity must
be restricted as directed or the platform administrator
can increase the HDESLIM.
1.19.4 4 Cannot allocate the configuration structure
Explanation: Indicates either a basic Open Server
failure or an extreme shortage of memory and swap
space.
1.20.4 4 CS_CONTEXT allocation failed.
Explanation: The context allocation routine failed
when it tried to load localization files. The SYBASE
environment variable is set incorrectly or the
localization files are missing.
1.21.2 2 Unable to configure the maximum number of user
events to %1!.
Explanation: An error occurred when you tried to
configure the Open Server's run-time maximum
number of application-specific defined event types.
Refer to the Open Server Server-Library Reference
Manual for an explanation of events. Refer to the
Backup Server error log for more information, and
contact Sybase Technical Support.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
695
1.22.2 2 Unable to configure the maximum number of
SRV_PROCS to %1!.
Explanation: An attempt to configure the Open
Server run-time values to allow the specified number
of Server threads failed. Backup Server uses one
thread per dump or load connection plus an additional
thread for each stripe. Use the -P option to increase the
number of threads.
1.23.2 2 Unable to configure the maximum number of network
read buffers to %1!.
Explanation: An attempt to configure the Open
Server run-time values to allow the specified number
of network read buffers failed. These buffers are used
for Server to Server connections, and the configuration
value is hard coded to 10.
1.24.2 2 Unable to configure the maximum number of
connections to %1!.
Explanation: Attempt to configure the Open Server
run-time values to allow the specified number of
network connections failed. The value of the -C option
(/connections in Digital OpenVMS) to the
backupserver command is used for the configurable
value. Check the line in your RUN_servername file
and see the entry for backupserver in Adaptive
Server Utility Programs for your platform.
1.25.1 1 Logging Backup Server messages in file `%1!'\n
Explanation: Indicates that Backup Server messages
are being written to the file named.
1.26.1 1 Unable to open Backup Server message log file `%1!'\n
Explanation: Check the path to the message log file.
Make sure that the SYBASE environment variable is
set correctly.
1.27.1 1 Operating system swap space is low. The operating
system may kill the Backup Server.
Explanation: This is an RS6000 error only. The
operating system will kill “random” processes in an
effort to free space for critical processes. This message
indicates that the Backup Server could be chosen. If
necessary, reconfigure the Backup Server process as
critical.
Number Severity Text and Explanation
Backup Server Error Messages 1.1.2 - 1.63.2
696
1.28.2 2 Open Server routine %1! failed. See Backup Server
error log for additional information. \n
Explanation: Internal error, contact Sybase
Technical Support. This is a catch-all message for any
Open Server function that raises an error for which
Backup Server has determined the affected routine but
not the exact error.
1.29.2 2 Unable to start the Backup Server. See Backup Server
error log for additional information. \n
Explanation: At Backup Server initialization time,
the attempt to put Backup Server into a state in which
it can run failed. Refer to any Open Server messages
that are displayed.
1.30.2 2 Backup Server encountered error freeing memory.\n
Explanation: Internal error, contact Sybase
Technical Support. An error occurred when an attempt
was made to free a block of memory from Backup
Server's run-time heap. Either the memory was
previously freed or there is another error in the Open
Server routines for freeing memory. Check the Backup
Server error log for any Open Server messages
pertinent to this problem.
1.31.2 2 Unable to configure the maximum number of network
connections to %1!. The number of network
dump/load stripes that the Backup Server can run
simultaneously is %2!.
Explanation: Attempt to set the maximum number of
network connections (DBPROCESSes) that the Server
can originate failed. Refer to the usage of the -N
command line option. It may be too large for DB-
Library to handle.
1.32.2 2 Unexpected failure in `cs_strcmp()' routine.
Explanation: Internal error, contact Sybase
Technical Support. An error occurred when comparing
two strings to see if they are equal, greater than, or less
than each other. The cause of the error could be an
illegal string in length or content or that the character
sets of the two strings are incompatible for
comparison.
1.33.0 0 Backup Server Internal Error
Explanation: This informational text may be a
component of another message.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
697
1.34.1 1 Unable to set one or more trace flags; continuing.
Explanation: Attempt to set the Open Server run-
time trace flags failed. Check to see that the trace flags
are valid and in the proper format.
1.35.0 0 <new_volume_name>
Explanation: This informational text may be a
component of another message. No action is
necessary.
1.36.1 1 Unable to configure Async IO. If Adaptive Server is
using Async IO on block special devices, then dump
and loads may be inconsistent. Refer to the server
release notes.
Explanation: HP only: could not initialize and
configure the asynchronous I/O system to be used
when accessing database devices. Check the Backup
Server error log and contact Sybase Technical Support.
1.37.4 4 Could not allocate event flag, server %1!: code %2!
message %3!.
Explanation: This is an Digital OpenVMS error only.
An attempt to allocate an event flag failed. Backup
Server cannot start. Probably an internal error.
1.38.4 4 Could not get master lock on server name, server %1!:
code %2! message %3!.
Explanation: Digital OpenVMS only: an attempt to
obtain a lock identifying this as the “master” Backup
Server failed for the reason specified in %3!. Backup
Server cannot start.
1.39.4 4 This backup server is unnamed, and so cannot acquire
the master lock it needs to boot successfully. Backup
Server must shut down.
Explanation: Digital OpenVMS only: no Server
name was given when attempting to acquire an
exclusive lock on the master lock name, which is
constructed from the Server name. Use showserver to
check whether Backup Server was started with a
Server name by means of the /SERVER_NAME
qualifier or the translation of the DSLISTEN logical
name.
Number Severity Text and Explanation
Backup Server Error Messages 1.1.2 - 1.63.2
698
1.41.4 4 A server named %1! is already running. Could not
obtain stop-lock.
Explanation: Digital OpenVMS only: another
Backup Server with the same logical name is already
running. This Backup Server cannot start.
1.42.4 4 STOP semaphore failed, code %1! message %2!.
Explanation: Digital OpenVMS only: failed to queue
the lock required to shut down Backup Server via
stopserver. Backup Server cannot start.
1.43.4 4 Failed getting system information: sys$getsyi failed,
code %1! message %2!.
Explanation: An unexpected condition, fatal to the
execution of the Backup Server, has occurred. The
session must exit immediately.
1.44.1 1 Backup Server could not set the server language to
`%1!'. The specified language may not be a valid
language, or the language may not be installed under
$SYBASE/locales. The default language is in use.
Explanation: Attempt to set the Backup Server's
language failed. Refer to the Backup Server error log
for more information. The specified language may not
be a valid language, or the language may not be
installed under $SYBASE/locales.
1.45.1 1 Backup Server could not set the server character set to
`%1!'. The specified character set may not be a valid
character set, or the character set may not be installed
under $SYBASE/locales. The default character set is
in use.
Explanation: Attempt to set the Backup Server's
character set failed. Refer to the Backup Server error
log for more information. The specified character set
may not be a valid character set or the character set
may not be installed under $SYBASE.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
699
1.46.1 1 CSLIB routine %1! failed. See Backup Server error
log for additional information.
Explanation: This is the catch-all message for CS-
Library (Client/Server Library) functions that return
an error. Currently, the only reference to this error
occurs when Backup Server is attempting to configure
the localization properties of the process. Refer to the
Backup Server error log for more information. There
could be something wrong with the specified language
or character set, for example the specified character set
is not valid for the specified language. Contact Sybase
Technical Support if a resolution cannot be determined.
1.47.1 1 Backup Server could not set the server
language/character set to `%1!/%2!'. The specified
language/character set combination may not be valid,
or the language/character set combination may not be
installed under $SYBASE/locales. The default
language/character set is in use.
Explanation: Attempt to set the Backup Server's
language and character set failed. Refer to the Backup
Server error log for more information. The specified
language or character set may not be valid or the
language or character set may not be installed under
$SYBASE/locales.
1.48.2 2 Attempt to dispatch Backup Server by Service Control
Manager returned operating system error = %1!(%2!).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
1.49.2 2 Attempt to register Service Control Handler returned
operating system error = %1!(%2!).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
Number Severity Text and Explanation
Backup Server Error Messages 1.1.2 - 1.63.2
700
1.50.2 2 Attempt to set Control Status returned operating
system error = %1!(%2!).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
1.51.2 2 Service Control Handler received an invalid control
code = %1!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
1.52.1 1 Backup Server terminating because of system
shutdown
Explanation: Information, no user action necessary.
1.53.2 2 Attempt to create thread returned operating system
error = %1!(%2!).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
1.54.2 2 Attempt to connect to registry returned operating
system error = %1!(%2!).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
1.55.2 2 Attempt to open registry key returned operating system
error = %1!(%2!).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. This is an NT
specific message.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
701
1.56.2 2 The SYBASE environment variable must be set.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. Follow any
instructions given.
1.57.2 2 Backup Server encountered an error while attempting
to create a message queue. The Open Server routine
srv_createmsgq failed. This session cannot continue.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
1.58.2 2 Error: Unable to disable the `%1!' system registered
procedure.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
1.59.2 2 Error: Unable to spawn thread to drop the disallowed
system registered procedures.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
1.60.2 2 Unable to configure %1! connections and %2! service
threads which requires %3! message queues. The
maximum number of message queues is %4!.
Explanation: The value of the -C and -P option are
such that the number of message queues exceed the
allowed maximum. Restart the Backup Server with
reduced values for these parameters.
1.61.2 2 The SYTAPE environment variable must be set.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit. Follow any
instructions given.
Number Severity Text and Explanation
Backup Server Error Messages 2.1.2 - 3.55.2
702
Backup Server Error Messages 2.1.2 - 3.55.2
1.62.2 2 Unable to load the Sytos DLL that SYTAPE is set to.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
1.63.2 2 Unable to configure %1! connections and %2! service
threads which requires %3! messages. The maximum
number of messages is %4!.
Explanation: The value of the -C and -P option are
such that the number of message queues exceed the
allowed maximum. Restart the Backup Server with
reduced values for these parameters.
Number Severity Text and Explanation
Number Severity Text and Explanation
2.1.2 2 Open Server initialization failed. Unable to start %1!.
Explanation: The user should check the installation.
This error can also arise from memory and swap space
shortage.
2.2.4 4 Open Server Server Fatal Error: %1!.%2!.%3!: %4!
Explanation: This indicates a fault within the Open
Server layer that forces program exit. The error code
placeholder should be matched to the Open Server
error codes for diagnosis. Check installation.
2.3.2 2 Open Server Session Fatal Error: %1!.%2!.%3!: %4!
Explanation: Interpret as for 2.2.4, except only the
session exits, not the whole Server.
2.4.2 2 Open Server Error: %1!.%2!.%3!: %4!
Explanation: Interpret as for 2.2.4, except Server and
session processing continue. Example: missing
localization file.
CHAPTER 4 Backup Server Error Messages
703
2.5.2 2 Couldn't define %1! event; Backup Server must exit.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.6.2 2 Login information unavailable.
Explanation: The Backup Server could not access
the session login information to perform
authentication due to unauthorized session initiator or
programming bug. Contact Sybase Technical Support.
2.7.2 2 Remove server TDS version must be equal to or greater
than 4.6. This session must exit.
Explanation: Connection was attempted with an
obsolete TDS version. Backup Server communicates
reliably only with System 10 Adaptive Servers and
other Backup Servers.
2.8.2 2 Couldn't create semaphore for session %1!. This
session must exit.
Explanation: Indicates Open Server MUTEX
initialization failure or session limit reached.
2.9.4 4 The number of connections must be an integer.
Explanation: Indicates illegal -C (/connections in
Digital OpenVMS) option value for the backupserver
command. Check the line in your RUN_servername
file.
2.10.2 2 A trace flag specifier must be an integer.
Explanation: UNIX only: The argument to the
backupserver command's -T (/trace in Digital
OpenVMS) option was not an integer. Check the line
in your RUN_servername file.
2.11.2 2 Failed to get lock to send packet to client, spid: %1!,
lockstatus %2!.
Explanation: Internal error, contact Sybase
Technical Support. An error occurred when attempting
to lock an Open Server MUTEX (mutually exclusive
object) which only one user at a time can lock. Refer to
the Backup Server error log for more information.
Number Severity Text and Explanation
Backup Server Error Messages 2.1.2 - 3.55.2
704
2.12.2 2 The diagnostic option specifier must be an integer.
Option is `%1!'
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.13.2 2 Unable to get connection endpoint. srv_thread_props()
returned an error.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.14.2 2 Unable to determine connection type. fstat() returned
an error: %1!
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.15.2 2 Connection refused. The owner id of the connection
named pipe is not the same user id as that of the
Backup Server process.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.16.2 2 Error: unable to disable registered procedures.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.17.2 2 Unrecognized security option `%1!'.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
2.18.4 4 The number of service threads must be a positive
integer up to the maximum of %1!. Specified value
was `%2!'.
Explanation: The value specified for -P option is
invalid. Restart backup server with a valid value.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
705
2.19.2 2 Invalid verbosity level: A verbosity level specifier
must be an integer from 0 to 3.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session must exit.
3.1.2 2 Unrecognized RPC received--ignored.
Explanation: The session initiator sent an
unrecognized RPC. Indicates ad hoc RPC was sent, or
a programming bug in Adaptive Server or Backup
Server. Contact Sybase Technical Support.
3.2.2 2 Symbol %1! not found in TDS table.
Explanation: Internal message; customers will likely
never see it; it is only included here for completeness.
3.3.2 2 %1!: May not specify Backup Server scanning or free-
page clearing for a secondary phase.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate a violation of
the dump synchronization protocol of the RPC API.
3.4.2 2 %1!: Must specify Backup Server scanning in order to
clear free pages at LOAD time.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate a violation of
the dump synchronization protocol of the RPC API.
3.5.2 2 %1!: Could not lock session %2! to begin phase.
Explanation: Internal error, contact Sybase
Technical Support. This indicates an error or bug in the
Open Server MUTEX mechanism.
3.6.1 1 %1!: Phase %2! is currently active. Only one phase
may be active at a time.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.7.2 2 %1!: phase %2! already concluded.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
Number Severity Text and Explanation
Backup Server Error Messages 2.1.2 - 3.55.2
706
3.8.2 2 %1!: May not begin phase %2! before completing an
earlier phase, number %3!, for which there is
uncompleted work.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.9.2 2 %1!: May not initiate Backup Server scanning for a
phase for which run-lists have been queued.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.10.2 2 %1!: phase %2! not active.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.11.2 2 %1! SANITY: PHASE for phase no. %2! not at head
of list.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.12.2 2 May not submit RPC %1! unless performing a DUMP.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.13.2 2 %1!: Illegal phase number %2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.14.2 2 Logical page %1! is not in the given database map.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.15.2 2 The disk piece for page %1! does not belong to phase
%2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.16.2 2 %1!: There is no session of id %2! in progress.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
707
3.17.2 2 Pathname parameter must specify an absolute
pathname. Rejected value: %1!
Explanation: Adaptive Server sent its present
working directory to the Backup Server and that
directory was not recognized as an absolute path
specifier.
3.18.2 2 Adaptive Server Enterprise did not specify absolute
pathname root before sending the relative device
pathname %1!.
Explanation: Adaptive Server sent a device
specification that was not recognized as an absolute
path specification, and had not previously sent its
present working directory.
3.19.2 2 Combining device pathnames %1! and %2! exceeds
the maximum pathname length.
Explanation: The combination of Adaptive Server's
present working directory and the relative device name
is too long for Backup Server's internal buffer.
3.20.2 2 %1!: RPC rejected--missing parameters.
Explanation: The number of parameters passed to
Backup Server for the specified RPC does not match
the number of parameters expected for that RPC. If
you are sending Backup Server the RPC via your own
customized mechanism, check that mechanism for the
correct RPC count. Otherwise, contact Sybase
Technical Support.
3.21.2 2 %1! SANITY: run list size > %2!.
Explanation: The total size of the run lists for the
bs_run_list RPC will exceed the size used to store the
run lists internally within Backup Server. If you are
sending Backup Server the RPC via your own
customized mechanism, check that mechanism for the
correct size of the run lists. Otherwise, contact Sybase
Technical Support.
3.22.2 2 %1!: Session %2! does not exist.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.23.2 2 %1!: Could not queue run list for session %2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
Number Severity Text and Explanation
Backup Server Error Messages 2.1.2 - 3.55.2
708
3.24.2 2 %1!: RPC rejected, phase %2! already concluded.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.25.2 2 %1!: May not submit run lists for phases in which
Backup Server conducts the scan.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.26.2 2 %1! SANITY: parameter data overflows I/O block.
Explanation: Internal error, contact Sybase
Technical Support. Error with dump header or trailer
processing in either Server. The total parameter sizes
are defined to equal the I/O block size.
3.27.2 2 Invalid RPC sequence at RPC %1!.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.28.2 2 Non-contiguous database map, session %1!, lpn %2!.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate an Adaptive
Server programming bug, defective database disk
mapping information sent.
3.29.2 2 No virtual mapping for logical page %1!.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate an Adaptive
Server programming bug, defective database disk
mapping information sent.
3.30.2 2 Bs_normdbmap received an overlapping disk piece.
Explanation: Internal error, contact Sybase
Technical Support. These errors indicate an Adaptive
Server programming bug, defective database disk
mapping information sent.
3.31.2 2 Improper parameter count %1! for RPC %2!.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
709
3.32.2 2 Incorrect type for parameter #%1! for RPC %2!;
expected %3! got %4!.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.33.2 2 SANITY: premature last run list.
Explanation: Internal error, contact Sybase
Technical Support.
3.34.2 2 SANITY: more stripes than extents.
Explanation: Internal error, contact Sybase
Technical Support.
3.35.2 2 RPC %1! refused following previous FAILURE return.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.36.2 2 RPC %1!: parameter %2! may not be NULL.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.37.2 2 SANITY: RPC %1!: expected parameter %2! got
parameter %3!.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.38.2 2 There is no primary phase %1! for secondary phase
%2!.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the dump
synchronization protocol of the RPC API.
3.39.2 2 RPC %1! can only be executed in a slave server.
Explanation: These errors indicate an Adaptive
Server programming error, violation of the RPC API.
Number Severity Text and Explanation
Backup Server Error Messages 2.1.2 - 3.55.2
710
3.40.2 2 Illegal length for parameter #%1! for RPC %2!;
expected %3! got %4!.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.41.2 2 Illegal max-length for parameter #%1! for RPC %2!;
expected %3! got %4!.
Explanation: Internal error, contact Sybase
Technical Support. Error in the session initiator
(Adaptive Server or Backup Server), a violation of the
RPC API.
3.42.1 1 %1! is complete (database %2!).
Explanation: Informational message that Backup
Server processing for the session is complete (the
dump or load command may continue to run, for
example, to clear the region of the loaded database
above the dump-time high page).
3.43.1 1 Dump phase number %1! completed.
Explanation: Informational message that a dump
synchronization phase has completed.
3.44.2 2 The Backup Server is already performing a deferred
shutdown; only one may be active at a time.
Explanation: Shutdown is in progress and will occur
when all dumps and loads have completed.
3.45.1 1 Attention received: cancelling deferred shutdown.
Explanation: Internal error, contact Sybase
Technical Support.
3.46.2 2 Deferred shutdown wait failed, cancelling deferred
shutdown.
Explanation: Internal error, contact Sybase
Technical Support.
3.47.2 2 The Backup Server is undergoing shutdown. Your
session will terminate immediately. Please reattempt
connection later.
Explanation: This message is issued in response to a
dump or load command after a shutdown request has
been sent but before the Backup Server has actually
shut down.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
711
3.48.1 1 The Backup Server will go down immediately.
Terminating sessions.
Explanation: This is the final message sent to the
session that issued the shutdown command.
3.49.2 2 RPC %1! does not allow option %2!.
Explanation: An RPC inconsistency was detected.
This could be caused by incompatible releases of
Backup Server and Adaptive Server.
3.50.2 2 Non-privileged connection is not authorized to execute
privileged RPC `%1!'.
Explanation: Some RPCs are “privileged,” that is,
they can only occur in the context of an Adaptive
Server-initiated dump. Users who attempt to
programmatically duplicate one of these RPCs are
prevented from doing so.
3.51.2 2 Database device #%1!, name %2! has already been
declared as #%3!, name %4!.
Explanation: Internal error, contact Sybase
Technical Support. The dump or load command as
translated by Adaptive Server does not make sense.
The sysdevices table may be corrupt.
3.52.2 2 Database device #%1! has not been declared.
Explanation: Internal error, contact Sybase
Technical Support. The dump or load command as
translated by Adaptive Server does not make sense.
The sysdevices table may be corrupt.
3.53.2 2 Malformed option list received, RPC: %1!.
Explanation: Internal error, contact Sybase
Technical Support. The dump or load options as
passed from Adaptive Server do not make sense. The
problem may be possible to work around by
rearranging, adding or removing options to the dump
or load command.
3.54.1 1 Waiting for processes to complete.
Explanation: This message is sent to the session
issuing a shutdown command if there are outstanding
dump or load requests and nowait was not specified.
3.55.2 2 RPC %1!, parameter `%2!': `%3!' is an invalid value.
Explanation: Internal error, contact Sybase
Technical Support. Adaptive Server requested an
unknown function.
Number Severity Text and Explanation
Backup Server Error Messages 4.1.2 - 4.75.3
712
Backup Server Error Messages 4.1.2 - 4.75.3
Number Severity Text and Explanation
4.1.2 2 Device `%1!': volume `%2!' appears to contain data
written in a format that the Backup Server does not
recognize. Please use a different volume, or initialize
this volume through the operating system.
Explanation: Digital OpenVMS only: the tape may
be of foreign origin. Digital OpenVMS volume init
may know how to confirm that data can be
overwritten. Will be followed by an additional
operating system message elaborating on the situation.
4.2.3 3 Adaptive Server Enterprise sent an overlapping disk
piece.
Explanation: Database is corrupt. Run dbcc
diagnostics on your database and refer to Adaptive
Server Error Messages for corrective measures.
4.3.2 2 Device %1! is not in use by any session on this server.
Explanation: Indicates user addressed
sp_volchanged execution to an inactive device. Check
parameters.
4.4.2 2 Device %1! does not belong to session <%2!>.
Notification failed.
Explanation: Indicates a device specified in an
sp_volchanged execution does not belong to the
named session. Check parameters.
4.5.2 2 Notification attempt failed--message channel for
session <%1!> is closed.
Explanation: Indicates user addressed
sp_volchanged execution to a nonexistent session.
Check parameters.
4.6.2 2 Failed to create or attach shared tape i/o buffers.
Explanation: Indicates unavailability of shared
memory on the platform, possibly caused by memory
shortage or kernel configuration limit reached. Check
resource availability. This is probably a Backup Server
problem.
CHAPTER 4 Backup Server Error Messages
713
4.7.2 2 Device %1! already in use.
Explanation: A session attempted to use an archive
device owned by another session. Select a different
archive device.
4.8.2 2 Mirror device types don't match: %1!.
Explanation: This error is part of a not yet
implemented feature, included here only for
completeness.
4.9.2 2 Label validation error: read returned %1! reading
label. Read:n%2!
Explanation: These errors indicate a mislabeled or
illegal-format archive volume. User should use offline
commands to verify that the tape contains Sybase
information. The following commands submitted
repeatedly in order will display the beginning and
ending label characters for each file on the tape:
dd if=<tape_device> bs=2048 | od
-cmt
-f <tape_device> fsf 1dd
if=<tape_device>
bs=2048 | od -c
Zero bytes reported from “dd” and “od” denotes no
further data on the tape.
4.10.2 2 Label validation error: first label not VOL1.
Explanation: Same as Error # 4.9.2
4.11.2 2 Label validation error: seek to %1!s failed, %2!.
Explanation: Same as Error # 4.9.2
4.12.2 2 Label validation error: %1! label not found.
Explanation: Same as Error # 4.9.2
4.13.2 2 Device `%1!': can't determine how to set density on
channel %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session will exit.
4.14.2 2 Label validation error: too many header labels.
Explanation: Errors similar to 4.9.2–4.12.2.
4.15.2 2 Label validation error: seek to trailer labels failed.
Explanation: Errors similar to 4.9.2–4.12.2.
Number Severity Text and Explanation
Backup Server Error Messages 4.1.2 - 4.75.3
714
4.16.2 2 Label validation error: read of tape mark failed.
Explanation: Errors similar to 4.9.2–4.12.2.
4.17.2 2 The stripes on the specified devices have completed,
but more dump stripes exist.
Explanation: This message arises when loading from
fewer stripes than the number used at dump time. At
load time, there must be at least one instance of every
device type used at dump time.
4.18.2 2 Unsupported device type. The stat() system call
returned type '%1!' for '%2!'. Refer to your operating
system documentation for more details.
Explanation: The archive device type is either an
operating system file, raw fixed disk, raw unloadable
disk (for example, floppy disk), tape, or network
location (device_name AT
remote_backup_server_name). Select a device of a
legal type.
4.19.2 2 Label validation error: too many trailer labels.
Explanation: Errors similar to 4.9.2–4.12.2.
4.20.2 2 Device `%1!': I/O error, write of tape mark failed.
Explanation: Errors similar to 4.9.2–4.12.2.
4.21.2 2 Device `%1!' should be marked `list only', but is not.
Cannot continue this command.
Explanation: Errors similar to 4.9.2–4.12.2.
4.22.1 1 Option %1! is not valid for device `%2!'.
Explanation: Indicates a device option not
appropriate for the device type. Review legal options
for device types.
4.23.2 2 %1!: read %2!: %3!.
Explanation: Indicates a read or write system call
error on a disk or file device. Investigate possible
causes (for example, out-of-space condition.) This
error aborts the dump or load.
4.24.2 2 %1!: write %2!: %3!.
Explanation: Indicates a read or write system call
error on a disk or file device. Investigate possible
causes (for example, out-of-space condition.) This
error aborts the dump or load.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
715
4.25.2 2 Device `%1!': %2! is an inappropriate density value
for this device.
Explanation: Digital OpenVMS only: the density
value specified in the dump or load command is not
valid. Expected values are: none specified, 800, 1600,
6250, 6666, 10000, and 38000.
4.26.2 2 Volume validation error: failed to obtain device
information, device: %1! error: %2!.
Explanation: Backup Server is unable to sense the
type of a given device. Verify that the device is of a
legal type and that the Backup Server process has
operating system permission to access it.
4.27.2 2 Volume validation error: attempt to close %1! returned
%2!.
Explanation: A UNIX file failed to close. The first
parameter is the file name and the second is the UNIX
error message that was returned.
4.28.2 2 Device `%1!': set mode failed on channel %2!; status
= 0x%3!.
Explanation: Digital OpenVMS only: could not set
device density. The “status” line will contain the
operating system error code.
4.29.2 2 Device `%1!': sense mode failed on channel %2!;
status = 0x%3!.
Explanation: Digital OpenVMS only: could not
sense device characteristics. The “status” line will
contain the operating system error code.
4.30.2 2 Volume validation error: attempt to open %1! returned
%2!.
Explanation: Indicates an error opening or closing a
database device.
4.31.2 2 Device `%1!': failed to skip back to beginning of tape
on channel %2!; status = 0x%3!.
Explanation: Digital OpenVMS only: volume init
error. The “status” line will contain the operating
system error code.
4.32.2 2 Failed to allocate memory for tape i/o buffer.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session will exit.
Number Severity Text and Explanation
Backup Server Error Messages 4.1.2 - 4.75.3
716
4.33.2 2 Header labels of rejected volume:
Explanation: Display of the data Backup Server
found where it expected ANSI volume labels. Verify
that the proper volume is loaded.
4.34.1 1 Device `%1!':\nVolume name:'%2!'\n
Explanation: Information, no user action necessary.
4.35.1 1 Device `%1!':\t\nLabel name:\t'%2!'\nVolume
id:\t'%3!'\nAccess
code:\t'%4!'\nReserved:\t'%5!'\nOwner
id:\t'%6!'\nReserved:\t'%7!'\nLabeling version:\t%8!\n
Explanation: Information, no user action necessary.
4.36.1 1 Device `%1!':\t\nFile name:\t'%2!'\nCreate date &
time:\t%3!, %4!\nExpiration date & time:\t%5!,
%6!\nDatabase name:\t'%7!'\n
Explanation: Information, no user action necessary.
4.37.1 1 Device '%1!':\t\nLabel id:\t'%2!'\nFile
name:\t'%3!'\nStripe count:\t%4!\nDevice
typecount:\t%5!\nArchive volume
number:\t%6!\nStripe position:\t%7!\nGeneration
number:\t%8!\nGeneration version:\t%9!\n
Explanation: Information, no user action necessary.
4.38.1 1 Device `%1!':\nLabel id:\t'%2!'\nRecord
format:\t'%3!'\nMax. bytes/block:\t%4!\nRecord
length:\t%5!\nBackup format
version:\t%6!\nReserved:\t'%7!'\nDatabase
name:\t'%8!'\nBuffer offset
length:\t%9!\nReserved:\t'%10!'\n
Explanation: Information, no user action necessary.
4.39.1 1 Device `%1!': illegible file date & time found;
continuing.
Explanation: This error is raised when Backup
Server attempts to list the contents of a tape. Media
failure or corruption could be indicated. Backup
Server will continue listing contents (other files may be
fine).
4.41.1 1 Creating new disk file %1!.
Explanation: This message occurs when attempting
to dump to a non-existent disk FNAME.
4.42.2 2 Couldn't obtain channel to multibuffering subprocess,
error: %1!
Explanation: An attempt to fork a subprocess failed.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
717
4.43.2 2 Couldn't create multibuffering subprocess.
Explanation: Backup Server was unable to complete
start-up of the multibuffering subprocess. File
descriptors may be exhausted (Error 4.42). Retry
session when Backup Server activity is lower. Possible
virtual memory shortage (Error 4.43).
4.45.2 2 The maximum number of %1! stripe devices has been
exceeded.
Explanation: A single dump or load session may use
a maximum of 32 archive stripes. Reduce the number
of archive devices in the dump or load command.
4.46.2 2 Length error on I/O -- transferred %1! bytes, expecting
to transfer %2! bytes.
Explanation: Digital OpenVMS only: Backup
Server requested the operating system to read or write
%2 bytes and only %1 bytes were actually transferred.
Probably device or media failure.
4.50.2 2 Device %1!: The blocksize %2! of the dump file is not
within the range of %3! to %4!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic. The session will exit.
4.51.2 2 Archive devices `%1!' and `%2!' do not belong to the
same file group.
Explanation: Internal error, contact Sybase
Technical Support. The tapes/devices do not belong to
the same archive group. To the Backup Server, it
appears that “tapes” from two different dumps are
mounted in devices requested by the current load.
4.52.2 2 There should be %1! load stripes, but the command
only specifies %2!. One or more required devices have
been omitted from the command line.
Explanation: Backup Server supports database loads
on fewer devices than were used for the dump.
However, at least one device of each type (4 mm, 8
mm, and so on) must be supplied. Backup Server
verifies that a load command specifies all needed
device types. If it does not, this error is raised.
Number Severity Text and Explanation
Backup Server Error Messages 4.1.2 - 4.75.3
718
4.53.2 2 The load command specifies too many devices of type
`%1!': expected %2!, got %3!.
Explanation: Similar to 4.52.2; however, this is the
reverse case. Backup Server cannot load from more
stripes than were used for the original dump.
4.54.2 2 The load command specifies too few devices of type
`%1!': expected %2!, got %3!.
Explanation: At least one type of each device must
be specified in the load command
4.55.2 2 Device validation error: couldn't open raw device %1!,
error: %2!
Explanation: These errors denote failure to obtain
hardware characteristics after establishing the device
type. Check permissions on the device special file,
investigate the returned operating system error
message.
4.56.2 2 Device validation error: couldn't obtain tape drive
characteristics for device %1!, error: %2!
Explanation: These errors denote failure to obtain
hardware characteristics after establishing the device
type. Check permissions on the device special file,
investigate the returned operating system error
message.
4.57.2 2 Device validation error: couldn't obtain disk drive
characteristics for device %1!, error: %2!
Explanation: These errors denote failure to obtain
hardware characteristics after establishing the device
type. Check permissions on the device special file,
investigate the returned operating system error
message.
4.58.1 1 Database %1!: %2! kilobytes %3!ed.
Explanation: This message conveys the progress of
the dump or load session. %3 is “DUMP” or “LOAD”.
4.59.3 3 Archive device %1! must either be a STRIPE or
MIRROR.
Explanation: Internal error, contact Sybase
Technical Support. This error can occur only if
Adaptive Server incorrectly translated a dump
command.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
719
4.60.2 2 Archive device %1! does not support a valid tapemark.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.61.2 2 Archive device %1! does not support %2! operation.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.62.3 3 Multibuffering subprocesses died, archive %1!.
Explanation: This error message may indicate that
the Backup Server cannot find the sybmultbuf
program. Check $SYBASE/bin to see if sybmultbuf is
there.This can also happen if the Backup Server cannot
locate the sybmultbuf binary because it has received
an incorrect parameter.The correct use of the -M flag
is: $SYBASE/bin/backupserver -
M$SYBASE/bin/sybmultbuf A third possibility is that
the Backup Server has had trouble forking the
sybmultbuf process. Check the Backup Server's
srv.log, which may contain more information regarding
this problem. For emulator failure accompanied by
this error message, see Errors in Backup Server Error
Log.
4.63.2 2 End-of-volume reading labels, archive %1!.
Explanation: Backup Server encountered a tape file
mark when attempting to read the ANSI labels.
Indicates validation attempt on a blank tape (not an
error), a non-ANSI tape or programming error. The
tape volume should be examined off line with the
commands given above. If the volume was the final
volume of the load and the I/O has proceeded normally
to this point (as evinced by progress messages, etc.)
then the load I/O can be considered successful. If not,
the load should be reattempted.
4.64.3 3 SANITY: Scheduled ACK events exceed stripe count.
Explanation: Internal error, contact Sybase
Technical Support.
Number Severity Text and Explanation
Backup Server Error Messages 4.1.2 - 4.75.3
720
4.67.2 2 Device %1!: This tape device requires the CAPACITY
option.
Explanation: Backup Server does not know how to
detect end-of-tape on this device. Therefore capacity
must be specified on dump, or you must specify the
device as a logical device name from sysdevices.
4.68.2 2 Write data to a network device (slave site: %1!, device:
%2!) failed.
Explanation: This messages are self-explanatory.
Further details will appear in a 4.82.2 message, which
will immediately follow this message.
4.69.2 2 Read data from the network device (slave site: %1!,
device: %2!) failed.
Explanation: This messages are self-explanatory.
Further details will appear in a 4.82.2 message, which
will immediately follow this message.
4.70.2 2 Device %1!: Unable to query ODM database for device
attributes. ODM error code = %2!.
Explanation: RS6000 only: Since Backup Server has
failed to determine device characteristics, it cannot
ensure that the device is configured for extended file
marks.
4.71.2 2 Device %1!: Is not configured for extended file marks.
Explanation: RS6000 only: Multi-file devices must
be reconfigured with extended tape marks. This is so
that tape marks can be overwritten on multi-file
dumps.
4.72.2 2 Write data to the archive device `%1!' failed. I/O error:
%2!
Explanation: This messages are self-explanatory.
Further details will appear in a 4.82.2 message, which
will immediately follow this message.
4.73.2 2 Read data from the archive device `%1!' failed. I/O
error: %2!
Explanation: This messages are self-explanatory.
Further details will appear in a 4.82.2 message, which
will immediately follow this message.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
721
Backup Server Error Messages 4.76.3 - 4.147.2
4.74.2 2 Unable to %1! database information file %2! : %3!.
Explanation: UNIX Backup Servers use a temporary
file (created in /tmp) to pass database device names to
the sybmultbuf program. An I/O error with this file has
occurred. User should verify that /tmp is world-
writable, has sufficient space, and contains no unused
files of the form BS_servername.number.
4.75.3 3 Device %1!: %2! is not a legal virtual disk number.
Explanation: Internal error, contact Sybase
Technical Support. Backup Server cannot determine
what portions of the specified database device should
be backed up because information about the device
sent from Adaptive Server does not correspond with
the actual physical device.
Number Severity Text and Explanation
Number Severity Text and Explanation
4.76.3 3 Device %1!: %2! is not a legal virtual block number.
Explanation: Internal error, contact Sybase
Technical Support. Backup Server cannot determine
what portions of the specified database device should
be backed up because information about the device
sent from Adaptive Server does not correspond with
the actual physical device.
4.77.2 2 Device %1! may not be used: minimum blocksize for
I/O exceeds device maxiumum of %2!.
Explanation: Backup Server requires tape devices to
support an I/O size of at least 2K. The tape device
found has a maximum I/O size less than 2K. This
message should never appear. If it does, user should
check device name specification. If correct, user must
use another device.
4.78.2 2 Option %1!: illegal value %2!.
Explanation: This indicates the user has supplied an
illegal value for a device option. Review the device
options and legal values.
Backup Server Error Messages 4.76.3 - 4.147.2
722
4.79.2 2 Server %1!, device %2!: illegal I/O size %3!--max
%4!.
Explanation: Indicates a programming bug in a local
or remote Backup Server. The I/O service layer has
received a read or write request size that exceeds the
available buffer size.
4.80.2 2 Server %1!, device %2!: You must use the no-rewind-
on-close tape device.
Explanation: Backup Server requires all tape devices
to use the no-rewind-on-close option, so that it can
fully control tape positioning.
4.81.2 2 Server %1!: device %2! is open for writing; you may
not specify the @fname parameter when changing
volumes.
Explanation: The @fname parameter is meaningful
only at load time, to select a certain file to load from a
multi-file volume. At dump time, the Backup Server
assigns a name to the file that will contain the dump.
Message 6.28.1 returns the assigned name.
4.82.2 2 Operating system error, server %1! device %2!: code
%3! message %4!.
Explanation: This message appears when a system
call (perhaps performed as part of a higher-level
operation) has failed. It is intended primarily for
diagnostic use and should be interpreted in the context
of immediately preceding messages.
4.83.2 2 Device %1!: The specified blocksize %2! is not within
the range of %3! to %4!.
Explanation: The user-specified block size is out of
range. Respecify block size within the listed limits.
4.84.1 1 Device %1!: The specified blocksize of %2! will be
truncated to %3! which is a multiple of %4!.
Explanation: The user-specified block size was
truncated to be a multiple of 2048.
4.85.1 1 Device %1!: Disk model %2! does not exist in the
/etc/disktab file. Using default values for this device.
Explanation: The disk device is not configured in
/etc/disktab, so a default disk block size will be used.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
723
4.86.2 2 Unable to initialize Async IO on the database device
%1!. Backup Server must use Async IO on a block
special devices because Adaptive Server Enterprise is
doing the same.
Explanation: This is an HP-specific error. If
Adaptive Server Enterprise is using asynchronous I/O
for a block special device, then backup Server must do
the same in order to guarantee disk coherency. Block
I/O without asynchronous isa buffered I/O operation.
With asynchronous I/O, it is not buffered. If two
processes access the same disk, one using buffered I/O
and the other using nonbuffered I/O, the current image
of a disk page may be ignored by one of the processes.
4.87.2 2 Device %1!: uname() failed with error: %2!.
Explanation: HP only: Backup Server is trying to
identify the machine as an HP 800 or HP 700. The
uname call (which gets this information) failed.
4.88.2 2 Device %1!: Could not determine device type due to
unknown machine model. Expected models are
HP9000/800 & 700 series.
Explanation: Related to Error 4.87.2. After getting
the machine name with the uname call, Backup Server
could not identify the device type because it could not
identify the machine type. Only 800 and 700 series
machines are expected.
4.89.2 2 Allocation of Resource Tag failed.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.90.2 2 Allocation of Resource Tag for tape i/o failed.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.91.2 2 Registering of application failed. OS error returned
%1!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
Backup Server Error Messages 4.76.3 - 4.147.2
724
4.92.2 2 Unregistering of application failed. OS error returned
%1!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.93.2 2 Read from %1! failed: OS error returned %2!, errno
%3!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.94.2 2 Write to %1! failed: OS error returned %2!, errno
%3!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.95.2 2 Unable to expand file %1!. OS error returned %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.96.2 2 Unable to set end of file for %1!. OS error returned
%2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.97.2 2 Asynchronous I/O failed for %1!. OS error returned
%2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.98.2 2 Unable to reserve device %1! in Control Mode. OS
error returned %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
725
4.99.2 2 Open unable to mount media for device %1! : OS error
returned %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.100.2 2 Unable to dismount media for device %1! : OS error
returned %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.101.2 2 Unable to reserve device %1! in IO Mode. OS error
returned %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.102.2 2 Unable to locate device %1! in the Media Manager
database.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.103.2 2 Requested seek type %1! is invalid.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.104.2 2 Memory Allocation for I/O buffer failed.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.105.2 2 Received invalid return code %1! in I/O completion
status.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
Backup Server Error Messages 4.76.3 - 4.147.2
726
4.106.2 2 Unable to forward a file mark: OS error returned %1! .
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.107.2 2 Error in forwarding %1! file marks.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.108.2 2 Unable to back over a file mark: OS error returned %1!
.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.109.2 2 Error in backing over %1! file marks.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.110.2 2 Attepmt to write EOF on device %1! failed. OS error
returned %2! .
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.111.2 2 Unable to rewind device %1!: OS error returned %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.112.2 2 Unable to unload media in device %1!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
727
4.113.2 2 Unable to go to end of media.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.114.2 2 Unable to retension device.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.115.2 2 Open of %1! failed, unable to expand device name to
fullpath.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.116.2 2 Open of %1! failed, unable to determine volume
number. Volume = %2! Fullpath = %3!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.117.2 2 Unable to get volume mapping information for volume
%1! in path %2!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.118.3 3 Unable to detect database device %1!
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.119.2 2 Unable to release device %1!
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
Backup Server Error Messages 4.76.3 - 4.147.2
728
4.120.3 3 Unable to locate state information for this stripe.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.121.3 3 Local semaphore handle is NULL for asynchronous
disk i/o.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.122.2 2 Unable to allocate semaphore for disk operations on
device %1!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.123.2 2 Operating system error, server %1! device %2!
errcode %3!.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.124.2 2 Archive API error for device='%1!': Vendor
application name=%2!, Library version=%3!, API
routine=%4!, Message=%5!
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.125.1 1 Archive API information for device='%1!': Vendor
application name=%2!, Library version=%3!,
Message=%4!.
Explanation: Information, no user action necessary.
4.126.3 3 Unable to get current date and time. Internal error.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
729
4.127.2 2 Internal Error on device %1!: Attempting to determine
if device is non-rewinding. Failed to get the OS version
when converting data returned from uname(2).
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.128.2 2 Failed to start multibuffering subprocesses for archive
device `%1!'. Look at the Backup Server error log for
more information.
Explanation: Either the sybmultbuf process was not
created successfully or the sybmultbuf process died
immediately after creation. Check the backup server
error log for any error message from the sybmultbuf
process.
4.129.2 2 Device %1! may not be used with physical blocksize
configured as %2!. In order to be usable by Backup
Server a device's blocksize must be configured to be
both less than or equal to %3! and to be an even divisor
of that value.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.130.2 2 Device: `$1!'. The stream identifier `%2!' contains
invalid characters. The valid character are, alphabetic,
numeric, and underscore.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.131.2 2 Device: `%1!'. The stream identifier `%2!' has an
incorrect length. A valid length is from 1 to 30 bytes
long.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.132.1 1 Attempting to open bytestream: `%1!'
Explanation: Information, no user action necessary.
4.132.1 1 Attempting to open byte stream device: `%1!'
Explanation: Information, no user action necessary.
Number Severity Text and Explanation
Backup Server Error Messages 4.76.3 - 4.147.2
730
4.133.2 2 Invalid path or no execute permission for
multibuffering subprocess binary: %1!
Explanation: The sybmultbuf binary could not be
found. Check the pathname in the -M option or
$SYBASE/bin for the existence of sybmultbuf binary
(in NT sybmbuf.exe). Also, check if the binary has
execute permissions.
4.134.2 2 Invalid Device: you cannot dump to or load from the
null device, '%1!'.
Explanation: You cannot dump to null device since
you cannot recover the dump from it. Select a device
of a legal type.
4.135.2 2 Invalid Device: you cannot dump to or load from a
directory, '%1!'.
Explanation: The specified archive device is a
directory name. Specify a device name or a disk file
name.
4.136.2 2 uname failed with OS error '%1!'.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.137.2 2 Invalid OS release number '%1!'
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.138.2 2 Device '%1!': operating system call 'readlink' failed
with error '%2!'.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
4.139.2 2 [%1!] The '%2!' call failed for device '%3!' with error
number %4! (%5!). Refer to your operating system
documentation for further details. Look for '%6!' in the
backup server errorlog for additional information from
SYBMULTBUF.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
731
4.140.2 2 [%1!] The '%2!' call failed with error number %3!
(%4!). Refer to your operating system documentation
for further details. Look for '%5!' in the backup server
errorlog for additional information from
SYBMULTBUF.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
4.141.2 2 [%1!] The '%2!' call failed for device '%3!' with error
number %4! (%5!). Refer to your operating system
documentation for further details.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
4.142.2 2 [%1!] The '%2!' call failed with error number %3!
(%4!). Refer to your operating system documentation
for further details.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
4.143.2 2 [%1!] A failure occurred for device '%2!'. Look for
'%3!' in the backup server errorlog for additional
information from SYBMULTBUF.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
4.144.2 2 [%1!] A failure occurred. Look for '%2!' in the backup
server errorlog for additional information from
SYBMULTBUF.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
4.145.2 2 [%1!] Error for device '%2!'. %3!
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
4.146.2 2 [%1!] Error occurred. %2!
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf..
Number Severity Text and Explanation
Backup Server Error Messages 5.1.2 - 6.89.2
732
Backup Server Error Messages 5.1.2 - 6.89.2
4.147.2 2 Operating system error. Code %1! message %2!.
Explanation: The message has 93 secondary state
values used to determine where a failure occurred in
sybmultbuf.
Number Severity Text and Explanation
Number Severity Text and Explanation
5.1.2 2 The mirror devices (site: %1!) and the primary
device(site: %2!) must reside at the same site.
Explanation: This message is part of the
uncompleted dump mirroring feature. All mirrors for
a stripe must reside on the same host.
5.2.2 2 Cannot allocate the login record.
Explanation: This error occurs when the dblogin call
fails, probably due to a memory resource problem.
5.3.2 2 Cannot open a connection to the slave site `%1!'.
Explanation: An attempt to connect to a remote
Backup Server encountered this failure. Look for:
Memory or swap space shortage
No remote Backup Server running
Wrong listening address
5.4.2 2 RPC (`%1!') initialization fails.
Explanation: Internal error, contact Sybase
Technical Support. Failure in dbrpcinit.
5.5.2 2 Cannot add a parameter to the RPC (`%1!') call
Explanation: Internal error, contact Sybase
Technical Support. Failure in dbrpcparam.
5.6.2 2 Cannot send the RPC (`%1!').
Explanation: Check to see that the local or remote
Backup Server is still available.
5.7.2 2 RPC (`%1!') execution failed.
Explanation: These messages point to difficulties in
issuing an RPC to a remote Backup Server. Probable
cause is an Open Server programming error.
CHAPTER 4 Backup Server Error Messages
733
5.8.2 2 RPC as_cmd execution failed - slave server: %1!,
device: %2!, command type: %3!.
Explanation: These messages point to difficulties in
issuing an RPC to a remote Backup Server. Probable
cause is an Open Server programming error.
5.9.2 2 RPC as_pagerun execution failed - slave server: %1!,
device: %2!.
Explanation: These messages point to difficulties in
issuing an RPC to a remote Backup Server. Probable
cause is an Open Server programming error.
5.11.2 2 RPC bs_end_load execution failed - slave server: %1!,
device: %2!.
Explanation: These messages indicate failure to
deliver the named RPCs to the remote Backup Server.
Adjacent messages provide more detail. Probable
causes are sudden death of the remote Backup Server,
or a programming error.
5.12.2 2 Missing device name parameter @devname, RPC:
%1!, command: %2!.
Explanation: Internal error, contact Sybase
Technical Support. Check the compatibility of local
and remote Backup Servers.
5.13.2 2 Received an unknown command. RPC: %1!,
command: %2!.
Explanation: Internal error, contact Sybase
Technical Support. Check the compatibility of local
and remote Backup Servers.
5.14.2 2 Cannot set the value of an RPC return parameters,
RPC: %1!
Explanation: Internal error, contact Sybase
Technical Support. Check the compatibility of local
and remote Backup Servers.
5.15.2 2 Slave server received %1! bytes of data that is more
than @count %2! specified in as_pagerun.
Explanation: Internal error, contact Sybase
Technical Support. Violation of the RPC API.
5.16.2 2 DB-Library error, error number %1!, severity %2!:
%3!
Explanation: The installed DB-Library error
handling function returns this error. Adjacent
messages provide more detail.
Number Severity Text and Explanation
Backup Server Error Messages 5.1.2 - 6.89.2
734
5.17.2 2 Cannot get the character set currently in use.
Explanation: The remote Backup Server could not
set the character set to its default setting for the initial
connection from a client of the local Backup Server.
5.18.2 2 Cannot set character set `%1!' in the login record.
Explanation: The remote Backup Server could not
set the character set to the set specified by the remote
connection.
5.19.2 2 Cannot get the language currently in use.
Explanation: The remote Backup Server could not
set the language to its default setting for the initial
connection from a client of the local Backup Server.
5.20.2 2 Cannot set language `%1!' in the login record.
Explanation: The remote Backup Server could not
set the language specified by the remote connection.
5.21.2 2 Remote DUMP/LOAD is not allowed when
interfacing to a stripe for device `%1!'.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
6.28.1 1 Dumpfile name `%1!' section number %2! mounted on
%3! `%4!'
Explanation: This message has a critical role. It
contains the file name assigned to the archive file at
dump time. If the dump goes to a multifile volume, the
user or the application must record the dumpfile name
in persistent storage and specify it at load time in order
to locate the file for loading from the multifile archive.
If the dumpfile name is lost, it will be necessary to scan
the tape off- line with the commands given under
message 4.12.2 to locate the dumpfile name.
6.29.1 1 unnamed dumpfile, section number %1! mounted on
device `%2!'
Explanation: Dumpfile name is lost. See above
message.
6.30.1 1 Device %1!: Volume cataloguing complete.
Explanation: This is an informational message
indicating that the load with listonly command has
completed successfully for the specified archive
device.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
735
6.31.2 2 Volume rejected.
Explanation: Backup Server refuses to use the
mounted volume. Adjacent messages provide more
detail. The volume either has non-ANSI structure or
there is a Backup Server programming error.
6.32.2 2 %1!: volume not valid or not requested (server: %2!,
session id: %3!.)
Explanation: The data on the device is not in proper
dump format. If you are loading, use another volume.
If you are dumping, user may overwrite.
6.33.2 2 %1!: Volume already contains %2! kilobytes, which is
larger than the specified capacity of %3! kilobytes.
Explanation: A multi-file dump device contains
more data than was specified in the capacity clause.
6.34.2 2 \n%1!\n%2!\n%3!
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
6.35.2 2 Volume validation error: bad magic number %1!,
expected %2!.
Explanation: Indicates a non-Sybase archive
mounted on the drive. Replace with a Sybase dump
archive.
6.36.2 2 Header labels of rejected volume:
Explanation: Preamble message to display labels of
rejected volume.
6.37.2 2 Volume validation error: Load block size of %1! must
equal volume block size of %2!.
Explanation: Indicates a non-Sybase archive (illegal
block size) mounted on the drive. Replace with a
Sybase dump archive.
6.38.1 1 Header labels of volume on `%1!':
Explanation: Information, no user action necessary.
6.39.0 0 tape drive
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
Number Severity Text and Explanation
Backup Server Error Messages 5.1.2 - 6.89.2
736
6.40.0 0 disk
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
6.41.1 1 Header labels of mounted volume:
Explanation: Preamble message to display labels of
mounted volume.
6.42.0 0 disk file
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
6.43.0 0 floppy disk
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
6.44.0 0 device
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
6.45.1 1 Be sure to remove the tape/floppy from drive %1!
(server: %2!, session id: %3!).
Explanation: Reminder message appears when
nounload (default) is specified for an unloadable
device.
6.46.1 1 %1!: Mount the next volume to read.
Explanation: Requests mounting of the next volume
in sequence for load.
6.47.1 1 %1!: Mount the next volume to write.
Explanation: Requests mounting of the next volume
in sequence to continue dump.
6.48.1 1 %1!: Volume on device `%2!' has restricted access
(code %3!).
Explanation: Reports ANSI restricted-access code in
label prior to confirming overwrite request.
6.49.1 1 %1!: Volume to be overwritten on `%2!' has not
expired: creation date on this volume is %3!, expiration
date is %4!.
Explanation: Requests verification of overwrite of
unexpired volume.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
737
6.50.1 1 %1!: Dumpfile `%2!' section %3! found instead of
`%4!' section %5!.
Explanation: The volume just read is out of order.
Mount the correct volume.
6.51.1 1 %1!: Mount the next volume to search.
Explanation: Reports that the requested dumpfile
(specified by the file option) was not found on the
volume.
6.52.1 1 %1!: Volume to be overwritten on `%2!' has
unrecognized label data.
Explanation: A single file dump device has non-
Sybase dump data. This is a prompt set to the user
asking if the data is to be overwritten.
6.53.1 1 %1!: Volume on device `%2!' cannot be opened for
write access. Mount another volume.
Explanation: Check write protection.
6.54.1 1 %1!: Volume on device `%2!' is expired and will be
over written.
Explanation: A single dump file device has media
with expired dump data on it. The user is prompted
whether the data is to be overwritten.
6.55.1 1 The volume mounted on `%1!' does not belong to the
same archive as other, previously mounted volumes.
Explanation: The creation time of this volume does
not match the other volumes or stripes.
6.56.2 2 The volume mounted on device `%1!' could not be
positioned to append another dump file. This dump
device may only support one dump file per volume set.
Explanation: The mounted volume is either full, or
can only hold one dump file.
6.57.1 1 Device `%1!' supports one dump file per volume set.
Explanation: Information, no user action necessary.
6.58.1 1 Device `%1!' supports multiple dump files per volume
set.
Explanation: Information, no user action necessary.
6.61.2 2 Volume validation error: Volume change request not
allowed on non-mountable devices, device name: %1!.
Explanation: Requests mounting of next volume in
sequence to locate requested dump file.
Number Severity Text and Explanation
Backup Server Error Messages 5.1.2 - 6.89.2
738
6.65.2 2 Volume validation error: illegal volume change, device
%1!: volume for stripe %2! mounted while stripe %3!
loading still in progress.
Explanation: Reminds user that all volumes of a
dump-time stripe must complete loading on the device
before the first volume of another dump-time stripe
may begin loading.
6.66.2 2 Volume validation error: illegal volume change, device
%1!: volume mounted out of order, expected volume
%2!, got volume %3!
Explanation: Volumes must be loaded in the same
order in which they were dumped.
6.78.1 1 EXECUTE sp_volchanged\n\t@session_id =
%1!,\n\t@devname = `%2!%3!',\n\t@action = { `%4!'
| `%5!' | `%6!' }%7!%8!
Explanation: Template for sp_volchanged
execution. proceed means continue operation with the
currently mounted volume. retry means redo the
validation check that led to the prompt (presumably on
a new volume). abort means abort the entire dump or
load session.
6.80.2 2 Session %1! is exiting by request from
sp_volchanged.\nData written in this session are
incomplete and invalid.\nAborting session.
Explanation: The user requested an abort through
sp_volchanged.
6.81.2 2 Unrecognized volume change prompt id (internal
error); task must exit.
Explanation: Indicates a Backup Server
programming error. Retry the dump or load command,
avoiding unnecessary volume manipulations.
6.82.2 2 %1! is not a recognized sp_volchanged action.
Explanation: User provided an illegal @action value
to sp_volchanged. The value must be proceed, retry, or
abort.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
739
6.83.2 2 Volume validation error: Volume name mismatch,
volume name %1!, expected volume name %2!.
Explanation: Volumes within a stripe must have the
same name in the ANSI VOL1 label. It is possible for
a user to execute the dump command properly and still
receive this error at load time, if the first volume was
overwritten using the dumpvolume option and the
second volume, with a different name, was appended
to.
6.84.2 2 Volume validation error: illegal volume change,
device %1!: stripe %2! is already loaded.
Explanation: User remounted a tape for a stripe that
has already been loaded.
6.85.0 0 byte stream
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
6.86.2 2 Unexpected error reading from volume change
response message queue for device '%1!'.
Explanation: Failed to read from volume change
message queue.
6.87.1 1 %1!: Volume on device `%2!' contains user data. Erase
it or mount another volume.
Explanation: The mounted volume is not ready for
use. Erase it or exchange it for another.
6.88.1 1 Volume on device `%1!' has unrecognized format or
not formatted.
Explanation: The mounted volume is not ready for
use. Format it or exchange it for another.
6.89.2 2 The SYTAPE environment variable must be set.
Explanation: The SYTAPE environment variable
must be set before continuing.
Number Severity Text and Explanation
Backup Server Error Messages 7.1.2 - 8.17.2
740
Backup Server Error Messages 7.1.2 - 8.17.2
Number Severity Text and Explanation
7.1.2 2 Memory error: failed to allocate an `%1!' structure.
Explanation: Not enough memory available to
Backup Server. See “Note” at the top of this section.
7.2.2 2 Option `%1!': %2! is an invalid value; value must be
an even multiple of %3!.
Explanation: Illegal value for a dump or load option.
7.3.2 2 Option error: when you specify %1!, you may not
specify %2!.
Explanation: Illegal combination of options in a
dump or load command.
7.4.2 2 Option `%1!': `%2!' is an invalid value -- check the
documentation for allowable values.
Explanation: Unrecognized value specified for a
dump or load command.
7.5.2 2 `%1!' is a badly formed value string.
Explanation: Syntax error in dump or load command
option.
7.6.2 2 Option `%1!': `%2!' is an invalid volume label. The
maximum length is %3!.
Explanation: Volume label is longer than 6
characters.
7.7.2 2 Option `%1!' is not valid.
Explanation: Unrecognized dump or load option.
7.8.2 2 Option `%1!' may not be negated.
Explanation: You cannot use no with this option.
7.9.2 2 Option `%1!' does not take any value; remove `='.
Explanation: This option does not allow you to
specify a value.
7.10.2 2 Option `%1!' may not have more than one value.
Explanation: User specified more than one value
after “=”, and the option only permits one value.
7.11.2 2 Option `%1!' may not take a value when it is negated.
Explanation: User specified an option with a value
and no. The combination is illegal for this option.
CHAPTER 4 Backup Server Error Messages
741
7.12.2 2 Option `%1!' requires a value, but none was specified.
Explanation: You must specify a value for these
options: density, blocksize, capacity, dumpvolume,
retaindays, or file.
7.13.2 2 Option `%1!': `%2!' is not unique -- supply more
characters.
Explanation: User abbreviated a keyword following
a value, and the abbreviation is ambiguous.
7.14.2 2 Option error: when you specify %1!, you must also
specify %2!.
Explanation: Invalid combination of options.
7.15.2 2 Option `%1!' is not valid for the present command.
Please check the documentation for correct usage.
Explanation: load option used during a dump
command, or vice versa.
7.16.0 0 and
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
7.17.0 0 or
Explanation: Internal informational message,
usually a component of another message. No user
action necessary.
8.1.2 2 Device %1!: Failure to open for read/write. Operating
system message: `%2!'.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
8.2.2 2 Device %1!: Failure to rewind tape device.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
8.3.2 2 Device %1!: Failure to write minimum block size of
%2! bytes.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
Backup Server Error Messages 7.1.2 - 8.17.2
742
8.4.2 2 Device %1!: Auto-configuration failure. This tape
device is not supported.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
8.5.1 1 Warning, unable to open device configuration file %1!
for reading. Operating system error %2!.
Explanation: The tape auto config feature uses a
configuration file. It creates it the first time the tape
auto config tests are run. This informational message
is printed if the configuration file does not exist
already and hence it is about to create one.
8.6.1 1 Warning, the format of the device configuration %1!
file is invalid. Configuration information will not be
saved.
Explanation: Information, no user action necessary.
8.7.1 1 Warning, unable to open device configuration file %1!
for writing. Operating system error %2!. Configuration
information will not be saved.
Explanation: Information, no user action necessary.
8.8.1 1 Warning, unable to write to device configuration file
%1!. Operating system error %2!. Configuration
information will not be saved.
Explanation: Information, no user action necessary.
8.9.1 1 Warning, unable to close device configuration file %1!.
Operating system error %2!. Configuration
information will not be saved.
Explanation: Information, no user action necessary.
8.10.2 2 Device %1!: Not found in configuration file %2!.
INIT needs to be specified to configure the device.
Explanation: The tape device specified is of
unknown type to the backup server. In order to
determine its capabilities, backup server needs to run
auto configuration tests. This requires the user to
specify 'with init' clause on the dump command line,
which will overwrite the data on the tape.
8.11.1 1 Device %1!: Will be auto-configured and the results
saved in the configuration file %2!. The configuration
will take additional time.
Explanation: Information, no user action necessary.
Number Severity Text and Explanation
CHAPTER 4 Backup Server Error Messages
743
8.12.2 2 Device %1!: the operating system device type is
different than what is in the configuration file %2!.
Please remove entry for this device in the
configuration file and reconfigure the device by
issuing a DUMP with the INIT qualifier.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
8.13.2 2 Device %1!: the operating system file mark type is
different than what is in the configuration file %2!.
Explanation: The operating system file mark type is
different than what is specified in the configuration
file.
8.14.1 1 Backup Server tape configuration file %1! revision is
not compatible.
Explanation: Information, no user action necessary.
8.15.1 1 Device %1!: not found in tape configuration file. Tape
configuration will be attempted.
Explanation: Information, no user action necessary.
8.16.2 2 Device %1!: Auto-configuration failure. The device
functions as rewind on close. Please specifiy the no
rewind on close device interface.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
8.17.2 2 Device %1!: Auto-configuration failure. Internal or
system call error encountered while checking for
rewind on close.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
Number Severity Text and Explanation
Backup Server Error Messages 7.1.2 - 8.17.2
744
745
CHAPTER 5 Component Integration Services
Error Messages
This chapter gives the error number, message text, and a brief explanation
for Component Integration Services error messages.
Component Integration Services Error Messages
Number Severity Text and Explanation
11201 16 A remote table definition must be defined before the
`existing' option is used (object `%.*s').
Explanation: Use sp_helpobjectdef to compare the
table name on the remote server with the remote table
name mapped to the table in your command. If the
remote table does not exist, first create the table on the
remote server or use create table.
11202 16 Unable to create table `%.*s' because it has no remote
storage location defined. Creation of local user tables
is allowed only in the master and tempdb databases.
Explanation: Define the remote storage location
using sp_addobjectdef, then rerun this command.
11203 16 The command ’%s’ is not legal for objects of this type.
External definition: %.*s
Explanation: Adaptive Server cannot perform the
requested action. Rewrite your command using a valid
object, or contact the Object Owner if the remote
object should not be defined as type rpc.
11204 15 There is an error in the syntax of the object definition
`%.*s'.
Explanation: Command failed. Check syntax and
semantics of your object definition and rewrite the
command.
Component Integration Services Error Messages
746
11205 16 Datatype `%s' is unsupported for server `%.*s'.
Explanation: The datatype is not supported by the
server where the remote object is located. Rewrite the
command using a valid datatype.
11206 16 Unable to connect to server `%.*s'.
Explanation: Refer to the writeup “Unable to Access
Remote Server” in Appendix A “Troubleshooting” of
the Component Integration Services User's
Guide.
11207 10 Warning, table definition does not contain all columns
found in remote object `%.*s'; (defined: %d found:
%d)
Explanation: This is an informational message.
Contact the Object Owner about the warning issued in
this message.
11208 16 No column named `%.*s' found in remote object
`%.*s'.
Explanation: If the syntax is correct, refer to the
writeup “Problem Retrieving Data From Remote
Objects” in Appendix A “Troubleshooting” of the
Component Integration Services User's Guide.
11209 16 Column type mismatch in remote object `%.*s' for
column `%.*s'; (defined: %d found: %d).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11210 16 Column length mismatch in remote object `%.*s' for
column `%.*s'; (defined %d found: %d).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshootin ” of the Component Integration
Services User's Guide.
11211 16 Handling of null values in remote object `%.*s' for
column `%.*s' differs from that defined; (defined: `%s'
found: `%s').
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
Number Severity Text and Explanation
CHAPTER 5 Component Integration Services Error Messages
747
11212 16 Identity attribute mismatch for column `%.*s';
(defined: `%s' found: `%s').
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11213 16 Column count mismatch in remote object `%.*s';
(defined: %d found %d).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11214 16 Remote object `%.*s' does not exist.
Explanation: If the syntax is correct, refer to the
writeup “Unable to Access Remote Object” in
Appendix A “Troubleshooting” of the Component
Integration Services User's Guide.
11215 16 Remote object `%.*s' not uniquely identified; %d
objects with the same name and owner were found.
Explanation: The remote server contains more than
one object with the name specified by
sp_addobjectdef. Use sp_dropobjectdef to drop the
object, and reenter the object definition with an owner
name or database name to further qualify the remote
object.
11216 16 Internal Ct-Lib/Cs-Lib error %d: `%.*s'.
Explanation: Command failed due to an internal
Adaptive Server problem. Report the error to your
System Administrator.
11217 10 Entered passthru mode to server `%.*s'.
Explanation: This is an informational message. No
action is required.
11218 10 Exited passthru mode from server `%.*s'.
Explanation: This is an informational message. No
action is required.
Number Severity Text and Explanation
Component Integration Services Error Messages
748
11219 17 Cannot open a connection to site `%.*s' because there
are no free remote descriptors (RDES). Increase the
configuration parameter for user connections and
reboot the server.
Explanation: Command failed due to resource
limitation. Modify the command to fit available
resources, retry when the resource is available, or
contact your System Administrator to address the
resource problem.
11220 16 Parameter cannot be NULL.
Explanation: Adaptive Server could not perform the
requested action. Rewrite the command with an entry
for the parameter.
11221 16 No external login for suserid %d, server name `%.*s'.
Explanation: The remote server cannot be accessed
with your login. Have the Database Owner or System
Administrator set up your external login using
sp_addexternlogin.
11222 12 Parameter %d must be datatype CHAR or VARCHAR.
Explanation: Command failed. Specify an object of
the correct type.
11223 17 Insufficient memory is available to allocate structures
needed to access a remote site.
Explanation: Command failed due to resource
limitation. Modify the command to fit available
resources, retry when the resource is available, or
contact your System Administrator to address the
resource problem.
11224 16 Cannot open a connection to site `%.*s' because it does
not have PASSTHRU or RPC capabilities.
Explanation: Use sp_helpobjectdef to verify the
object is mapped to a remote server. If the server is
remote, have the System Administrator reconfigure it
to allow passthrough connections.
11225 16 Server class has not been defined for `%.*s'.
Explanation: No server class has been defined for the
remote server. Use sp_helpserver to check the server
definition, and have your System Administrator correct
the entry.
Number Severity Text and Explanation
CHAPTER 5 Component Integration Services Error Messages
749
11226 16 Server class (%d) for server `%.*s' is not supported.
Explanation: An invalid server class has been
defined for the remote server. Use sp_helpserver to
check the server definition, and have your System
Administrator correct the entry.
11227 16 Statement `%s' is unsupported by `%.*s'.
Explanation: The SQL statement uses a datatype or
syntax that is not supported by the server class of the
server where the remote object resides. Rewrite the
command using correct syntax or a valid datatype.
11228 18 Remote text/image data length less than expected for
column `%.*s'.
Explanation: Command failed due to internal
Adaptive Server problem. Report the error to your
System Administrator.
11229 16 Unable to commit transaction on remote server %.*s.
Explanation: During a transaction involving
multiple servers, the local server was unable to
broadcast a commit request to a remote server. Work
done locally as part of the transaction will be rolled
back.
11230 16 Unable to prepare transaction on remote server %.*s.
Explanation: During a transaction involving
multiple servers, the local server was unable to
broadcast a prepare request to a remote server. A
rollback request has been sent to all remote servers
involved in the transaction. Work done locally as part
of the transaction will be rolled back.
11231 16 Unable to rollback transaction on remote server %.*s.
Explanation: During a transaction involving
multiple servers, the local server was unable to
broadcast a rollback request to a remote server. Work
done locally as part of the transaction will be rolled
back.
11232 18 Unable to access cursor process status structure (PSS);
update cannot be completed.
Explanation: Command failed due to internal
Adaptive Server problem. Report the error to your
System Administrator.
Number Severity Text and Explanation
Component Integration Services Error Messages
750
11233 16 Column mismatch in remote object `%.*s' for column
`%.*s'; (column must be defined with length >= 10 or
as DATETIME).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide
11234 16 Column mismatch in remote object `%.*s' for column
`%.*s'; (column must be defined with length >= 8 or as
DATETIME).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11235 16 Column mismatch in remote object `%.*s' for column
`%.*s'; (column must be defined with length >= 26 or
as DATETIME).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11236 16 Update or `complex INSERT' of non-NULL
TEXT/IMAGE data is unsupported by server `%.*s'.
Use WRITETEXT instead.
Explanation: Adaptive Server could not perform the
requested action. Modify your command as shown in
the error message.
11237 16 TEXT/IMAGE value too long for INSERT/UPDATE
on server `%.*s'. Use WRITETEXT instead.
Explanation: Adaptive Server could not perform the
requested action. Modify your command as shown in
the error message.
11238 16 Complex INSERT of TEXT/IMAGE data is not
supported. Use WRITETEXT instead.
Explanation: Adaptive Server could not perform the
requested action. Modify your command as shown in
the error message.
11242 10 Component Integration Services recovery started.
Explanation: This is an informational message. No
action is required.
Number Severity Text and Explanation
CHAPTER 5 Component Integration Services Error Messages
751
11243 10 Component Integration Services recovery complete.
Explanation: This is an informational message. No
action is required.
11244 10 Deallocating text/image data for external object `%.*s'.
Explanation: This is an informational message. No
action is required.
11245 10 Checking external objects.
Explanation: This is an informational message. No
action is required.
11246 16 Precision or scale mismatch in remote object `%.*s' for
column `%.*s'; (defined: %d,%d found: %d,%d).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11247 16 Scale mismatch in remote object `%.*s' for column
`%.*s'; (defined: %d found: %d).
Explanation: Refer to the writeup “Problem
Retrieving Data From Remote Objects” in Appendix
A “Troubleshooting” of the Component Integration
Services User's Guide.
11248 14 Remote server `%.*s' is currently configured as read
only.
Explanation: You do not have permission to execute
this command. Contact the System Administrator to
change permissions.
11249 10 Executing Partial Query Remotely
Explanation: This is an informational message
generated by showplan. No action is required.
11250 10 EXISTS TABLE: Executing Query Remotely
Explanation: This is an informational message
generated by showplan. No action is required.
11251 10 Dynamic Update
Explanation: This is an informational message
generated by showplan. No action is required.
11252 10 Select for Update
Explanation: This is an informational message
generated by showplan. No action is required.
Number Severity Text and Explanation
Component Integration Services Error Messages
752
11253 10 Dynamic Delete
Explanation: This is an informational message
generated by showplan. No action is required.
11254 10 Select for Delete
Explanation: This is an informational message
generated by showplan. No action is required.
11255 10 Remote Cursor Operation
Explanation: This is an informational message
generated by showplan. No action is required.
11256 10 %.*s
Explanation: This is an informational message
generated by showplan. No action is required.
11257 10 %.*s
Explanation: This is an informational message
generated by showplan. No action is required.
11258 11 No column with column id `%d' found in local table.
Explanation: Check the local table for the column
not found and re-enter the command with the correct
name.
11259 10 Warning, no mapping for remote column named `%.*s'
in local object `%.*s'.
Explanation: This is an informational message.
Contact the Object Owner about the warning issued in
this message.
11263 10 Server Name: %.*s
Explanation: This is an informational message
generated by showplan. No action is required.
11264 10 Text of generated SQL:
Explanation: This is an informational message
generated by showplan. No action is required.
11265 10 Executing Query Remotely
Explanation: This is an informational message
generated by showplan. No action is required.
11266 16 The sp_columns result set returned by the remote
server is incomplete. Each row must contain at least
%d columns, but only %d are present.
Explanation: Command failed due to remote server
problem. Report the error to your System
Administrator.
Number Severity Text and Explanation
CHAPTER 5 Component Integration Services Error Messages
753
11267 16 Unable to create table '%.*s' on remote server; this
server not configured for heterogeneous data access.
Explanation: Command failed. Contact your System
Administrator to install the Extended Enterprise
Option of Adaptive Server Enterprise prior to
accessing remote servers that are not server class
sql_server.
11268 16 Unable to insert into a text/image column because the
table does not contain a unique index.
Explanation: Command failed. The table must have
a unique index to execute a select...into or
insert...select command, since the table has text or
image columns and is owned by a server of class
direct_connect or sds.
11269 16 The optimizer could not find a unique index which it
could use to retrieve the resulting timestamp value
Explanation: Command failed due to invalid or
illegal request. Check syntax, semantics, and
permissions. Take any corrective action indicated by
message.
11270 16 Column '%.*s' does not allow NULL. Any column
defined as a parameter column for RPC tables must
allow NULL. A parameter column is a column whose
name begins with an underscore.
Explanation: Adaptive Server could not perform the
requested action. Rewrite the command and specify
NULL in the parameter column definition.
11271 16 Column '%.*s' must precede all parameter columns. A
parameter column is a column whose name begins
with an underscore.
Explanation: Adaptive Server could not perform the
requested action. Rewrite the command and put result
column definitions before parameter column
definitions-all column names that begin with an
underscore must appear at the end of the list.
11272 16 Action requested is not valid for remote tables (%.*s).
Explanation: Command failed due to invalid request.
You cannot enter this command using proxy tables (the
command can only be used with local tables).
Number Severity Text and Explanation
Component Integration Services Error Messages
754
11273 10 Encounter %d conversion errors during processing of
external statistics; some rows have been ignored.
Explanation: update statistics cannot generate
complete statistics because the proxy table has
columns with datatypes or widths that are different
from the corresponding column at the remote location.
11277 16 Operating system error %d: ’%.*s’.
Explanation: Command failed. Check query syntax
and semantics.
11278 16 The file at the specified path is not a directory (%.*s).
Explanation: Command failed. Check query syntax
and semantics.
11279 16 Only the file name can be changed, and it is not
included in the SET list.
Explanation: Command failed. Check query syntax
and semantics.
11280 16 The pathname length must be 255 bytes or less.
Explanation: Command failed. Check query syntax
and semantics.
11281 16 Cannot enable full-text search services because there is
no license available.
Explanation: Command failed. Check your CIS
configuration.
11282 16 Cannot create the file (%.*s). A file with the same
name already exists.
Explanation: Command failed. Check query syntax
and semantics.
11283 16 External file access is not enabled or not licensed.
Explanation: Command failed. Check your CIS
configuration.
11284 16 The target of a ’select into existing table’ statement
must be a proxy table.
Explanation: Command failed. Check query syntax
and semantics.
Number Severity Text and Explanation
755
CHAPTER 6 Adaptive Server Error Messages
This chapter contains the text of all the numbered Adaptive Server error
messages through 14007. Each message is followed by a short explanation
and brief instructions on what to do when you see the error.
Messages in the 17xxx and 18xxx series are informational and error
messages returned by stored procedures. For help with a system procedure
message, refer to the discussion of that procedure in the "System
Procedures" section of the Adaptive Server Reference Manual. ASE
functions and commands used in a stored procedure may generate their
own error messages, with an error number below 17xxx and severity of 10
or higher; for help with those messages, refer to the appropriate error
number in this chapter.
Since dbcc checkstorage faults are somewhat different in concept from
other error messages, they do not appear in this chapter. For a listing of
dbcc checkstorage faults, see “How to Analyze dbcc checkstorage Faults”
in the Encyclopedia of Tasks chapter.
Working with Error Messages
This chapter shows all numbered messages applicable to Adaptive Server
Versions 11.0.x through 12.0. The message text itself corresponds to the
Version 12.0 text. Accordingly, specific messages may or may not appear
in your server version, and the message text may differ from what is
shown here.
Warning! If your site utilizes any applications based on Adaptive Server
error messages, note that characteristics such as the text of a message, its
severity, and so on are subject to change from one version to the next.
Messages may also be withdrawn or replaced by new messages. Exercise
caution, therefore, in using the existence, or any other characteristics of a
message, as the basis for your applications.
Working with Error Messages
756
Use this chapter as an error reference. Look up the error number and note the
severity. Then use the accompanying explanation (available for most, though
not all, messages) to determine your next course of action. If the error is one of
the commonly occurring server messages documented in the chapter “Error
Message Writeups,” the explanation will refer you to that chapter. In other
cases, it gives you guidance on the nature of the error and what to do next.
Generally speaking, the severity level of a message corresponds to the type and
severity of the problem that the server encountered. For a complete description
of severity levels, see “Adaptive Server Error Logging” in the System
Administration Guide.
CHAPTER 6 Adaptive Server Error Messages
757
Server Error Messages 1 - 199
Number Severity Text and Explanation
21 10 WARNING - Fatal Error %ld occurred at %S_DATE. Please note the error and time,
and contact a user with System Administrator (SA) authorization.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the
message.
101 15 Line %d: SQL syntax error.
Explanation: Command failed. Check syntax and semantics.
102 15 Incorrect syntax near `%.*s'.
Explanation: Refer to the writeup for Error 102.
103 15 The %S_MSG that starts with `%.*s' is too long. Maximum length is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
104 15 Order-by items must appear in the select-list if the statement contains set operators.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
105 15 Unclosed quote before the character string `%.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
106 16 Too many table names in the query. The maximum allowable is %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
107 15 The column prefix `%.*s' does not match with a table name or alias name used in the
query. Either the table is not specified in the FROM clause or it has a correlation name
which must be used instead.
Explanation: Refer to the writeup for Error 107.
108 15 The order-by position number `%ld' is out of range of the number of items in the select-
list.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
109 15 There are more columns in the INSERT statement than values specified in the VALUES
clause. The number of values in the VALUES clause must match the number of columns
specified in the INSERT statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Server Error Messages 1 - 199
758
110 15 There are fewer columns in the INSERT statement than values specified in the VALUES
clause. The number of values in the VALUES clause must match the number of columns
specified in the INSERT statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
111 15 %s must be the first command in a query batch.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
112 15 Variables are not allowed in %s statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
113 15 Missing end comment mark '*/'.
Explanation: Command failed. Check syntax and semantics.
114 15 `%.*s' is not a recognized DUMP DATABASE/TRANSACTION truncation option.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
115 15 The offset `%d' given in a CONTROLROW command does not correspond to the
beginning of a statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
116 15 The symbol `*' can only be used for a subquery select list when the subquery is
introduced with EXISTS or NOT EXISTS.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
117 15 The %S_MSG name `%.*s' contains more than the maximum number of prefixes. The
maximum is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
118 15 `%s' option name length plus value string length must total less than %d characters.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
119 15 Must pass parameter number %d and subsequent parameters as `@name = value'. Once
the form `@name = value' has been used, all subsequent parameters must be passed in
the form `@name = value'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
120 15 The SELECT list for the INSERT statement contains fewer items than the INSERT list.
The number of SELECT values must match the number of INSERT columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
759
121 15 The SELECT list for the INSERT statement contains more items than the INSERT list.
The number of SELECT values must match the number of INSERT columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
122 15 The debug option `%d' is larger than the maximum allowed. The highest option
available is %d.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
123 15 Must attach a value to the binary prefix `0x'; zero-length binary value is not allowed.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
124 15 CREATE PROCEDURE contains no statements.
Explanation: Command failed. The CREATE PROCEDURE command must contain
at least one SQL statement.
126 15 Cannot nest CREATE PROCEDURE statements.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
127 15 This CREATE may only contain 1 statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
128 15 The name `%.*s' is illegal in this context. Only constants, constant expressions, or
variables allowed here. Column names are illegal.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
129 15 Fillfactor `%d' is not a valid percentage; fillfactor must be between 1 and 100.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
130 15 The comparison operator `= ALL' is not currently supported.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
131 15 The size (%d) given to the %S_MSG `%.*s' exceeds the maximum. The largest size
allowed is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
132 15 The label `%.*s': has already been declared. Label names must be unique within a query
batch or stored procedure
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
Server Error Messages 1 - 199
760
133 15 A GOTO statment references the label `%.*s' but the label has not been declared.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
134 15 The variable name `%.*s' has already been declared. Variable names must be unique
within a query batch or stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
135 15 Cannot use a BREAK statement outside the scope of a WHILE statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
136 15 Cannot use a CONTINUE statement outside the scope of a WHILE statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
137 15 Must declare variable `%.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
138 15 Illegal correlation clause in a subquery.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action. (This error is not raised in Release 11.0 and higher.)
139 15 Cannot assign a default value to a local variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
140 15 Can only use IF UPDATE within a CREATE TRIGGER.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
141 15 A SELECT statement that assigns a value to a variable must not be combined with data-
retrieval operations.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
143 15 A compute-by item was not found in the order-by list. All expressions in the compute-
by list must also be present in the order-by list
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
144 15 Cannot use an aggregate in an expression used for the by-list of a GROUP BY clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
145 15 A subquery with no aggregate functions may only contain expressions in its GROUP
BY clause that are in the select-list.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
761
146 15 Cannot perform an aggregate function on a column from a table not declared in the same
subquery.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
147 15 An aggregate function may not appear in a WHERE clause unless it is in a subquery
that is in a HAVING clause, and the column being aggregated is in a table named in a
FROM clause outside of the subquery.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
148 15 Incorrect time syntax in time string `%.*s' used with WAITFOR.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
149 15 Time value `%.*s' used with WAITFOR is not a legal value. Check date/time syntax.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
150 15 Both terms of an outer join must contain columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
151 15 `%.*s' is an invalid money value.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
152 15 Subqueries that use DISTINCT with a GROUP BY clause are not currently supported.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action. (This error is not raised in Release 11.0 and higher.)
153 16 Variables/Parameters are not allowed in the ORDER BY clause.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
154 15 %S_MSG is not allowed in %S_MSG.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
155 15 `%.*s' is not a recognized %s option.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
156 15 Incorrect syntax near the keyword `%.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
158 15 Too many ORDER BY expressions. The maximum is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
Server Error Messages 1 - 199
762
159 15 For DROP INDEX, must give both the table and the index name, in the form
tablename.indexname
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
160 15 Rule does not contain a variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
161 15 Rule contains more than one variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
162 15 The select list item identified by the order by number `%ld' is a `*', rather than a column
name. When ordering by column number, a column name must appear in the select list
position that corresponds to the order by number.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
163 15 The COMPUTE BY list does not match the ORDER BY list.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
164 15 GROUP BY expressions must refer to column names.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
165 16 Privilege %s may not be GRANTed or REVOKEd.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
166 15 %s does not allow specifying the database name as a prefix to the object name.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
167 16 May not create a trigger on a temporary object.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
168 15 The %S_MSG `%.*s' is out of the range of machine representation (%d bytes).
Explanation: Command failed. Check syntax and semantics.
169 15 Expression `%d' and `%d' in the ORDER BY list are same. Expressions in the ORDER
BY list must be unique.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
171 15 Can't use SELECT INTO in Browse Mode.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
763
172 15 Can't use HOLDLOCK in Browse Mode
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
173 15 The definition for column `%.*s' must include a datatype.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
174 15 The function `%.*s' requires %d arguments.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
175 15 Functions may only be nested to level %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
176 15 Function `%.*s' is not yet implemented.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
177 15 %s cannot create a temporary object (with `#' as the first character name.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
178 15 A RETURN statement with a return status may only be used in a SQL stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
179 15 Can't use the OUTPUT option when passing a constant to a stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
180 15 There are too many parameters in this CREATE PROCEDURE statement. The
maximum number is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
181 15 Can't use the OUTPUT option in a DECLARE statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
182 15 Table and column names must be supplied for the READTEXT or WRITETEXT utility.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
183 15 The scale (%d) for column `%.*s' must be within the range %d to %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
Server Error Messages 1 - 199
764
184 15 Invalid money datatype specification for column `%.*s'. Only money(19, 4) is allowed
for non-external tables.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
185 15 Data stream is invalid for WRITETEXT command in bulk form.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
186 15 Data stream missing from WRITETEXT command.
Explanation: Command failed. Check the syntax of the WRITETEXT command.
187 15 Odd number of bytes in IMAGE data.
Explanation: While inserting text/image data, an upper limit on the send may have
been reached. Check the data sent and consider using ct_command or other alternative.
188 15 Can't specify a log-device in a CREATE DATABASE statement without also specifying
at least one non-log-device.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
189 15 Function `%.*s' requires %d to %d arguments.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
190 15 Can not update the global variable `%.*s'.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
191 15 Some part of your SQL statement is nested too deeply. Please re-write the query or break
it up into smaller queries.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
192 15 Can't create a view inside a stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
193 15 The object or column name starting with `%.*s' is too long. The maximum length is %d
characters.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
195 15 `%.*s' is not a recognized %S_MSG.
Explanation: Command failed due to invalid or illegal request. Adaptive Server
cannot perform the requested action.
196 15 SELECT INTO must be the first query in a SQL statement containing set operators.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
765
Server Error Messages 200 - 299
197 15 WITH CHECK OPTION is not allowed in the definition of a union view.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
198 15 Browse mode is invalid for statements containing set operators.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
199 15 An INSERT statement may not contain a SELECT statement that assigns values to a
variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
201 16 Procedure %.*s expects parameter %.*s, which was not supplied.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
202 11 Internal error -- Unable to open table at query execution time.
Explanation: Command failed. There may be a Adaptive Server problem. Contact
Sybase Technical Support. (This error is not raised in Release 11.1 and higher.)
203 16 The name `%.*s' is not a valid identifier.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
204 20 Normalization error; node %s
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
205 16 All queries in a SQL statement containing set operators must have an equal number of
expressions in their target lists.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
206 16 Operand type clash: %s is incompatible with %s
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Server Error Messages 200 - 299
766
207 16 Invalid column name `%.*s'.
Explanation: Refer to the writeup for Error 207.
208 16 %.*s not found. Specify owner.objectname or use sp_help to check whether the object
exists (sp_help may produce lots of output).
Explanation: Refer to the writeup for Error 208.
209 16 Ambiguous column name %.*s
Explanation: Command failed. Check syntax and semantics. A column name may
need the full table specification or alias.
210 16 Syntax error converting DATETIME from BINARY/VARBINARY string.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
211 16 Syntax error converting SMALLDATETIME from BINARY/VARBINARY string.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
212 16 Expression result length exceeds maximum: max - %d found - %d
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
213 16 Insert error: column name or number of supplied values does not match table definition.
Explanation: Refer to the writeup for Error 213.
214 16 Cannot convert parameter %.*s to type %.*s expected by procedure.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
216 20 Attempt to automatically drop temporary table failed.
Explanation: Refer to the writeup for Error 216.
217 16 Maximum stored procedure nesting level exceeded (limit %d).
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
218 16 Given parameter %.*s is too large; maximum size for this parameter is %d bytes.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
219 16 Print format failed to match with a result column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
220 16 Arithmetic overflow error for type %s, value = %ld.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
767
221 16 Column of type (%s) does not allow nulls. It may not be compared with null.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
222 20 Unintelligible query plan step encountered.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
223 11 Object %ld specified as a default for tabid %ld, colid %d is missing or not of type default.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
224 11 Object %d specified as a rule/check constraint for tabid %d, colid %d is missing or not
of type default.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
225 11 Cannot run query--referenced object (name %.*s) dropped during query optimization.
Explanation: Refer to the writeup for Error 225.
226 16 %s command not allowed within multi-statement transaction.
Explanation: Refer to the writeup for Error 226.
227 16 Arithmetic overflow error ocurred while converting the string `%.*s' to type %s.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
228 14 Query is based on a view that no longer exists (id = %ld)--cannot run.
Explanation: Command failed. Check your Adaptive Server environment for the
object not found and re-enter the command with the correct name. (This error is not raised
in Adaptive Server 11.1 and higher.)
229 14 %s permission denied on object %S_OBJID, database %S_DBID, owner %.*s
Explanation: Refer to the writeup for Error 229.
230 14 %s permission denied on column %.*s of object %S_OBJID, database %S_DBID,
owner %.*s
Explanation: You do not have the permission to execute this command. Have the
object owner or a user with the needed role run this command.
231 11 Getdefault: no such default. id=%ld dbid=%d
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
232 16 Arithmetic overflow error for type %s, value = %f.
Explanation: Refer to the writeup for Error 232.
233 16 The column %.*s in table %.*s does not allow null values.%S_EED
Explanation: Refer to the writeup for Error 233.
Number Severity Text and Explanation
Server Error Messages 200 - 299
768
234 16 There is insufficient result space to convert MONEY value to CHAR.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
235 16 Precision error during %S_MSG conversion of %s value `%s' to a %s field.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
236 16 The conversion from CHAR to MONEY resulted in a MONEY overflow error.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
237 16 There is insufficient result space to convert MONEY value to %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
238 16 There is insufficient result space to convert %s value (= %d) to MONEY.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
239 16 Table `%.*s' does not exist. Please refer to sysobjects for correct name.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
240 16 There is insufficient result space to convert DATETIME value to CHAR.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
241 16 Scale error during %S_MSG conversion of %s value `%s' to a %s field.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
242 16 The conversion of CHAR to DATETIME resulted in a DATETIME value out of range.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
243 16 Type `%.*s' is not a defined system type.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
244 16 The conversion of CHAR value `%.*s' overflowed an INT1 field, use a larger integer
field.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
245 16 Domain error during %S_MSG conversion of %s value `%s' to a %s field.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
769
246 16 The conversion of CHAR value `%.*s' overflowed an INT2 field, use a larger integer
field.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
247 16 Arithmetic overflow during %S_MSG conversion of %s value `%s' to a %s field .
Explanation: Refer to the writeup for Error 247.
248 16 The conversion of CHAR value `%.*s' overflowed an INT4 field. Maximum integer
value exceeded.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
249 16 Syntax error during %S_MSG conversion of %s value `%s' to a %s field.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
251 16 Unable to allocate ancillary table for query optimization. Maximum number of tables in
a query (%d) exceeded.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
252 16 Can't group by a bit field.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
253 16 Maximum number of group-by expressions exceeded. Limit is %d, found %d aggregate
expressions.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
254 16 Maximum number of columns in a work table (%d) exceeded.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
255 16 Size of row in the worktable for grouped aggregate, %d bytes, exceeds the maximum row
size (%d bytes). Cannot run this query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
256 16 The data type `%s' is invalid for the %s function. Allowed types are: CHAR/VARCHAR
and BINARY/VARBINARY.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 200 - 299
770
257 16 Implicit conversion from datatype `%s' to `%s' is not allowed. Use the CONVERT
function to run this query.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
258 20 Database `%.*s' missing during query recompile.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
259 16 Ad-hoc updates to system catalogs not enabled. A user with System Security Officer
(SSO) role must reconfigure system to allow this.
Explanation: Refer to the writeup for Error 259.
261 16 `%.*s' is not a recognized global variable.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
262 16 %s permission denied, database %S_DBID, owner %.*s
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
263 16 Must specify table to SELECT * FROM.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
264 16 Column name %.*s appears more than once in the result column list.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
265 16 Insufficient result space for %S_MSG conversion of %s value `%s' to a %s field.
Explanation: See the writeup for Error 265. If this error was raised when using a
system stored procedure on large databases or devices, it may be due to an Adaptive
Server problem. Contact Sybase Technical Support to upgrade to a version in which the
problem is resolved.
266 16 Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRAN is
missing. Previous count = %ld, Current count = %ld.
Explanation: Check command syntax for missing COMMIT or ROLLBACK
TRANSACTION. Use @@trancount in stored procedures to check transaction count.
267 16 Object `%.*s' cannot be found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
268 16 You can't run SELECT INTO in this database. Please check with the Database Owner.
Explanation: Refer to the writeup for Error 268.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
771
269 16 NULL value cannot be specified for conversion from datatype `%s' to `%s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
270 16 Table `%.*s' can't be modified.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
272 16 Can't update a TIMESTAMP column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
273 10 Warning: A non-null value cannot be inserted into a TIMESTAMP column by the user.
The database timestamp value has been inserted into the TIMESTAMP field instead.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
274 20 A SYSTEM exception was raised with an unrecognized minor number %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
276 16 The parameter `%.*s' in the procedure `%.*s' was not declared as an OUTPUT
parameter.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
277 16 There was a transaction active when exiting the stored procedure `%.*s'. The temporary
table `%.*s' was dropped in this transaction either explicitly or implicitly. This transaction
has been aborted to prevent database corruption.
Explanation: Refer to the writeup for Error 277.
278 16 TEXT, IMAGE and off-row Java datatypes may not be used in a GROUP BY clause.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
279 16 TEXT and IMAGE datatypes and off-row Java datatypes are invalid in this subquery or
aggregate expression.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
280 16 Only TEXT and IMAGE datatypes are valid with the TEXTPTR function.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
281 16 %d is not a valid style number when converting from DATETIME to a character string.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Number Severity Text and Explanation
Server Error Messages 200 - 299
772
282 10 Procedure `%.*s' attempted to return a status of NULL, which is not allowed. A status
of 0 will be returned instead.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
283 16 You can't use browse mode with DBLIB 2.0 -- you must upgrade to DBLIB 4.0 in order
to run this query.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
284 16 Rules may not be bound to TEXT or IMAGE datatypes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
285 16 READTEXT and WRITETEXT commands may not be used with views.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
286 16 The logical tables INSERTED and DELETED may not be updated.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
287 16 %s command not allowed within a trigger.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
288 16 The PATINDEX function operates on CHAR, VARCHAR, and TEXT datatypes only.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
290 16 Trace 3604 is illegal within a stored procedure.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
291 16 Access to sysgams is disallowed.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
292 16 There is insufficient result space to convert SMALLMONEY value to CHAR.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
294 16 The conversion from CHAR to SMALLMONEY resulted in a SMALLMONEY
overflow error.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
773
Server Error Messages 300 - 399
296 16 The conversion of CHAR to SMALLDATETIME resulted in a SMALLDATETIME
value out of range.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
297 16 There is insufficient result space to convert SMALLDATETIME value to CHAR.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
298 16 The conversion from DATETIME to SMALLDATETIME resulted in a
SMALLDATETIME overflow error.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
Number Severity Text and Explanation
Number Severity Text and Explanation
301 16 Query contains an illegal outer-join request.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
303 16 The table `%.*s' is an inner member of an outer-join clause. This is not allowed if the
table also participates in a regular join clause.
Explanation: Semantic error in query. Inner join and outer join were mixed.
304 16 The table `%.*s' is outer-joined with itself.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
305 16 The column `%.*s' (user type:%.*s) is joined with `%.*s' (user type:%.*s). The user
types are not compatible: underlying types must be identical in order to join.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
306 16 TEXT and IMAGE datatypes may not be used in a WHERE clause, except with the LIKE
expression.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Server Error Messages 300 - 399
774
307 10 Index `%.*s' specified as optimizer hint in the FROM clause of table `%.*s' does not
exist. Optimizer will choose another index instead.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
308 20 Table not open for range table entry `%d', objid `%ld', dbid `%d'.
Explanation: Refer to the writeup for Error 308.
309 20 Wrong sdes for range table entry `%d'. Expected object `%ld', dbid `%d', got object `%ld',
dbid `%d'.
Explanation: Incorrect sdes was obtained due to an Adaptive Server problem. Contact
Sybase Technical Support to upgrade to a version in which the problem is resolved.
310 10 Index id %d on table id %d cannot be used in the optimization of a query as it is
SUSPECT. Please have the SA run DBCC REINDEX on the specified table.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
311 16 The optimizer could not find a unique index which it could use to scan table `%.*s' for
cursor `%.*s'.
Explanation: Refer to the writeup for Error 311.
312 16 Index id %d on table `%.*s' is explicitly specified in cursor `%.*s' declared for update.
This index is either not unique or its key includes a column in the for update of list. This
cursor my be closed on an update or a delete.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
313 16 The optimizer could not find a unique index which it could use to perform an isolation
level 0 scan on table `%.*s'.
Explanation: Refer to the writeup for Error 313.
314 16 WARNING: A non-unique clustered index has been forced on an isolation level 0 scan
on table ’%.*s’. If the scan must restart, the scan will be repositioned at the beginning of
the duplicate key group. Thus, it is possible that this can infinitely loop.
Explanation: Refer to the writeup for Error 314.
315 16 Internal error - The SQL Server was unable to find a join order to run this query. Please
inform technical su pport.
Explanation: Internal Adaptive Server error. A table may be circularly dependent upon
itself. Contact Sybase Technical Support.
316 17 Cannot compile the query because the space required for the search arguments (%d
bytes) exceeds the maximum amount of memory that can be granted. Try reducing the
number of search arguments.
Explanation: Reduce number of sargs. Try breaking up the query into multiple queries.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
775
317 16 A subquery in this query is correlated to an inner table of an outerjoin. This is not allowed
in TSQL semantics.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
318 18 sysstatistics catalog was read and an inconsistency was found, please run update statistics
and contact Sybase Technical Support
Explanation: There was an internal Adaptive Server problem. Perform the diagnostic
action indicated in the message. (Version 11.9.2 and higher.)
319 18 Statistics cannot be read for table '%.*s', column '%.*s' due to previous errors
Explanation: There was an internal Adaptive Server problem. (Version 11.9.2 and
higher.)
320 10 Index id %d on table id %d cannot be used in the optimization of a query as it is
SUSPECT. Please drop and re- create the index on the specified table.
Explanation: Use sp_helpindex to obtain index information, then drop and recreate the
index. (Version 11.9.2 and higher.)
321 18 Internal statistics calculation inconsistency. Please contact Sybase technical support
Explanation: (Version 11.9.2 and higher.)
322 18 Internal error: systabstats statistics could not be read, please contact Sybase Technical
Support.
Explanation: (Version 11.9.2 and higher.)
323 10 WARNING: Edited statistics are overwritten. Table: '%.*s' (objectid %ld), column:
'%.*s'.
Explanation: (Version 11.9.2 and higher.)
324 10 Invalid simulated value (%ld) ignored for %S_MSG '%.*s'. Actual value (%ld) used
instead.
Explanation: (Version 11.9.2 and higher.)
325 18 Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing
the query plan, check its correspondence to the query. If not, please contact Sybase
Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
326 16 ALTER TABLE ’%.*s’ failed. The table is %d-way partitioned, and a %d-way parallel
plan was generated due to lack of parallel resources. Increase the value of ’max parallel
degree’ and ’number of worker processes’ to at least %d, and try again.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
Number Severity Text and Explanation
Server Error Messages 400 - 499
776
Server Error Messages 400 - 499
Number Severity Text and Explanation
401 16 Unimplemented command or expression %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
403 16 Invalid operator for datatype op: %s type: %s.
Explanation: Refer to the writeup for Error 403.
404 19 Too many ANDs or ORs in expression (limit %d per expression level). Try splitting
query or limiting ANDs and ORs.
Explanation: Refer to the writeup for Error 404.
405 20 Cannot route query results - query internal representation corrupted - for operation %s,
datatype %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
406 23 Ord_needed: Can't find index for varno=%d, objid=%ld.
Explanation: The database may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
407 19 You query creates too many internal work tables and/or user tables: the maximum is %d.
Simplify the query and try again.
Explanation: Command failed when a configurable limit was exceeded. Reconnect to
Adaptive Server and perform any corrective action indicated by the message. Report the
error to your System Administrator.
408 20 Is_var: Unknown data type %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
409 16 The %s operation cannot take a %s datatype as an argument.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
410 20 Compute clause #%d, `by' expression #%d is not in the order-by list.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
CHAPTER 6 Adaptive Server Error Messages
777
411 20 Compute clause #%d, aggregate expression #%d is not in the select list.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
412 16 Cannot update more than 1 sysindexes row at a time.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
413 17 Maximum procedure %s count exceeded. Limit is %d. Modify the procedure to use
fewer %ss.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
414 16 The current query would generate a key size of %d for a work table. This exceeds the
maximum allowable limit of %d.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
415 16 The current query would require an index on a work table to be built with %d keys. The
maximum allowable number of keys is %d.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
416 16 Create of work table failed because row size would be %d. This exceeds the maximum
allowable size of a row in a table, %d.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
418 20 Can't find the real column name corresponding to the column heading `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
420 16 TEXT and IMAGE datatypes may not be used in an ORDER BY clause.
Explanation: Check query syntax.
421 16 TEXT, IMAGE and off-row Java datatypes may not be selected as DISTINCT.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
422 19 Too many nested expressions or logical operators to compile. Try splitting query or
limiting ANDs and ORs.
Explanation: Command failed when a configurable limit was exceeded. Reconnect to
Adaptive Server and perform any corrective action indicated by the message. Report the
error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 400 - 499
778
423 20 Table referenced in a foreign key constraint is missing, database = `%S_DBID', table =
`%S_OBJID'.
Explanation: This error is caused by an Adaptive Server problem which allows a
referenced table in a referential integrity constraint to be dropped. Contact Sybase
Technical Support to upgrade to a version in which the problem is resolved.
424 20 Failed to enforce a referential constraint, database = `%S_DBID', table = `%S_OBJID'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run. (This error is not raised in Adaptive Server 11.1 and
higher.)
425 20 Referencing table in a foreign key constraint is missing, database = `%S_DBID', table =
`%S_OBJID'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
426 20 Primary key column referenced in a foreign key constraint is missing, database =
`%S_DBID', table = `%S_OBJID'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
427 20 Referencing column in a foreign key constraint is missing from system catalog, database
= `%S_DBID', table = `%S_OBJID'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
428 20 There are more than %d referential constraints on table %.*s. Please reduce the number
of referential constraints before trying this query.
Explanation: Refer to the writeup for Error 428.
429 18 Invalid constraint type passed to compile referential constraint. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
430 18 Constraint id info in the resvar for check constraints is missing. This is an internal error,
database = `%S_DBID', table = `%S_OBJID'.
Explanation: This error occurs when Adaptive Server fails to find an expected
constraint during query processing. Contact Sybase Technical Support to upgrade to a
version in which the problem is resolved.
431 26 Node off RESDOM is not MULTARG as expected.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
779
432 16 Security Label datatypes may not be used in an ORDER BY clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
433 17 Unable to allocate work table to process referential constraint. Query exceeds the
maximum limit (%d) of work tables. Either simplify the query or reduce the number of
referential constraints on the tables involved in the query.
Explanation: Resource error while trying to allocate worktable to process deferred
update on a table with referential constraints. Take corrective action described in
message.
434 16 Work table cannot be allocated for processing the order by clause which requires a sort.
Maximum limit (%d) of work tables is exceeded while processing this query. Simplify the
query and retry.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
435 16 Database `%.*s' is not available. The `%s' statement will not be executed because the
cross-database referential constraint on table `%.*s' cannot be enforced. Contact your
System Administrator about the availability of database `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
436 16 The `%s' statement will not be executed because the cross-database referential constraint
on table `%.*s' cannot be enforced. A table or constraint definition is missing in database
`%.*s'. Contact your System Administrator.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
441 18 Deadlock occurred in SQL Process %d, While accessing referencing tables.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
442 16 Maximum number of user tables under all sides of a UNION statement can not exceed
%d. Please simplify the query and retry.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
444 16 The index %d for the table %ld was not found in database %d. The index may have been
dropped while this query was being compiled.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
445 16 Compute clause referenced too many variable length columns; note that each aggregate
occupies 2 columns, except for the AVG which occupies 4 columns. The maximum
number of variable length columns is %d
Explanation: Adaptive Server could not perform the requested action. Modify query to
conform to the specified limits.
Number Severity Text and Explanation
Server Error Messages 500 - 599
780
Server Error Messages 500 - 599
446 16 The COMPUTE clause #%d, aggregate expression #%d may produce a result that is
wider than 255 bytes, the maximum computed result allowed.
Explanation: Adaptive Server could not perform the requested action. Check query.
Number Severity Text and Explanation
Number Severity Text and Explanation
501 20 There is no result-list for a SELECT statement.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Adaptive Server
11.0 and higher.)
502 18 Internal error encountered in merging rows; resubmit query batch.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
504 11 Stored procedure `%.*s' not found.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
508 20 No begin-row pointer found in plan.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
509 11 User name `%.*s' not found.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
510 20 Bad eop type 0x%x .
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
511 16 Attempt to update or insert row failed because resultant row of size %d bytes is larger
than the maximum size (%d bytes) allowed for this table.
Explanation: Refer to the writeup for Error 511.
512 16 Subquery returned more than 1 value. This is illegal when the subquery follows =, !=, <,
<= , >, >=, or when the subquery is used as an expression.
Explanation: Refer to the writeup for Error 512.
CHAPTER 6 Adaptive Server Error Messages
781
513 16 A column insert or update conflicts with a rule imposed by a previous CREATE RULE
command. The command was aborted. The conflict occurred in database `%S_DBID',
table `%S_OBJID', column `%.*s'
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message. (Not raised
in Release 11.0 and higher.)
514 20 Expression stack overflow. Usually this is because built-in functions have been nested
too deeply. Try to rephrase the query using less deeply nested functions.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
515 16 Attempt to insert NULL value into column `%.*s', table `%.*s'; column does not allow
nulls. Update fails.%S_EED
Explanation: Refer to the writeup for Error 515.
516 18 Attempt to get system date/time failed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
517 16 Adding a value to a %s field caused overflow.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
518 16 Cannot convert type `%s' to type `%s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
519 16 Overflow resulted from MONEY multiplication.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
520 16 Overflow resulted from MONEY division.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
521 16 Overflow resulted from MONEY addition.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
522 16 Overflow resulted from MONEY subtraction.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
523 16 Overflow resulted from %s minus operation.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
524 16 Overflow resulted from MONEY remainder (modulo) operation.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 500 - 599
782
526 18 SQL Server has run out of alarms. Re-run your command when there are fewer users
running WAITFOR, or ask your System Administrator to raise the configuration
parameter ’number of alarms’.
Explanation: Retry later, or increase the configuration parameter `number of alarms'.
527 20 Cannot remove alarm.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
528 20 System error detected during attempt to use upsleep system call.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
529 16 Explicit conversion from datatype `%s' to `%s' is not allowed.
Explanation: Command failed due to invalid request. Consult the Adaptive Server
Reference Manual for information on datatype conversions.
530 16 Attempt to insert NULL value into column %d in work table (table id %ld); column does
not allow NULLS. UPDATE fails.
Explanation: Refer to the writeup for Error 530.
532 16 The timestamp (changed to %.*s) shows that the row has been updated by another user.
Explanation: The command failed and no data was updated in the database because an
integrity check or other semantic check on the data failed.
533 20 Can't find a range table entry for range %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
534 16 TEXT and IMAGE datatypes require DBLIB version 4.0 or greater.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
535 16 Difference of two datetime fields caused overflow at runtime.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. The result of the DATEDIFF function may be too large.
536 16 Invalid length parameter with value of %d passed to the substring function.
Explanation: Check command syntax. There may be more constraints to report than
sp_helpconstraint can fit.
537 16 Overflow resulted from a SMALLMONEY remainder operation.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
783
538 16 `%.*s' cannot be found. This language might have been dropped. Please contact a user
with System Administrator (SA) role.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
539 20 Unexpected internal access methods error %d, state %d. Please report to Technical
Support the following information: dbid=%d, objectid=%ld, curcmd=%d,
plasterror=%ld, pstat=0x%lx, p2stat=0x%lx, xactid=(%ld, %d).
Explanation: Refer to the writeup for Error 539.
540 16 Schema for table `%.*s' has changed since compilation of this query. Please re-execute
query.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
541 18 An unknown arithmetic exception type was reported. The transaction has been aborted.
This is an internal system error. Please contact a user with System Administrator (SA)
role.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
542 16 An invalid datetime value was encountered. Value exceeds year 9999.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
543 18 Constraint id information not found upon constraint violation, dbname = `%S_DBID',
table name = `%.*s'. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
544 16 Unknown Constraint violation occurred, database = `%.*s', table name = `%.*s',
constraint name = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
545 18 Constraint violation occurred, entry for the constraint missing from system catalog,
database = `%.*s', table name = `%.*s', constraint name = `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
546 16 Foreign key constraint violation occurred, dbname = `%.*s', table name = `%.*s',
constraint name = `%.*s'.%S_EED
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
547 16 Dependent foreign key constraint violation in a referential integrity constraint. dbname
= `%.*s', table name = `%.*s', constraint name = `%.*s'.%S_EED
Explanation: Refer to the writeup for Error 547.
Number Severity Text and Explanation
Server Error Messages 500 - 599
784
548 16 Check constraint violation occurred, dbname = `%.*s', table name = `%.*s', constraint
name = `%.*s'.%S_EED
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
549 18 Constraint violation occurred, bad constraint type passed to the exception handler.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
550 16 The attempted insert or update failed because the target view was either created WITH
CHECK OPTION or spans another view created WITH CHECK OPTION. At least one
resultant row from the command would not qualify under the CHECK OPTION
constraint.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
551 20 An unknown EVAL was sent to the execution module.
Explanation: Refer to the writeup for Error 551.
552 16 A column insert or update conflicts with a rule bound to the column. The command is
aborted. The conflict occured in database `%.*s', table `%.*s', rule `%.*s', column
`%.*s'.%S_EED
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
553 16 The number of parameters/variables in the FETCH INTO clause does not match the
number of columns in cursor `%.*s' result set.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
554 16 The UPDATE/DELETE WHERE CURRENT OF to the cursor `%.*s' failed because the
row has changed since it was fetched.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
555 16 The UPDATE/DELETE WHERE CURRENT OF to the cursor `%.*s' failed because the
key of the row used in identifying the row changed since it was fetched.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
556 16 The table referenced in the UPDATE/DELETE WHERE CURRENT OF is not part of
the result set tables of cursor `%.*s'.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
557 16 The cursor `%.*s' can not be used as it could not be found. It is possible that either it was
not declared or it is not available in the current context.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
785
558 16 Attempt to open cursor `%.*s' which is already open.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
559 16 Attempt to use a cursor `%.*s' which is not open. Use the system stored procedure
sp_cursorinfo for more information.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
560 16 The UPDATE/DELETE WHERE CURRENT OF failed for the cursor `%.*s' because it
is not positioned on a row.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
562 16 The CURINFO datastream was not sent before the cursor command so no current cursor
context is available.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
563 16 There is already another cursor with the name `%.*s' at the nesting level `%d'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
564 16 The cursor identifiers are not available.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
565 16 The open processing for cursor `%.*s' did not stop anywhere. The DECLARE CURSOR
could have been an invalid statement or there is some internal problem.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
566 26 The procedure buffer is not linked to the procedure header for an execute cursor `%.*s'.
This is probably an internal system problem.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
567 14 You must have the following role(s) to execute this command/procedure: `%.*s' . Please
contact a user with the appropriate role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
568 14 The caller does not have the required System Security Officer (SSO) role. Please contact
a user with System Security Officer (SSO) role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 500 - 599
786
569 16 The specified object with object ID `%d' is not found.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
570 14 Only a person with System Security Officer (SSO) role can change another person's
password.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
571 16 Invalid user specified, password left unchanged.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
572 14 Invalid caller's password specified, password left unchanged.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
573 16 New password specified is too short. Minimum length of acceptable passwords is 6
characters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
574 16 New password supplied is the same as the previous password. Please supply a different
new password.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
575 16 Error occured in internal encryptionroutines.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
576 18 Access was denied into the master database. Password left unchanged.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
577 18 The caller of the set_password builtin was not found! Password left unchanged.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
578 18 Date acquisition function failed. Unable to retrieve the correct date in the set_password
builtin function. Password left unchanged.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
579 18 Unable to start a transaction in the set_password builtin. Password left unchanged.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
787
580 18 Unable to update Syslogins in the set_password builtin. Password left unchanged.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
581 18 Unable to open Syslogins table in the set_password builtin. Password left unchanged.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
582 16 Cursor `%.*s' was closed implicitly because the current cursor position was deleted due
to an update or a delete. The cursor scan position could not be recovered. This happens
for cursors which reference more than one table.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
583 16 The cursor `%.*s' had it's current scan position deleted either because of a
DELETE/UPDATE WHERE CURRENT OF or a regular searched DELETE/UPDATE.
You must do a new FETCH before doing an UPDATE or DELETE WHERE CURRENT
OF.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
584 16 Explicit value specified for identity field in table `%.*s' when IDENTITY_INSERT is set
to OFF.
Explanation: The command failed and no data was updated in the database because an
integrity check or other semantic check on the data failed.
585 16 Explicit value must be specified for identity field in table `%.*s' when
IDENTITY_INSERT is set to ON.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
586 16 Illegal identity value specified for identity field `%.*s' in table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
587 16 Identity value overflow for field `%.*s' while inserting into table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
588 20 Failure adding identity column to table `%.*s' via select into.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
589 16 Invalid role string received.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Number Severity Text and Explanation
Server Error Messages 500 - 599
788
590 16 Dynamic SQL error - Prepared statement `%.*s' does not exist.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
591 16 Dynamic SQL error - Prepared statement `%.*s' is already being used by a cursor.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
592 16 The DELETE WHERE CURRENT OF to the cursor `%.*s' failed because the cursor is
on a join.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
593 16 The UPDATE WHERE CURRENT OF to the cursor `%.*s' failed because column `%.*s'
being updated was not specified in the FOR UPDATE OF list.
Explanation: Command failed. You tried to update a column not named in the cursor's
FOR UPDATE list.
594 16 The UPDATE WHERE CURRENT OF to the cursor `%.*s' failed because column `%.*s'
being updated was not specified in the SELECT list.
Explanation: Command failed. You tried to update a column not named in the cursor's
SELECT list.
595 16 Trying to return NULL from stored procedure for bit variable `%.*s'
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
596 17 Your query overflowed the space allocated for aligning internal data structures. Please
simplify your query by breaking it up into a series of shorter queries.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
599 16 The procedure, `%.*s', that cursor `%.*s' is declared on has been dropped and recreated
since the first time the cursor was opened.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
789
Server Error Messages 600 - 699
Number Severity Text and Explanation
601 21 Descriptor for system table `%ld' in database `%d' not found in the descriptor hash table.
Explanation: Refer to the writeup for Error 601.
602 21 Could not find row in sysindexes for dbid `%d', object `%ld',index `%d'. Run DBCC
CHECKTABLE on sysindexes.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
603 19 There are not enough system session descriptors available to run this query. Raise the
value of the configuration parameter ’number of aux scan descriptors’ or retry your query
later.
Explanation: Refer to the writeup for Error 603.
604 21 Could not find row in sysobjects for object `%ld' in database `%.*s'. Run DBCC
checktable on sysobjects.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
605 21 An attempt was made to fetch logical page `%ld' in database `%.*s' from cache `%.*s'.
Page belongs to object with id `%ld', not to object `%.*s'.
Explanation: Refer to the writeup for Error 605.
607 21 Insufficient room was allocated in the session descriptor for object `%.*s' for search
arguments. Only %d search arguments were anticipated.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
608 0 Buffer holding logical page %ld of object '%.*s' in database '%.*s' was not kept in the first
or second slot o f the session descriptor for that object during a scan.
Explanation: (Version 11.9.2 and higher.)
610 19 Maximum number of databases that may be accessed by a transaction is 16. This number
has been exceeded by this query.
Explanation: Command failed when a non-configurable limit was exceeded. Adaptive
Server could not recover gracefully. Reconnect to Adaptive Server, and report the error
to your System Administrator.
611 21 Attempt made to end a transaction that is idle or in the middle of an update.
Explanation: Refer to the writeup for Error 611.
Server Error Messages 600 - 699
790
612 21 Attempt made to log a row of unknown type %d.
Explanation: Attempt made to write a log record of unknown type. Report the error to
your System Administrator.
613 21 Request made to retrieve more rows from an already completed scan of object `%.*s' in
database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted.
614 21 Adaptive Server accessed a row that has an illegal length of %d while in data
base ’%.*s’. %S_PAGE. The minimum row length is %d. The page size is %d.
Explanation: Refer to the writeup for Error 614.
615 21 Unable to find database table.
Explanation: Run dbcc checks on the database. (This error is not raised in Adaptive
Server 11.0 and higher.)
616 20 Attempt to hash a previously hashed descriptor for object `%.*s' in database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run. (Not raised in 11.0 and higher releases).
617 20 Descriptor for object `%ld' in database `%d' not found in the hash table during attempt to
unhash it.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
618 21 A varno of %d was passed to opentable - the largest valid value is %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
619 20 A deferred update was requested but the query is not one of INSERT, DELETE or
UPDATE.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
620 21 Log record encountered at deferred update time with either a row length of less than 2 or
an invalid log type. The log type was %d and the row length was %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
621 21 A log record was encountered of type %d that is not one of the valid deallocation types.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
791
622 20 Opentable was passed a varno of %d. Object ’%.*s’ in database ’%.*s’ already has that
session descriptor in use. This occured while opening object id %d in database id %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
623 21 Adaptive Server failed to retrieve a row via its RID in database ’%.*s’ because the target
page is not a data page. %S_RID. %S_PAGE.
Explanation: Refer to the writeup for this error.
624 21 Adaptive Server failed to retrieve a row via its RID in database ’%.*s’ because the
requested RID has a higher number than the last RID on the page. %S_RID. %S_PAGE.
Explanation: Refer to the writeup for this error.
625 21 Adaptive Server failed to retrieve a row via its RID in database ’%.*s’ because the entry
in the offset table for that RID is less than or equal to 0. %S_RID. %S_PAGE.
Explanation: Refer to the writeup for this error.
627 20 A transaction tried to call beginupdate while in state `prepare'.
Explanation: There may be a problem due to an application issuing a PREPARE
statement followed by an update. Check the application SQL code.
628 13 Attempt to issue `SAVE TRANsaction' when there is no active transaction.
Explanation: Rerun the command that raised this error.
629 21 Clustered index row entry for data page %ld is missing in index page %ld of table
'%S_OBJID' in database '%S_D BID'; index row contains data page %ld instead. You can
recreate the clustered index to fix this error. Xactid is (%ld, %d).
Explanation: Refer to the writeup for this error.
630 21 The end of page limit has been exceeded while building an offset table for object %ld on
page %ld, page addr 0x%lx, eop addr 0x%lx, sargptr addr 0x%lx.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
631 21 The length of %d passed to delete row routine for the row at offset %d is incorrect on the
following page: %S_PAGE. The expected row length is %d. The offset should be no
greater than %d.
Explanation: Refer to the writeup for this error.
632 20 Memmove() was called with a length of %d - maximum allowed length is %d.
Explanation: The error may be caused by data corruption. Run dbcc checkdb on the
database that was being accessed, and correct any errors reported.
633 21 The PG_DEALLOC bit set by recovery is on at runtime on the following page.
%S_PAGE.
Explanation: Report the error to your System Administrator. (Not raised in Release
11.0 and higher.)
Number Severity Text and Explanation
Server Error Messages 600 - 699
792
634 20 Memmove() was called with an address of 0x%lx and a length of %d - which would cross
the boundary address of 0x%lx.
Explanation: There is a possible Adaptive Server problem. Run dbcc checks on the
database that was being accessed when the error occurred.
635 20 Process %d tried to remove DES resource lock that it doesn't hold - %S_DES .
Explanation: Report the error to your System Administrator. (Not raised in Release
11.0 and higher.)
637 20 Index shrink program returned invalid status of 0.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. Run dbcc indexalloc, checktable.
638 20 Memmove() was called with an address of 0x%lx - which is not allocated memory.
Explanation: There is a possible Adaptive Server problem. Run dbcc checks on the
database that was being accessed when the error occurred.
639 21 Attempt to fetch logical page %ld dbid %d failed - page is not currently allocated.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
640 21 Attempt to insert/delete row on wrong type of page. %S_PAGE.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
641 21 Attempt to add BEGINUPDATE record in transaction %S_RID that already has an active
CMD.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
642 20 Attempt to begin update in transaction %S_RID which already has an active transaction.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
643 20 Attempt to read page %ld in database `%.*s' which is not allocated.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
644 21 Index row entry for data row id (%ld, %d) is missing from index page %ld of index id %d
of table ’%S_OBJID’ in database ’%S_DBID’. Xactid is (%ld,%d). Drop and re-create
the index.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
793
649 21 Could not find the clustered index entry for Page %ld Objid %ld status 0x%x. Index page
%ld was searched for this entry in database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
650 26 Page %ld of table ’%.*s’ (id = %ld) in dbid %d not locked.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
651 26 Startscan was called with an illegal combination of index and scan mode.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
652 20 The buffer 0x%lx should be kept in sdes 0x%lx on entry to this function and it is not.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
653 26 Buffer not rlocked. %S_BUF. %S_PAGE.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
654 26 Page %ld, dbid %d not exclusive locked.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
655 26 Page should be marked as having overflow page: %S_PAGE.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
656 26 Locking not stipulated while attempting to modify page. %S_PAGE.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
657 26 Passed buffer pointer for previous page is for page %ld, when the actual previous page
is %ld. These pages are in database `%*.s'.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
658 22 Last log page in database `%.*s' incorrectly identified as page %ld. Run DBCC
checktable on syslogs.
Explanation: Report the error to your System Administrator. (Not raised in Release
11.0 and higher.)
659 16 Table id %d contains suspect indexes. This table is only available for read-only purposes
until the DBCC REINDEX command has been run on the indicated table to rebuild its
suspect indexes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 600 - 699
794
660 10 Index id %d cannot be used to access table id %d as it is SUSPECT. Please have the SA
run the DBCC REINDEX command on the specified table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
661 21 As part of a transaction rollback, an attempt was made to modify object `%S_OBJID' in
database `%.*s', even though the current session is not holding an exclusive lock on that
object.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
662 18 The index with index id `%d' on object with object id = `%d' was not found during cursor
scan fixups. The fixup was being done for cursor `%.*s'. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
663 18 The lock on page `%d' for object with object id = `%d' could not be obtained during
cursor scan fixups. The fixup was being done for cursor `%.*s'. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
664 18 The parameters passed to cursfix_main() were not correct. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
665 18 The cursor fixup is being done for the pre delete case with the data row for a scan using
a non-clustered index and there was no fixup done for pre-delete of the non-clustered
index row. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
666 18 The current position deleted bit is set for an SDES but there is no fixup information
saved. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
667 26 Illegal locking strategy encountered at scan initialization. Object %S_OBJID, database
%S_DBID. This is an internal error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
668 18 The cursor `%.*s' which is scanning a list of rids i.e a work table is having it's tables
changed. This cursor should be read only and the tables should be private to it's query.
This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
795
669 18 The length computation of the row %d is wrong. Ensure that row-length is no greater than
max possible size of %d. This error was detected during cursor scan fixups for cursor
’%.*s’. This is an internal error. The processing is being stopped for the current query.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
670 16 Out of bound insert attempted on table `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
671 14 Writetext is not allowed in reclassify mode.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
672 16 Out of bound update attempted on table `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
673 16 Out of bound delete attempted on table `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
674 20 Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed
because the cache id `%ld' in scan_context is invalid. scan_context={objid `%ld', indid
`%ld', cid `%ld'}. Contact Technical Support for assistance.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
675 20 Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed
because no object id was specified. scan_context={objid `%ld', indid `%ld', cid `%ld'}.
Contact Technical Support for Assistance.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
676 21 NULL cache id specified in log record.
Explanation: Report the error to your System Administrator. (Not raised in Release
11.0 and higher.)
677 20 Invalid Buffer Cache Access: Attempt to locate page `%ld', dbid `%ld', objid `%ld', indid
`%ld' in cache failed because the cache ID was not set in the scan_context structure.
Contact Technical Support for assistance.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Number Severity Text and Explanation
Server Error Messages 600 - 699
796
678 20 Invalid Buffer Cache Access: Could not open object `%ld' in database `%d'
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
679 20 Inconsistent update state found during expensive direct update of object `%ld'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
680 20 Attempt to extend the log in database `%.*s' failed due to an internal error. The returned
status was %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
682 20 The buffer 0x%lx , page number '%ld' for object '%.*s' in database '%.*s' should be
latched on entry to this f unction and it is not.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run. (Version 11.9.2 and higher.)
683 20 Failed to get lock on data page '%ld' row '%ld' for object '%.*s' in database '%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run. (Version 11.9.2 and higher.)
684 26 Page %ld, Row %d, for object '%.*s' in database '%.*s' is not exclusive locked.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server. (Version 11.9.2 and
higher.)
685 21 Expected page %ld to be in cache `%.*s' for object id %ld, index id %d, database id %d.
Instead, the server brought the page into wrong cache `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Report the
error to your System Administrator.
686 20 Expected page %ld to be in cache `%.*s' for object id %ld, index id %d, database id %d.
Instead, the server brought the page into wrong cache `%.*s'.
Explanation: Page %ld is corrupted.
688 21 Insufficient CFS while redo of expanding update on page %ld belonging to object %ld.
CFS - %ld, length of new row - %ld
Explanation: Command failed due to internal Adaptive Server problem. Report the
error to your System Administrator.
689 10 An unexpected log record (log op %d) was encountered when scanning the log for a
trigger.
Explanation: Informational message. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
797
Server Error Messages 700 - 799
690 20 Pageno in lk_pglocked (%ld) different from lockobj (%ld).
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
691 20 Encountered invalid logical page '%ld' while accessing object '%ld' in database '%d'. This
is an internal system error. Please contact Sybase Technical Support.
Explanation: See the writeups for Error 691 and Error 605.
692 20 Uninitialized logical page '%ld' was read while accessing object '%ld' in database '%d'.
Please contact Sybase Technical Support.
Explanation: See the writeups for Error 692 and Error 605.
693 20 Multiple copies of logical page '%ld' from database '%d' reside in more than one cache.
This is an internal system error. Please contact Sybase Technical Support.
Explanation: See the writeups for Error 693 and Error 605.
694 24 An attempt was made to read logical page '%ld', virtpage '%ld' from virtual device '%d'
for object '%ld' in database '%d'. The page was not read successfully. You may have a
device problem or an operating system problem.
Explanation: See the writeups for Error 694 and Error 605.
695 21 An attempt was made to read logical page '%ld' for object '%ld' in database '%d' from
disk. Wrong logical page '%ld' was brought into cache '%.*s'.
Explanation: See the writeups for Error 695 and Error 605.
696 21 An attempt was made to fetch logical page '%ld' in tempdb from cache '%.*s'. Page
belongs to object '%ld' and not to object '%ld'. Restart of SQL Server will clear the error.
Please contact your System Administrator for help.
Explanation: See the writeups for Error 696 and Error 605.
697 21 An attempt was made to fetch logical page '%ld' for object '%ld' in database '%d' from
cache '%.*s'. Wrong logical page '%ld' was found in cache.
Explanation: See the writeups for Error 697 and Error 605.
Number Severity Text and Explanation
Number Severity Text and Explanation
701 19 There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry
later, or ask your SA to reconfigure SQL Server with more procedure cache.
Explanation: Refer to the writeup for this error.
Server Error Messages 700 - 799
798
702 20 Memory request for %d bytes exceeds the size of single page of %d bytes.
Explanation: Refer to the writeup for this error.
703 17 You cannot run this procedure, trigger, or SQL batch because it requires more than %ld
pages of memory. Break it up into shorter queries, if possible.
Explanation: Refer to the writeup for this error.
704 20 Tried to free procedure header 0x%lx, but it's still in use by procedure `%.*s' at procedure
buffer 0x%lx.
Explanation: The problem may be due to memory corruption. Shut down and restart
Adaptive Server to clear the memory structures.
705 19 There is no room for process %d to store PROC_HDR 0x%lx in Pss.
Explanation: Command failed when a configurable limit was exceeded. Reconnect to
Adaptive Server and report the error to your System Administrator.
706 20 Process %d tried to remove PROC_HDR 0x%lx that it does not hold in Pss.
Explanation: Refer to the writeup for this error.
707 20 System error detected during attempt to free memory at address 0x%lx. Please consult
the SQL Server error log for more details.
Explanation: Refer to the writeup for this error.
708 17 There is insufficient system memory to run kernel task. spid %d, kpid %d.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
709 17 There is insufficient system memory to continue login process for spid %d.
Explanation: See the writeup for Error 709.
710 20 Memory request for %d bytes is too small.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
711 17 There is presently insufficient system memory to allocate %ld bytes for new structures.
Please try again when there is less activity on the system.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
712 17 There is insufficient heap memory to allocate %ld bytes. Please increase configuration
parameter ’heap memory per user’ or try again when there is less activity on the system.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
799
Server Error Messages 800 - 899
Number Severity Text and Explanation
801 20 Process %d tried to remove resource lock it doesn't hold on buffer 0x%lx - %S_PAGE in
cache %s.
Explanation: Check the Adaptive Server error log for 1105 or other errors. Restart
Adaptive Server.
803 20 Unable to place buffer `0x%lx' from cache `%.*s' holding logical page `%ld' in sdes for
object `%.*s' - either there is no room in sdes or buffer already in requested slot.
Explanation: Refer to the writeup for this error.
804 20 Unable to find buffer `0x%lx' from cache `%.*s' holding logical page `%ld' in sdes
`0x%lx' kept buffer pool for object `%.*s'.
Explanation: Refer to the writeup for this error.
805 21 Unable to find descriptor for object `%.*s' in database `%.*s' in hash table when marking
buffer dirty or flushing syslogs.
Explanation: Report the error to your System Administrator. (Not raised in Release
11.0 and higher.)
806 21 Could not find virtual page for logical page %ld in database `%S_DBID'.
Explanation: Refer to the writeup for this error.
807 10 Logical page %ld in buffer 0x%lx already kept in SDES for object `%.*s' in database
`%.*s'.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator. (Not raised in Release 11.0 and higher.)
808 20 Alloc page buffer pool in Pss is full - logical pages %ld, %ld, and %ld in respective
databases `%.*s', `%.*s' and `%.*s' are already held there. Cannot add logical page %ld
in database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
809 20 Buffer 0x%lx, alloc pg %ld, in database `%.*s' not in alloc buf pool in Pss.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
810 20 Attempt to pin log page buffer.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run. (Not raised in Release 11.0 and higher.)
Server Error Messages 800 - 899
800
811 21 Attempt to grab buffer (from cache `%.*s') which is on descriptor chain.
Explanation: Report the error to your System Administrator. Adaptive Server must be
restarted and DBCC diagnostics run. This error occurs in diagserver.
812 21 Attempt to grab a pinned buffer.
Explanation: Adaptive Server encountered an internal error affecting all current
processes. The server must be restarted.
813 20 Logical page `%ld' in database `%S_DBID', cache `%.*s' is already hashed.
Explanation: Refer to the writeup for this error.
814 20 Keep count of buffer `0x%lx' in cache `%.*s' holding logical page `%ld' in database
`%.*s' has become negative.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
815 21 Unable to find buffer holding sysindexes page in the cache - pageno = %ld dbid = %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
816 20 Process %d tried to remove a buffer resource lock %S_BUF that it does not hold in SDES
%S_SDES.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run. (Not raised in Release 11.0 and higher.
817 20 Process %d tried to remove a buffer resource lock %S_BUF that it does not hold in Pss
0x%lx.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
818 19 There is no room to hold the buffer resource lock %S_BUF in SDES %S_SDES.
Explanation: Command failed when a configurable limit was exceeded. Reconnect to
Adaptive Server and report the error to your System Administrator.
819 19 There is no room for process %d to hold buffer resource lock %S_BUF in Pss.
Explanation: Command failed when a non-configurable limit was exceeded. Adaptive
Server could not recover gracefully. Reconnect to Adaptive Server, and report the error
to your System Administrator.
820 21 Attempt to dirty non-log buffer %S_BUF which is in I/O.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
801
821 20 Attempt to unhash buffer in cache `%.*s' at `0x%lx' with a buffer pageno of `%ld' and
database id `%ld' with HASHED status set failed - buffer was not found. `%S_PAGE'.
Explanation: Refer to the writeup for this error.
822 21 Could not start I/O for request BLKIO flags = 0x%lx, size = %ld, errcode = 0x%lx,
%S_BUF.
Explanation: Refer to the writeup for this error.
823 24 I/O error detected during %S_MSG for %S_BUF.
Explanation: Refer to the writeup for this error.
824 21 Attempt made to write page in buffer in database that has no entry in sysdatabases.
%S_BUF.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run. (Not raised in Release 11.0 and
higher.
825 21 Attempt made to write page in buffer in database with no DBTABLE structure -
sysdatabases row marked as in use by process %d. %S_BUF.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run. (Not raised in Release 11.0 and
higher.
826 20 Attempt made to hold allocation page %ld that is already in Pss pool. Database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run. (Not raised in Release 11.0 and higher.
827 20 Attempt to dirty unkept page `%ld' in database `%.*s', cache `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
829 21 A problem with ordered writes was detected. Please call SYBASE.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run. (Not raised in Release 11.0 and
higher.
830 20 Invalid magic number %ld for aux kept buffer structure 0x%x, for sdes 0x%x, object id
%ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Number Severity Text and Explanation
Server Error Messages 800 - 899
802
831 20 Unable to find buffer 0x%x holding logical page %ld in sdes 0x%x, aux keep struct
0x%x, for object `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
832 20 Unable to place buffer 0x%x holding logical page %ld in sdes for object `%.*s' - there is
no room in sdes aux keep pool.
Explanation: Adaptive Server encountered an internal error or an error due to lack of
resources. Report the error to your System Administrator.
833 20 Attempt to read logical page %ld, database `%S_DBID' into buffer 0x%x that is hashed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
834 20 Illegal attempt to clean buffer: %S_BUF.
Explanation: Refer to the writeup for this error.
835 20 Illegal attempt to change contents of buffer: %S_BUF.
Explanation: Shut down and restart Adaptive Server to clear the buffer structure.
836 21 Attempted to grab lru header.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
837 21 Attempted to grab wash header.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
838 21 Grabbed buffer not marked in wash: %S_BUF.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
839 21 Grabbed buffer dirty but not writing: %S_BUF.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
840 17 Device `%.*s' (with physical name `%.*s', and virtual device number %d) has not been
correctly activated at startup time. Please contact a user with System Administrator (SA)
role.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
803
841 10 Attempt to set bufreserves in RESOURCE structure to negative value while unclaiming
cache.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
842 20 Attempt to set bufclaims in PSS structure for process %d to negative value while
unclaiming cache.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
843 20 Unable to find original instance of buffer `0x%x' holding logical page `%ld' in cache
`%.*s' for object `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
844 20 Attempt to unpredirty buffer %S_BUF which is %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
845 20 Attempt to do a large I/O for page %ld in database `%.*s' with buffer 0x%x, which is not
a large buffer.
Explanation: Reconnect to Adaptive Server. Report the error to your System
Administrator so DBCC diagnostics can be run. (Not raised in Release 11.0 and higher.)
846 10 Hardware error detected writing logical page `%ld', virtual page `%ld' for dbid `%ld',
cache `%.*s'. The user process will sleep until write completes successfully.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
847 10 Checkpoint process detected hardware error writing logical page `%ld', virtual page `%ld'
for dbid `%ld', cache `%.*s'. It will sleep until write completes successfully.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
848 21 Could not start I/O for device `%.*s' (with physical name `%.*s', and virtual device
number %d). Operating system error %d.
Explanation: Reconnect to Adaptive Server. Report the error to your System
Administrator so DBCC diagnostics can be run. (Not raised in Release 11.0 and higher.)
849 21 I/O error detected for device `%.*s' (with physical name `%.*s', and virtual device
number %d).
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Server Error Messages 800 - 899
804
850 20 Wrong cache descriptor in buffer `0x%x', page `%d', dbid `%d'. Cache descriptor points
to cache `%.*s'.
Explanation: Internal error with a buffer pointer. Reconnect to Adaptive Server. Report
the error to your System Administrator so DBCC diagnostics can be run. (Not raised in
Release 11.0 and higher.)
851 20 Wrong cluster mask for cache `%.*s', mask encountered = %d, should = %d.
Explanation: Internal error with a cache descriptor. Reconnect to Adaptive Server.
Report the error to your System Administrator so DBCC diagnostics can be run. (Not
raised in Release 11.0 and higher.)
852 20 Command Failed: Invalid request to move `%ld' buffers from the `%ld'K pool of the
`%.*s' cache to the `%ld'K pool. Source pool only contains `%ld' buffers. Retry the
command specifying fewer buffers.
Explanation: Refer to the writeup for this error.
853 16 Invalid Configuration: Unable to start SQL Server since no information is available for
configuring the data cache. The server may be started with a default configuration using
the -c startserver option.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
854 20 Fatal buffer pool error. Please contact Sybase technical support.
Explanation: Internal error in finding a buffer pool descriptor. Report the error to your
System Administrator. (Not raised in Release 11.0 and higher.)
855 16 Bad prefetch size of %d encountered.
Explanation: Refer to the writeup for this error.
856 16 Command Failed: Cannot move buffers from the `%ld'K pool to the `%ldK' pool. `%ld'K
pool does not exist. Please specify a valid buffer pool.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
857 16 Command Failed: Cannot bind or unbind database `%S_DBID' to or from a cache
because it is currently in use. Retry the command once all users have stopped using the
database.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
858 16 Cache `%.*s' does not exist.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
859 20 Invalid Buffer Cache Access: Attempt to locate page `%ld', database `%ld' in cache failed
because the cache id `%ld' in scan_context is invalid. Scan_context = {objid `%ld', indid
`%ld', cid `%ld'}. Contact Technical Support for assistance.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
805
860 20 Invalid Buffer Cache Access: Attempt to locate page `%ld', dbid `%ld' objid `%ld', indid
`%ld' in cache failed because the cache ID was not set in the scan_context structure.
Contact Technical Support for assistance.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
861 16 Command Failed: Cannot bind object `%ld', dbid `%d' to cache because you have an
open cursor on the target object. Retry the command after closing the cursor.
Explanation: Refer to the writeup for this error.
862 16 Command Failed: Database `%d' must be in single user mode to bind target object.
Explanation: Command failed. The database must be in single user mode to execute
this command.
863 20 Buffer resources in cache %s, id %d are unavailable. Please re-run this query or ask the
system administrator to re-configure buffer cache memory.
Explanation: Refer to the writeup for this error.
864 16 Command Failed: Cannot bind object `%ld', dbid `%d' to cache because you have active
level0 scans on the target object. Retry the command after terminating the scans.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
865 21 Error deleting row from Sysattributes during cache binding validation.
Explanation: Adaptive Server was unable to delete an existing row from sysattributes.
This is an internal error affecting all processes using the current database. Report the error
to your System Administrator.
866 21 Error inserting row into Sysattributes during cache binding validation.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
867 16 The system table Sysattributes or its indices may not be bound to a named cache.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
868 16 The system table Sysallocpg may not be bound to a named cache.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
869 21 Error updating row %S_RID in Sysattributes during cache binding validation.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Server Error Messages 800 - 899
806
870 10 WARNING!!! You may have to change the log I/O size for the database `%.*s'. Current
setting is `%dK' and the cache `%.*s' does not have a `%dK' memory pool.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
871 20 Process %d is trying to release a latch on buffer 0x%x (dbid: %d, pageno: %d) without
holding a latch on the buffer.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
872 20 Process %d is trying to get a %s latch on buffer 0x%x (dbid: %d, pageno: %d) while
already holding a %s latch on the buffer.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
873 20 Process %d is requesting %s latch on buffer 0x%x (dbid: %d, pageno: %d) while holding
%d latches. A process can hold only %d latches at a time.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
874 20 Process %d is trying to unkeep buffer 0x%x (dbid: %d, pageno: %d) without releasing the
%s latch it holds on t he buffer.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run. This is an informational message. Unless otherwise
specified, no action is required. Contact your System Administrator about any warning
issued in the message.
875 20 Unable to grab a buffer to allocate a page to the log in database id %d. Tried %d buffers
in the wash but found them to be pinned (either directly or indirectly). See the error log
for more information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
876 20 The process is holding log semaphore on database %d and is about to sleep on
mass=0x%x with stat=0x%x for page=%ld which is being written by some other process
that needs the log semaphore. This causes a deadlock, and can only be cleared by a reboot.
Explanation: Adaptive Server encountered an internal error affecting the current
process. The System Administrator can clear the problem by restarting the server.
878 21 Task %d was expected to hold latch on buffer 0x%x of page %ld in database %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
807
Server Error Messages 900 - 999
879 21 Task %d was expected to hold exclusive latch on buffer 0x%x of page %ld in database
%d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
880 10 Your query is blocked because it tried to write and database ’%.*s’ is
in quiesce state. Your query will proceed after the DBA performs QUIESCE DATABAS
E RELEASE.
Explanation: Your query cannot be processed at this time. Retry when the database
becomes available.
Number Severity Text and Explanation
Number Severity Text and Explanation
902 24 Hardware error detected reading logical page %ld, virtual page %ld in database `%.*s'.
Explanation: Hardware error detected. Report the error to your System Administrator.
The database may have to be reloaded. It may be necessary to contact your hardware
vendor.
903 23 Unable to find row in sysindexes for clustered index on system catalog %d in database
%d. This index should exist in all databases. Run DBCC CHECKTABLE on sysindexes
in the database.
Explanation: Refer to the writeup for this error.
904 22 Unable to find master database row in sysdatabases. Cannot open master database.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
905 17 Unable to allocate a DBTABLE descriptor to open database ’%S_DBID’. Close or drop
another database before opening this one, or ask your System Administrator to
raise the configuration parameter ’number of open databases’.
Explanation: Refer to the writeup for this error.
906 23 Could not locate row in sysobjects for system catalog %d in database %d. This system
catalog should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the
database.
Explanation: Refer to the writeup for this error.
Server Error Messages 900 - 999
808
908 22 Unable to find any entries in sysusages for dbid `%d', database `%S_DBID'. Run DBCC
CHECKTABLE on sysusages in the master database.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
909 21 More than %d entries required to build the logical-virtual translation table for database
`%S_DBID'. The database is too fragmented.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
910 17 Could not allocate a new object descriptor for required system catalog in database `%d'.
Another database must be closed or objects in another database dropped in order to open
this database.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
911 16 Attempt to locate entry in sysdatabases for database `%.*s' by name failed - no entry
found under that name. Make sure that name is entered properly.
Explanation: Refer to the writeup for this error.
912 21 DBTABLE descriptor cannot be found for database `%.*s' which is supposed to be
already open.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
913 22 Could not find row in sysdatabases with database id %d. Run DBCC CHECKTABLE on
sysdatabases.
Explanation: Refer to the writeup for this error.
915 21 Descriptor for system catalog `%.*s' not found in DBTABLE chain for database `%.*s' -
all system catalogs should reside permanently in this chain.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
916 14 Server user id %d is not a valid user in database `%.*s'
Explanation: Refer to the writeup for this error.
917 20 Illegal attempt to close the master database for the last time - this database must always
be open.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
918 14 Database `%.*s' has not yet been recovered - please wait before accessing this database.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
809
919 21 Database `%.*s' was marked `suspect' by an earlier attempt at recovery. Check the SQL
Server errorlog for information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
920 22 Could not find syslogs row in sysindexes for database `%.*s'. Run DBCC
CHECKTABLE on this system catalog.
Explanation: There may be a corrupt table or index. Adaptive Server must be restarted
and dbcc diagnostics run.
921 14 Database `%.*s' has not been recovered yet - please wait and try again.
Explanation: Refer to the writeup for this error.
922 14 Database `%.*s' is being recovered - will wait until recovery is finished.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
923 14 User %d not allowed in database `%.*s' - only the owner of this database can access it.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
924 14 Database `%.*s' is already open and can only have one user at a time.
Explanation: Refer to the writeup for this error.
925 19 Maximum number of used databases for each query has been exceeded. The maximum
allowed is %d.
Explanation: Refer to the writeup for this error.
926 14 Database `%.*s' cannot be opened. An earlier attempt at recovery marked it `suspect'.
Check the SQL Server errorlog for information as to the cause.
Explanation: Refer to the writeup for this error.
927 14 Database <%d> cannot be opened - it is in the middle of a load.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
928 14 Database `%.*s' cannot be opened - it is currently being created. Wait and try query
again.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
929 21 Attempting to close a database which is not open. Please contact Technical support.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
930 14 Database `%.*s' cannot be opened because either an earlier system termination left
LOAD DATABASE incomplete or the database is created with `for load' option. Load the
database or contact a user with System Administrator (SA) role.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
Server Error Messages 900 - 999
810
931 21 Database `%.*s' cannot be opened because of a failure to initialize the global timestamp.
This indicates that a problem exists in the log for the current database. Please contact
Technical support for assistance.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
932 22 Database `%.*s' cannot be opened because the log for the current database is corrupt.
Page %ld of the log is linked to a page that belongs to a database object with id %ld.
Please contact Technical support for assistance.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
933 22 Logical page %ld of the log encountered while retrieving highest timestamp in database
`%.*s' is not the last page of the log and we are not currently recovering that database.
Explanation: Refer to the writeup for this error.
934 21 Fatal error encountered while freeing up DBTABLE structure.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run. (Not raised in Release 11.0 and higher.)
935 10 WARNING - the timestamp in database `%.*s' is approaching the maximum allowed.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
936 14 The Model database is unavailable. It is being used to create a new database.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
937 14 Database `%.*s' is unavailable. It is undergoing LOAD DATABASE.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
938 14 Database `%.*s' is unavailable. It is undergoing LOAD TRANSACTION.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
939 20 Illegal dbtable unlock: %S_DBT.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
940 26 Dbtable in wrong state for operation: %S_DBT.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
941 20 Illegal database context operation.
Explanation: See the writeup for Error 941.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
811
942 20 Database cannot be opened because a system descriptor cannot be installed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
943 14 Database `%.*s' cannot be opened since an attempt to upgrade it was unsuccessful.
Explanation: Command failed. The database is not available, this may be due to an
upgrade failure. Contact your System Administrator.
944 20 Function %s requires that the user be in the database being worked on. Process %d
passed it a dbtable for database %d, but is using database %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
945 21 Unable to locate page %ld for database id %d in the in-memory copy of Sysusages
(spid=%ld). This is an internal error. Please contact Sybase Technical Support.
Explanation: Refer to the writeup for this error.
946 10 A %S_MSG has prevented Sysusages changes for database %.*s from being copied into
memory. Please run sp_dbremap to complete database space changes.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
947 14 Database `%.*s' has been marked as having corrupt security labels. Please contact a user
with the System Administrator, System Security Officer, or Oper role or the Database
Owner.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
948 14 Database `%.*s' is unavailable. It is undergoing a security label consistency fix.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
949 14 Database `%.*s' is unavailable. It is being bound to a named cache.
Explanation: When a database is bound to a named cache, all objects in that database
are bound to that cache unless they are explicitly bound to a different cache. Binding a
database to a named cache requires an exclusive lock on the database. Error 949 occurs
when you try to access an object in a database that is in the process of being bound to a
named cache. Try again later, once the bind has completed.
950 14 Database `%.*s' is currently offline. Please wait and try your command again later.
Explanation: See the writeup for Error 950.
951 14 Database identity for server user id %d changed after permission checking in database
`%.*s'. Please try again.
Explanation: Command failed. The database is not available at this time. Wait and try
again.
Number Severity Text and Explanation
Server Error Messages 900 - 999
812
952 20 Database '%.*s' cannot be opened because a system index descriptor cannot be installed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
953 11 Page '%ld', passed to curunreservedpgs built-in function, is an invalid page number in
database ID '%d'. The highest page number in this database is '% ld'.
Explanation: Command failed. Check your command and re-enter with the correct
parameters.
954 10 Warning: The database ’%.*s’ is using an unsafe virtual device ’%.*s’. The recovery of
this database can not be guaranteed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
955 16 This command attempts to modify data in database ’%.*s’, dbid ’%d’. Modifications are
not allowed in this database.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
956 16 The database ’%.*s’ does not have separate log segment. Log pre-allocation is not
feasible for this database.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
957 16 Server wide log pre-allocation is disabled. Log pre-allocation is not possible at this time.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
958 16 Enabling or disabling log prealloation is not allowed for system databases.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
959 16 Database ’%.*s’ cannot be opened because an earlier system termination left DROP
DATABASE incomplete. Drop the database or run ’DBCC CHECKALLOC’ to correct
allocation information.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
960 16 Operation ’%S_MSG’ is not currently supported for database ’%.*s’.
Explanation: Adaptive Server could not perform the requested action. Check your
query; contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
813
Server Error Messages 1000-1099
Number Severity Text and Explanation
1000 18 Abstract Plan (AP) Internal Error : An error occurred while looking for the AP group ID
in sysattributes. If the error persists, please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
1001 18 Abstract Plan Internal Error : Attempting to hard-cast the non-object data structure at %1!
as an APOM object. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
1002 16 Abstract Plan (AP) : The query does not contain an UNION operator to match the one in
the AP expression. The AP will not be applied. Check the AP syntax and its
correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1003 16 Abstract Plan (AP) : The number of operands of the UNION operator in the AP differs
from the number of sides of the UNION SQL query. The extra items will be ignored.
Check the AP syntax and its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1004 16 Abstract Plan (AP) : The AP expression does not contain an UNION operator to match
the one in the SQL query. The AP will not be applied. Check the AP syntax and its
correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1005 16 Abstract Plan (AP) : The number of operands of the PLAN operator in the AP differs from
the number of steps needed to compute the query. The extra items will be ignored. Check
the AP syntax and its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1006 16 Abstract Plan (AP) : The SQL query step does not create a work table matching the one
described by the corresponding STORE operator in the AP. This part of the AP will not
be applied. Check the AP syntax and its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Server Error Messages 1000-1099
814
1007 16 Abstract Plan (AP) : The AP expression describes a bushy join tree, while the Server only
supports left deep join trees. The bushy right join operand will not be applied. Check the
AP syntax.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1008 16 Abstract Plan (AP) : The SQL query step does not contain a subquery to match the
subquery %d described in the AP. The subquery will be ignored. Check the AP syntax and
its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1009 16 Abstract Plan (AP) : The SQL query step does not contain a base table to match the base
table ’%.*s’ described in the AP. The base table will be ignored. Check the AP syntax and
its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1010 16 Abstract Plan (AP) : The SQL query step does not contain a work table to match the work
table ’%.*s’ described in the AP. The work table will be ignored. Check the AP syntax
and its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1011 16 Abstract Plan (AP) : The AP expression uses the work table ’%.*s’, but does not define
it through a STORE operator. The table will be ignored. Check the AP syntax.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1012 16 Abstract Plan (AP) : The AP expression describes the materialization of a join, while the
Server only supports single table reformatting. The operand of the STORE operator will
be ignored. Check the AP syntax.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1013 16 Abstract Plan (AP) : %s; line %d, occurring near ’%.*s’. Check the AP syntax.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1014 16 Abstract Plan (AP) : The correlation name ’%.*s’ is used in the AP expression for the
table ’%.*s’ and in the SQL query for the table ’%.*s’. The table will be ignored. Check
the AP syntax and its correspondence to the query.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1015 16 Abstract Plan (AP) : You cannot use a variable of type %s. Use CHAR, VARCHAR or
TEXT instead.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
815
1016 16 Abstract Plan (AP) : There is no destination group for the new AP. The AP was not
created. Specify a destination group within the statement or enable the AP capture mode.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1017 18 Abstract Plan (AP) : sysqueryplans manager error. The operation was aborted, no AP was
created or deleted.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
1018 16 Abstract Plan (AP) : There is no AP group with the name ’%.*s’. The AP mode settings
will not be changed.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1019 16 Abstract Plan (AP) : The %s mode is already enabled for group ’%.*s’. The AP mode
settings will not be changed. To enable the LOAD mode for another group, disable it first.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1020 16 Abstract Plan (AP) : The REPLACE sub-mode is already enabled.
Explanation:
1021 16 Abstract Plan (AP) : The DUMP mode is not enabled. Adaptive Server cannot enable the
REPLACE sub-mode. Enable the DUMP mode first.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1022 16 Abstract Plan (AP) : The %s mode is not currently enabled. The AP mode settings will
not be changed.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1023 0 Abstract Plan (AP) : The LOAD mode is not enabled. Adaptive Server cannot enable the
EXISTS CHECK sub-mode. Enable the LOAD mode first.
Explanation: Refer to the Adaptive Server Reference Manual for information about the
stored procedure you were running when you got this message.
Number Severity Text and Explanation
Server Error Messages 1100-1199
816
Server Error Messages 1100-1199
Number Severity Text and Explanation
1101 17 Unable to allocate new page for database `%.*s'. There are no more pages available on
valid allocation pages. Space can be created by dropping objects, extending the database,
or dumping the log with no_log.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem. (Not raised in Release 11.0 and higher.)
1102 22 Unable to locate allocation page %ld for database `%.*s'. This allocation page contains
the extent that the target allocation page is in, but the allocation page is not in the
translation table in the DBTABLE. Run DBCC CHECKTABLE on sysusages.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1103 21 Allocation page %ld in database `%.*s' has different segment id than that of the object to
which we are allocating. Run DBCC CHECKALLOC.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run. (Not raised in Release 11.0 and higher.)
1104 20 Conflict between number of extents marked in log record in the allocation bitmap and the
allocation count. Allocation count is %d. Bitmap is 0x%lx 0x%lx 0x%lx 0x%lx.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics (dbcc checkalloc) can be run on the database.
1105 17 Can't allocate space for object `%.*s' in database `%.*s' because `%.*s' segment is full.
If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER
DATABASE or sp_extendsegment to increase size of the segment.
Explanation: Refer to the writeup for this error.
1106 20 First pass through allocation page %ld found %d free extents. After logging, only found
%d free extents.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run. (Not raised in Release 11.0 and higher.)
1108 21 Cannot deallocate extent %ld, database %d. Object id %ld, index id %d, status %d in
extent does not match object id %ld, index id %d, status %d in object being deallocated.
Run DBCC CHECKALLOC.
Explanation: Refer to the writeup for this error.
CHAPTER 6 Adaptive Server Error Messages
817
1109 21 Attempt to read allocation page %ld failed either because object ID is not correct (%ld)
or the page ID is not correct (%ld).
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run. (Not raised in Release 11.0 and higher.)
1110 20 Attempt to resource lock allocation page %ld in database `%.*s' by process %d while
allocating to non-syslogs object `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1111 20 Extent bitmap on allocation page %ld in database `%.*s' does not have extents marked
that are being removed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1112 20 Extent bitmap on allocation page %ld in database `%.*s' already has extents marked that
are being added.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1113 20 Extent %ld already locked while allocating it in database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1114 20 Attempt to resource lock page %ld in database `%.*s' by process %d failed because lock
is already held by process %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1115 20 Attempt to transfer a resource lock to process ID 0 on allocation page %ld in database
`%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1116 20 Attempt to backout the allocation of LOG page %ld, in database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1117 21 Extent chain for object %ld is not correctly linked.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
Server Error Messages 1100-1199
818
1120 20 Adaptive Server failed to access page %ld in database ’%.*s’ because it is not an
allocation page.
Explanation: Refer to the writeup for this error.
1122 20 Attempt to read allocation page before openning SYSALLOCPGS.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1123 20 Failed to get lock on OAM pg.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1124 20 Failed to get lock on allocation page %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1125 20 Attempting to allocate page %ld in database %d to extent %ld which belongs to another
object. Object id and index id in page are %ld, %ld. Object id and index id in extent are
%ld, %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1127 20 Internal Error: The OAM has no room for new inserts. Check OAM for object %ld,
index %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1128 22 The OAM entry for allocation page %ld is missing from the OAM which starts on page
%ld.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1129 10 The requested update to the OAM for object %ld, dbid %ld, index %d, oam page %ld,
would cause a negative page count. allocation page: %ld, oamarray used: %ld, oamarray
unused: %ld, deltaused: %ld, deltaunused: %ld, spid: %ld. Contact your System Admin.
Explanation: Refer to the writeup for this error.
1130 22 A dealloc log record has been detected which does not have an OAM page supplied.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1131 22 The OAM for object %ld, index %d, oam page %ld, database=%d, is currently allocated
to another object.
Explanation: See the writeup for Error 1131.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
819
1132 22 Attempted to log allocation to the log.
Explanation: Report the error to your System Administrator. Adaptive Server must be
restarted.
1133 22 Page %ld was expected to be an OAM page for %ld and it is not.
Explanation: Refer to the writeup for this error.
1134 20 Failed to get lock on OAM page %ld. This should never happen.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
1135 10 Page %ld was given as a target page for allocation to object %ld index id %d and there
is no entry in the OAM for this page. This may indicate corruption of the OAM. Please
run checkalloc on database %.*s.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
1136 21 `Please run the upgrade38 utility before attempting to upgrade your database to MP.'
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
1137 21 `There is insufficient space in database %.*s to run this upgrade.'
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
1138 21 `Failed to complete allocation of SYSGAMS in database %.*s.'
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
1139 20 Impossible deadlock on page mgr lock.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1140 20 `Page mgr lock should not already be held.'
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1141 20 Unexpected value returned to page manager routine: %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics (tablealloc, checkalloc) can be run.
1142 22 Invalid OAM Page %ld. Found pstat=0x%x, object=%ld, database=%d, indid=%d.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
Server Error Messages 1100-1199
820
1143 22 Invalid OAM Page %ld. Expected object=%ld. Found object=%ld, database=%d,
pstat=0x%x, indid=%d.
Explanation: Refer to the writeup for this error.
1144 21 Page number %ld is higher than the highest page in database `%.*s': %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
1145 20 ss %d was expected to hold logical lock on page %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics (checkalloc, tablealloc) can be run.
1146 20 Process %d was expected to hold logical lock on object %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics (checkalloc, tablealloc) can be run.
1147 20 Process %d trying to do a logged operation on a non-logged object %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1148 16 Error: %d, Severity: %d, State: %dn
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1149 21 A Log Run Deallocation routine was passed one or more bad parameters. The bad
parameter is either %ld or %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
1150 20 Failed to get intent lock on object %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1151 11 Object %ld passed to OAM builtin function no longer exists in database %d.
Explanation: An OAM-related system function such as ROWCNT was called with
incorrect arguments, or called for an object which has been dropped.
1152 11 Page %ld passed to OAM builtin function is not an OAM page for object %ld in database
%d.
Explanation: An OAM-related system function such as ROWCNT was called with
incorrect arguments.
1153 11 OAM page %ld passed to rowcnt function is an unallocated page in database %d.
Explanation: Check the arguments passed to the system function ROWCNT.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
821
Server Error Messages 1200-1299
1154 16 WARNING!!! Attempt to do a prefetch of size %dK is not allowed. The prefetch request
is reset to the maximum prefetch size of %dK.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1155 20 Invalid page validation type, %d, requested for page %ld, object %S_OBJID, indid %d in
database %S_DBID.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1156 20 Unable to update the page linkage status for the data only locked table %ld in database
%d due to an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1157 10 Insert free space value %d in page header of DOL datapage %ld belonging to object id
%ld in database ’%.*s’ is incorrect. It has been recomputed and is now %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
1201 20 lock_logical was called with illegal locktype %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1203 20 Caller of lock manager is incorrectly trying to release or downgrade a lock which it
doesn't hold. spid=%d loc ktype=%d dbid=%d page number (or objid for table
lock)=%ld, objid (if not a table lock)=%ld, row number=%ld.
Explanation: Refer to the writeup for this error.
1204 19 SQL Server has run out of LOCKS. Re-run your command when there are fewer active
users, or contact a user with System Administrator (SA) role to reconfigure SQL Server
with more LOCKS.
Explanation: Refer to the writeup for this error.
Server Error Messages 1200-1299
822
1205 13 Your server command (process id #%d) was deadlocked with another process and has
been chosen as deadlock victim. Re-run your command.
Explanation: Refer to the writeup for this error.
1221 26 Lock free chain linkage has been corrupted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1222 26 A non lock is linked on the free chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1223 26 Lock hash table linkage has been corrupted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1224 26 A structure from outside the lock area has been linked onto a lock hash chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1225 26 Lock record chain linkage has been corrupted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1226 26 A non lock record is linked onto a semaphore cursor.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1227 26 Semaphore cursor chain linkage has been corrupted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1228 26 A non semaphore cursor is linked onto a semaphore.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1229 26 The actual number of free locks does not match the free lock count.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1230 26 A semaphore cursor has no lock records linked to it.
Explanation: An internal locking/synchronization rule was broken. Shut down and
restart Adaptive Server. Report the error to Sybase Technical Support.
1231 26 An incorrect lock structure is linked on the free chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1232 26 An incorrect lock structure is linked onto a hash chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
823
1233 26 An incorrect lock structure is linked a chain of lock structures.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1234 26 An incorrect lock structure is linked to a semaphore.
Explanation: An internal locking/synchronization rule was broken. Shut down and
restart Adaptive Server. Report the error to Sybase Technical Support.
1235 26 A semaphore cursor at the head of a semaphore queue is marked as waiting.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1236 26 A semaphore cursor not at the head of a semaphore queue is marked as not waiting.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1237 26 A semaphore cursor has mutually incompatible lock records linked to it.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1238 26 %d locks not accounted for.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1239 26 %d extra locks found.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1241 26 A semaphore cursor refers to a different semaphore than the one it is linked to.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1242 26 A lock record refers to a different semaphore cursor than the one it is linked to.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1243 26 Couldn't find object to be released.
Explanation: Refer to the writeup for this error.
1244 20 Could not find address lock at address 0x%lx while trying to release it.
Explanation: An internal locking/synchronization rule was broken. Report the error to
Sybase Technical Support.
1245 26 Lock record and process disagree.
Explanation: An internal locking/synchronization rule was broken. Report the error to
Sybase Technical Support.
1246 26 Process attempting to wait on a lock that does not belong to it.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
Server Error Messages 1200-1299
824
1247 26 Process attempting to wait on a lock that has already been waited for.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1249 20 Process became runnable before lock it was waiting for was released.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to Sybase Technical Support.
1250 26 A non-preallocated semaphore cursor encountered while trying to obtain a semaphore.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1251 26 An in-use preallocated semaphore cursor was encountered.
Explanation: An internal locking/synchronization rule was broken. Report the error to
Sybase Technical Support.
1252 26 Lock header linkage has been corrupted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1253 26 The wrong number of lock records was found on a semaphore cursor.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1254 26 While following the lock record chain for a process, a lock record belonging to a different
process was encountered.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1255 26 Unlinking a duplicate lock caused a task to be awakened.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1256 26 Encountered a non-preallocated semaphore cursor on a chain that should only have
preallocated semaphore cursors.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1258 26 A process is not waiting for a lock that it should be waiting for.
Explanation: An internal locking/synchronization rule was broken. Report the error to
Sybase Technical Support.
1259 26 A process is waiting for a lock that has been granted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1260 26 A process is waiting for a lock that it did not request.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
825
1261 20 Attempt to promote from page to table locking on objid %ld encountered an internal
error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1262 20 No matching xdes found. Lock was requested for objid %ld, dbid %d, type %d, by
process %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1263 26 A process was found to be waiting for the same object twice.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1265 20 A lock manager routine expected a lock record as an argument but was passed something
else. lr=0x%x, lrmagic=% c.
Explanation: Refer to the writeup for this error.
1266 20 Upgrade of lock on object id or page number %ld left the lock ungranted.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. If the problem persists, report it to your System
Administrator.
1267 26 A lock record at the head of a semaphore queue is not marked as granted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1268 26 A lock record is marked as granted, but isn't at the head of the semaphore queue.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1269 10 Temporary buffer overflow occurred while scanning the lock table. Rows will be missing
in syslocks for one or more objects.
Explanation: This is an informational message. A non-configurable limit was exceeded
but processing continues. No action is required.
1270 26 A task attempted to release a semaphore that it had not previously obtained.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1271 26 A task attempted to acquire a semaphore with a preallocated semaphore cursor that did
not belong to it.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
Server Error Messages 1200-1299
826
1272 20 Invalid parameter(s) passed to lock manager.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1273 16 Syntax error at line %d of file %s starting at `%s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1274 16 Error with input file %s: %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1275 16 The lock unit test can only be run with a single engine on line.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1276 26 Attempt to acquire a lock in dbid %d while in an internal transaction. This is an internal
error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1277 20 In a call to lock_multiple(), the lock requests were out of order. They should be sorted
by object id, dbid.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1278 26 This semawait (1st) should only have one lockrec.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1279 19 SQL Server has run out of locks on engine %d. Re-run your command when there are
fewer active users, or contact a user with System Administrator (SA) role to reconfigure
maximum engine freelocks or number of locks.
Explanation: Refer to the writeup for this error.
1280 26 Lock sleeptask (or waittask) chain has been corrupted.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1281 26 A structure of the wrong type is linked to the lock sleeptask (or waittask) chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
Sybase Technical Support.
1282 26 An incorrect lock sleeptask structure is linked to the Lock Sleeptask chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
827
1283 19 Could not change deadlock checking period because SQL Server has run out of alarms.
Please retry the command later.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
1284 26 Used Lock Sleeptask Entry not in Chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1285 26 Un-used Lock Sleeptask Entry in Lock Sleeptask Chain.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1286 26 Missing Preallocated Lock Sleeptask Entry.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1287 16 Freelock transfer block size (%d) cannot be more than half the number of freelocks
allowed per engine (%d). To increase the number of freelocks allowed per engine please
increase maximum engine freelocks.
Explanation: See the System Administration Guide for more information about `max
engine freelocks'.
1288 16 Setting maximum engine freelocks to %d allows only %d freelocks per engine. This
value cannot be less than twice the value of freelock transfer block size. Please reduce
freelock transfer block size to %d and reattempt this command.
Explanation: See the System Administration Guide for more information about
`freelock transfer block size'.
1289 20 Internal Error in lock manager routine: Invalid lock mode %s, requested by task (family
id %d, spid %d) conflicts with existing family request mode %s belonging to task (family
id %d, spid %d).
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1290 20 Internal Error in lock manager routine: Attempted lock upgrade from %s to %s in parallel
query thread (family id %d, spid %d) is Illegal.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1291 20 Internal Error in lock manager routine: Attempted lock anti-inheritance is an illegal
operation for a non-parent thread (fid %d, spid %d).
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1292 20 Internal Error in lock manager routine: Thread (fid %d, spid %d) incorrectly attempted to
acquire a non-queueing %s lock when thread (fid %d, spid %d) in its family already holds
an insufficient %s lock on objid %d, dbid %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 1300-1399
828
Server Error Messages 1300-1399
1293 20 Internal Error in lock manager routine: Process (fid %d, spid %d) incorrectly attempted
to transfer locks to itself, from a process (fid %d, spid %d) belonging to a different family.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1294 26 Lock_logical was called with an illegal 'op' parameter: %d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1295 26 Unconditional lock request for table or page %d, dbid %d was made while holding a latch.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1298 26 Unexpected position for NKL semawait. This indicates a programmer error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
1299 26 NKL semawait is at an improper position in the queue.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
Number Severity Text and Explanation
1301 16 The Propagation Context Data entry could not be saved. There is already an entry with
the same key values for the context provided.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
1302 16 A Propagation Context Data value could not be returned in parameter %d because the
datatype of the return parameter does not match the datatype of the stored field.
Explanation: Command failed. Check the syntax of the SQL statement calling the
system function.
1303 16 The second argument for this Propagation Context Data built-in command specifies the
number of keys supplied with the call. This argument must be of datatype `integer'.
Explanation: Command failed. Check the syntax of the SQL statement calling the
system function.
1304 16 This Propagation Context Data built-in function requires at least %d arguments.
Explanation: Command failed. Check the arguments of the SQL statement calling the
system function.
CHAPTER 6 Adaptive Server Error Messages
829
1305 16 This Propagation Context Data built-in function requires one argument.
Explanation: Command failed. Check the arguments of the SQL statement calling the
system function.
1306 16 The second argument for this Propagation Context Data built-in command specifies the
number of keys supplied with the call. The value `%d' supplied is more than the keys
given. At most `%d' arguments may be keys for this call.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1307 18 Internal Error in Propagation Context routines: An invalid or garbaged command 0x%x
was seen by pcxt__cmdinit().
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1308 18 Internal Error in Propagation Context routines:
pcxt__nodenew(PCXT_NODE_ENTRY) copied %d arguments, expected %d
arguments.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1309 18 Internal Error in Propagation Context routines: An invalid or garbaged node type 0x%x
tried to free memory at 0x%x in pcxt__nodefree(). The request was ignored.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1310 18 Internal Error in Propagation Context routines: The memory tracking fields in the PCD
resource structure are inconsistent: inuse %d, free %d. Some PCD memory may not be
reclaimed until the login session ends.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1311 18 Internal Error in Propagation Context routines: An invalid or garbaged node type 0x%x
was seen by pcxt__nodedup().
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1312 18 Internal Error in Propagation Context routines: An invalid or garbaged node type 0x%x
was seen by pcxt__nodenew().
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1313 18 Internal Error in Propagation Context routines: An invalid or garbaged event type 0x%x
was seen by pcxt_event().
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 1500-1599
830
Server Error Messages 1500-1599
1314 16 The built-in function requested %d data fields as return parameters. The Propagation
Context Data entry that was selected contains only %d data fields. It is an error to request
more data fields than exist in the entry.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1315 16 Argument %d of this Propagation Context Data built-in command must be of datatype
`integer'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1316 10 Context Name is (%.*s)
Explanation: This is an informational message.
1317 10 Attribute Name (%.*s) Value (%.*s)
Explanation: This is an informational message.
1318 16 Attributes in SYS_SESSION cannot be set.
Explanation: This is an informational message.
Number Severity Text and Explanation
Number Severity Text and Explanation
1501 20 Sort failure
Explanation: Refer to the writeup for this error.
1502 20 Sort Internal Error: Bad Sort Descriptor!!
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1503 20 Sort Internal Error: The Root page of right/left sub-index tree is missing.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1504 20 Internal Sort Error. Empty Index Page found.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
CHAPTER 6 Adaptive Server Error Messages
831
1505 14 Create unique index aborted on duplicate key. Primary key is `%S_KEY'
Explanation: Refer to the writeup for this error.
1507 10 Warning: deleted duplicate row. Primary key is `%S_KEY'
Explanation: Report the error to your System Administrator. You may need to increase
swap space.
1508 14 Create index aborted on duplicate rows. Primary key is `%S_KEY'
Explanation: Refer to the writeup for this error.
1509 20 Row compare failure of RIDs (%ld, %d) and (%ld, %d), keycnt = %ld, compflags = %ld,
rowformat = %ld, minlen = %ld.
Explanation: Refer to the writeup for this error.
1510 17 Sort failed: Out of space in database `%.*s'
Explanation: Refer to the writeup for this error.
1511 20 Sort cannot be reconciled with transaction log
Explanation: Adaptive Server encountered an internal error indicative of some problem
in logging/recovery. Reconnect to Adaptive Server. Report the error to your System
Administrator.
1513 20 Reuse of extent failed in sort
Explanation: Adaptive Server encountered an internal error indicative of some problem
in logging/recovery. Reconnect to Adaptive Server. Report the error to your System
Administrator.
1514 21 Sort failed because it attempted to allocate page %ld and found that the page was busy.
Buffer %S_BUF contains a cached and referenced page with objid %ld indid %ld and
status 0x%x.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
1515 20 Bad session descriptor for sort
Explanation: This error occurs during a sort operation when the server finds that a
session descriptor (pointing to row ID’s) is invalid. Shut down and restart the server to
correct the problem.
1519 20 Internal Sort Error. A transaction that is involved in Parallel Sort is being redone.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Restart Adaptive Server.
1520 18 Sort failed for table `%.*s' in database `%.*s' because internal count of used pages is
incorrect. Run DBCC TABLEALLOC to correct the value.
Explanation: The create index command allocates a work area based on an estimate in
the OAM page of the number of data pages in the table. If this value is too low, the work
area is too small, the sort fails, and Error 1520 is raised. Use dbcc tablealloc to update
the page count and correct this error.
Number Severity Text and Explanation
Server Error Messages 1500-1599
832
1521 18 Sort failed because a table in tempdb used for the processing of the query had a bad data
page count. Tempdb should not have been damaged.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Restart Adaptive Server.
1522 20 Sort failure. Prevented overwriting of allocation page in database `%S_DBID' by aborting
sort.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Run `dbcc checkdb' and check available space.
1523 20 Sort failure. Prevented incorrect extent deallocation by aborting sort.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Run `dbcc checkdb' and check available space.
1525 21 Sort Failure. Rollforward of sort encountered sort descriptor timestamps out of sequence.
Old timestamp in log: %04x %08lx. New timestamp in log: %04x %08lx. Timestamp in
sort descriptor: %04x %08lx.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1526 17 Sort failure. The configure size for data cache (%.*s) is not sufficient to handle the sort
buffers (%d) requested. Please reconfigure the data cache or sort buffers and try the
command again.
Explanation: Command failed due to resource limitation on the specified data cache.
Contact your System Administrator to address the resource issue (see System
Administration Guide for help with configuring memory).
1527 20 Sort failure. Unknown exception returned from bufclaimcache: %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1528 21 Character data comparison failure. An unrecognized Sort-Map-Element type (%d) was
found in the server-wide default sort table at SMEL entry [%d].
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1529 21 Character data comparison failure. A list of Sort-Map-Elements from the server-wide
default sort table does not end properly. This list begins at SMEL entry [%d].
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
1530 16 Create index with sorted_data was aborted because of row out of order. Primary key of
first out of order row is `%S_KEY'
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
833
1531 16 The sorted_data option cannot be used for a nonclustered index if the keys are not unique
within the table. Create index was aborted because of duplicate keys. Primary key is
`%S_KEY'.
Explanation: Refer to the writeup for this error.
1532 20 Invalid merge page. %s on page %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator so dbcc checks (tablealloc,
indexalloc) can be run .
1533 20 Internal Sort error. Extend read returns an invalid page. Requested pageno=%ld Read
pageno=%ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator so dbcc checks (tablealloc,
indexalloc) can be run .
1534 20 Internal Sort error: Attempt to split presorted clustered data page failed. Attempted to split
page, pageno = %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1535 20 Internal Sort error: Attempt to split presorted clustered data page failed. Split page, pageno
= %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1536 20 Internal Sort error. Presorted clustered data page invalid. Page, pageno = %ld, parm1 =
%d, parm2 = %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1537 17 Cannot create clustered index on partition table due to not enough sort buffers. Configure
at least %ld sortbuffers to create the clustered index on partition table.
Explanation: The parallel sort expect at least N number of sort buffers where N= number
of consumers to run the parallel sort. Modify the command to fit available resources, retry
when the resource is available, or contact your System Administrator to address the
resource problem.
1538 17 Parallel degree %ld is less than required parallel degree %ld to create clustered index on
partition table. Ch ange the parallel degree to required parallel degree and retry.
Explanation: Command failed due to resource limitation. Contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
Server Error Messages 1500-1599
834
1539 17 Only %d worker processes are available when %d worker processes are required. Process
aborted.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
1540 10 Warning: Only %d worker processes are available when %d worker processes are required.
Explanation: This is an informational message.
1541 10 Internal sort error: cannot allocate memory in data sampling.
Explanation: This is an informational message. No action is required.
1542 10 Internal sort error: Too small a sample set!
Explanation: This is an informational message. No action is required.
1543 20 Cannot create a pipe group for sorting in parallel.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1544 20 Parallel Sort: Cannot initiate producers and consumers.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1545 20 Parallel sort parent driver cannot send message to child thread.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1546 20 Parallel sort parent driver cannot receive message from child threads.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1547 20 Parallel sort parent driver error in waiting for child threads
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1548 10 The Create Index is done using %s
Explanation: This is an informational message. No action is required.
1549 10 Partition Element: %ld
Explanation: This is an informational message. No action is required.
1550 10 Sort buffer size: %ld
Explanation: This is an informational message. No action is required.
1551 10 Parallel degree: %ld
Explanation: This is an informational message. No action is required.
1552 10 Number of producer threads: %ld
Explanation: This is an informational message. No action is required.
1553 10 Number of consumer threads: %ld
Explanation: This is an informational message. No action is required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
835
1554 10 Number of output devices: %ld
Explanation: This is an informational message. No action is required.
1555 10 Number of sampled records: %ld
Explanation: This is an informational message. No action is required.
1556 16 No such message!
Explanation: Check command syntax and semantics.
1557 10 Inconsistent distribution map (%d elements without element information)!
Explanation: This is an informational message. No action is required.
1558 10 Empty distribution map
Explanation: This is an informational message. No action is required.
1559 10 The distribution map contains %d element(s) for %d partitions.
Explanation: This is an informational message. No action is required.
1560 10 Warning: Number of filled elements differs from the data structure.
Explanation: This is an informational message. No action is required.
1561 20 Producer cannot insert rows into pipe buffers.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator.
1562 10 The sort for Worktable%d is done in %s
Explanation: This is an informational message. No action is required.
1563 10 The sort for %.*s is done in %s
Explanation: This is an informational message. No action is required.
1564 10 Psort option is not enabled in this database. Create Index will be done using Serial Sort
Explanation: This is an informational message. No action is required unless you wish to
use parallel sort for the operation.
1565 20 The database option pllsort option is not enabled in this database. Create Clustered Index
on partition table cannot be done using Serial Sort. Set the pllsort database option and
rerun.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1566 10 Warning: Attempt to create a clustered index on the partitioned table '%.*s' with distinct
key values less than the number of partitions. Some partitions will be empty if the index is
successfully created.
Explanation: This is an informational message. No action is required.
1567 20 Create Index Internal Error %ld detected
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 1500-1599
836
1568 16 Unable to find sort order. Please check sort order ID or name.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1569 17 Unable to get a conversion handler for the built-in sort function.
Explanation: Command failed due to resource limitation. Contact your System
Administrator to address the resource problem.
1570 10 The generated sortkey has been truncated.
Explanation: This is an informational message. No action is required.
1571 10 Unknown sort order ID %ld. Using binary sort order instead.
Explanation: This is an informational message. No action is required.
1572 16 Unknown sort order file name '%.*s' or Unicode cache is full.
Explanation: Command failed due to invalid or illegal request.
1573 16 Can't open the directory $SYBASE/collate/unicode.
Explanation: Command failed due to invalid or illegal request. Check syntax and
permissions.
1574 20 Begin transaction failed when attempting to update syscharsets sort order information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1575 20 Unable to open syscharsets table to update sort order information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1576 20 Unable to lock syscharsets table to update sort order information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1577 20 Update of sort order informarion in syscharsets failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1578 20 Unable to insert sort order information into syscharsets.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1579 16 Error converting characters into Unicode to generate sort keys. There maybe illegal byte(s)
in source string, or failure to allocate memory.
Explanation: Command failed due to invalid or illegal request.
1580 16 Unable to generate sortkey.
Explanation: Command failed due to invalid or illegal request.
1581 16 Create index was aborted because pages in the data only locked table are not linked.
Explanation: Notify your System Administrator so that dbcc diagnostics can be run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
837
1582 17 Failed to allocate memory for %ld auxiliary keep buffers. Try this operation when there is
enough memory in the procedure cache, or increase the procedure cache memory and retry
the sort operation.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
1583 20 Found a rowlen of %ld, from the merge, while building index on %.*s. The maximum row
length is %ld. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1584 20 Unable to build the parent page at level %d while building index on %.*s. Please contact
Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1585 20 Validation of datapage %ld in table %.*s failed. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1586 20 Internal Sort Error. Attempt to hash a buffer from cache %.*s into cache %.*s. Please
contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1587 20 Empty buffer 0x%lx or mismatch in page or row number. SDES page=%ld, rownum=%ld,
RID page=%ld, rownum=%ld. Ple ase contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1588 20 Attempt to create an index with sorted data option failed. Please contact Sybase Technical
Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1589 20 Found bad merge type %d while merging sub-indexes. Please contact Sybase Technical
Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1590 20 Internal error. Pipe create operation failed. Please report this to Sybase Technical Support
staff.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1591 20 Internal error. Pipe destroy operation failed. Please report this to Sybase Technical Support
staff.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 1500-1599
838
1592 20 Internal error. Pipe open operation failed. Please report this to Sybase Technical Support
staff.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1593 20 Internal error. Pipe close operation failed. Please report this to Sybase Technical Support
staff.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1594 20 Internal error. Pipe read operation failed. Please report this to Sybase Technical Support
staff.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1595 20 Internal error. Pipe write operation failed. Please report this to Sybase Technical Support
staff.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1596 20 Internal Sort Error. Attempt to hash a buffer from cache %.*s into cache %.*s. Please
contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1597 17 Sort failure: Number of available sort buffers (%d) is less than the number required (%d)
for executing this query. Contact your system administrator to reconfigure the number of
sort buffers and try the query again.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
1598 21 Can not use Unilib Thai Dictionary Sort Order because dataserver may have memory
corruption.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator. Adaptive Server must
be restarted and DBCC diagnostics run.
1599 21 Can not use Unilib Thai Dictionary Sort order because the conversion handle needed is
NULL. Please check server’s error log file.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
839
Server Error Messages 1600-1699
Number Severity Text and Explanation
1601 21 There are not enough `user connections' available to start a new process. Retry when there
are fewer active users, or ask your System Administrator to reconfigure SQL Server with
more user connections.
Explanation: Refer to the writeup for this error.
1602 21 Unable to initialize network %d
Explanation: Refer to the writeup for this error.
1603 21 Process priority %d invalid or no process slots available
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1604 21 Process not runnable or kpid %d not within range
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
1605 21 Failed to open virtual socket for new connections
Explanation: Refer to the writeup for this error.
1606 21 Failed to initialize network receive buffer
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
1607 21 Failed to initialize network send buffer
Explanation: A problem was encountered by a client process connecting to Adaptive
Server. If the problem recurs, contact your Network Administrator.
1608 18 A client process exited abnormally, or a network error was encountered. Unless other
errors occurred, continue processing normally.
Explanation: Refer to the writeup for this error.
1609 21 Kpid %d out of range
Explanation: A problem was encountered by a client process connecting to Adaptive
Server. If the problem recurs, contact your Network Administrator.
1610 21 Could not kill process %d
Explanation: A problem was encountered by a client process connecting to Adaptive
Server. If the problem recurs, contact your Network Administrator.
1611 21 Could not install quit function
Explanation: A problem was encountered by a client process connecting to Adaptive
Server. If the problem recurs, contact your Network Administrator.
Server Error Messages 1600-1699
840
1612 21 Could not install attention function
Explanation: A problem was encountered by a client process connecting to Adaptive
Server. If the problem recurs, contact your Network Administrator.
1613 21 Could not close network %d connection for server process %d.
Explanation: Refer to the writeup for this error.
1614 21 Could not yield process
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
1615 21 Process unable to sleep
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1616 21 Failed to flush receive stream buffer
Explanation: A problem was encountered by a client process connecting to Adaptive
Server. If the problem recurs, contact your Network Administrator.
1617 21 Could not infect process %d
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1618 21 Could not spawn the checkpoint process, unable to continue.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1619 21 Could not open TEMPDB, unable to continue.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
1620 21 Failure to open master db for the first time
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
1621 18 Type `%c' not allowed before login.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1622 18 Type `%c' not implemented.
Explanation: Refer to the writeup for this error.
1623 21 Warning: dataserver -p option fails. Please check for state `%d' to see where it fails.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
841
Server Error Messages 1700-1799
1624 18 Warning: Errors occured while initializing thresholds on tempdb. Trying to continue the
startup. Thresholds might not be active on tempdb.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1625 21 Warning: dataserver -u option failed. Please check for state ’%d’ to see where it failed.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator. Adaptive Server must
be restarted and DBCC diagnostics run.
1637 16 Could not initialize SSL master context.
Explanation: There was an SSL error during login. Report the error to your System
Administrator.
1638 16 Execution of login script ’%.*s’ failed with last error = %d. See server errorlog
for details.
Explanation: Report the error to your System Administrator.
1639 16 Login script ’%.*s’ does not allow you to login to the server. Contact your
database administrator.
Explanation: Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
1701 16 Creating table ’%.*s’ failed because the minimum row size would be %d bytes. This
exceeds the maximum allowable size of a row for this table, %d bytes.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
query to conform to the requirement specified in the error message.
1702 16 %s failed because definition of column ’%.*s’ in table ’%.*s’ exceeds the limit of %d
columns per table.
Explanation: Refer to the writeup for this error.
1703 17 Failed to allocate disk space for a work table in database `%.*s'. You may be able to free
up space by using the DUMP TRANsaction command, or you may want to extend the size
of the database by using the ALTER DATABASE command.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Server Error Messages 1700-1799
842
1704 16 Only the SA can create the system table `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
1705 16 Must create system table `%.*s' in the Master Database.
Explanation: Command failed due to invalid or illegal request, check current database.
System table shown in the message should be created in master database.
1706 16 System table `%.*s' was not created, because ad-hoc updates to system catalogs are not
enabled.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
1707 18 Could not create system table `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1708 16 Warning: Row size (%d bytes) could exceed row size limit, which is %d bytes.
Explanation: Adaptive Server could not perform the requested action. Modify your
table schema to meet the requirement indicated in the error message.
1709 16 Referenced table name missing in a referential constraint declaration on table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1710 16 Referenced table `%.*s' specified in a referential constraint declared on `%.*s' does not
exist in the database `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1711 16 There is no unique constraint on the referenced columns in the referenced table `%.*s'
specified in referential constraint declaration on the table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1712 18 Internal inconsistency - constraint exists in sysconstraints table, but not sysobjects table,
id = %d.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1714 16 Exceeded maximum allowed referenced columns, %d, in a single referential constraint
declaration, table = ’%.*s’, database = ’%.*s’.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the requirement for the objects or variables shown in the error message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
843
1715 16 The number of columns in a foreign key column list and primary key/referenced column
list not the same in referential constraint declaration on table `%.*s', in database `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1716 18 Invalid system table given for status update, this is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1717 16 System catalog column/table specified for status change not found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1718 16 The number of columns in a forign key column list is less than a primary/referential
column list in a referential constraint declaration, table = `%.*s', data base = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1719 16 Primary key does not exist for the table referenced in a referential constraint declaration,
table = `%.*s', data base = `%.*s'.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
1720 16 A column referenced in a referential constraint declaration does not exist, referencing
table = `%.*s', data base = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1721 16 Column types of referencing and referenced columns don't match. referencing column =
`%.*s', referenced column = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1722 16 Column lengths of string type referencing and referenced columns don't match.
referencing column = `%.*s', referenced column = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1723 16 Column precision and scale of numeric referencing and referenced columns don't match.
referencing column = `%.*s', referenced column = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1724 16 The number of columns in a forign key column list is greater than a primary/referential
column list in a referential constraint declaration, table = `%.*s', data base = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 1700-1799
844
1725 16 SELECT INTO failed because column %d in table `%.*s' has a null column name. Null
column names are not allowed.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1726 18 Internal inconsistency: database id %d sent to crt_main() does not match Pss->pcurdb
value of %d.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
1727 20 The crt_main() function is trying to put too many lock requests in the lock_requests[]
array.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
1729 10 An object with the same name, but owned by a different user, is already being replicated.
The table `%.*s' is not marked as replicated.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
1730 10 Due to an internal error the table `%.*s' is not marked as replicated. Please contact your
System Administrator (SA) for help.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
1732 20 Failed to reserve/initialize allocation hints space in table `%.*s'.
Explanation: See the writeup for Error 1732.
1734 16 You cannot specify both a default value of NULL and a NOT NULL constraint for
column `%.*s' in table `%.*s'. Retry your command with only one of these column
options.
Explanation: The SQL statement is semantically incorrect. Choose either NULL or
NOT NULL.
1736 16 Cannot create auditing-related tables in any database other than sybsecurity database.
Explanation: This message is generated when an SSO tries to create audit tables in a
database other than sybsecurity.
1737 16 Cannot create tables starting with `sysaudits_'.
Explanation: This message is generated when a user tries to create a table starting with
sysaudits_. This is not allowed.
1738 16 Creating this referential constraint would result in the total number of referential
constraints of table %.*s exceeding %d. Please run: 'sp_helpconstraint %.*s' to find out
the number of referential constraints that this table has.
Explanation: Adaptive Server could not perform the requested action.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
845
1739 10 Warning: Parameter `exp_row_size' is not applicable to table `%.*s' in allpages locking
scheme
Explanation: Retry the command if necessary. Do not specify exp_row_size on an
allpages-locked table. Use this parameter only for tables that use the data-only-locked
scheme and contain variable length rows.
1740 10 Warning: Parameter `max_rows_per_page' is not applicable to table `%.*s' in `datapages'
or `datarows' locking scheme
Explanation: Do not specify max_rows_per_page on a data-only-locked table. Use
this parameter only for tables that use the allpages-locked scheme.
1741 10 Warning: Parameters `exp_row_size' and `max_rows_per_page' both specified for table
`%.*s'. Only parameter appropriate to lock scheme specified will be used internally, but
both are stored. See users manual for more information.
Explanation: You cannot mix parameters for data-only-locked tables and all-pages-
locked tables in one DDL command.
1742 16 Expected row size specified on table '%.*s' is invalid. Expected row size should be either
0, 1 or between minrow length %d and maxrow length %d
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1743 10 Multiple lock schemes specified on the table '%.*s'. Lock scheme has to unique.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1744 10 Internal error: Dataonly Lock scheme is not supported on this system table '%.*s'. Contact
sybase technical support for help.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
1750 20 Failed to reserve attribute space for table '%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1751 20 Failed to initialize attribute space for table '%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1752 16 Table '%.*s' has fixed length schema. Parameter 'exp_row_size' is not applicable to tables
with fixed length schema.
Explanation: Cannot specify an expected row size for fixed-length tables. See the
writeup for Error 1739.
1753 16 DELETE STATISTICS failed on table '%.*s' see error log for more information.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions.
Number Severity Text and Explanation
Server Error Messages 1700-1799
846
1754 16 DELETE STATISTICS duplicate column '%.*s' specified, column can only be referenced
once.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions.
1755 16 DELETE STATISTICS column name '%.*s' not found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions.
1756 18 syscolumns cannot be read.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
1757 10 UPDATE STATISTICS - could not obtain required locks on table '%.*s
Explanation: Report this error to your System Administrator.
1758 10 UPDATE STATISTICS failed to complete on table '%.*s
Explanation: Report this error to your System Administrator.
1759 16 UPDATE STATISTICS number of step values requested '%d' must be greater than or
equal to '%d' values
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1760 16 UPDATE STATISTICS - index and column list cannot be specified at the same time
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1761 13 Deadlock detected on '%.*s' while processing statistics
Explanation: Rerun the command that raised this error.
1762 18 Cannot insert rows into sysstatistics
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
1763 18 Cannot insert rows into sysstatistics, due to multiple equal frequency values, please
contact Sybase Techn ical Support
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
1764 18 Failed to insert row into worktable, when projecting base table on to work table for
collecting statistics .
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
847
1765 10 Unable to start a level zero scan on table '%.*s' for UPDATE STATISTICS. This can
happen if some DDL command like ALTER/CREATE INDEX/REORG/DROP is active
on the table.
Explanation: Retry the scan after completing the DDL command.
1766 16 Cannot create syscoordinations tables in any database other than sybsystemdb.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
1767 16 Number of variable length columns exceeds limit of %d for allpage locked
tables. %s for ’%.*s’ failed.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
1768 10 Warning: Potential offset of column ’%.*s’ (%d bytes) and subsequent variable-
length columns in table %.*s exceeds limit of %d bytes for column-offset of
variable-length columns in DOL tables. Future inserts to this table may fail.
Explanation: This informational messages indicates that your DDL command may
cause problems at future inserts into the DOL table. Check and modify the DDL to meet
the Adaptive Server requirement shown in the error message.
1769 16 Variable-length column ’%.*s’ starts at column-offset %d bytes and is non-
nullable. This will prevent inserting any data into that column as the column
offset exceeds the limit of %d bytes for column-offsets in DOL tables. %s ’%.*s’
failed.
Explanation: Modify your DDL command to meet the Adaptive Server requirement for
the objects or variables shown in the error message.
1770 16 %s failed. Addition of column ’%.*s’ to table ’%.*s’ exceeds maximum row
width. Rows must be between %d bytes and %d bytes.
Explanation: Adaptive Server could not perform the requested action. Modify your
DDL command to meet the Adaptive Server requirement for the objects or variables
shown in the error message.
1771 10 Warning: Maximum row size exceeds allowable width. It is being rounded down
to %d bytes.
Explanation: This informational message indicates that your DDL is being modified to
meet the Adaptive Server requirement for the objects or variables shown in the error
message.
1772 10 Warning: Update of SYSSTATISTICS row (sequence no %d, format ID %d,
column IDs: %s) failed. Statistics row deleted. Regenerate statistics for these
columns.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
Number Severity Text and Explanation
Server Error Messages 1800-1899
848
Server Error Messages 1800-1899
Number Severity Text and Explanation
1801 16 Database `%.*s' already exists
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1802 11 CREATE DATABASE failed. Some disk names listed in command were not found.
Check that names exist and are spelled correctly before re-running
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
1803 17 CREATE DATABASE failed. Could not allocate enough disk space for a new database
on the disks named in the command. Total space allocated must be at least %d Mbytes
(%ld logical pages) to accommodate copy of Model Database.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
1804 10 There is no disk named `%.*s'. Checking other disk names.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
1805 10 CREATE DATABASE: allocating %ld logical pages (%d.%d megabytes) on disk ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
1806 21 Crdb_dbrow: Getnext SCAN_NOINDEX on sysdatabases.dbid failed to find row for
MODELDBID.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
1807 17 MODEL database in use, cannot create new database. Contact a user with System
Administrator (SA) role before re-running CREATE DATABASE.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
1808 21 Crdb_disk: Getnext SCAN_NOINDEX on sysdevices.status=DEFAULT failed to find
default rows
Explanation: Refer to the writeup for this error.
1809 14 CREATE DATABASE must be preceded by a `USE master' command. Check with your
DBO <or a user with System Administrator (SA) role> if you do not have permission to
USE master.
Explanation: Refer to the writeup for this error.
CHAPTER 6 Adaptive Server Error Messages
849
1810 16 CREATE DATABASE failed because of incorrectly specified or unavailable space. Total
number of megabytes specified and available must be at least %d megabytes so Model
Database can be copied to the new database.
Explanation: Refer to the writeup for this error.
1811 16 `%.*s' is the wrong type of device for CREATE or ALTER database. Please check
sysdevices. The CREATE or ALTER is aborted.
Explanation: Refer to the writeup for this error.
1813 16 Cannot open new database `%.*s'. CREATE DATABASE is aborted.
Explanation: Refer to the writeup for this error.
1814 10 Problem creating Temporary Database - if out of space, please extend and reboot. If some
other problem, please contact Technical Support.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
1816 16 CREATE or ALTER DATABASE failed because the device '%.*s' has no space available
either for log or for data.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1817 16 Problem allocating extents for SYSGAMS. Create/alter database is aborted.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1818 17 CREATE DATABASE failed because the device `%.*s' is not online.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
1820 20 This command adds %S_MSG space to disk `%.*s', which previously contained only
%S_MSG. You must specify WITH OVERRIDE to force this allocation.
Explanation: Adaptive Server encountered an internal error affecting the current
process. In order to mix data and log space take corrective action as indicated in the error
message.
1822 16 Invalid database maxhold provided.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1823 16 Invalid label provided. Dbmaxhold must be dominated by your maxwrite.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1824 16 Invalid label provided. Dbmaxhold must dominate your minwrite.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 1800-1899
850
1825 14 Invalid curwrite label for creating sybsecurity database, label must be DATA_HIGH.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
1828 16 Cannot create sybsecurity with the log segment and the default segment on the same
device.
Explanation: An SSO tried to create the sybsecurity database with default segment and
log segment on the same device.
1829 16 CREATE DATABASE failed because there is no space left on any of the data disk(s)
specified.
Explanation: CREATE DATABASE failed because there is no space left on any of the
specified data disk(s).
1830 16 Cannot create a proxy database without a storage location defined: create database
<dbname> with default_location = ’pathname’ for proxy_update
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1831 16 Cannot create this database since system proxy databases are enabled on the companion
server in failed over mode.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1832 16 Disk ’%.*s’ is failed over. The CREATE or ALTER database command is aborted.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1833 0 Cannot create a system proxy database through T-SQL.
Explanation: Refer to the Adaptive Server Reference Manual for information about
the stored procedure you were running when you got this message.
1834 16 CREATE DATABASE of ’%.*s’ failed because the name is reserved for failed over
system database.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
1835 16 Arithmetic overflow error for parameter ’%s’.
Explanation: Adaptive Server could not perform the requested action. Check query and
retry.
1836 10 Warning: creating a proxy database whose estimated space requirements are %d
pages, yet only %d pages are available.
Explanation: Adaptive Server could not perform the requested action. Check query and
retry.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
851
Server Error Messages 1900-1999
1837 16 CREATE DATABASE failed to create a dedicated data segment. The specified data
segment size is too small to accommodate the data from the model database
.
Explanation: Adaptive Server could not perform the requested action. Check query and
retry.
Number Severity Text and Explanation
Number Severity Text and Explanation
1901 16 Column `%.*s' -- Can't create index on a column of BIT data type.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
1902 16 Cannot create more than one clustered index on table `%.*s'. Drop the existing clustered
index `%.*s' before creating another
Explanation: Refer to the writeup for this error.
1903 16 %d is the maximum allowable size of an index. Composite index specified is %d bytes.
Explanation: Refer to the writeup for this error.
1904 16 Cannot specify more than %d column names for index key list. %d specified.
Explanation: A composite index is any index that uses more than one column. Error
1904 occurs when more than 31 columns are combined in a single composite index .
Change your create index statement to include no more than the maximum number of
columns allowed.
1905 21 Could not find `zero' row for index `%.*s' the table in sysindexes.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
1906 11 Cannot create an index on table `%.*s', because this table does not exist in database
`%S_DBID'.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
1907 10 Create index on non-empty table not supported yet
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Server Error Messages 1900-1999
852
1908 16 Too many parameters -- symbol table overflow.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1909 16 Can't use duplicate column names in index key list. Column name `%.*s' listed more than
once.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1910 16 Cannot create more than %d indexes on one table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1913 16 There is already an index on table `%.*s' named `%.*s'
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1914 16 Cannot create index on object `%.*s' because it is not a user table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1915 14 Only the owner of table `%.*s' or a user with System Administrator (SA) role can create
an index on it.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
1916 16 CREATE INDEX options %s and %s are mutually exclusive.
Explanation: Refer to the writeup for this error.
1918 10 Non-clustered index (index id = %d) is being rebuilt.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
1919 16 Column `%.*s' -- Can't create index on a column of TEXT or IMAGE data type.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1920 16 A column in a primary key constraint's column list is not constrained to be not null,
column name: `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1921 16 An index with the same columns in the same order already exists on the table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1922 16 An unknown index creation error occurred: %d.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
853
1923 16 A table cannot have more than one primary key, attempt to define a second primary key
failed on table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1924 16 You cannot create an index on the sysaudits table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1927 25 Create Index failed because user curwrite level is not equal to the level of table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
1928 16 Cannot create clustered index '%.*s' on '%.*s' which has %d partitions because the
maximum number of partitions allowed on a table with clustered index is %d.
Explanation: Refer to the writeup for this error.
1929 20 Failed to reserve/initialize allocation hints space in index `%.*s' on table `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
1930 16 Cannot specify more than %d column names for index key list. %d specified. Check
sp_dboption for nonunique index option, it has added an extra key for indentity coulumn.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
(Discontinued in 11.9.2).
1931 16 You cannot re-create the same non-clustered index (ID %d) for object ID %ld in database
`%.*s' because you dropped it twice in a single transaction. Transaction rolled back.
Explanation: For a database which has been marked for `ddl in tran', a non-clustered
index cannot be re-created if it has already been dropped twice within a transaction.
1932 16 You cannot re-create the same clustered index for object ID %ld in database `%.*s' more
than once in a single transaction. Transaction rolled back.
Explanation: For a database which has been marked for `ddl in tran', a clustered index
cannot be re-created more than once within a transaction.
1933 12 The object `%.*s' is not a partitioned table. UPDATE PARTITION STATISTICS can only
be run on partitioned tables.
Explanation:
1934 16 Invalid partition number %d. Valid partition number is a positive integer.
Explanation: Re-try the query using a valid number.
1936 10 Warning: Clustered index '%.*s' has been created on the empty partitioned table '%.*s'.
All insertions will go to the first partition. To distribute the data to all the partitions, re-
create the clustered index after loading the data.
Explanation: This is an informational message. Take the indicated action if you wish to
distribute data across partitions.
Number Severity Text and Explanation
Server Error Messages 1900-1999
854
1937 10 Warning: Clustered index '%.*s' has been created on the partitioned table '%.*s' with %d
partitions using the segment %d with %d devices. For complete I/O parallelism, each
partition should be on a separate device.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
1938 16 Cannot create index or unique constraint because cursor '%.*s' is still open. Close the
cursor(s) before creating index or constraint.
Explanation: Re–try the query after taking the indicated action.
1939 16 Cannot create a clustered index with sorted_data option on the 11.0 partitioned table
'%.*s'. This option isn't allowed. To create the index do not use this option.
Explanation: Re–try the query using the recommended action.
1940 16 Cannot create clustered index on table '%.*s' because there are one or more isolation level
0 scans, or RE ORG command, active on the table.
Explanation: Retry the command after the scans are complete.
1941 10 Warning: Clustered index '%.*s' has been created with ignore_dup_row on table '%.*s',
which uses data-only locking. ignore_dup_row cannot be enforced for subsequent
insertions and updates.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
1942 16 You cannot drop and re-create the same clustered index with sorted data for object ID %ld
in database '%.* s' in a single transaction. Transaction rolled back.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
1944 16 The clustered index cannot be created on a partitioned table using serial sort. The
CONSUMER value specified in the CREATE INDEX command must be greater than 1.
Explanation: Modify your DDL command to meet the Adaptive Server requirement for
the objects or variables shown in the error message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
855
Server Error Messages 2000–2099
Number Severity Text and Explanation
2001 10 Cannot use duplicate parameter names. Parameter name `%.*s' listed more than once.
Explanation: Check command syntax and semantics.
2002 10 Cannot use variable `%.*s' without first declaring it.
Explanation: Check command syntax and semantics.
2004 16 Procedure `%.*s' has already been created with group number %d - create procedure with
an unused group number
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
2005 18 Maximum procedure %s count exceeded. Limit is %d. Modify the procedure to use
fewer %ss.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2007 11 Cannot add rows to sysdepends for the current stored procedure because it depends on
the missing object `%.*s'. The stored procedure will still be created.
Explanation: This is an informational message or a message header. No action is
required.
2008 16 The object `%.*s' is not a procedure so you cannot create another procedure under that
group name.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
2009 16 Group number not allowed in ESP creation.
Explanation: You cannot use group numbers when creating extended stored
procedures.
2010 16 A procedure by that name already exists.
Explanation: Use a different name for the new procedure.
2011 16 System stored procedures (that is, stored procedures beginning with 'xp _' or 'sp_' and
which are owned by the dbo) can only be created in either 'master' or 'sybsystemprocs'.
Explanation: You tried to create a system stored procedure in a database that does not
allow it. You must use master or use sybsystemprocs, and re-try procedure creation.
Server Error Messages 2100–2199
856
Server Error Messages 2100–2199
Number Severity Text and Explanation
2103 16 Cannot create a trigger on a view, name: %.*s
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2106 11 Cannot create a trigger on table `%.*s', because this table does not exist in database
`%S_DBID'.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
2108 16 Cannot CREATE TRIGGER on table `%.*s',because you can only create a trigger on a
table in the current database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2109 16 Cannot CREATE TRIGGER on table `%.*s', that accesses `inserted' or `deleted' because
the table was created with the no_log option
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2110 20 The proccreate() function is trying to put too many lock requests in the lock_requests[]
array.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2111 16 Create trigger aborted. User's cuwrite is not equal to the hurdle of table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2112 16 Cannot CREATE TRIGGER on table `%.*s', because it is a system table. Triggers are not
allowed on system tables.
Explanation: Triggers are not allowed on system tables. Check your query and working
database context.
CHAPTER 6 Adaptive Server Error Messages
857
Server Error Messages 2200–2299
Number Severity Text and Explanation
2200 10 System databases that did not fail over cannot be shut down.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2201 11 Unable to find database %.*s in sysdatabases. Cannot shut down the database.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
2202 16 You cannot start database shutdown from the database to be shut down.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2203 18 Warning: HA Subsystem Internal Error - unable to spawn thread executing database
shutdown in synchronous mode.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
2204 16 Database %.*s dbid %d was found to be in use after it was marked for shutdown.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2205 18 Warning: HA Subsystem Internal Error - child thread suicide failed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
2206 10 Database %.*s with dbid %d is already shut down.
Explanation: This is an informational message or a message header. No action is
required.
2207 10 DBS_DEBUG_MSG: after cleaning the buffers
Explanation: This is an informational message or a message header. No action is
required.
2208 10 DBS_DEBUG_MSG: asking all tasks to reach 1st barrier
Explanation: This is an informational message or a message header. No action is
required.
2209 10 DBS_DEBUG_MSG: **** stopped %d
Explanation: This is an informational message or a message header. No action is
required.
Server Error Messages 2200–2299
858
2210 10 DBS_DEBUG_MSG: waiting for tasks to reach 1st barrier
Explanation: This is an informational message or a message header. No action is
required.
2211 10 DBS_DEBUG_MSG: Wait on dbt keep count and freeing of resources done in
asynchronous mode by the dbshutdown process: %d
Explanation: This is an informational message or a message header. No action is
required.
2212 10 DBS_DEBUG_MSG: Wait on dbt keep count and freeing of resources done in
synchronous mode by the dbshutdown process: %d
Explanation: This is an informational message or a message header. No action is
required.
2213 10 DBS_DEBUG_MSG: now waiting for dbtable keeps to drain out
Explanation: This is an informational message or a message header. No action is
required.
2214 10 DBS_DEBUG_MSG: final checks
Explanation: This is an informational message or a message header. No action is
required.
2215 10 DBS_DEBUG_MSG: final checks
Explanation: This is an informational message or a message header. No action is
required.
2216 10 DBS_DEBUG_MSG: after bufdbclean
Explanation: This is an informational message or a message header. No action is
required.
2217 10 DBS_DEBUG_MSG: dbshutdown completed for database %.*s with dbid %d
Explanation: This is an informational message or a message header. No action is
required.
2218 10 DBS_DEBUG_MSG: child process %d is executing failover dbshutdown
asynchronously
Explanation: This is an informational message or a message header. No action is
required.
2219 20 Warning: HA Subsystem Internal Error - database shutdown was not attempted because
the name change of the proxy databases failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2220 20 Unable to spawn Quiesce Database Agent. Aborting QUIESCE DATABASE command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
859
2221 16 QUIESCE DATABASE Error: Tag name %.*s is already in use. Use a different name.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2222 16 QUIESCE DATABASE with RELEASE option failed. No quiesce process with tag name
%.*s exists or it is being released by another process.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2223 20 Unable to put process %ld to sleep. Aborting QUIESCE DATABASE command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2224 16 QUIESCE DATABASE: Invalid option for QUIESCE DATABASE.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2225 16 Only %d databases allowed in a single QUIESCE DATABASE command.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2226 16 Only %d simultaneous executions of QUIESCE DATABASE commands allowed. Try
your command later.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2227 10 Process %ld successfully executed QUIESCE DATABASE with HOLD option for tag
%.*s. Processes trying to issue IO operation on the quiesced database(s) will be
suspended until user executes Quiesce Database command with RELEASE option.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2228 10 QUIESCE DATABASE command with tag %.*s is being executed by process %ld.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2229 10 Process %ld successfully executed QUIESCE DATABASE with RELEASE option for
tag %.*s.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2230 17 QUIESCE DATABASE: Failed to allocate memory.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
Server Error Messages 2200–2299
860
2231 16 Permission denied. Only a user with SA role can execute QUIESCE DATABASE
command.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
2232 16 QUIESCE DATABASE Error: Database %.*s does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
2233 16 QUIESCE DATABASE Error: Database %.*s is already quiesced or it is currently being
quiesced by another process.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
2234 18 QUIESCE DATABASE: Failed to open transaction or xls. Internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
2235 16 QUIESCE DATABASE Error: Database %.*s is already specified earlier in this
command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
2236 16 QUIESCE DATABASE Error: Process %ld is aborted, as transactions in prepare state did
not finish within the prescribed time limit.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
2237 10 QUIESCE DATABASE: Waiting for multi-database prepare transaction to complete.
Retry count: %d.
Explanation: This is an informational message or a message header. No action is
required.
2238 18 QUIESCE DATABASE: Could not acquire %.*s due to %.*s.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
2239 16 QUIESCE DATABASE Error: The user has aborted this transaction.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
2240 10 WARNING: master database is in quiesce state, sp_helpdb on database %.*s may not
reflect its status change. Please use dbcc dbtable command (status3 field) to inspect the
correct status.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
861
2241 16 QUIESCE DATABASE failed because database %.*s has not been dumped since it was
created or upgraded. You must perform a dump database before you can issue QUIESCE
DATABASE command.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2242 10 QUIESCE DATABASE is in progress on database %.*s. After it completes, DUMP
DATABASE will resume automatically.
Explanation: This is an informational message or a message header. No action is
required.
2243 16 QUIESCE DATABASE failed with error %ld. See the error log for more detail.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2244 16 QUIESCE DATABASE Error: Unable to open database %.*s.
Explanation: Check syntax and object name.
2245 16 QUIESCE DATABASE Error: Unable to issue a checkpoint on database %.*s because it
is in quiesce state.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2246 10 DBS_DEBUG_MSG: Process %d INCR dbt_keep to %d for %.*s with dbid %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2247 10 DBS_DEBUG_MSG: Process %d DECR dbt_keep to %d for %.*s with dbid %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2248 16 Prepared transactions were found in the system. Reissue the command after the prepared
transactions are completed or consult a System Administrator.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2249 16 Waiting for prepared transactions to complete...
Explanation: This is an informational message or a message header. No action is
required.
2250 17 Warning: dbshutdown failed on database %.*s with dbid %d because the tasks using this
database could not be terminated within the timeout period.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
Server Error Messages 2200–2299
862
2251 17 Warning: HA Subsystem Internal Error - dbshutdown failed on database %.*s with dbid
%d because the database was found to be in use after it was marked for shutdown.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2252 16 Cannot restart database %.*s with dbid %d because it has not been shut down successfully
or it is a HA proxy database.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2253 10 Deleting a stale row with session ID %d from syssessions.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2254 10 Unable to delete a stale row with session ID %d from syssessions.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2255 10 Unable to commit the deletion of stale rows from syssessions.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2256 16 Unable to shut down database ’%.*s’ with dbid %d because another database shutdown
or restart is executing. Try your command later.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2257 18 Internal Error - Validation of database keep counts failed during database shutdown of
database ’%.*s’ with dbid %d. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
2258 18 Internal Error - Process %d has kept some database eventhough it is terminating. Please
contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
2259 16 Warning: System process %d is using the database ’%.*s’, dbid %d while a database
shutdown is being attempted. If the database shutdown is unsuccessful, retry it later.
Explanation: This is an informational message or a message header. No action is
required.
2260 16 Warning: spid %d is performing a quiesce on database ’%.*s’, dbid %d while a database
shutdown is being attempted. If the database shutdown is unsuccessful, retry it later after
releasing the quiesce.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
863
2261 10 Dbshutdown in progress for database %.*s with dbid %d. Timeout left %d secs. Please
wait.
Explanation: This is an informational message or a message header. No action is
required.
2262 10 QUIESCE DATABASE HOLD was invoked with FOR EXTERNAL DUMP.
Non-logged writes status in database ’%.*s’ has been cleared. For subsequent
transaction dumps, LOAD TRANSACTION will require as a target the
externally-produced copy you have just created.
Explanation: This is an informational message . Note this information for future use.
2263 17 %s for tag name ’%s’ failed: an alarm function could not be installed.
Explanation: Command failed due to resource limitation. Retry when the resource is
available, or contact your System Administrator to address the resource problem.
2264 10 QUIESCE DATABASE HOLD for tag name %s has not finished yet. QUIESCE
DATABASE RELEASE will wait until it finishes.
Explanation: This is an informational message or a message header. No action is
required.
2265 10 Unable to write statistics for object %ld in database %ld. After booting against
the external copy created during quiesce state, and onlining the database for
write access, please run update statistics on this table.
Explanation: Perform the indicated action. To determine the table name, run isql
command select object_name(object-id).
2266 10 Unable to write statistics for all indexes of object %ld in database %ld. After
booting against the external copy created during quiesce state, and onlining the
database for write access, please run update statistics on all indexes.
Explanation: Perform the indicated action. To determine the table name, run isql
command select object_name(object-id).
2267 10 Unable to write statistics for index %ld of object %ld in database %ld. After
booting against the external copy created during quiesce state, and onlining the
database for write access, please run update statistics on this index.
Explanation: Perform the indicated action. To determine the table name, run isql
command select object_name(object-id).
2268 10
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 2300–2399
864
Server Error Messages 2300–2399
Number Severity Text and Explanation
2300 10 HA Config successfully loaded the HA Services Library for NT version ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2301 16 HA Config Error: The ha_add_companion() built-in function was called with null
parameter(s). Retry with non-null parameter value(s).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2302 16 HA Config Error: The cluster login ’%s’ in server ’%s’ is invalid or does not have
ha_role.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2303 10 HA Config Warning: The cluster login ’%s’ in server ’%s’ has sa_role - this is a potential
security problem.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2304 16 HA Config Error: The resource ’%s’ is already managing the ASE server ’%s’ as a
clustered server in the MSCS cluster.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2305 16 HA Config Error: Failed to create MSCS cluster group ’%s’ (operating system error %d
- does a group of this name exist already?).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2306 10 Creating MSCS cluster group ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2307 10 Creating MSCS cluster resource ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2308 16 HA Config Error: Failed to create MSCS cluster resource ’%s’ (operating system error
%d - does a resource of this name exist already?).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
CHAPTER 6 Adaptive Server Error Messages
865
2309 16 HA Config Error: Failed to obtain the state for cluster resource ’%s’ (operating system
error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2310 16 HA HAConfig Error: Failed to open cluster group ’%s’ containing the cluster resource
for the ASE server (operating system error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2311 16 HA Config Internal Error: Unable to initialize and allocate memory. Try restarting the
server.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2312 16 HA Config Error: Unable to write cluster resource properties for ASE server ’%s’
(operating system error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2313 16 HA Config Error: The ha_remove_companion() built-in function was called with null
parameter(s). Retry with non-null parameters(s).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2314 10 Successfully removed cluster resource ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2315 16 HA Config Error: The ha_failback() built-in function was called with null parameter(s).
Retry with non-null parameter(s).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2316 16 HA Config Error: An error was encountered when moving group ’%s’ (operating system
error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2317 10 Successfully moved group ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2318 16 HA Config Error: The ha_checkalive() built-in function was called with null
parameter(s). Retry with non-null parameter(s).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
Server Error Messages 2300–2399
866
2319 16 HA Config Error: Unable to open cluster resource ’%s’ managing the ASE server
(operating system error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2320 16 HA Config Error: Preexisting cluster resource ’%s’ is not of type ’%s’ (did this resource
exist before configuration began?).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2321 16 HA Config Error: Could not find the cluster node where the ASE server ’%s’ is installed
(operating system error %d - is the ASE server running under an NT domain
administration account?).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2322 16 HA Config Error: Unable to open the cluster node name ’%s’ in order to move the ASE
server’s group to it (operating system error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2323 16 HA Config Error: Failed to move cluster group ’%s’ to node ’%s’ (operating system error
%d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2324 16 HA Config Error: Unable to set the owning node of cluster group ’%s’ to ’%s’ (operating
system error %d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2325 10 Checking administration and cluster logins have correct ASE server roles.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2326 10 Checking if the ASE server ’%s’ is already managed by a cluster resource.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2327 10 Creating cluster resource and cluster group to manage ASE server.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2328 10 Moving new cluster group ’%s’ to primary cluster node ’%s’.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2329 20 HAPC Internal Error: Invalid input %d to internal functions.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
867
2330 17 HAPC Internal Error: Invalid rpc(%d) request.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2331 17 HACFG Internal Error: This dbcc command is not applicable for Table ’%.*s’ in database
’%.*s’.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2332 17 HACFG Internal Error: Internal SQL failed. Unable to execute dbcc command.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2333 17 HACFG Internal Error: The sub command ’%.*s’ for ha_admin() dbcc command is either
not implemented or invalid in database ’%.*s’.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2334 17 CP Error: The dbcc command conncheck failed. Received message ’%.*s’ while
expected msg ’%.*s’.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2335 10 Unable to obtain lock on the server state. Either lock was left behind by previous HA
configuration command or, currently it is locked by another HA configuration operation.
See System Administration Manual for details.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2336 10 HACFG Internal Error: State machine error. Current states of local(%d) and remote(%d)
server are incompatible for operation %d.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2337 10 HACFG Internal Error: State machine error. Invalid operation (%d) on the current server
state (%d).
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2338 10 HACFG Internal Error: State machine error. Next states of local(%d) and remote(%d)
server are incompatible for operation %d.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
Server Error Messages 2300–2399
868
2339 10 HACFG Internal Error: State machine error. Unable to set the state.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2340 10 HACFG Internal Error: State machine error. Unable to get the state.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2341 10 Pathname check failed. Pathname ’%.*s’ exists in companion servers.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2342 10 HACFG Internal error: Pathname check failed. Invalid device type(%d) specified.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2343 16 HA system is not enabled. Cannot accept any ha services commands. Please refer to
System Administration guide to enable HA services.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
2344 10 HACFG: Handshake failed. Could not receive the Node Id from the Handshake Initiator.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2345 10 HACFG Internal error: Could not find Sysattributes row in database (%d) for HA state
information.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2346 10 HACFG Internal Error: State machine error. Current state (%d) and next state (%d) are
incompatible for operation %d.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2347 10 HACFG Internal Error: State machine error. Invalid state (%d).
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2348 10 ACFG Internal Error: State machine error. Current state(%d) and next state(%d) are same.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2349 10 HACFG Internal Warning: The store procedure ’%.*s’ can’t be found in the HA
Restriction Class table.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
869
2350 10 HACFG Internal Warning: The store procedure ’%.*s’ is not allowed at the restriction
class (%d).
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2351 10 HACFG Internal Warning: The restriction class (%d) is invalid.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2352 10 Writing new cluster resource’s properties
Explanation: This is an informational message or a message header. No action is
required.
2353 10 Checking ASE server has the correct set of physical disks in its cluster group.
Explanation: This is an informational message or a message header. No action is
required.
2354 10 Found existing resource ’%s’ for ASE server in group ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2355 16 HA Config Error: Unable to bring cluster resource ’%s’ online (operating system error
%d).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2356 10 Bringing cluster resource online.
Explanation: This is an informational message or a message header. No action is
required.
2357 10 Locating the cluster node for the primary ASE server.
Explanation: This is an informational message or a message header. No action is
required.
2358 10 HA Error: You must be in the master database to execute stored procedure ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2359 10 High Availability Basis Services loaded: version ’%s’.
Explanation: This is an informational message or a message header. No action is
required.
2360 16 HA Config Error: Could not find servername ’%s’ in interfaces file.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2361 16 HA Config Error: Server ’%s’ currently not running on a cluster.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
Server Error Messages 2300–2399
870
2362 16 HA Config Error: Server ’%s’ and server ’%s’ are not running on the same cluster;
companionship setup failed.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2363 16 HA Config Error: Failed to open temporary file ’%s’.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2364 10 HA Config Warning: Failed to remove temporary file ’%s’. Please remove it manually to
prevent possible permission problem later.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2365 16 HA Config Error: System command ’%s’ failed.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2366 16 HA Config Error: Resource group ’%s’ does not seem to be running on any node at all.
Please check its status manually before rerunning this command.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2367 16 HA Config Error: Resource ’%s’ is running but not on node ’%s’.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2368 16 HA Config Error: Could not find useful information from the output of system command
’%s’.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
2369 10 HA Config Warning: Could not set the PendingTimeout and RestartThreshold properties
for cluster resource ’%s’. These properties may need set manually by the cluster
administrator.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2370 10 Setting new cluster resource’s PendingTimeout to %d and RestartThreshold to %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2371 16 HA Config Error: Unable to obtain path to the ’%s’ device. Please check the path and
ensure that it is less than ’%d’ characters.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
871
Server Error Messages 2400–2499
2372 16 HA Config error: Server mismatch. Local server version is ’%d’, remote server
version is ’%d’. The server versions must be the same.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
2373 16 HA configuration error: The logical page size of this Adaptive Server is ’%d’.
The logical page size of the remote Adaptive Server is ’%d’. To configure for
HA, the two servers must have the same logical page size.
Explanation: HA configuration failed. Primary and companion servers must have the
same logical page size.
Number Severity Text and Explanation
Number Severity Text and Explanation
2401 11 Character set conversion is not available between client character set `%.*s' and server
character set `%.*s'.
Explanation: Refer to the writeup for this error.
2402 16 Error converting client characters into server's character set. Some character(s) could not
be converted.
Explanation: Refer to the writeup for this error.
2403 10 WARNING! Some character(s) could not be converted into client's character set.
Unconverted bytes were changed to question marks (`?').
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2404 18 Buffer overflow converting characters from client into server's character set.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2405 18 Internal error occurred while converting characters.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2406 16 Cannot use SET CHAR_CONVERT ON, since this session has never had codeset
conversions turned on.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Server Error Messages 2400–2499
872
2407 17 Cannot use the requested character set since the character set cache is full.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2408 11 Cannot find the requested character set in Syscharsets: id = %d.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
2409 11 Cannot find the requested character set in Syscharsets: name = `%.*s'.
Explanation: Refer to the writeup for this error.
2410 18 Unexpected error returned from the Character Set Manager: return value = %d.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2411 10 No conversions will be done.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2412 10 Existing character conversions (if any) will remain in effect.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2414 10 Since only 7-bit ASCII characters are allowed with the special character set `ascii_7', the
language for this session is being forced to `us_english'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2415 10 Due to previous errors, the language for this session is being forced to `us_english'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2416 10 Due to codeset conversion errors in the remote servername/password list of the
LOGINREC, remote procedure calls to other servers may not work.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2417 11 Unable to use Unicode-based character set conversion - client character set '%.*s' and
server character set '%.*s' are incompatible.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
2418 11 Unable to load Unicode-based character set conversion table '%.*s' - table not found.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
2419 11 Unable to load Unicode-based character set conversion table '%.*s' - the conversion table
is corrupted. Please notify your system administrator.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
873
2420 17 Unable to load Unicode-based character set conversion table '%.*s' - Unicode conversion
cache is full. Please notify your system administrator to add mode unicode buffers.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2421 11 Unable to use Unicode-based character set conversion - The requested character set is not
supported: id = %d.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
2422 11 Unable to use Unicode-based character set conversion - The requested character set is not
supported: name = '%.*s'.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
2423 18 Unexpected error returned from Unilib functions: return value = %d.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
2424 16 TEXT data not supported when data size is changing between the ’%.*s’ and ’%.*s’
character sets due to character set conversion. The conversion ratio is %d:%d. Please
connect again with conversions off, or use client-side conversions.
Explanation: This message is raised when data is shrinking or growing and an attempt is
made to access TEXT data. The first two arguments are filled in with the server and client
character set names, respectively. The second two arguments are the expansion factors
from server to client.
2425 18 Unable to use Unicode-based character set conversion - Can not get conversion handle for
server’s default character set. Please check server’s error log file.
Explanation: This message is raised when client tries to setup a Unicode conversion and
server’s conversion handle is not installed during startup. Report the error to your System
Administrator.
2426 10 LONGCHAR datatype not allowed on output because client does not support it.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
2427 10 LONGCHAR datatype not allowed on output because unicode conversions have not been
enabled. Please see the System Administrator for asistance.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
2428 10 Unrecongnized server or client unilib character set ID. Expansion factor is set to 1.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
2429 10 No matched unilib character set ID for the server or client character set ID. Expansion
factor is set to 1.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
Number Severity Text and Explanation
Server Error Messages 2500–2599
874
Server Error Messages 2500–2599
2431 10 WARNING! Some character(s) in the source string are considered illegal bytes in server’s
character set. All bytes after the first illegal bytes are truncated.
Explanation: This will be returned when conversion hits illegal bytes in the source string.
This is an informational message. Unless otherwise specified, no action is required.
2432 16 Illegal byte sequence encountered in Unicode data during %S_MSG conversion
of %s value ’%s’ to a %s field.
Explanation: This will be returned when conversion hits illegal bytes in the source string.
Check source data and receiving datatype.
2433 16 Illegal byte sequence encountered in Unicode data.
Explanation: Check data and the source and receiving datatype.
Number Severity Text and Explanation
Number Severity Text and Explanation
2501 16 Table named %.*s not found; check sysobjects
Explanation: Refer to the writeup for this error.
2502 16 Table Corrupt: A page is linked in more than one chain; check this page:page number=%ld
allocation status=%d
Explanation: Refer to the writeup for this error.
2503 16 Table Corrupt: Page linkage is not consistent; check the following pages: (current
page#=%ld; page# pointing to this page=%ld; previous page# indicated in this page=%ld)
Explanation: Refer to the writeup for this error.
2504 16 Table Corrupt: The index id in alloc page does not match the index id in sysindexes (alloc
page#=%ld; extent id=%ld; index id in alloc=%d; index id in sysindexes=%d)
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2505 16 Table Corrupt: Free offset in page header is not reasonable; free offset should be >= %d
and <= %d; check this page and offset (page#=%ld freeoffset on the page header=%ld)
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2506 16 Table Corrupt: The values in adjust table should be in ascending order starting from the
end of the table (page#=%ld row#=%d); check adjust table in this row
Explanation: Refer to the writeup for this error.
CHAPTER 6 Adaptive Server Error Messages
875
2507 16 Table Corrupt: Offset table is incorrect (page#=%ld row#=%d offset in offset table is=%d
correct offset is=%d)
Explanation: Refer to the writeup for this error.
2508 16 Table Corrupt: Row length is incorrect (page#=%d row#=%d minimum row length=%d
row length=%d)
Explanation: A dbcc check detected table corruption. Refer to Encyclopedia of Tasks in
this document, and Checking Database Consistency in the System Administration Guide,
for help in identifying the affected object and determining appropriate corrective action.
2509 16 Table Corrupt: The row number and offset of each row in the page should have a matching
entry in row number table; check this page (page#=%d row#=%d offset in row number
table=%d)
Explanation: Refer to the writeup for this error.
2510 16 Key mismatch between index page %ld, at offset %d and data page %ld (row ID %d) in
database ’%.*s’. Drop and re-create index id %d of table ’%.*s’.
Explanation: Refer to the writeup for this error.
2511 16 Keys of index id %d for table ’%.*s’ in %S_MSG not in correct order. Drop and re-create
the index. (index page %d)
Explanation: Refer to the writeup for this error.
2512 16 Table Corrupt: The specified row number %d in index page %ld cannot be found on data
page %ld
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2513 16 Table Corrupt: Object id %ld (object name = %S_OBJID) does not match between %.*s
and %.*s
Explanation: Refer to the writeup for this error.
2514 16 Table Corrupt: Type id %ld (type name = %.*s) does not match between %.*s and %.*s
Explanation: Refer to the writeup for this error.
2516 16 Table Corrupt: Segment number %d does not match between %.*s and %.*s
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2517 16 Table Corrupt: Procedure id %ld (procedure name = %S_OBJID) does not match between
%.*s and %.*s
Explanation: Refer to the writeup for this error.
2518 16 Database Corrupt: Incorrect last checkpoint in syslogs
Explanation: This message is generated when dbcc checkcatalog detects corruption in
the syslogs table of a database. Collect dbcc output and report the error to Sybase Technical
Support.
Number Severity Text and Explanation
Server Error Messages 2500–2599
876
2519 16 Database Corrupt: The last checkpoint in sysdatabases is incorrect. Syslogs recorded a
different checkpoint
Explanation: Refer to the writeup for this error.
2520 16 Database named %.*s not found; check sysdatabases
Explanation: Refer to the writeup for this error.
2521 16 Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to correct the
problem. (alloc page#=%ld, extent id=%ld, logical page#=%ld, object id in extent=%ld,
index id in extent=%ld, object name=%S_OBJID)
Explanation: Refer to the writeup for this error.
2522 16 Table Corrupt: The object id %ld (object name = %.*s) in page# %ld is different from the
object id %ld (object name = %.*s) in sysindexes
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2523 16 Table Corrupt: Page number %ld is out of range for this database %S_DBID. The
maximum page number in this database is %ld
Explanation: There may be possible corruption in a database or a database object.
Collect dbcc output and report the error to Sybase Technical Support.
2524 16 Table Corrupt: Row length is inconsistent between the computed row length and the
recorded row length on page; check the following page and row: pageno=%ld row#=%d
computed row length=%d row length on page=%ld
Explanation: Refer to the writeup for this error.
2525 16 Table Corrupt: Object id wrong; tables: alloc page %ld extent id=%ld l page#=%ld objid
in ext=%ld (name = %S_OBJID) objid in page=%ld (name = %S_OBJID) objid in
sysindexes=%ld (name = %S_OBJID)
Explanation: Refer to the writeup for this error.
2526 16 Incorrect DBCC command: Please see the SQL Server Reference Manual for DBCC
commands and options.
Explanation: An attempt was made to execute an invalid dbcc command, or an
incorrect number of parameters has been passed to a dbcc command.
2527 10 DBCC detected internal database inconsistancy; contact a user with System Administrator
(SA) role.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2528 10 DBCC execution completed. If DBCC printed error messages, contact a user with System
Administrator (SA) role.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2529 16 Table Corrupt: Attempted to get page %ld, object %ld; got page %ld, object %ld.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
877
2531 16 Table Corrupt: Index id on extent should be 0; check the following page and ids: alloc
page=%ld extent=%ld index id on extent=%d
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2532 16 Table Corrupt: No syslogs entry in sysindexes.
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2533 16 Table Corrupt: Incorrect index key length %d in internal (sarg) structure.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2534 16 Table Corrupt: No keys found on index page %ld. Offset for the free space: (freeoff=%ld)
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2535 16 Table Corrupt: Page# %ld belongs to object id %ld (object name = %.*s) not object id %ld
(object name = %.*s)
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2536 10 Checking %.*s: Logical pagesize is %ld bytes
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2537 10 Checking %ld.
Explanation: This is an informational message. No action is required.
2538 10 Alloc page %ld (# of extent=%ld used pages=%ld ref pages=%ld)
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2539 10 Total (# of extent=%ld used pages=%ld ref pages=%ld) in this database
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2540 16 Table Corrupt: Page is allocated but not linked; check the following pages and ids:
allocation pg#=%ld extent id=%ld logical pg#=%ld object id on extent=%ld (object name
= %S_OBJID) indid on extent=%ld
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
Server Error Messages 2500–2599
878
2541 16 Table Corrupt: object id does not match between extent in allocation page and sysindexes;
check the following extent: alloc pg#=%ld extent#=%ld object id on extent=%ld (object
name = %.*s) object id in sysindexes=%ld (object name = %.*s)
Explanation: Refer to the writeup for this error.
2542 16 Table Corrupt: Extent is linked in more than one chain. Check the following allocation
page and extent: alloc pg#=%ld extent#=%ld status=%d
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2543 16 Table Corrupt: Extent structures are linked incorrectly; check the following extent: alloc
pg#=%ld extent#=%ld previous extent# on this extent=%ld previous extent should be=%ld
Explanation: Refer to the writeup for this error.
2544 16 Table Corrupt: Extent id %ld on allocation pg# %ld had object id %ld (object name =
%.*s) on but used bit off
Explanation: Refer to the writeup for this error.
2545 16 Table Corrupt: Extent#=%ld on allocation pg#=%ld was used but object id was 0,
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2546 16 Table Corrupt: Extent id %ld on allocation pg# %ld has objid %ld and used bit on, but
reference bit off.
Explanation: Refer to the writeup for this error.
2547 16 Table Corrupt: Segment number %d specified for use in the segment map in sysusages has
no entry in syssegments. The entry in sysusages is for dbid %d (db name = %S_DBID),
with a virtual starting address of %ld.
Explanation: Run dbcc checkcatalog, collect dbcc output and report the error to Sybase
Technical Support.
2548 16 There is no default segment specified in syssegments.
Explanation: Information in syssgements may be corrupt. Run dbcc checkcatalog,
collect dbcc output and report the error to Sybase Technical Support.
2549 16 There is more than one default segment specified in syssegments.
Explanation: Information in syssgements may be corrupt. Run dbcc checkcatalog,
collect dbcc output and report the error to Sybase Technical Support.
2550 16 Missing segment in sysusages segmap.
Explanation: Refer to the writeup for this error.
2551 10 The following segments have been defined for database %d (database name %S_DBID).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
879
2556 20 Page #%ld of sysindexes in database %d not found in cache after read.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2557 14 Only the owner of object `%.*s' or a user with System Administrator (SA) role can run
DBCC %s on it.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
2558 16 Extent not within segment: Object %ld, indid %d includes extents on allocation page %ld
which is not in segment %d.
Explanation: Refer to the writeup for this error.
2559 16 Data page number %ld is empty but is not the first page. Status = 0x%x.
Explanation: Refer to the writeup for this error.
2560 16 Incorrect parameter passed to DBCC command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2561 16 Unable to open log for database %d.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2562 16 %s cannot access object `%.*s' because it is not a table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2563 14 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can
run the DBCC CHECKCATALOG command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
2564 14 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can
run the DBCC CHECKDB command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
2565 14 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can
run the DBCC CHECKALLOC/CHECKGAM command.
Explanation: You do not have the permission to execute this command. Have the
database owner or a user with SA role run this command.
2567 14 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can
run the DBCC DBREPAIR command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 2500–2599
880
2568 16 Page %ld is out of range for this database
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2570 10 Warning - Page %ld has DEALLOC bit on - indid %d, status 0x%x
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2571 14 Permission denied. Only a user with System Administrator (SA) role can use the DBCC
command `%.*s'.
Explanation: Refer to the writeup for this error.
2572 10 Database `%S_DBID' is not in single user mode - may find spurious allocation problems
due to transactions in progress.
Explanation: Refer to the writeup for this error.
2573 16 Database `%.*s' is not marked suspect. You cannot drop it with DBCC.
Explanation: Refer to the writeup for this error.
2574 16 Index page number %ld is empty. Status = 0x%x.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2575 16 The last page %ld in sysindexes for table `%.*s' has next page # %ld in its page header.
The next page # should be NULL. Please check sysindexes.
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2576 16 The %S_MSG page %ld specified in sysindexes for table `%.*s' can not be found. Please
check sysindexes.
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2577 16 The root page %ld in sysindexes for table `%.*s' has next page # %ld and previous page #
%ld in its page header. Both the next page # and the previous page # should be NULL.
Please check sysindexes.
Explanation: There may be possible corruption in a database or a database object.
Takeany corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2578 16 The first page %d in sysindexes for table ’%.*s’ has previous page # %d in its page header.
The previous page # should be NULL. Please check sysindexes.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
881
2579 10 The total number of data pages in this table is %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2580 16 The clustered index page (%S_PAGE) has an unexpected key pointer to an overflow data
page (%S_PAGE). Please check page status.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2581 16 Data page (%S_PAGE) indicates that an overflow page is linked to it; however, the next
page (%S_PAGE) has not been marked as an overflow page. Please check page status.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2582 16 Data page (%S_PAGE) has been marked as an overflow page; however, the previous page
(%S_PAGE) does not indicate that there is an overflow page linked to it.
Explanation: See the writeup for Error 2582.
2583 10 Number of data pages counted by DBCC differs from count in the data OAM.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2584 16 The last key in the previous page (%S_PAGE) is equal to the first key in the current page
(%S_PAGE); however, the status of current page does not indicate that it is an overflow
page.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2585 16 The last key in the previouse page (%S_PAGE) is equal to the first key in the current page
(%S_PAGE); however, the status of previous page indicates that there is a disconnected
overflow page.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2586 16 The last key in the previous page (%S_PAGE) is equal to the first key in the current page
(%S_PAGE); however, the status of previous page indicates that there is no overflow page.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
Number Severity Text and Explanation
Server Error Messages 2500–2599
882
2587 16 The last key in the previouse page (%S_PAGE) is not equal to the first key in the current
page (%S_PAGE); the current page is an overflow page; however, the status of previous
page indicates that there is no disconnected overflow page.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
2589 16 Object `%.*s' must have its status updated in sysobjects, to reflect the intent of repairing
the index on it.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2590 16 DBCC option available for system tables only.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2591 16 Could not find index row which has id %d for table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2592 10 %s index successfully restored for object `%.*s' in `%.*s' database.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2593 10 There are %d rows in %ld pages for object `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2594 16 Invalid index id specified (index id = %d).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2595 16 Database `%.*s' must be set to single user mode before executing this command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2596 16 %S_PAGE has an incorrect pgfreeoff value of %d. The offset should be %d.
Explanation: Refer to the writeup for this error.
2597 16 The database is not open. Please issue a `use %.*s' and re-run the DBCC command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2598 16 Indexes on sysobjects and sysindexes cannot be recreated.
Explanation: You cannot recreate the indexes on these system tables.
2599 16 Invalid monitor group specified: `%.*s'. Please re-enter.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
883
Server Error Messages 2600–2699
Number Severity Text and Explanation
2601 14 Attempt to insert duplicate key row in object `%.*s' with unique index `%.*s'%S_EED
Explanation: Refer to the writeup for this error.
2603 21 Insufficient space (%d bytes) on logical page %ld of index %d for object ’%.*s’ when
inserting row of length %d bytes on index page.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
2610 22 Could not find leaf row in nonclustered index `%.*s' page %ld that corresponds to data
row from logical data page %ld, row offset %d during update index attempt after data
page split in dbid %d.
Explanation: Refer to the writeup for this error.
2613 20 Attempt to remove resource lock on buffer holding logical page %ld failed - the buffer
was not resource locked.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2615 14 Attempt to insert duplicate row in table `%.*s' with index `%.*s' in database `%.*s'.
Could drop and recreate index with ignore duprow or allow duprow.
Explanation: Refer to the writeup for this error.
2616 20 Buffer holding logical page %ld cannot move to slot 1 since buffer holding logical page
%ld is already there.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2617 20 Buffer holding logical page %ld not found in keep pool in SDES for object `%.*s'
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2618 20 Couldn't find dupkey group starting at offset %d on page %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Server Error Messages 2600–2699
884
2619 20 Keys did not match overflow page when inserting row at end of page (%S_PAGE) that
has overflow page (%S_PAGE) that is not disconnected in dbid = %d.
Explanation: Adaptive Server encountered an internal error when inserting a data row
into a clustered index overflow page. Report the error to your System Administrator so
dbcc diagnostics can be run.
2620 21 The offset of the row number at offset %d does not match the entry in the offset table of
the following page: %S_PAGE.
Explanation: Refer to the writeup for this error.
2621 20 Process %d already has the buffer we are using for an allocation resource locked:
%S_PAGE.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2622 21 Insufficient room on this page to insert a row of length %d. %S_PAGE.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
2623 21 The PG_DEALLOC bit is on in this page at runtime - should have been turned off by
deallocating page in recovery. %S_PAGE.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
2624 21 Insert into table %S_DES fails because rowlength %d is less than minlen %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
2625 20 Deadlock encountered in log allocation for database `%.*s'. This state should not be
reached.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2626 21 Illegal attempt to insert duplicate key row in the clustered index for object `%.*s' in
database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
2627 22 Leaf page %ld in table %ld, index %d, dbid %d is empty - please rebuild the index.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
(Discontinued in 11.9.2)
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
885
Server Error Messages 2700–2799
2628 21 In database `%.*s', page %ld is linked forward to page %ld, but that page is linked
backward to page %ld. Please report this internal error to Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Number Severity Text and Explanation
2701 10 Database name `%.*s' ignored, creating table in Tempdb.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2702 16 Database `%.*s' does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2703 16 Segment `%.*s' does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2705 16 Column names in each table must be unique. Column name `%.*s' in table `%.*s' is
specified more than once.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2706 11 Table `%.*s' does not exist.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
2710 16 You are not the owner specified for the object named `%.*s' in this command (CREATE,
ALTER, TRUNCATE, UPDATE STATISTICS, or BULK INSERT). The database owner
can use the SETUSER command to assume the identity of another user.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
2714 16 There is already an object named `%.*s' in the database.
Explanation: Refer to the writeup for this error.
Server Error Messages 2700–2799
886
2715 16 Can't find type '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2716 16 Can't specify a length or scale on type '%.*s'.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2717 16 Specified length is too large for type '%.*s'.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2718 16 Column or parameter #%d: -- can't specify Null values on a column of type BIT.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2719 14 You must be the owner of table '%.*s' or a System Administrator to update the table's
statistics.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
2721 11 Could not find a default segment to create the table on. Contact a user with System
administrator (SA) role to specify a default segment in syssegments.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
2724 10 Parameter `%.*s' has an invalid data type.
Explanation: An invalid datatype was specified for a table column or stored procedure
parameter when creating the object. Check SQL syntax.
2727 11 Cannot find index `%.*s'.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
2728 21 Could not find sysobjects row for table `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
2729 16 Procedure `%.*s' group number 1 already exists in the database. Choose another
procedure name or procedure number.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
887
2730 11 Cannot create procedure `%.*s' with a group number of %d because a procedure with the
same name and a group number of 1 does not currently exist in the database. Must
CREATE PROCEDURE `%.*s';1 first.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
2731 16 Column or parameter #%d: -- can't specify column width of zero for `%.*s'.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
2732 16 User error number %ld is invalid. Number must be between %d and %d.
Explanation: SQL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2734 16 User name %.*s does not exist in sysusers.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2735 16 Object text is too long. Please shorten the object text or split into multiple objects. Text
which caused overflow starts at: ’%.*s’.
Explanation: Adaptive Server could not perform the requested action. Determine the
maximum text size using the information in the message, and use one of the recommended
options to correct the problem.
2736 16 Owner name that was specified is a group name. Objects cannot be owned by groups.
Explanation: QL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2737 16 Message passed to %s must be of type CHAR or VARCHAR.
Explanation: QL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2738 16 A table can only have one timestamp column. Since table `%.*s' already has one, you can't
add the column `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2739 16 TEXT and IMAGE datatypes are invalid for parameters or local variables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2740 16 SET LANGUAGE failed because `%.*s' is not an official language name or a language
alias on this SQL Server.
Explanation: Command failed. Use sp_helplanguage and see the Adaptive Server
Reference Manual for help with language maintenance.
2741 16 SET DATEFORMAT date order `%.*s' is invalid.
Explanation: Command failed. See the Adaptive Server Reference Manual for help with
dateformat.
Number Severity Text and Explanation
Server Error Messages 2700–2799
888
2742 16 SET DATEFIRST %d is out of range.
Explanation: Command failed. See the Adaptive Server Reference Manual for help with
datefirst.
2743 16 %s command requires %S_MSG parameter.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2744 16 Index distribution page was %ld, now %ld. Perhaps another UPDATE STATISTICS
command is currently running. Retry your command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2745 16 %s command is missing an argument position specifier.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2746 16 Duplicate position specifier in format string of %s command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2747 16 Incorrect position specifier in format string of %s command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2748 16 Message number %ld, passed to RAISERROR, does not exist in the %s catalog.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2749 16 Number of argument position specifiers in %s command is greater than the number of
arguments passed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2750 16 Can not have more than %d arguments in a call to %s.
Explanation: QL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2751 16 %s command failed because the resulting string exceeded the maximum length of %d
bytes.
Explanation: QL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2752 20 The PRINT/RAISERROR function received an illegal datatype of `%s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2753 20 Received an error code of `%d' from `intl_strblist()'.
Explanation: Refer to the writeup for Error 2753.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
889
2754 16 There is an argument position specifier that is out of range in a call to %s. Valid argument
position specifiers must be in the range from 1 to %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2756 16 Specified type precision %d more than the maximum precision %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions.
2757 16 Specified scale %d more than the specified precision %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2758 16 Resdom says that column or parameter has no arguments but the length is non-zero. Given
length %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2759 10 Internal error: illegal tree encountered.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
2760 10 Column name `%.*s' does not exist in target table.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
2761 10 Failed to create declarative constraints on table `%.*s' in database `%.*s'.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
2762 16 The `%s' command is not allowed within a multi-statement transaction in the `%.*s'
database.
Explanation: QL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2763 16 An attempt to grant CREATE TABLE permission to PUBLIC in tempdb failed.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
2764 16 Identity field `%.*s' must be a numeric with a scale of 0 and not null allowed.
Explanation: QL Server could not perform the requested action. Rewrite the command
to conform to the requirement specified in the error message.
2765 16 A table can only have one identity column. Since table `%.*s' already has one, you can't
add the column `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 2700–2799
890
2766 16 Cannot use logsegment to create a user table or an index.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2767 16 The table with id=<%ld> in dbid=<%d> does not exist. It may have been created in a
concurrently running transaction that rolled back and is now inaccessible.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2768 16 SET label (CURREAD, CURWRITE) failed because new value is an invalid label, or new
value doesn't satisfy the dominance relationships among session labels.
Explanation: An invalid label was encountered in `set curread' or `set curwrite'
command.
2769 16 Invalid maxhold label specified for the table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2770 16 Invalid minhold label specified for the table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2771 16 Invalid hold label specified. A table's maxhold label should always dominate it's minhold
label.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2772 16 Invalid hold label specified. Only labels below your @@maxwrite are acceptable.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2773 16 Invalid hold label specified. Only labels above your @@minwrite are acceptable.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2774 16 Hold label provided is above database maxhold. Please provide a label below the database
maxhold.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2775 20 Object is not a table, or table has NULL maxhold and/or minhold value.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2776 16 The `set update_mode' command only takes in a CHAR or VARCHAR argument.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
891
2777 16 Invalid update_mode provided. The only allowable update modes are: reclassify,
over_range, and standard.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2778 12 The object `%.*s' is not a table. Update statistics can be used only on user tables or system
tables
Explanation: UPDATE STATISTICS can only be run on a table. The operation is illegal
for other objects.
2779 20 Lock request count has overrun the lock request array boundary. This is an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2780 20 maxlen (%d) is less than length (%d)
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2781 18 Internal Error. Master to DB SLID conversion failed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2782 16 An untyped variable in the PREPARE statement `%.*s' is being resolved to a TEXT or
IMAGE type. This is illegal in a dynamic PREPARE statement.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2783 14 The user's curwrite needs to be at the table's hurdle when updating a table's statistics.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
2784 18 Internal row labeling error occured.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2786 16 MAX_ROWS_PER_PAGE value of %d is invalid. It must be between 0 and %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2787 16 Cache, %s, cannot be found in sysconfigures.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2790 16 Setting maximum online engines to %d causes number of engine freelocks (%d) to fall
below half the value of freelock transfer block size (%d). Please increase maximum engine
freelocks to %d and reattempt this command.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Number Severity Text and Explanation
Server Error Messages 2800–2899
892
Server Error Messages 2800–2899
2792 16 Cannot change curread label with open cursors. Please contact a user with System Security
Officer (SSO) role for help.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2793 16 User error number %ld is of invalid type. Number must be an integer.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
2794 16 SET PROCESS_LIMIT_ACTION { ABORT | QUIET | WARNING } failed because '%.
*s' is not a valid parameter.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. .
2795 10 The value of 'parallel_degree' (`%d') cannot be larger than the value of configuration
parameter 'max parallel degree' (`%d'). The value '%d' is used for 'parallel_degree'.
Explanation: This is an informational message. No action is required. .
2796 16 The values of 'parallel_degree' and 'scan_parallel_degree' cannot be less than zero.
Explanation: Command failed due to invalid or illegal request. .
2797 10 The value of 'parallel_degree' (`%d') cannot be larger than the value of 'parallel_degree' set
by a calling procedure. The value '%d' is used.
Explanation: This is an informational message. No action required. .
2798 10 The value of 'scan_parallel_degree' (`%d') cannot be larger than the lesser of the
configuration parameter 'max scan parallel degree' (`%d') and current 'parallel_degree'
(`%d'). The value `%d' is used for 'scan_parallel_degree'.
Explanation: This is an informational message. No action required. .
Number Severity Text and Explanation
Number Severity Text and Explanation
2801 20 Bad procedure status: 0x%x.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Release 11.0 and
higher.
2802 20 Both the tree and plan pointer are set; Ambiguous procedure.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Release 11.0 and
higher.
CHAPTER 6 Adaptive Server Error Messages
893
2803 20 Bad pointer encountered during remapping: 0x%x.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2804 20 Stored procedure `%.*s' is out of sync with its own procedure header.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2805 20 Bad pointer 0x%lx encountered while remapping stored procedure `%.*s'. Must re-create
procedure.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2806 20 Stored procedure `%.*s' is corrupted. Must re-create procedure.
Explanation: See the writeup for Error 2806.
2807 18 Process %d could not unlock stored procedure `%.*s' because the procedure is not
currently locked by that process.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2808 18 Incorrect object structure returned from getobject.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2809 18 The request for %S_MSG `%.*s' failed because `%.*s' is a %S_MSG object.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2810 18 Cache reports negative usage count for procedure `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
2811 18 Cannot create procedure dbid %d, objid %ld, with a group number of %d.
Explanation: Refer to the writeup for this error.
2812 16 Stored procedure `%.*s' not found. Specify owner.objectname or use sp_help to check
whether the object exists (sp_help may produce lots of output).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
2813 20 Procedure %.*s in procedure buffer 0x%lx not properly linked with procedure header
0x%lx.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Release 11.0 and
higher.
Number Severity Text and Explanation
Server Error Messages 2800–2899
894
2814 20 Procedure %.*s in procedure buffer 0x%lx does not contain the same object id as
procedure header 0x%lx.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2815 20 Procedure %.*s in procedure buffer 0x%lx contains page address 0x%lx which is not
aligned on a 2K boundary.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2816 20 Procedure %.*s in procedure buffer 0x%lx contains page address 0x%lx which is not
within any memory map.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Release 11.0 and
higher.
2817 20 Procedure %.*s in procedure buffer 0x%lx contains page address 0x%lx which should be
allocated.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2818 20 You must provide both name and object id in order to install a procedure.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2819 20 You must provide both name and object id in order to remove a procedure.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2820 20 You must provide procedure buffer to remove the procedure %.*x.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2821 16 You must drop and recreate procedure %.*s.
Explanation: Command failed. Take indicated corrective action. You may need to
drop/recreate triggers, rules and defaults for the table.
2822 20 Bad version number encountered for procedure %.*s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
895
2823 20 Process %d tried to remove a PROC_BUF 0x%lx named `%.*s' that it does not hold in the
hold procedure linked list.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
2824 19 Process %d cannot hold PROC_BUF 0x%lx named `%.*s' because it holds another
PROC_BUF 0x%lx named `%.*s'. A process can only hold one view, rule, or default at a
time.
Explanation: Command failed when a non-configurable limit was exceeded. Adaptive
Server could not recover gracefully. Reconnect to Adaptive Server, and report the error to
your System Administrator.
2825 20 Process %d tried to remove a PROC_BUF 0x%lx named `%.*s' that it does not hold.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2826 20 Process %d has held the PROC_BUF 0x%lx named `%.*s' in the hold procedure linked
list already; Check your procedure cache.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
2827 20 Procedure `%.*s' in procedure buffer 0x%lx is not properly hashed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Release 11.0 and
higher.
2832 17 There are no more available procedure buffers. Configure your system for more.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
2833 26 While cleaning up descriptor for object %d, a procedure buffer was found in use (use count
= %d)
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
2834 26 Expected to find procedure buffer with usage count of %d and not %d.
Explanation: Incorrect count detected for a procedure buffer. Shut down and restart
Adaptive Server to clear the error.
2835 16 The procedure tree is old. Use the sp_remap procedure to remap all the procedures in this
database.
Explanation: Refer to the writeup for this error.
2836 26 The cursor `%.*s' is already tracking another procedure. This is an internal error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
Server Error Messages 2900–2999
896
Server Error Messages 2900–2999
2837 16 The object `%.*s' must be recompiled. Use `sp_recompile %.*s', then rerun your
command.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
2838 16 Invalid procedure name
Explanation: Attempted to execute a stored procedure without specifying a procedure
name. (Not raised in Release 11.0 and higher.)
2841 16 The text for the object '%.*s' is missing in syscomments. This object can not be accessed.
Explanation: Check syntax and object name. .
2843 16 The dynamic statement ’%.*s’ could not be found. This may be due to insufficient
metadata descriptors for the number of tables and procedures in use by Adaptive Server.
Configure the serverwide ’%s’ parameter to accommodate more objects.
Explanation: Query failed due to resource limitation. Take the recommended action.
Number Severity Text and Explanation
Number Severity Text and Explanation
2901 19 Exception stack limit (%d) exceeded.
Explanation: Command failed when a non-configurable limit was exceeded. Adaptive
Server could not recover gracefully. Reconnect to Adaptive Server, and report the error
to your System Administrator.
2902 10 Simulating error %d, state %d, at line %d in file %.*s.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
2903 20 While processing an exception, another exception occurred, which could result in some
internal resources not being released.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. .
CHAPTER 6 Adaptive Server Error Messages
897
Server Error Messages 3000 - 3099
Number Severity Text and Explanation
3001 21 DUMP DATABASE for database `%.*s' failed: insufficient memory to allocate backout
structure.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3003 20 DUMP DATABASE failed to establish a connection to the Backup Server. Attempt to
dump database `%.*s' has failed.
Explanation: Check the Backup Server error log. Check that Backup Server is running.
3004 14 You must be the DBO of database %.*s or have Operator (OPER) role to run DUMP
DATABASE.
Explanation: This error occurs when you try to run dump database on a database that you
do not own and for which you do not have the oper (Operator) role. Ask the DBA to grant
you the operator role. It is good practice to run dbcc checkalloc and dbcc checkdb before
each database dump.
3005 10 DUMP DATABASE failed to end flushlist synchronisation. In database `%.*s', some
transactions may be suspended and further DUMP DATABASEs blocked, requiring reboot
of the SQLServer.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3008 17 There is not enough server memory available to complete this dump database.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3015 10 WARNING: In order to LOAD the master database, the SQL Server must run in single-
user mode. If the master database dump uses multiple volumes, you must execute
sp_volchanged on another SQL Server at LOAD time in order to signal volume changes.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3016 17 DUMP DATABASE for `%S_DBID' cannot continue because of insufficient log space.
Free some log space with DUMP TRANSACTION or turn off replication.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Server Error Messages 3100 - 3199
898
Server Error Messages 3100 - 3199
Number Severity Text and Explanation
3101 16 Database in use. A user with System Administrator (SA) role must have exclusive use
of database to run load.
Explanation: You cannot use load database while a database is in use by any user. This
error occurs when you try to load a dump while users are still accessing the database. Wait
until all users are off the database, then run load database again. Make sure you are not
in the database while attempting to issue the load command. Sybase recommends running
all load commands from master, although any database other than the target can be used.
3102 16 Specified file `%.*s' is not in valid dump database format.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
3103 17 LOAD DATABASE for database `%.*s' failed: insufficient memory to allocate backout
structure.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3105 16 Data on dump will not fit into current database. Need %d Mbyte database.
Explanation: Refer to the writeup for this error.
3108 16 LOAD DATABASE must be used in single user mode if trying to restore the Master
database.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
3109 16 This dump was created from the Master database. A dump from Master can only be
loaded as part of the Restore Master procedure.
Explanation: Load failed. To check that you are using the correct dump, run load with
listonly=full.
3110 14 You must be the DBO of database %.*s or have Operator (OPER) role to run LOAD
DATABASE.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
3111 16 This dump was not created from the Master database. Master can only be loaded from a
dump of the Master database.
Explanation: Load failed. To check that you are using the correct dump, run load with
listonly=full.
CHAPTER 6 Adaptive Server Error Messages
899
3112 16 Cannot load any database other than Master when server in single-user mode.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
3113 21 Database %.*s does not have an entry in SYSUSERS for the DBO.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3114 21 Database %.*s does not have an entry in Sysdatabases.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3115 10 User %.*s in database %.*s has suid %d, which is the same as the suid of the DBO (as
defined in Sysdatabases). User %.*s will be given suid %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
3116 10 When all load transactions have been completed for database %.*s, user %.*s should be
given a unique suid.
Explanation: This is an informational message but may required followup action.
3117 10 Database %.*s already has a user with suid %d. Please call Technical Support.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3118 16 LOAD DATABASE has been interrupted by a USER ATTENTION signal. A LOAD
DATABASE must be completed in this database before it will be accessible.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3120 16 The database you are attempting to LOAD was DUMPed under a different sort order ID
(%d) or character set ID (%d) than the ones running on this server (SortOrd = %d,
CharSet = %d). If the sort orders differ, at least one of them is non-binary.
Explanation: Refer to the writeup for this error.
3121 16 Index %s.%s (objid = %ld, indid = %d) may be invalid. It uses CHAR or VARCHAR
columns in its key and was created under a different sort order ID (%d) or charset ID (%d)
than the ones on this server (SortOrd=%d, CharSet=%d).
Explanation: Indicates that the sort order may have changed between the time that the
database was dumped and loaded back in again; it may also be caused by using dump and
load between different servers. Drop and re-create the index.
3122 21 Failed to patch the transaction log for database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Server Error Messages 3100 - 3199
900
3123 16 The dump header contains an invalid dump type code: %ld. This is not a valid transaction
log dump or database dump.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3124 10 This is a %S_MSG dump of database ID %d, name ’%.*s’, from %S_DATE. SQL Server
version: %.*s. Backup Server version: %.*s. Database page size is %ld.
Explanation: This is an informational message.
3125 10 Database contains %ld pages; checkpoint RID=(%S_RID); next object ID=%ld; sort
order ID=%d, status=%d; charset ID=%d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
3126 10 Log begins on page %ld; checkpoint RID=%S_RID; previous BEGIN XACT
RID=(%S_RID); sequence dates: (old=%S_DATE, new=%S_DATE); truncation
page=%ld; %ld pages deallocated; requires database with %ld pages.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3127 10 All dumped pages have been loaded. SQL Server is now clearing pages above page %ld,
which were not present in the database just loaded.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
3128 10 SQL Server has finished clearing database pages.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
3129 10 Failed to clear in-load status bit for database `%.*s'.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3130 16 Database maxhold label found in dump is an invalid security label. Discontinuing load.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3131 16 Database hurdle label found in dump is an invalid security label. Discontinuing load.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3132 16 Server Data Low label found in dump is an invalid sensitivity label. Discontinuing load.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3133 16 Server Data High label found in dump is an invalid sensitivity label. Discontinuing load.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
901
3134 10 Security label consistency check failed. Please run DBCC SECURITY
(LABEL_CHECK, `%S_DBID', {FULL | NOREPORT}, FIX) after all loads have been
performed in order to make this database usable.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3135 10 Please run DBCC SECURITY (LABEL_CHECK, , [FULL | NOREPORT], FIX) after
all loads have been performed.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3136 10 Database log version=%d; database upgrade version=%ld.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
3137 10 Use the ONLINE DATABASE command to bring this database online; SQL Server will
not bring it online automatically.
Explanation: After a load sequence completes, you must use 'online database' to bring
the database back online. This command also upgrades databases.
3138 10 User defined role '%.*s' used in database '%.*s' does not exist in this server. Use
CREATE ROLE to create this role after the database online.
Explanation: After onlining the database upon completion of a load sequence, a role is
found to be missing from the server. Create the role now for consistency.
3139 10 The user name, '%.*s', in SYSUSERS is the same as a role name in this Server. See the
Security Administration Guide for information on how to resolve this naming conflict.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3140 10 The group name, '%.*s', in SYSUSERS is the same as a role name in this server. See the
Security Administration Guide for information on how to resolve this naming conflict.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3141 16 Object ’%.*s’ in database ’%.*s’ is owned by login ’%.*s’ who does not exist in this
server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
3142 16 Cannot load database ’%.*s’ because it is failed over.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 3200 - 3299
902
Server Error Messages 3200 - 3299
3143 16 The master database you are attempting to load was dumped under a different sort order
id (%d) or character set id (%d) than the ones running on this server (sort order id = %d,
character set id = %d).
Explanation: This message is generated when an attempt is made to load a master
database and the dump was performed on a source server running with a sort order/charset
which is different than the sort order/charset on the target server. The load can only go
ahead under trace 3100, and only after consultation with Sybase Technical Support.
3144 16 Since this load may render the master database unusable, this load will only be permitted
under the 3100 traceflag. Please contact Sybase Technical Support regarding the correct
usage of this traceflag.
Explanation: This message is generated when an attempt is made to load a master
database and the dump was performed on a source server running with a sort order/charset
which is different than the sort order/charset on the target server. The load can only go
ahead under trace 3100, and only after consultation with Sybase Technical Support.
3145 10 Warning: an invalid cross-database reference exists in loaded database %.*s (dbid %d).
Make sure that it can be enforced. Referencing dbid is %d. Referenced dbid is %d. Dump
origin is of database %.*s (dbid %d).
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3146 10 SQL Server cannot load this database dump because the version in the dump is
newer than the version in the database. Database: log version=%d, upgrade
version=%ld. Dump: log version=%d, upgrade version=%ld.
Explanation: You can only load a dump to the same or higher version server.
Number Severity Text and Explanation
Number Severity Text and Explanation
3201 16 No dump device has been specified.
Explanation: Refer to the writeup for this error.
3202 16 Received MULTARG is not for device name as expected.
Explanation: A MULTARG is a structure ASE uses to store in memory information
about the device being dumped to. This error is raised if the dump command is passed a
MULTARG which is not for a dump device and you are running diagserver. If you see this
error, call Sybase Technical Support, providing the server version and SWR level, the
Backup Server version, ASE and Backup Server error logs, text of all errors, and the
operating system error log.
CHAPTER 6 Adaptive Server Error Messages
903
3203 16 Backup Server has detected a SQL Server error.
Explanation: Refer to the writeup for this error.
3204 16 User aborted DUMP or LOAD for database `%S_DBID'.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
3205 26 DUMP failed in database `%S_DBID': attempt to add run to full run list.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3206 20 Backup Server has returned an unexpected status to SQL Server: %d.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3207 16 More parameters have been specified to DUMP or LOAD than can be passed to the
Backup Server.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3208 16 Unexpected end of file while reading beginning of dump. Please confirm that dump media
contains a valid SQL Server dump. The SQL Server error log may contain more
information on the problem.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3209 16 `%.*s' is not a DUMP or LOAD device. Please check sysdevices.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3210 20 DUMP or LOAD of database `%.*s' encountered lock denial on SYSDEVICES to prevent
deadlock. Deadlock should not have been possible.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3211 20 DUMP failed in database %.*s: error occurred executing RPC.
Explanation: Refer to the writeup for this error.
3212 17 DUMP failed in database %.*s: unexpected status executing RPC: %d.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3213 0 An I/O error was detected while doing I/O on buffer 0x%x.
Explanation: Refer to the Adaptive Server Reference Manual for information about the
stored procedure you were running when you got this message.
3214 21 %s: virtual page %ld does not belong to any valid disk device.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Server Error Messages 3200 - 3299
904
3216 10 Backup Server session id is: %ld. Use this value when executing the `sp_volchanged'
system stored procedure after fulfilling any volume change request from the Backup
Server.
Explanation: This is an informational message. See the writeup for Error 3216.
3217 20 %s for database `%.*s' failed to write the dump header.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3218 21 %s for database `%.*s' failed to write the dump trailer.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3219 21 The Backup Server encountered an invalid dump trailer page, so SQL Server is not able
to correctly recover database `%.*s'. Because of this error, the database is now suspect.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3220 17 Could not establish communication with Backup Server `%.*s'. Please make sure that
there is an entry in Sysservers for this server, and that the correct server is running.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3221 20 Could not install a function required to create a %s; returned error code is %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
3222 20 Attempt to write a %S_MSG failed; returned error code is %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3223 20 Attempt to read a %S_MSG failed; returned error code is %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3224 20 INTERNAL ERROR: function `%s' was passed an invalid dump type code: %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3225 21 I/O failed while attempting to clear pages starting at page %ld of disk number %ld.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
905
3226 21 Attempt to allocate a %s failed -- there are none available. SQL Server is unable to clear
unused pages in the database being loaded. Because of this error, the database is unusable.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3227 10 No extent-sized buffers were available, so pages are being cleared by writing each page
separately. Please be patient; %ld pages are being written, which may take a substantial
amount of time. (Rough estimate: %ld minutes.)
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3228 17 Insufficient contiguous SQL Server memory to allocate DB disk status array; %d bytes
were required.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3229 10 For logical disk device `%.*s', primary device `%.*s' is not active. Secondary device
`%.*s' will be used.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3230 24 For logical disk device `%.*s', neither primary device `%.*s' nor secondary device `%.*s'
is active. %s cannot continue.
Explanation: Hardware error detected. See the writeup for Error 3230.
3231 20 Invalid disk side token: %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3232 17 For logical disk device `%.*s', %S_MSG physical disk device `%.*s' has become
unmirrored since the start of %s. Resulting work is invalid.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3233 17 %s for database `%S_DBID' failed: an alarm function could not be installed.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3234 20 %s for database `%S_DBID' failed to remove alarm with ID = %d.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3235 20 For logical disk `%.*s', %S_MSG physical device is internally designated DB device for
%s, but Sysdevices.status value `0x%x' conflicts.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 3200 - 3299
906
3236 10 Remirroring the affected portions of the usage map that are on mirrored devices.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3237 20 %s failed to find disk status entry for virtual page `%ld'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3238 20 Internal I/O error on %S_MSG pysical device on virtual page number `%ld' while %s was
remirroring loaded database.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3239 17 %s could not allocate a large IO buffer. Try again later.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3240 20 Unable to obtain the SQL Server's current working directory. The SQL Server must have
search permission on its current working directory and the name must be shorter than %d
bytes.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3241 20 Unable to get IO access type for device `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3242 20 Internal sensitivity label inconsistency encountered during dump. Conversion of Data
High, Data Low, database maxhold, or database hurdle to human-readable string failed.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3243 10 Loading a dump from a non-B1 SQL Server into a B1 SQL Server is not allowed.
Explanation: The dump you are trying to load may not be compatible with your Server
version.
3244 20 %s failed for database `%S_DBID' with an internal transaction logging system failure;
returned error code is %ld.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3246 18 Unable to update the sysdatabases.dumptrdate column for dbid %d. The next DUMP
TRANSACTION on the database will automatically correct this.
Explanation: The database DUMP TRANSACTION date could not be updated.
3247 16 %s for database '%.*s' failed: connection to %S_MSG failed. %S_MSG may have been
shut down with no wait, or killed with an operating system command.
Explanation: Check that the remote server is running.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
907
Server Error Messages 3300 - 3399
3248 16 LOAD DATABASE / TRANSACTION failed because of page size incompatibility. The
current page size is %ld, and the page size in the dump is %ld.
Explanation: You can only load a dump to a server using the same page size.
Number Severity Text and Explanation
Number Severity Text and Explanation
3301 21 Invalid log record found in syslogs (logop %d).
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3303 21 Failed to find SAVEPT in log for xact %S_RID, current number is %d, looking for %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3305 21 Page %ld in database `%.*s' read in during runtime or load xact was uninitialized.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3306 21 Process %d was expected to hold logical lock on page %ld instead of process %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3307 21 Process %d was expected to hold logical lock on page %ld in database %S_DBID for
object %S_OBJID, index number %d.
Explanation: Refer to the writeup for this error.
3308 21 Page %ld was expected to have %s lock on it.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3309 21 While in backout, process %d was chosen as deadlock victim while waiting for a resource
lock on page %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Server Error Messages 3300 - 3399
908
3310 21 Cannot find log record with RID: (%ld, %d).
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3311 22 Space left (%d bytes) on page %ld is insufficient to move data of %d length.
Explanation: Report the error to your System Administrator.
3312 22 Free offset %d is invalid on page %ld. It must be within %d and %d.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
3313 10 Error while redoing log row in database `%S_DBID'. %S_RID.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3314 10 Error while undoing log row in database `%.*s'. %S_RID.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3315 21 While redoing a transaction, the end of the log was encountered before the endxact
record.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3316 21 While redoing a transaction, an attempt to reget an XCMD row failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3317 16 ROLLBACK TRIGGER can only be executed when a trigger is executing. It may be
called directly by the trigger, or from a stored procedure executed directly or indirectly
from a trigger.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3318 21 Failed to start a scan on syslogs, Error number %ld
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
909
Server Error Messages 3400 - 3499
Number Severity Text and Explanation
3401 21 Rec_init: getnext SCAN_RID of last checkpoint failed on Rid from sysdatabases.
%S_RID.
Explanation: See the writeup for Error 3401.
3403 22 During recovery initialization, page %ld was encountered. This page belongs to object
%ld, not the log.
Explanation: Refer to the writeup for this error.
3404 21 Rec_complete: Could not open controlling database (id %d) of controlling database in
multi-db transaction.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3405 10 Recovering database `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3406 10 %d transactions rolled forward.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3407 10 %d transactions rolled back.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3408 10 Recovery complete.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3409 10 Roll forward transaction `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3410 10 Roll back transaction `%.*s' -- was aborted.
Explanation: This is an informational message. See the writeup for Error 3410.
3411 10 Roll back transaction `%.*s' -- no `end transaction'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Server Error Messages 3400 - 3499
910
3412 21 Database %d, table %ld. Attempt to mark table as suspect. Getnext SCAN_CLUST on
sysobjects.objid failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3413 21 Database %d. Attempt to mark database as suspect failed. Getnext NC scan on
sysdatabases.dbid failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3414 10 Database `%.*s' (dbid %d): Recovery failed. Check the SQL Server errorlog for further
information as to the cause.
Explanation: Refer to the writeup for this error.
3417 21 Cannot recover the master database, exiting.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3418 21 Not enough deses to open `%.*s'.
Explanation: Refer to the writeup for this error.
3419 16 Unable to proceed with the recovery of dbid <%d> because of previous errors. Continuing
with the next database.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3421 21 Unable to recover database `%.*s' because of a failure to initialize the global timestamp.
This indicates that a problem exists in the log for the current database. Please contact
Technical support for assistance.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3423 21 Error recovering database `%.*s' - could not find expected BEGIN TRANSACTION
record at location: %S_RID.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3424 21 No more room in transaction table for transaction (%ld, %d).
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
3425 21 Transaction (%ld, %d) not found in transaction table.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
911
3426 10 Could not make log consistent during special recovery of database %d. Please contact
Technical support for assistance.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3429 21 Error recovering database `%.*s' - could not connect to commit service to check
completion status of xact: %S_RID.
Explanation: Refer to the writeup for this error.
3430 16 Could not add a checkpoint record during special recovery of database %d. If you intend
to do updates in this database, first free up space by running DUMP TRANasction WITH
NO_LOG, and then checkpoint the database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3431 10 Could not build an allocation map for the database %.*s. It does not have a DBINFO
structure
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3433 16 Name is truncated to `%.*s'. The maximum name length is %d.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3434 20 Cannot change sortorder. Server shutting down. Restart to continue with sortorder
unchanged.
Explanation: See the writeup for Error 3434.
3435 20 Sortorder cannot be changed because user objects or user databases exist.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3436 20 Cannot rebuild index %d for the `%.*s' table in the `%.*s' database.
Explanation: A database maintenance operation failed. Restart Adaptive Server and take
any corrective action indicated by the message. Check the Adaptive Server error log.
3437 10 Please run sp_dbupgrade in database %.*s to update system catalogs.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3438 21 Function %s was called by process %d, which is not the recovery process.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3439 10 Database `%S_DBID' has inconsistent security labels. Disabling use of database.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
Number Severity Text and Explanation
Server Error Messages 3400 - 3499
912
3440 10 System stored procedures are not currently accessible due to a recovery error. Please
consult the errorlog. You may need to drop and re-create the sybsystemprocs database and
re-run the installmaster SQL script if the error is unrecoverable.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3443 16 Invalid log version found for database `%S_DBID': `%d'. A log version greater than `%d'
is from an later, incompatible version of SQL Server. Database cannot be opened.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
3444 10 Database `%.*s' is now online.
Explanation: This is an informational message. It appears when a database is brought
online by an online database command, or when database recovery is complete. online
database marks the database available for public use after a normal load sequence and, if
needed, upgrades a pre-11.0 database and transaction log dumps to the current version of
Adaptive Server.
3445 10 SQL Server could not bring database `%.*s' online.
Explanation: Refer to the writeup for this error.
3446 16 You do not have privilege to bring database `%.*s' online.
Explanation: Refer to the writeup for this error.
3447 10 Database `%.*s' appears to be in the process of being loaded; SQL Server will not bring it
online automatically. Use the ONLINE DATABASE command to bring this database
online.
Explanation: Refer to the writeup for this error.
3448 10 Database `%.*s' appears to be at an older revision than the present installation; SQL Server
will assess it, and upgrade it as required.
Explanation: This is an informational message. It is raised when you upgrade a database
to the current ASE version (via sybinit or via online database) and is displayed at the start
of the upgrade process.
3449 10 Database ’%.*s’: beginning upgrade step [ID %5d]: %S_MSG %s
Explanation: This informational message tells you that Adaptive Server is beginning an
upgrade step. The text of the message includes the database name, which upgrade step is
being performed, the name of the object being upgraded, the task ID of the Server internal
upgrade function, and the index name, if applicable. No action is required.
3450 20 Database `%.*s': upgrade item %d contains a bad action identifier, %d. Please report this
internal error to Sybase technical support.
Explanation: This error occurs during upgrade (via sybinit or online database). An
upgrade item is a step required by the upgrade, and an action identifier is a number
denoting actions to be performed for the upgrade item. Report this error to Sybase
Technical Support, providing server version and SWR level, full text of the message, and
server error log.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
913
3451 20 Database `%.*s': upgrade has failed for this database. Please refer to previous messages
for the cause of the failure, correct the problem and try again.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
3452 20 Database `%.*s': upgrade item %d depends on item %d, which could not be installed.
Please refer to previous messages for the cause of the failure, correct the problem and try
again.
Explanation: Refer to the writeup for this error.
3453 20 Database `%.*s': upgrade failed to open table %d. This table should exist in every
database.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3454 10 Database `%.*s': SQL Server could not completely upgrade this database; upgrade item
%d could not be installed.
Explanation: Refer to the writeup for this error.
3455 20 Database `%.*s': SQL Server could not find its internal description of system table `%.*s'.
Please report this internal error to Sybase technical support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
3456 20 Database `%.*s': during an upgrade, SQL Server could not create table `%.*s'.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3457 20 Database `%.*s': the dependency list for upgrade item %d contains an invalid identifier,
%d. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3458 20 Database `%.*s': upgrade was asked to locate column `%.*s' for table `%s'; this column
does not exist. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3459 20 Database `%.*s': upgrade could not determine the name of table ID `%d'. Please refer to
previous error messages to determine the problem. Fix the problem, then try again.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3460 20 Database `%.*s': upgrade could not record the installation of upgrade item `%d'. Please
refer to previous error messages to determine the problem. Fix the problem, then try again.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
Server Error Messages 3400 - 3499
914
3461 20 Database `%.*s': upgrade could not install required upgrade item `%d'. Please refer to
previous error messages to determine the problem. Fix the problem, then try again.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3462 10 Database `%.*s': upgrade could not install optional upgrade item `%d'. Please refer to
previous error messages to determine the problem. Upgrade will continue.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3463 20 Database `%.*s': upgrade was asked to create an index on table `%s'; this table does not
exist. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3464 20 Database `%.*s': upgrade item %d has a bad format: info=%d, data='%s'. Please report
this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3465 20 Database `%.*s': upgrade could not locate a row in systypes with usertype=%d and
type=%d. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3466 20 Database `%.*s': upgrade could not locate systypes.name where usertype=%d and
type=%d. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3467 20 Database `%.*s': Index `%s.%s' has id %d in Sysindexes, but %d in our internal
description. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3468 20 Database `%.*s': upgrade was asked to create index %d on table `%s', but there is no such
index. Please report this internal error to Sybase technical support.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3469 20 Database `%.*s': upgrade failed to create index %d on table `%s'. Please refer to previous
error messages to determine the problem. Fix the problem, then try again.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
3470 10 SQL Server could not completely upgrade database `%.*s', but the database was online
when upgrade began, so it will be left online.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
915
3471 10 Database `%.*s' can not be brought online because it has replicated tables that have not
been completely transferred. It will come online automatically after replication is
complete.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3472 21 Unable to access database '%.*s' (dbid %d): recovery failed, please contact Sybase
Technical Support.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3473 21 There is no space available in SYSLOGS for process %d to log a record for which space
has been reserved. It may be necessary to add space to the log segment. The internal error
number is %d.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3474 21 During redo the page timestamp value is less than old timestamp from log. Page #= %ld,
object id = %ld, page timestamp=%04x %08lx. Log old timestamp=%04x %08lx.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3475 21 There is no space available in SYSLOGS for process %d to log a record for which space
has been reserved. This process will retry at intervals of one minute. The internal error
number is %d.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3476 16 Redo pass: %d records done (%d%%); %d records left.
Explanation: This is an informational message.
3477 16 Undo pass: %d records done (%d%%); %d records left.
Explanation: This is an informational message.
3478 21 During undo the page timestamp value is less than new timestamp from log. Page #= %ld,
object id = %ld, page timestamp=%04x %08lx. Log new timestamp=%04x %08lx.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3479 10 Redo pass of recovery has processed %d committed and %d aborted transactions.
Explanation: This is an informational message.
3480 10 Undo pass of recovery has processed %d incomplete transactions.
Explanation: This is an informational message.
3481 10 Undo pass of recovery has processed %d incomplete nested top actions.
Explanation: This is an informational message.
3482 10 Redo pass of recovery has reinstantiated %d prepared transactions
Explanation: This is an informational message.
Number Severity Text and Explanation
Server Error Messages 3400 - 3499
916
3483 10 Undo pass of recovery has resolved %d prepared transactions
Explanation: This is an informational message.
3484 21 Recovery encountered an error in acquiring locks for reinstantiated transactions. Please
consult the Adaptive Server errorlog for further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3485 21 Recovery encountered an error while reserving space for log records for which space had
already been reserved during run time. Please consult the Adaptive Server errorlog for
further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3486 21 Recovery failed to open a session with the transaction log during transaction
reinstantiation. Please consult the Adaptive Server errorlog for further information as to the
cause.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3487 21 Recovery detected an incorrect internal transaction state during transaction reinstantiation.
Please consult the Adaptive Server errorlog for further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3488 21 Recovery encountered an internal error during transaction reinstantiation. Please consult
the Adaptive Server errorlog for further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
3489 10 Warning: A transaction ’%.*s’ that updated system tables was found to be in a prepared
state, and is being unconditionally rolled back. Please consult your System Administrator.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3490 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3491 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
917
3492 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3493 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3494 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3495 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3496 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3497 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3498 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
3499 16 This error message number is reserved for a recovery message that must also be printable
as a kernel message. Recovery error messages not to be printed as kernel messages are
added under the RECOVER2 major error number.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 3500 - 3599
918
Server Error Messages 3500 - 3599
Server Error Messages 3600 - 3699
Number Severity Text and Explanation
3501 21 Could not get sysdatabases row for database `%d' at checkpoint time.
Explanation: This message indicates a problem with the Replication Agent Thread due
to shutdown or abnormal termination. Contact your System Administrator.
3502 21 No checkpoint records found in syslogs for database `%.*s'.
Explanation: This message indicates a problem with the Replication Agent Thread due
to shutdown or abnormal termination. Contact your System Administrator.
3504 0 Sysindexes page # %ld in database ’%.*s’ is not in buffer cache at checkpoint after
getindex call.
Explanation: This message is not used but is present in sysmessages.
3505 14 Only the DBO of database %S_DBID or a user with System Administrator (SA) role may
run the checkpoint command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
3508 10 Attempt to set `%.*s' database to single user mode failed because the usage count is %ld.
Make sure that no other users are currently using this database and rerun CHECKPOINT.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
3604 10 Duplicate key was ignored.
Explanation: Refer to the writeup for this error.
3605 10 Duplicate row was ignored.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3606 10 Arithmetic overflow occurred.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
CHAPTER 6 Adaptive Server Error Messages
919
3607 10 Divide by zero occurred.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3608 10 Null value used in an expression.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3612 10 Execution Time %ld.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3613 10 Parse and Compile Time %ld.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3614 10 Total writes for this command: %ld
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3615 10 Table: %.*s scan count %ld, logical reads: (regular=%ld apf=%ld total =%ld), physical
reads: (regular=%ld apf=%ld total=%ld), apf IOs used=%ld
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3616 22 Non-leaf page %D in table %D, index %d is empty - please rebuild the index.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
3618 10 Transaction has been aborted.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3619 10 Unable to write CHECKPOINT record in database %d because the log is out of space.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
3620 10 Automatic checkpointing is disabled in database `%.*s' because the log is out of space. It
will continue when the DBO successfully checkpoints the database. Please free up some
space or extend the database and then run CHECKPOINT.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3621 10 Command has been aborted.
Explanation: Refer to the writeup for this error.
3622 10 Domain error occurred.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
Server Error Messages 3600 - 3699
920
3623 10 A transaction on a no_log table was undone. Check the errorlog file in the SQL Server
directory for details.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3624 10 Truncation error occurred.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3625 10 Table: %.*s scan count %lu, logical reads: %lu, physical reads: %lu, estimated I/O cost:
%lu.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3626 17 The transaction was aborted because it used too much stack space. Either use sp_configure
to increase the stack size, or break the query into smaller pieces. spid: %d, suid: %d,
hostname: %.*s, application name: %.*s
Explanation: Refer to the writeup for this error.
3627 10 Conversion of char/varchar datatype to security label datatype failed.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3628 10 Conversion of security label datatype to char/varchar datatype failed.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
3629 10 Statement: %d Subquery: %d cache size: %d hits: %d misses: %d
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
3630 10 Total estimated I/O cost for statement %u (at line %u): %ld.
Explanation: This message is informational and is displayed if you have enabled
Resource Limits for the server.
3631 10 Total actual I/O cost for this command: %ld.
Explanation: This is an informational message. No action is needed.
3632 10 Command batch has been aborted.
Explanation: This is an informational message.
3634 20 Task %d is trying to release a latch 0x%x which is already free.
Explanation: This is an internal error affecting the current process. Contact your SA.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
921
Server Error Messages 3700 - 3799
Number Severity Text and Explanation
3701 11 Cannot drop the %S_MSG `%.*s', because it doesn't exist in the system catalogs.
Explanation: Refer to the writeup for this error.
3702 16 Cannot drop the %S_MSG `%.*s' because it is currently in use.
Explanation: Refer to the writeup for this error.
3703 11 Cannot drop the %S_MSG with object-id %ld in database %d, because it doesn't exist in
the system catalogs.
Explanation: Refer to the writeup for this error.
3704 16 Cannot drop the %S_MSG `%.*s' because you are not the owner or a user with System
Administrator (SA) role.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
3705 16 Cannot use DROP %s with `%.*s' because `%.*s' is a %S_MSG. Use DROP %s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3708 16 Cannot drop the %S_MSG `%.*s' because it is a system %S_MSG.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3709 16 Cannot drop `%.*s' because you are not currently in the master database.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
3710 16 Cannot use DROP with `%.*s' because `%.*s' is a %S_MSG. Use ALTER TABLE.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3711 16 Cannot use ALTER TABLE with `%.*s' because `%.*s' is a %S_MSG. Use DROP %s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3712 16 Cannot drop %S_MSG `%.*s' because it still has referential integrity constraints.
Explanation: A table cannot be dropped if it has dependent foreign keys or other
referential integrity constraints. Check the constraints associated with the table.
3716 16 The %S_MSG `%.*s' cannot be dropped because it is bound to one or more %S_MSG.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Server Error Messages 3700 - 3799
922
3718 11 Could not drop index `%.*s' because the table/clustered index entry cannot be found in the
sysindexes system catalog.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
3723 16 The table `%.*s' does not have the %S_MSG `%.*s'. Cannot drop.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3724 16 Level of table or object `%.*s' does not match user's curwrite level. Cannot drop.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3725 16 Level of index `%.*s' does not match user's curwrite level. Cannot drop.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3726 16 Level of database `%.*s' does not match user's curwrite level. Cannot drop.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3727 16 Can not drop the database `%.*s' because cursor `%.*s' is still open. Close the cursor(s)
before dropping the database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3728 16 Cannot drop this database `%S_DBID' as it has some dependencies (referential
constraints) from database `%S_DBID'. Drop the referencing database first, before
dropping the referenced database (dependent database).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3729 20 The dropo() function is trying to put too many lock requests in the lock_requests[] array.
Explanation: An internal Adaptive Server error occurred. Report the error to Sybase
Technical Support.
3730 16 Can not drop index `%.*s' because cursor `%.*s' is open. Close the cursor(s) before
dropping the index.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3731 16 Cannot drop table `%.*s' because it is partitioned.
Explanation: Refer to the writeup for this error.
3732 16 Cannot drop index `%.*s' because there are one or more isolation level 0 scans active on
table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
923
3733 10 Warning: There is an invalid cross-database reference in the system catalogs. The
referenced database '%.*s' does not exist.
Explanation: This is an informational message. Notify your System Administrator about
the message.
3734 10 Warning: There is an invalid cross-database reference in the system catalogs. The
referencing database '%.*s' does not exist.
Explanation: This is an informational message. Notify your System Administrator about
the message.
3735 10 Warning: There is an invalid cross-database reference in the system catalogs. A referenced
table, id %d, in database '%.*s' does not exist.
Explanation: This is an informational message. Notify your System Administrator about
the message.
3736 10 Warning: There is a missing referential constraint catalog entry in database '%.*s'.
Explanation: This is an informational message. Notify your System Administrator about
the message.
3738 16 Drop index error: %S_MSG `%.*s' does not have any indexes. Only tables have indexes.
Explanation: DROP INDEX was attempted on an object with no indexes. Only tables
with associated indexes may be targeted for this command.
3740 10 The `drop' command is bypassing updation of referential status bits and flags in database
`%.*s', because a referenced table, id %d, is non-existent. The command will execute
successfully (assuming no further errors in processing).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
(Not raised in 11.9.2).
3741 16 Cannot drop object `%.*s' because it is tagged as partitioned (# of slices=%ld) although it
shouldn't.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3742 11 Cannot drop the lightweight procedure '%.*s' because it doesn't exist.
Explanation: Command failed. Check your database for the object not found and re-enter
the command with the correct name.
3743 16 Can not drop the database ’%.*s’ because is is a system proxy database. Use the primary
server, and drop the primary database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3744 16 Can not drop the database ’%.*s’ because it is a failed over database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 3800 - 3899
924
Server Error Messages 3800 - 3899
3745 16 Cannot drop the database ’%.*s’ because it contains one or more Java classes that are being
used as datatypes for columns in table ’%.*s’. Drop the table before dropping the database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3746 16 Cannot drop table ’%.*s’ because option ’%s’ is set in database ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3748 16 Stored procedure %.*s is being used as automatic login script.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
3749 16 Database ’%.*s’ was incompletely dropped; see preceding error. Either re-run the
’DROP DATABASE’ command or run ’DBCC CHECKALLOC’ to fix allocation
information.
Explanation: Command failed due to invalid or illegal request. Take corrective action
indicated by message.
3750 16 Unable to drop %S_MSG with object ID %d in database %d, because locks could
not be acquired on system tables. Retrying.
Explanation: This is an informational message.
Number Severity Text and Explanation
Number Severity Text and Explanation
3801 16 There is no host variable corresponding to the one specified by the PARAM datastream.
This means that this variable `%.*s' was not used in the preceding DECLARE CURSOR
or SQL command.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
3802 18 There is no cursor information given with the current datstream. A cursor id of zero was
specified and no name was specified. The current batch of commands is being aborted.
This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3803 16 The statement used to define the cursor `%.*s' is neither a SELECT nor an EXECUTE.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
925
3804 16 More than one SELECT statement is used to define the cursor `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
3805 18 The token datastream length was not correct. This is an internal protocol error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3806 16 Both the READ ONLY and the FOR UPDATE options have been specified for cursor
`%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
3807 18 The datastream specifies a wrong option or command. The datastream is `%s'. This is an
internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3808 18 The column is not part of the RESDOM column list. This means the plan for the cursor
is corrupted. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3809 18 Unknown datatype token `%d' has been sent to the server. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3811 18 A wrong datastream has been sent to the server. The server was expecting token %d but
got the token %d. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3812 18 The datastream for token %d should only be sent after other datastreams. It can not be a
command datastream on it's own. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3813 18 A wrong datastream has been sent to the server. The server was expecting a dynamic sql
command token but got the token %d. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3814 16 The parameter of type %d did not have a valid value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
3816 18 Internal Syslabels manager Error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 3900 – 3999
926
Server Error Messages 3900 – 3999
3819 16 The dynamic PREPARE statement `%.*s' failed because of an internal problem while
sending the input parameters formats to the client.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
3820 16 The datastream length for the ’%s’ token exceeds the allowable maximum of 65535 bytes.
This can happen when Adaptive Server is sending a large number of columns or
parameters to a pre-12.5 client or remote server.
Explanation: Check that the client or remote server is compatible.
Number Severity Text and Explanation
Number Severity Text and Explanation
3901 17 This transaction uses too many databases and/or aggregates. The maximum allowed is
%d. The transaction must be split into smaller sections.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
3902 13 The commit transaction request has no corresponding BEGIN TRANSACTION.
Explanation: Adaptive Server detected an invalid transaction context for the
commands. Check your commands.
3903 13 The rollback transaction request has no corresponding BEGIN TRANSACTION.
Explanation: Adaptive Server detected an invalid transaction context for the
commands. Check your commands.
3904 21 Can't unsplit logical page %ld in object `%S_OBJID' in database `%S_DBID' - both
pages together contain more data than will fit on one page.
Explanation: Refer to the writeup for this error.
3905 21 Can't unsplit logical page %ld in object `%S_OBJID' in database `%S_DBID' - row
number %d is used on both pages.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
3906 16 Attempt to BEGIN TRANsaction in database `%.*s' failed because database is READ
ONLY.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
927
3907 21 Failed to receive results from PROBE. The distributed transaction named %.*s has not
been committed and data may be inconsistent across databases.
Explanation: Adaptive Server encountered an internal error with a distributed
transaction affecting all processes using the current database. Report the error to your
System Administrator.
3908 16 Attempt to BEGIN TRANsaction in database `%.*s' failed because database is in
BYPASS RECOVERY mode.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
3909 18 While closing transaction descriptor, server found it not marked as having a kept
database.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
3913 26 Attempt to use an inactive internal transaction. This is an internal system error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3914 26 Illegal internal transaction status. This is an internal system error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3915 26 Attempt to make a transaction in dbid %d internal. This is an internal system error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3916 26 Internal transaction lock context chains mixed up. This is an internal system error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3917 16 An attempt was made to startup a multi-database update in database `%S_DBID' after
starting up the master transaction in tempdb. This could render the database `%S_DBID'
unrecoverable and this update is therefore not allowed.
Explanation: Command failed due to invalid or illegal request. Check the database
context for the transaction. Take any corrective action indicated by message.
3921 14 You cannot start a %s transaction in master, model, or sybsystemdb.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
3922 26 Attempt to start a sub transaction without a parent transaction. This is an internal system
error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3923 26 Attempt to set parallel status on transaction by non-parent thread. This is an internal error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
Server Error Messages 3900 – 3999
928
3924 26 Illegal attempt to start sub-transaction by a parent thread. This is an internal error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3925 26 Attempt to set parallel status on transaction that is not in CMD mode. This is an internal
error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3926 26 Empty Parent Session Id passed to start a sub transaction. This is an internal system error.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
3927 17 Could not find an available transaction descriptor. Raise the value of the configuration
parameter ’txn to pss ratio’.
Explanation: Command failed when a configurable limit was exceeded. Report the
error to your System Administrator.
3928 16 An attempt was made by this thread (spid=%d) to attach to a transaction. This is illegal
because this thread is already associated with a transaction. Use systransactions to find
out more information.
Explanation: Query failed. Take any corrective action indicated by the message.
3929 16 An attempt was made by this task (spid=%d) to detach from a transaction. This is illegal
because this task is currently not associated with the transaction. Use systransactions table
to obtain more information.
Explanation: Query failed. Take any corrective action indicated by the message.
3930 20 Systransactions system table does not exist in this database. You need to upgrade to the
correct version. The command is aborted.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3931 16 Transaction Manager API '%.*s' failed. It was invoked with a wrong transaction type
'%ld'.
Explanation: Command failed due to invalid or illegal request. Check syntax and
semantics.
3932 16 Attempt to begin a multi database transaction failed. It is illegal to begin a subordinate
transaction in the master database.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
3933 16 Attempt to start an external transaction failed. It is illegal to begin an external transaction
from with in the scope of a local transaction.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
929
3934 16 Transaction manager has detected a nesting failure. Number of BEGIN TRAN commands
(issued after an attach operation) do not match the number of COMMIT TRAN
commands (issued before a detach operation).
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
3935 16 Fatal protocol error. xact_beginupdate() API was invoked in the wrong c ontext. The
transaction is currently in '%d' state.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
3936 0 Heuristic completion of transaction did not succeed. After ensuring that everything is ok,
use dbcc forget_xact() command to delete the entry from systransactions system table.
Explanation: Refer to the Adaptive Server Reference Manual for information about the
stored procedure you were running when you got this message.
3938 20 Fatal protocol error. xact_begin() API was invoked in the wrong context. The distributed
transaction is currently in ’%s’ state.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
3939 10 Illegal attempt to rollback transaction (xactname '%.*s') that has already committed in
database '%.*s', spid %d.
Explanation: Check command semantics and processing logic of your query.
3940 10 The MSDTC Service is not enabled. Please consult the errorlog and restart the MSDTC
Service.
Explanation: Check command semantics and processing logic of your query.
3941 10 The MSDTC Interface %s failed with error 0x%lx -- %s.
Explanation: Check command semantics and processing logic of your query.
3942 16 Database %s is not allowed to participate in a distributed transaction.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
3943 14 %s’ transactions are not allowed in an HA configuration.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
3944 16 Attempt to BEGIN TRANSACTION in database ’%S_DBID’ failed because the
database is in standby access mode.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
3945 16 You cannot begin an external transaction for a server that is in single-user mode.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
Number Severity Text and Explanation
Server Error Messages 3900 – 3999
930
3946 16 Cannot start external transaction without a DTM license.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
3947 16 A heuristic completion related operation failed. Please see errorlog for more details.
Explanation: Command failed due to invalid or illegal request. Check semantics and
working context.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
931
Server Error Messages 4000 – 4099
Number Severity Text and Explanation
4001 11 Cannot open default database `%.*s'.
Explanation: Command failed. Check syntax and your Adaptive Server environment.
4002 14 Login failed.
Explanation: Refer to the writeup for this error.
4013 14 Login failed - not a secure SQL Server.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4016 16 Language name in login record `%.*s' is not an official name on this SQL Server. Using
default `%.*s' from syslogins instead.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4017 16 Neither language name in login record `%.*s' nor language name in syslogins `%.*s' is an
official language name on this SQL Server. Using server-wide default `%.*s' instead.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4018 16 Your default language name from syslogins `%.*s' is not an official language name on this
SQL Server. Using server-wide default `%.*s' instead.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4019 16 Default date order `%.*s' for language `%.*s' is invalid. Using `mdy' instead.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4020 20 While reading characters from the client, the receiving buffer has been detected to be too
small.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
4022 10 The password has expired, but you are still allowed to log in. You must change your
password before you can continue. If a login trigger is set, it will not be executed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
4023 10 Your password will expire in %s days.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Server Error Messages 4000 – 4099
932
4024 10 The packet size (%d) specified at login time is illegal. Legal values are between 512 and
%d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
4025 10 A serious error was encountered while attempting to increase the packet size specified for
spid %d. The Network memory map maybe corrupt. Call Technical Support for further
assistance.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
4050 11 Component Integration Services not enabled or not installed.
Explanation: Command failed. Check your Adaptive Server environment.
4051 14 Security Control Layer has not been initialized. Security session cannot be established.
Explanation:
4052 14 Failed to allocate data structure for use by the Security Control Layer. Cannot establish a
security session.
Explanation:
4053 14 Security session setup failed during security session establishment.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
4054 14 Protocol negotiation failed during security session establishment.
Explanation:
4055 14 Unified Login through the underlying security mechanism is required to connect to the
SQL Server.
Explanation:
4056 16 Login name %.*s not found. Check and make sure an entry exists in Syslogins.
Explanation: You used an invalid login name. Check that the name exists in syslogins.
4057 16 Login name %.*s not a user in the current database.
Explanation: Check login and working database context.
4058 16 Login currently under set session authorization. It is required to go back to the original
identity before performing another set session authorization.
Explanation: You can only assume another identity from the original identity.
4059 16 Set session authorization requires a target identity. Please specify a valid login name.
Explanation: Check for missing information in query.
4060 16 Login name not found for suid %d. Check and make sure an entry exists in Syslogins.
Explanation: Check the syslogins system table.
4061 10 The SQL Server is using the default authentication information file for it's authentication
information.
Explanation: This is an informational message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
933
4062 10 Some of the requested security services are not supported by the underlying security
mechanism. Please contact a user with SSO_ROLE.
Explanation: This is an informational message but may require action as indicated.
4063 10 Security services being used for this connection are inadequate as per the SQL Server's
security configuration requirements. Please contact a user with SSO_ROLE.
Explanation: You may be logging in to Adaptive Server via an insecure connection.
4064 16 Invalid security service requested.
Explanation: Invalid or incorrect connection context. Contact a user with System
Security Officer (SSO) role.
4066 16 Login account %.*s is locked. Please contact a person with SA or SSO role.
Explanation: Contact the System Administrator to resolve the login security issue.
4067 14 Login failed because an incorrect password was supplied.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4068 14 HA Login failed. Session handle not found (sys:%d ses:%d).
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4069 14 HA Login failed. Session handle issued to different user: ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4070 14 HA Login failed. There is no failover in progress.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4071 14 HA Login failed. Failover timeout.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4072 14 HA Login failed. Failback timeout.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4073 14 HA Login failed. Server not in HA primary configuration.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4074 14 HA Login failed. Server not in HA secondary configuration.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4075 16 ’enable enterprise java beans’ option not set.
Explanation: Set the specified option to continue.
4076 16 EJB Config Error : SYBASE environment variable not set.
Explanation: Check your Adaptive Server environment.
Number Severity Text and Explanation
Server Error Messages 4000 – 4099
934
4077 16 EJB Config Error : SYBASE_EJB environment variable not set.
Explanation: Check your Adaptive Server environment.
4078 16 Enterprise java bean server is up and running.
Explanation: This is an informational message.
4079 16 Enterprise java bean server is down.
Explanation: This is an informational message. You may need to restart the EJB server.
4080 16 Enterprise java bean server not started since the auto start option is not enabled.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4081 16 Enterprise java bean server not started since no EJB server has been configured.
Explanation: Check your EJB documentation to configure the server.
4082 16 EJB Config Error : Could not obtain the directory where the krg file is located
Explanation: Check your EJB environment.
4083 16 Unable to open the ASE krg file
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4084 16 Unable to create the krg file for the ejb server
Explanation: Command failed due to invalid or illegal request.
4085 16 Unable to write %d bytes into the ejb server krg file
Explanation: Command failed due to invalid or illegal request.
4086 16 Could not execute login script for user %.*s
Explanation: Command failed due to invalid or illegal request.
4087 16 Unable to open ejb server property file %s.
Explanation: Command failed due to invalid or illegal request.
4088 16 Unable to open the listener property file %s.
Explanation: Command failed due to invalid or illegal request.
4089 10 Need to have a valid java license and the ’enable enterprise java beans’ option set to
execute this command
Explanation: Adaptive Server cannot perform the requested action. Take any corrective
action indicated by the message.
4090 10 There is no valid license for ASE_EJB hence the EJB Server feature is not enabled.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4091 10 The ’enable enterprise java beans’ configuration option needs to be set to execute this
command.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
935
Server Error Messages 4200 - 4299
4092 10 The ’enable enterprise java beans’ configuration option needs to be set to execute this
command.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4093 10 SSL Plus security modules loaded successfully.\n
Explanation: This is an informational message.
4094 16 The Enterprise Java Bean feature is not supported on this platform.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
Number Severity Text and Explanation
Number Severity Text and Explanation
4201 17 DUMP TRANSACTION for database `%.*s' failed: insufficient memory to allocate
backout structure.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4204 17 Unable to continue logged version of DUMP TRAN. No space left in database; use
NO_LOG option or run ALTER DATABASE. Else, an old transaction may be active; see
Syslogshold table.
Explanation: Refer to the writeup for this error.
4205 16 Syslogs does not exist in its own segment in database `%S_DBID' with segmap `%ld'
with logical start page number of `%ld'. You cannot use DUMP TRANSACTION in this
case, use DUMP DATABASE instead.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4206 16 You cannot run DUMP TRANsaction WITH NO_LOG inside a user transaction.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4207 16 Dump transaction is not allowed because a non-logged operation was performed on the
database. Dump your database or use dump transaction with truncate_only until you can
dump your database.
Explanation: Refer to the writeup for this error.
Server Error Messages 4200 - 4299
936
4208 16 DUMP TRANsaction to a dump device is not allowed while the trunc. log on chkpt.
option is enabled. Disable the option with sp_dboption, then use DUMP DATABASE,
before trying again.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4210 16 While attempting DUMP TRANsaction WITH NO_TRUNCATE, couldn't find database
%.*s.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4211 23 Couldn't complete DUMP TRANsaction WITH NO_TRUNCATE on database `%.*s',
because the log pointer in sysdatabases (page number %ld) is not accurate.
Explanation: The database may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
4212 16 Page %ld in database `%.*s' cannot be used as a truncation page because the page belongs
to object ID %ld and not to the log. Choose another page.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4213 16 Page %ld in database `%.*s' cannot be used as a truncation page because the page is not
allocated. Choose another page.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4214 16 Cannot use page %ld in database `%.*s' as the trunc page because the LTM trunc state is
not set to TRUNC_VALID. Set LTM trunc state to TRUNC_VALID with DBCC
SETTRUNC.
Explanation: Contact your System Administrator to address the Replication Server
LTM setting.
4215 21 %s failed in database %.*s: %ld not first log page in serially allocated log extent or
allocation page. Should be: %ld. Previous log record in scan: %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
4216 21 %s failed in database %.*s: unexpected end of log encountered on page %ld while
scanning for page %ld.
Explanation: Refer to the writeup for Error 4216.
4217 26 Failure during DUMP TRANSACTION in database `%S_DBID': caller does not possess
dump lock.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
937
4218 21 Failure during DUMP of database '%.*s': serial log page allocation rules broken .
Current page: %ld; next page: %ld; piece end: %ld; end-of-scan: %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
4219 21 DUMP TRANsaction encountered an unexpected end to the log page chain. Last page in
log as scanned: %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
4220 14 You must be the DBO of database %.*s or have Operator (OPER) role to run DUMP
TRANSACTION.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4221 16 DUMP TRANsaction to a dump device is not allowed where a truncate-only transaction
dump has been performed after the last DUMP DATABASE. Use DUMP DATABASE
instead.
Explanation: Refer to the writeup for Error 4221.
4222 16 DUMP TRANSACTION for database `%S_DBID' failed: log page (%ld) is on a data-
only segment. This is probably due to an incomplete move of the log to a device separate
from the data. Complete the log migration or contact the System Administrator.
Explanation: Refer to the writeup for Error 4222.
4223 18 Deadlock occurred in SQL Process %d.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
4224 16 An interruption occurred in process %d due to USER ATTENTION or connection
failure.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
4225 16 This database has not been dumped since it was created or upgraded. You must perform
a dump database before you can dump its transaction log.
Explanation: If this is a new database or one that was recently upgraded, it would be
invalid to attempt to dump the transaction log since there is no database dump. This error
is raised if you try to do dump transaction and no database dump exists. First dump the
database, then dump the transaction log.
4226 16 Logged DUMP TRANSACTION cannot run in database %.*s, because that databases's
log version (%d) disagrees with the SQL Server's log version (%d); use DUMP
TRANSACTION WITH NO_LOG. Versions will agree once ONLINE DATABASE has
run.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
Server Error Messages 4300 - 4399
938
Server Error Messages 4300 - 4399
4227 17 No space left in database master; creating user objects in master database not
recommended. Else, an old transaction may be active; see Syslogshold table.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4228 17 No space left in database `%S_DBID'; Use ALTER DATABASE to increase size of
database. Else, an old transaction may be active; see Syslogshold table.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4233 19 %s failed in database %.*s: Unable to find quiescent point in the log. Log backward scan
start marker (%d, %d) and end marker (%d, %d).
Explanation: Report the resource error to your System Administrator.
4234 21 %s failed on database %.*s: Unable to get the secondary truncation page %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
4235 20 %s failed in database %.*s: Bad quiescent point was found.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
4236 10 %s for database '%.*s' could not truncate the log. Either extend the log using ALTER
DATABASE ... LOG ON command or eliminate the oldest active transaction in database
'%. *s' shown in syslogshold table.
Explanation: Database maintenance operation failed. Take specified action.
4237 16 Cannot dump %s database’s log as distributed transaction resolution is not complete yet.
Please retry later.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
Number Severity Text and Explanation
4301 16 Database in use. A user with System Administrator (SA) role must have exclusive use
of DB to load transaction.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
CHAPTER 6 Adaptive Server Error Messages
939
4302 16 Specified file `%.*s' is not in valid dump transaction format.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4305 16 Specified file `%.*s' is out of sequence. Current time stamp is %S_DATE while dump
was from %S_DATE.
Explanation: Refer to the writeup for this error.
4306 16 There was activity on database since last load, unable to load. Must restart load sequence
with the load database to continue.
Explanation: If user transactions modify the transaction log between transaction dump
loads to a database, Error 4306 occurs and the load fails. Error 4306 would only occur if
someone ran the online database command for the database, someone did work in the
database, and then you tried to do a load transaction for the database. Begin again with
a load database or proceed to use the database without recovering all transactions.
4312 14 You must be the DBO of database %.*s or have Operator (OPER) role to run LOAD
TRANSACTION.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4313 16 Recreate index failed for table %ld, index %d. The table has been left in an inconsistent
state, and the index is missing, so LOAD TRANSACTION errors may result. Run DBCC
CHECKTABLE on the table if LOAD TRANSACTION succeeds.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4314 20 Cannot find table %ld to recreate index %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4315 20 Log scan for recreate index failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4316 16 Can only LOAD TRANsaction in master if SQL Server is in single-user mode.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4317 21 Could not read log page %ld for database `%*s'; the DBINFO structure for this database
is invalid, or the page chain is corrupt. Cannot proceed with LOAD TRANSACTION.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Server Error Messages 4300 - 4399
940
4318 21 Last log page `next free byte' value is out of range: %ld; should be no greater than %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
4319 21 Failed to patch the transaction log for database `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
4320 16 Dump or load commands require a logical dump device name from the sysdevices system
table. Use sp_addumpdevice to add `%.*s' to sysdevices.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4321 16 SQL Server can not load this transaction log dump because version information in the
dump does not match information in the database. Database: log version=%d, upgrade
version=%ld. Dump: log version=%d, upgrade version=%ld.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4322 16 SQL Server cannot load a dump of the master database that was dumped from an older
version of SQL Server. The current master database upgrade version is %ld, the dump
master database upgrade version is %ld.
Explanation: Refer to the writeup for this error.
4323 16 The specified RID (%d,%d) was not found in the transaction log.
Explanation: Check command parameters.
4324 20 The transaction log could not be opened for point in time recovery.
Explanation: Database log is not available for this maintenance operation.
4325 16 The specified recovery date (%S_DATE_LONG) is not between the start
(%S_DATE_LONG ) and end (%S_DATE_LONG) date.
Explanation: Check parameters for the point in time recovery command.
4327 10 A load transaction to a point in time will reset the transaction log sequence. A database
dump is required to restart the log sequence.
Explanation: This is an informational message.
4328 10 An early end-of-log has been forced in database ’%.*s’ prior to the end of the loaded
transaction log. The load sequence has been broken. Another LOAD TRANSACTION
cannot be performed without a preceding LOAD DATABASE.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
941
Server Error Messages 4400 - 4499
Number Severity Text and Explanation
4401 16 View `%.*s' no longer exists.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4402 16 Infinite loop in view definition. Cannot resolve the view definitions in the query to the
underlying tables.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4403 16 View `%.*s' is not updatable because it contains external aggregates , or group by clauses,
or internal aggregates . Internal aggregates may be generated by certain subqueries .
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4404 16 View `%.*s' is not updatable because either the view definition contains DISTINCT or
the view is built upon a view created with DISTINCT option.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4405 16 View `%.*s' is not updatable because the FROM clause names multiple tables.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4406 16 View `%.*s' is not updatable because a field of the view is derived or constant.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4408 19 The query and the views in it exceed the limit of %d tables.
Explanation: Command failed when a non-configurable limit was exceeded. Adaptive
Server could not recover gracefully. Reconnect to Adaptive Server, and report the error
to your System Administrator.
4409 20 The columns in the query definition and the view definition do not match.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4411 16 View `%.*s' does not allow this UPDATE because either it was created WITH CHECK
OPTION or it spans another view created WITH CHECK OPTION, and one of the update
columns appears in a multi-table expression in the WHERE clause of a CHECK OPTION
view.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Server Error Messages 4400 - 4499
942
4412 16 View `%.*s's definition contains `%.*s', which is a temporary object. Views can only be
based on permanent objects.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4413 16 View resolution could not succeed because the previously mentioned objects, upon
which the view directly or indirectly relies, do not currently exist. These objects need to
be recreated for the view to be usable.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4414 16 View `%.*s' does not allow INSERT because it is derived from more than one object and
it was either created WITH CHECK OPTION or it spans another view created WITH
CHECK OPTION.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4415 18 Internal system error: corrupt sequence tree encountered while processing the
DISTINCT view `%.*s'. Notify a user with System Administrator (SA) role.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
4416 19 Could not allocate a work table while processing views. The total number of work tables
generated by the query exceeds the limit (%d) of work tables. Simplify the query or the
views referenced in the query.
Explanation: Command failed when a non-configurable limit was exceeded. Adaptive
Server could not recover gracefully. Reconnect to Adaptive Server, and report the error
to your System Administrator.
4417 16 The view `%.*s' has one or more tables with any of the keywords
HOLDLOCK/NOHOLDLOCK that conflicts with the query to be run AT ISOLATION 0.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4418 16 Query has too many subqueries when all views are taken into account. Error found on
view `%.*s'. The limit is %d subqueries.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4420 16 View `%.*s' is not updatable, possibly due to an outer join being in the view, or due to a
subquery being in the select list of the view.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4422 16 View `%.*s' cannot be updated since no underlying tables are referenced.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
943
Server Error Messages 4500 - 4599
4423 16 View `%.*s' cannot be updated since view is the inner table of an outer join.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4424 16 View `%.*s' contains a table being updated, and this table is referenced elsewhere in the
query which is not allowed if create view WITH CHECK OPTION is used.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4425 16 View `%.*s' cannot have WITH CHECK OPTION applied since it contains subqueries.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4426 16 This query cannot be processed because it contains TEXT, IMAGE or off-row Java
columns and references a view defined with a subquery, an outer join, or a distinct clause.
Explanation: You cannot use view materialization for a query having TEXT/IMAGE
columns. View materialization needs to create a work table to store the result, and what
is copied to the work table is only the TEXT pointer. Forbiding queries that require view
materilization and select text columns from that view avoids stackstaces.
4427 16 View ’%.*s’ cannot be updated since the view definition contains a UNION operator.
Explanation: You cannot update view definitions that contain UNION.
Number Severity Text and Explanation
Number Severity Text and Explanation
4501 16 View `%.*s' has more columns defined than column names given.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4502 16 View `%.*s' has more column names specified than columns defined.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4503 20 The create view tree has a resdom with no right hand side. View `%.*s', resdom `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Server Error Messages 4600 - 4699
944
Server Error Messages 4600 - 4699
4504 16 CREATE TABLE failed because there was not enough space to allocate memory for the
table.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4505 16 CREATE VIEW failed because column ’%.*s’ in view ’%.*s’ exceeds the maximum of
%d columns.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4506 16 Column names in each view must be unique. Column name `%.*s' in view `%.*s' is
specified more than once.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
4507 16 Column `%.*s' specifies storage type %d, which does not currently exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4508 16 Views are not allowed on temporary tables. Table names that begin with `#' denote
temporary tables.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4509 10 Column names in each view must be unique. An unnamed column is specified more than
once in view `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
4601 14 This permission can only be GRANTed or REVOKEd by owner `%.*s' of object
`%S_OBJID', or by a user with GRANTable privileges in database `%S_DBID'
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
CHAPTER 6 Adaptive Server Error Messages
945
4602 14 Permission denied. Only users with System Administrator (SA) role can
GRANT/REVOKE CREATE DATABASE permission.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4603 14 Only owner of current database may GRANT/REVOKE this permission.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4604 16 There is no such user %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4605 25 Can't initiate update to sysprotects.
Explanation: Contact your System Administrator.
4606 16 GRANTed/REVOKEd privilege %s not compatible with object.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4607 16 Privilege %s may not be GRANTed or REVOKEd.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4608 16 Only users with System Administrator (SA) role can GRANT/REVOKE ALTER
DATABASE permission, and only to/from users with CREATE DATABASE permission.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4609 16 You cannot specify a column list with INSERT or DELETE.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4610 16 You may only GRANT or REVOKE permission on objects in the current database.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4611 16 The user `%.*s' has granted this privilege to other users. You must use REVOKE WITH
CASCADE to revoke privileges for `%.*s' as well as the other users.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
Number Severity Text and Explanation
Server Error Messages 4600 - 4699
946
4612 16 Too many users to revoke privileges from,due to cascading GRANT WITH GRANT. To
continue, use REVOKE WITH CASCADE on user `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4613 16 WITH GRANT OPTION does not apply to groups and roles.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4614 16 Column list may be specified either with the privileges or with the table. It cannot be
specified in both places.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4615 16 Permissions may not be revoked from either the DBO or the object owner.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4616 25 Public has been granted permission on the object with the grant option. Please revoke
the GRANT WITH GRANT option from public before revoking from any user/group.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4617 25 Public has GRANT WITH GRANT permission on at least one of the columns you are
trying to revoke. Please revoke the GRANT WITH GRANT option from public before
revoking from the users/groups.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4618 16 The user's curwrite must be at the security label of an object in order for that user to
grant/revoke access to that object.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4619 16 The user's curwrite must be at Data Low in order to grant/revoke create database
permission.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4620 16 The user must be in the master database in order to grant/revoke create database access.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
947
4621 16 Warning. All permissions except CREATE DATABASE are granted/revoked. Only
System Administrator can grant/revoke CREATE DATABASE permission.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
4622 10 Some or all of the specified privileges were not revoked because, they were not granted,
or they were granted by some other user.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
4623 18 Error encountered while retrieving column information. Aborting grant/revoke
command.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
4624 16 The user must be in the master database in order to grant/revoke connect access.
Explanation: Command failed. Check database context.
4625 16 The user must be in the master database in order to grant/revoke set session authorization
access.
Explanation: Command failed. Check database context.
4626 16 DBCC command ’%s’ cannot be assigned at the database-level.
Explanation: Command failed. Refer to the System Administration Guide for dbcc
usage.
4627 16 The user must be in the %.*s database to GRANT/REVOKE this command.
Explanation: Command failed.
4628 16 GRANT/REVOKE DBCC does not apply to groups or PUBLIC.
Explanation: Command failed. Refer to the Security Administration Guide for usage.
4629 16 DBCC command ’%s’ is a database-level command and ON <database | ALL> is
mandatory.
Explanation: Command failed. Refer to the System Administration Guide for dbcc
usage.
Number Severity Text and Explanation
Server Error Messages 4700 - 4799
948
Server Error Messages 4700 - 4799
Number Severity Text and Explanation
4701 11 Cannot truncate table `%.*s', because this table does not exist in database `%S_DBID'.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
4706 17 Could not truncate table `%.*s' because there is not enough room in the log to record the
deallocation of all of the index and data pages.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4708 16 Could not truncate object `%.*s' because it is not a table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4709 16 You are not allowed to truncate the system table `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4710 16 Cannot truncate table `%.*s' because you are not the owner or a user with System
Administrator (SA) role.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4711 14 Permission denied. @@curread does not dominate the maxhold of table `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4712 14 Permission denied. @@maxwrite does not dominate the maxhold of table `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4713 14 Permission denied. The minhold of table `%.*s' does not dominate @@minwrite.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4714 14 Permission denied. Only users possessing the SSO role can truncate the audit log.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4715 14 Permission denied. The hurdle of table `%.*s' does not equal @@curwrite.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
CHAPTER 6 Adaptive Server Error Messages
949
Server Error Messages 4800 - 4899
4716 16 Cannot truncate table `%.*s' because it is partitioned.
Explanation: Refer to the writeup for this error.
4717 16 Could not truncate table `%.*s' because there are referential constraints defined on it and
there are data rows in some of the referencing tables.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4718 17 Failed to write the TRUNCTAB log record for the execution of truncation of table '%.*s'
in database '%S_DBID'. The 'truncate table' command is aborted.
Explanation:
4719 20 TRUNCATE TABLE aborted due to an internal error. Failed to obtain the owner name
information associated with object ID %d in database '%S_DBID'. Please contact Sybase
Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
4720 16 Cannot truncate table '%.*s' because there are one or more isolation level 0 scans, or
REORG command, active on the table.
Explanation: Retry your command later.
Number Severity Text and Explanation
Number Severity Text and Explanation
4801 20 Bulk_main: opentable on BULK INSERT table failed. Dbid=%d name='%.*s'.
Explanation: The bulk copy command failed. Adaptive Server could not open the
specified table. Check command and target table.
4802 21 Bulk_main: getindex of primary index row failed on BULK INSERT table.
Explanation: There is a potential problem affecting the consistency of the system
catalog or the indexes on the table specified in the bcp command. Investigate with dbcc
checktable, checkcatalog and checkdb.
4804 21 Premature end-of-message while reading current row from host. Host program may have
died.
Explanation: The bcp activity could be incomplete. Although corruption is unlikely,
some rows in the target table for bcp may need to be cleaned up using delete/truncate table
command.
Server Error Messages 4800 - 4899
950
4805 17 The front end tool you are using does not support the feature of bulk insert from host,
please use the proper tools for this command.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4806 16 You cannot run the non-logged version of bulk copy in this database. Please check with
the DBO.
Explanation: Refer to the writeup for this error.
4808 10 The bulk copy of this table has been aborted because the CHECKPOINT record could not
be written in the log. Please free up space in the database.
Explanation: The bcp activity could be incomplete. Although corruption is unlikely,
some rows in the target table for bcp may need to be cleaned up using delete/truncate table
command. Restart the bcp job after cleanup.
4809 20 Unable to open SYSCOLUMNS in dbid %d to retrieve table schema information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4810 16 Expected TEXT token in data stream for bulk copy of text data.
Explanation: This error is seen when bulk copying in a table that has text/image
columns. Does not cause corruption but the bcp batch may be terminated.
4811 16 Expected column offset in data stream for bulk copy of text data.
Explanation: This error is seen when bulk copying in a table that has text/image
columns. Does not cause corruption but the bcp batch may be terminated.
4812 16 Expected row offset in data stream for bulk copy of text data.
Explanation: This error is seen when bulk copying in a table that has text/image
columns. Does not cause corruption but the bcp batch may be terminated.
4813 16 Expected text length in data stream for bulk copy of text data.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4814 20 Bulk_getschema: Unable to open the system catalog SYSCOLUMNS in database `%.*s'
while attempting to retrieve table schema information. Run DBCC CHECKTABLE on
sysobjects in `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4818 11 Error encountered while retrieving table schema information for object `%.*s' in database
`%.*s'. Re-check the schema for the table.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
951
4819 16 You cannot BCP into the sysaudits table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4820 16 Illegal identity value specified for identity column in table `%.*s' through BCP.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4821 16 Identity value overflow while inserting into table `%.*s' through BCP.
Explanation: This error is seen when bulk copying in a table that has an identity column.
Consider creating another table with a larger identity value range to load the data.
4822 14 You do not have the role required to run bcp in with the labelled option.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4823 16 Sensitivity label out of range for some row(s).
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4824 16 Invalid sensitivity label for some row(s).
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4825 16 Some row(s) not copied.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4826 16 Expected sensitivity label length in data stream for bulk copy of sensitivity label data.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4827 16 Expected row offset in data stream for bulk copy of sensitivity label data.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4828 16 Expected sensitivity label data in data stream for bulk copy of sensitivity label data.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4829 16 Attempt to copy in row sensitivity labels without using bulk copy labelled option. Labels
will be overwritten.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4830 16 The labelled option was specified, but row sensitivity labels were not passed in.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
Number Severity Text and Explanation
Server Error Messages 4800 - 4899
952
4831 16 Expected TEXT or SENSITIVITY token in data stream for bulk copy of text or sensitivity
label data.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4832 16 You cannot use a pre-10.0 client to bulk copy into a Secure SQL Server.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4833 16 Expected text data in data stream for bulk copy.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4834 17 Bulk copy failed due to insufficient SQL Server memory. Please retry later when there is
less load/users on the SQL server, or ask your System Administrator to reconfigure SQL
Server with more memory.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4835 18 Failed to update the identity pre-burn factor for table `%.*s' through BCP. Please re-try the
operation or contact your SA for details.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
4836 18 Error occurred while creating the identity value for table `%.*s' through BCP. Please re-
try the operation or contact your SA for details.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
4837 16 Bad row data received from the client while bulk copying into object %d in database %d.
Received a row of length %d while maximum possible row length is %d.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
4838 16 You cannot BCP into a view.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4839 18 Server has encountered badly formatted rows from bulk copy. Could not locate the row
position reserved for the insertion of the identity value.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4840 16 Bulk copy failed. You cannot specify a partition ID when doing BCP into table '%. *s'
because it has a clustered index.
Explanation: Check command parameters and retry.
4841 16 Bulk copy failed. Partition number %d does not exist in table '%.*s'.
Explanation: Check command parameters and retry.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
953
Server Error Messages 4900 - 4999
4842 16 Bulk copy failed. Partition number %d was specified for table '%.*s', but that table is not
partitioned.
Explanation: Check command parameters and table, and retry.
4843 10 Slow bulk copy is being used because table '%.*s' has triggers or indexes.
Explanation: This is an informational message. Bulk copy may take an extended period.
4844 16 Bulk copy failed. Identity start value %S_NUME was specified for table '%.*s', but that
table does not have an identity column.
Explanation: Check command parameters and table,and retry.
4845 16 Bulk copy failed. Client does not have the capability to bulk copy into the data- only locked
table '%.*s'.
Explanation: Check Adaptive Server and client environment, setup.
4846 20 Bulk copy failed. Error occurred while updating the last page of the table.
Explanation: Error in bulk copy affected current process. Contact System Administrator.
4847 16 BCP insert operation is disabled when LONGCHAR capability is turned on and data size
is changing between client and server character sets since BCP does not support
LONGCHAR yet.
Explanation: Illegal command.
Number Severity Text and Explanation
Number Severity Text and Explanation
4901 16 ALTER TABLE only allows columns to be added which can contain nulls. Column `%.*s'
cannot be added to table `%.*s' because it does not allow nulls.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4902 11 Cannot alter table `%.*s', because this table does not exist in database `%S_DBID'.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
4905 21 ALTER TABLE failed because page %ld of the system catalog sysindexes in database
`%.*s' is not in the cache.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
Server Error Messages 4900 - 4999
954
4909 16 Can't alter %.*s because it is not a table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4910 16 Cannot alter table `%.*s' because you are not the owner or a user with System
Administrator (SA) role.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4912 16 Cannot replace default to `%.*s.%.*s' because it already has a default bound using
sp_bindefault.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4913 16 Alter table command has unrecognized action. Cannot process.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4914 16 Cannot alter table `%.*s' because the alter table statement contains multiple identity fields.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4915 16 Cannot add new identity field to `%.*s' via alter table because the table already contains
an identity field.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4916 16 Cannot add new identity field to `%.*s' via alter table because the number of existing rows
(%ld) exceeds the maximum value for the specified precision (%d).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4917 20 Failure adding identity column `%.*s' to table `%.*s'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4918 16 Row length (%d) exceeds maximum row length (%d) when adding identity column
’%.*s’ to table ’%.*s’.
Explanation: Command failed due to invalid or illegal request. A server limit was
exceeded.
4919 16 Identity value overflow when adding column `%.*s' to table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
955
4920 16 Permission denied. A table can only be altered if the table's hurdle equals the user's
curwrite.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
4921 14 Permission denied. A table's labels cannot be altered while it is in use.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4922 14 Invalid hold label specified.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4923 14 Permission denied. A table's maxhold should always dominate its minhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4924 14 Permission denied. A table's maxhold should always be dominated by the maxhold of the
database that contains it.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4925 14 Permission denied. User maxwrite does not dominate specified maxhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4926 14 Permission denied. User minhold does not dominate specified minwrite.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4927 14 Permission denied. Maxhold label specified is below previous table maxhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4928 14 Permission denied. Minhold label specified is above previous table minhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4929 14 Permission denied. User minwrite is not dominated by specified maxhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4930 14 Permission denied. User maxwrite does not dominate specified minhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
4931 16 Cannot alter the table ’%.*s’ because it is a system table.
Explanation: Error raised if user attempts to add columns to a system table when allow
updates is off.
Number Severity Text and Explanation
Server Error Messages 4900 - 4999
956
4932 16 Dropping a column from a system table is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4933 16 Dropping a column from a replicated table is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4934 16 A column by this name doesn't exist in the table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4935 16 Dropping the only column in a table is not allowed.
Explanation: Command failed due to invalid or illegal request.
4936 17 Dropping the column failed while reformatting data on page %d, row %d. This command
is being rolled back.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4937 17 Deleting text pages failed. This command is being rolled back.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4938 20 Cannot undo a drop column command because the number of rows on the log record does
not match the number of rows on the data page.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4939 16 ALTER TABLE ’%.*s’ failed. You cannot drop column ’%.*s’ because it is being used by
an index. Drop the index ’%.*s’ before dropping this column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4940 16 ALTER TABLE failed. Dropping an identity column is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4941 16 ALTER TABLE ’%.*s’ failed. You cannot drop a column on which constraints are defined.
Drop the constraints before dropping this column.
Explanation: Command failed due to invalid or illegal request. Use sp_helpconstraint
for information on the object.
4942 16 ALTER TABLE ’%.*s’ failed. You cannot drop column ’%.*s’ which has a default bound
to it. Unbind the default (object id ’%ld’) before dropping this column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
957
4943 16 Dropping a column which is a primary key is not allowed. Drop the constraint (object id
`%ld') before dropping this column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4944 16 Dropping a column which is a foreign key is not allowed. Drop the constraint (object id
`%s') before dropping this column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4945 16 Cannot drop the column because cursor `%.*s' is still open. Close the cursor(s) before
dropping the column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4946 16 Dropping a column from a table which has a constraint associated with it is not allowed.
Drop the constraint (object id `%ld') before dropping this column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4947 16 Dropping an identity column from a table while identity_insert is `on' is not allowed. Set
identity_insert to `off' before dropping this column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4948 25 Dropping the column failed while logging data from page %d. This command is being
rolled back.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4949 20 The alttab_begin() function is trying to put too many lock requests in the lock_requests[]
array.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
4950 16 Cannot partition table `%.*s' because it is a system table.
Explanation: The partition clause of the alter table command allows you to partition
user tables that do not have a clustered index. Partitioning is not allowed for system tables.
4951 16 Cannot create %d partitions on the table '%.*s' with clustered index because the maximum
number of partitions allowed on a table with clustered index is %d.
Explanation: Refer to the writeup for this error.
4953 16 Cannot partition table `%.*s' because it is already partitioned.
Explanation: Refer to the writeup for this error.
4954 16 Cannot unpartition table `%.*s' because it is not partitioned.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
Server Error Messages 4900 - 4999
958
4955 16 Number of partitions must be greater than one
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4956 16 Cannot alter table if REORG command or level 0 scans are active.
Explanation: Refer to the writeup for this error.
4958 16 Cannot partition table `%.*s' because it is in a pre-System 11 database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4959 16 Dropping a TEXT/IMAGE column is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4960 16 Lock scheme currently on the table `%.*s' is corrupted. For this version of SQL server it
should have been set properly.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
4961 16 Cannot partition table '%.*s' because it has been partitioned and unpartitioned too many
times.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
4962 16 To partition: bcp the data out of the table, drop and recreate the table, and then bcp into a
partitioned/unpartitioned table.
Explanation: Follow the steps in the message to partitioned a table.
4963 16 Table '%.*s' is already locked in the desired locking scheme.
Explanation: This is an informational message. The command did not execute.
4964 17 Lock scheme conversion failed due to insufficient SQL Server memory. Please retry later
when there is less load/users on the SQL server, or ask your System Administrator to
reconfigure SQL Server with more memory.
Explanation: See the writeup for Error 4964.
4965 16 Lock scheme conversion on system tables not supported.
Explanation: You can only change lock schemes on a user table.
4966 10 Warning: Table '%.*s' with a clustered index has been partitioned. All data rows are in the
first partition and all data insertions will go to the first partition. To distribute the data to
all the partitions, re-create the clustered index.
Explanation: The table is partitioned but will not stay balanced unless you take the
specified action.
4967 16 Cannot execute '%.*s' command on table '%.*s', because this table does not exist in
database '%S_DBID'.
Explanation: Check syntax and working database.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
959
4968 16 The table '%.*s' you've specified is a system table. Executing the '%.*s' command is not
permitted on system tables.
Explanation: Invalid command.
4969 16 The table '%.*s' you've specified is a temporary table. Executing the '%.*s' command is not
permitted on temporary tables.
Explanation: Invalid command.
4970 16 Cannot unlock this table because the table is not locked in that mode.
Explanation: Invalid command.
4971 16 This table cannot be locked in '%.*s' mode because it was already locked in '%.*s ' mode.
Explanation: Invalid command.
4972 10 Warning: Empty Table '%.*s' with a clustered index has been partitioned. All data
insertions will go to the first partition. To distribute the data to all the partitions, re-create
the clustered index after loading the data.
Explanation: Table is partitioned but will become unbalanced with future inserts. Take
the recommended action to maintain partition balance.
4973 20 Row size (%d bytes) exceeded the maximum row size limit (%d bytes) for data only locked
format while changing the lock scheme from ALLPAGES to DATAONLY for object
’%.*s’ (ID %d) in database ’%.*s’ (ID %d). The lock scheme for the object was not
changed.
Explanation: Consult the System Administration Guide for more information.
4974 21 Process %d was expected to hold logical lock on object %ld.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator.
4975 16 Cannot alter table for lockscheme change because cursor '%.*s' is still open. Close the
cursor(s) before lockscheme change.
Explanation: Wait for the process holding the cursor to complete.
4977 16 You cannot run ALTER TABLE LOCK in this database because the 'select into/bulkcopy'
option is off. Please check with the DBO.
Explanation: Invalid or illegal command.
4978 16 User aborted ALTER TABLE LOCK change command for table %.*s
Explanation: DDL command aborted.
4979 20 ALTER TABLE LOCK change for table '%.*s' failed: insufficient memory to allocate
backout structure.
Explanation: Retry the DDL command when there is more memory available for the
task.
4980 17 No space left in database '%S_DBID'; Use ALTER DATABASE to increase size of
database. Else, an old transaction may be active; see Syslogshold table.
Explanation: Check the syslogshold table for long-running transactions.
Number Severity Text and Explanation
Server Error Messages 4900 - 4999
960
4981 16 Column offset, %d bytes, for variable-length column number %d exceeds the maximum
start offset for variable-length columns in DOL tables (%d bytes). The lock scheme for the
object ’%.*s’ was not changed.
Explanation: To change the lock scheme, bulk copy the table out, drop and re-create the
table with the new scheme, and bulk copy data back in.
4982 10 Due to an internal error the table '%.*s' cannot be converted to new lock scheme. Please
contact your System Administrator (SA) for help
Explanation: An Adaptive Server error occurred. Notify the System Administrator.
4983 10 Primary index (indid = %d) is suspect for table '%.*s'. Please check and reissue the lock
change command.
Explanation: Check the index and table using dbcc. You may need to recreate the index.
4984 10 Computed effective expected row size value(%d) for the table '%.*s' with the expected row
size value(%d) is invalid. Forcing the default value.
Explanation: This is an informational message.
4985 10 Warning: trigger ’%.*s’ is already enabled.
Explanation: This is an informational message.
4986 10 Warning: trigger ’%.*s’ is already disabled.
Explanation: This is an informational message.
4987 10 Enabling trigger ’%.*s’.
Explanation: This is an informational message.
4988 10 Disabling trigger ’%.*s’.
Explanation: This is an informational message.
4989 16 The trigger you specified (’%.*s’) does not exist. The ALTER TABLE command is being
terminated.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
4990 17 ALTER TABLE ’%.*s’ failed due to insufficient procedure cache. Retry later when there
is less load/users on Adaptive Server, or ask your System Administrator to reconfigure
Adaptive Server with more procedure cache.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4991 17 ALTER TABLE ’%S_OBJID’ in database %S_DBID (objectid %d) failed due to
an internal error. Please contact Sybase Technical Support.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4993 16 ALTER TABLE ’%.*s’ failed. Dropping all columns in a table is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
961
4994 16 ALTER TABLE ’%.*s’ failed. The number of columns in the resultant table (%d) exceeds
the current limit %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
4995 16 ALTER TABLE ’%.*s’ failed. Multiple references to the same column in ALTER TABLE
statements are not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
4996 16 ALTER TABLE ’%.*s’ failed. Adding non-NULL timestamp column ’%.*s’ is not
allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
4997 16 ALTER TABLE ’%.*s’ failed. Default clause is required in order to add non-NULL
column ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
4998 16 ALTER TABLE ’%.*s’ failed. Default value cannot be NULL when adding a non-NULL
column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
4999 16 ALTER TABLE ’%.*s’ failed. You cannot drop column ’%.*s’ on which a primary or
foreign key constraint is defined.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 5000 - 5099
962
Server Error Messages 5000 - 5099
Number Severity Text and Explanation
5001 16 User must be in Master Database.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
5002 16 Database %.*s does not exist; check sysdatabases.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5004 16 ALTER DATABASE failed. The size value is invalid.
Explanation: Command failed due to invalid or illegal request. Specify a positive (and
minimum allowed) value for the size parameter of the alter database command.
5005 10 Extending database by %ld pages (%d.%d megabytes) on disk %.*s
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5006 16 Could not find enough space on disks to extend database %.*s.
Explanation: Refer to the writeup for this error.
5008 16 System does not support Deextend Database currently.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5009 16 ALTER DATABASE failed. Some disk names listed in command were not found. Check
that names exist and are spelled correctly before re-running command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5011 14 Only the owner of database %.*s or a user with System Administrator (SA) role can
ALTER it.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5013 16 Cannot extend the MASTER database onto any device other than `master'. The ALTER
DATABASE was aborted.
Explanation: Refer to the writeup for this error.
5015 16 CREATE or ALTER DATABASE failed. The size specified must be %d megabyte(s) or
greater.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
963
5016 10 ALTER DATABASE failed. The Model database may not be larger than the Temporary
database. Alter tempdb first.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5017 16 ALTER DATABASE failed. Database %.*s not created with `for load' option.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5018 10 Caution: You have set up this database to include space on disk %d for both data and the
transaction log. This can make recovery impossible if that disk fails.
Explanation: This is an informational message. Keeping data and log separate is
recommended.
5020 14 Permission denied. @@curwrite has to be set equal to the database's hurdle in order for
the alter to proceed.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5021 14 Too many dbmaxhold specifications made.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5022 16 Invalid dbmaxhold provided.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5023 14 Permission denied. The database maxhold you specified does not dominate your
minwrite.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5024 14 Permission denied. The database maxhold you specified is not dominated by your
maxwrite.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5025 14 Permission denied. The database maxhold you specified does not dominate the current
database maxhold.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5026 10 Updating database maxhold.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 5000 - 5099
964
5028 16 ALTER DATABASE failed. This command will not make changes to a database that
would cause the number of device fragments to exceed the maximum of 128. Recreate the
database and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5029 16 ALTER DATABASE failed. Log space in master database has reached the last chance
threshold. Please free-up log space in master database and try again.
Explanation: This is a serious condition. Refer to “Managing Free Space With
Thresholds” in the System Administration Guide for immediate corrective action.
5030 16 The database %S_DBID is in the middle of a load sequence. Altering it will not let you
load other transaction dumps in the dump-set. If you still prefer to do it please use
OVERRIDE option.
Explanation: Retry the command after completing the load sequence.
5031 10 Database %S_DBID which is currently offline has been altered from size %d pages to %d
pages.
Explanation: This is an informational message.
5032 10 Alter database on '%S_DBID' broke the load sequence for that database.
Explanation: The alter command was executed in the middle of a transaction load
sequence.
5033 16 Attempt to alter database '%S_DBID' failed because it is in read-only mode.
Explanation: Determine why the query attempted to alter a read-only database. See the
writeup for Error 3906.
5036 16 ALTER DATABASE failed either because the database is failed over or system proxy
databases are enabled on the server in failed over mode.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5037 17 ALTER DATABASE for database ’%S_DBID’ was unsuccessful; it failed to update log
space values in internal persistent data structure.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
5038 10 Warning: Using ALTER DATABASE to extend the log segment will cause user
thresholds on the log segment within 128 pages of the last chance threshold to be disabled.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
965
Server Error Messages 5100 - 5199
Number Severity Text and Explanation
5101 15 Must give parameters for `DISK %s' command. Usage: %s.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
5102 15 No such command: `DISK %.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
5103 16 Illegal disk address range. The sum of VSTART and SIZE must be less than 16777216
(0x1000000).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5104 16 Device number %d already used.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5105 16 Device activation error. PHYSNAME `%.*s' may be incorrect.
Explanation: Check the physical device name.
5106 15 Parameter `%s' requires value of type `%s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
5107 15 Value is wrong type for parameter `%s' (requires type `%s').
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
5108 15 Parameter `%s' does not take a value.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
5109 16 No such parameter: `%.*s'.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5114 20 Could not yield.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator. (Not raised in Release 11.0 and
higher.)
Server Error Messages 5100 - 5199
966
5115 16 I/O error during disk initialization. PHYSNAME `%.*s' may be incorrect or %ld
(VSTART + SIZE) may exceed the size of the device. Please consult the SQL Server
error log for more details.
Explanation: Refer to the writeup for this error.
5116 14 Permission denied. Only users with System Administrator (SA) role can run DISK
commands.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5117 16 Unable to run DISK command. Must be in master database to run this command.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5118 16 Unable to run DISK REFIT. SQL Server must be booted with the -m option. Please see
your System Administration guide about the Restore Master procedure.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5119 18 Unable to reserve a buffer, aborting DISK REFIT command. Please retry Restore Master
procedure.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
5120 10 Bad segment map (%d) in sysusages for row with Dbid = %d, Logical Start = 0x%lx,
Virtual Start = 0x%lx, and Size = 0x%lx. Recommend you patch this value with correct
information after Disk Refit completes.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
5121 10 Warning: Disk Refit may not have the correct segment map information in sysusages.
Please review these after the command completes to verify their accuracy.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5122 10 The disk size must be >= %d device pages (%d MB).
Explanation: Check query parameters and retry.
5123 16 DISK INIT encountered an error while attempting to open/create the physical file. Please
consult the SQL Server error log (in the SQL Server boot directory) for more details.
Explanation: Refer to the writeup for this error.
5124 10 Activating disk ’%.*s’ of size %ld bytes.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5125 10 Failed to complete unmirror of logical device `%.*s' after recovery of the master
database.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
967
5126 16 The logical device `%.*s' does not exist in SYSDEVICES.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5127 16 The device `%.*s' is already mirrored and mirroring is enabled.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5128 16 The device `%.*s' is already mirrored but mirroring is disabled. Use the DISK
REMIRROR command to enable mirroring or unmirror the device.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5129 16 Syntax error detected in the value for parameter `mirror'. You must provide a valid
physical device/file name for this parameter.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5130 16 The value for parameter `mirror' translates to the same name as that for the primary
device. Use another physical device for the mirror.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5131 16 The device `%.*s' is not currently mirrored.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5132 10 DISK MIRROR encountered an error while attempting to create the physical file `%.*s'.
Please consult the SQL Server error log for more details.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5133 10 Unable to start i/o to `%.*s'. Please consult the SQL Server error log for details.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5134 10 Dynamic mirroring failed for logical device `%.*s'. Check the SQL Server error log for
more information.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5135 10 Starting Dynamic Mirroring of %ld pages for logical device `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5136 10 %*.d pages mirrored...
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 5100 - 5199
968
5137 10 Failed to mirror device `%.*s'.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5138 10 Failed to unmirror device `%.*s'.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5139 10 Failed to remirror device `%.*s'.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
5140 10 Creating the physical file for the mirror...
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5141 17 Unable to start Dynamic Mirroring because an i/o buffer is not currently available. Try
the command again later.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
5142 16 Mirroring for device `%.*s' is not currently enabled.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
5143 10 The remaining %ld pages are currently unallocated and will be mirrored as they are
allocated.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5144 16 You can't remove the secondary physical device for virtual device `%.*s' since it is
currently the only operational device. Use the SIDE=PRIMARY qualifier for the DISK
UNMIRROR COMMAND.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
5145 16 Error re-initializing device `%.*s'. Check SQL Server errorlog for more information.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5146 16 The VDEVNO of %ld is out of range. The maximum VDEVNO allowed is %ld.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5147 10 Device size set to %ld blocks.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
969
5148 16 Device `%.*s' already exists.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5149 16 You cannot remove the primary physical device for virtual device `%.*s' since it is
currently the only operational device. Use the SIDE=SECONDARY qualifier for the
DISK UNMIRROR COMMAND.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5150 16 DISK UNMIRROR cannot be performed, because database `%S_DBID' is currently
undergoing DUMP or LOAD. Either wait for that command to complete, or abort it.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5151 16 PHYSNAME `%.*s' is already in use.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
5152 16 DISK REFIT failed. Either the database is corrupted or the value of the VSTART
parameter supplied to DISK INIT and DISK REINIT were different.
Explanation: Check that the VDISK parameter supplied to DISK REINIT is consistent
with that supplied to DISK INIT.
5153 16 Device '%.*s' cannot be released since it is in use by database id '%S_DBID'. Drop that
database and retry.
Explanation: Illegal command. Check device before retrying.
5154 16 Device '%.*s' is not a valid database device.
Explanation: Check command syntax.
5155 16 The command 'DISK %s' cannot be executed since disk mirroring has been disabled. In
order to enable disk mirroring, use: sp_configure 'disable disk mirroring',0 and restart the
server.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5156 16 DISK INIT failed. All disks are either in use or reserved for failover of companion server
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5157 16 Disk refit command is not allowed within the failed over mode of the companion server
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5158 16 DISK INIT of ’%.*s’ failed because this name is reserved for failed over device.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
Number Severity Text and Explanation
Server Error Messages 5100 - 5199
970
5159 16 Only the master database can be recovered when attempting to use the DISK REFIT
command. Restart the server using trace flag 3608.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5160 16 Arithmetic overflow error for parameter ’%s’.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5161 16 There are no available device numbers. ASE allows a maximum of %d devices and all
the device numbers upto the maximum have been used.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5162 16 There are no available device numbers in the range 0 and the value of configuration
parameter ’number of devices’ %d. Please reconfigure ’number of devices’ to a
larger value and retry disk initialization.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5163 16 Disk initialization for logical device ’%.*s’ failed as a virtual disk descriptor could not
be allocated, possibly due to shortage of memory.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5164 10 Initializing %ld pages only; insufficient disk space.
Explanation: The operation was partially successful; it could not initialize the requested
number of pages.
5165 16 DISK RESIZE can proceed only when mirroring is permanently disabled. UNMIRROR
%S_MSG with mode = ’REMOVE’ and reexecute command.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
5166 16 DISK RESIZE encountered an error while attempting to open/resize the physical file
’%s’. Please consult the SQL Server error log (in the SQL Server boot directory) for
more details.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
971
Server Error Messages 5200 - 5299
Number Severity Text and Explanation
5201 26 Failure concurrent with dump in database %d: DFL Manager caller must be DUMP
DATABASE; instead, command token was %d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5202 26 DUMP DATABASE for database %d failed: DFL synchronisation is prematurely set.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5203 17 DUMP DATABASE for database %d failed: insufficient memory to allocate DFL.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
5204 26 DUMP DATABASE for database %d failed: initial DFL allocation will not fit in initial
memory block.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5205 26 DUMP DATABASE for database %d failed: duplicate dflheader found.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5206 26 DUMP DATABASE for database %d failed: dump flushlist structures have not been
allocated.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5207 26 DUMP DATABASE for database %d failed: DFL synchronisation is not set.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5208 10 User aborted DUMP DATABASE for database %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5209 26 Failure during concurrent dump in database %d: DFL Manager caller must not be
DUMP DATABASE, but is.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5210 26 Failure during dump in database %d: caller does not possess dump lock.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Server Error Messages 5600 - 5699
972
Server Error Messages 5600 - 5699
5211 26 Failure concurrent with dump in database %d: caller does not possess flushlist lock.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5212 26 Failure concurrent with dump in database %d: no DFL pieces on not-full list.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5213 26 Failure concurrent with dump in database %d: caller improperly holds flushlist lock.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5214 20 During DUMP DATABASE for database %d, flushlist closure not complete at end of
synchronisation.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
5215 26 DUMP DATABASE for database %d failed: could not find dflinfohead to deallocate.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5216 26 DUMP DATABASE for database %d failed: trailing piece in not-full list proved not-
empty.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5217 20 DFL Manager failed to sleep.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
5600 20 Adaptive Server internal error: Did not expect to find distributed transaction participant
descriptor for local participant.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
CHAPTER 6 Adaptive Server Error Messages
973
5601 20 Adaptive Server internal error: invalid input %d to internal functions.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
5602 17 Could not find an available distributed transaction participant descriptor. Retry later, or
please contact a user with System Administrator (SA) role to reconfigure your system for
more descriptors.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
5603 16 Adaptive Server cannot accept distributed transactions as transaction coordinator is not
enabled. Please contact a user with System Administrator (SA) role.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
5604 16 Adaptive Server internal error: Cannot register a remote distributed transaction
participant when process is not within a transaction.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
5605 16 %s RPC to the remote server ’%S_SRVID’ failed. Transaction key ’%.*s’. Return status
%d.
Explanation: Failure in Remote Procedure Call (RPC). Check syntax. Check sending
and receiving Adaptive Server environments for remote access.
5606 20 Adaptive Server internal error: Transaction coordinator setup failed during alarm
initialization.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5607 16 Could not reserve log space in sybsystemdb database. Retry your transaction later, or
please contact a user with System Administrator role.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
5608 16 The remote server ’%S_SRVID’ does not support distributed transactions.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
5609 16 The sybsystemdb database is not available.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
5610 16 The syscoordinations table in sybsystemdb database is not available.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
Server Error Messages 5600 - 5699
974
5611 21 Adaptive Server internal error: distributed transaction recovery boot count error.
Transaction boot count is %d, Server current boot count is %d.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
5612 16 System database %s is not allowed to participate in a distributed transaction.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
5613 20 Adaptive Server internal error: Could not release distributed transaction participant
descriptor to the free pool.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5614 16 Cannot start a remote distributed transaction participant on server ’%d’ as server does not
does not exist. Please contact a user with System Administrator role.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
5615 21 Adaptive Server internal error: ASTC task state %d is incorrect.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
5616 20 Adaptive Server internal error: invalid distributed transaction participant work identifier
%d for participant %d. Transaction key ’%.*s’.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5617 17 Adaptive Server internal error. Could not change engine affinity.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
5618 21 Adaptive Server internal error. Could not resolve distributed transaction states where
system database ’%s’ was a participant.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
5619 21 Adaptive Server internal error. Could not obtain count of in-doubt transactions for space
reservation.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
5620 21 Adaptive Server internal error. Could not reserve space for in-doubt transactions.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
975
5621 16 You cannot start non-transactional work on the remote server. ’enable xact coordination’
is off and the task enabled ’strict dtm enforcment’, which requires transactional work.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
5622 21 Adaptive Server Internal Error. Cannot allocate memory for transaction coordinator
processes.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
5623 21 Adaptive Server Internal Error: Cannot start transaction coordinator process.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
5624 20 Adaptive Server Internal Error: transaction coordinator protocol mismatch error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5625 20 Adaptive Server Internal Error: transaction coordinator was passed an invalid transaction
identifier length of ’%d’.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5626 17 Cannot allocate a gtrid object descriptor. Retry later, or a user with System Administrator
(SA) role to reconfigure your system for more total memory.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
5627 20 Adaptive Server Internal Error: Cannot release gtrid object descriptor to the free pool.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5628 20 Adaptive Server Internal Error: A distributed transaction descriptor was found in the
wrong state. state %d, status %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5629 16 Cannot start a remote distributed transaction participant as the local server is not named.
Please contact a user with System Administrator role.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
5630 16 Transactional connection to remote server ’%S_SRVID’ has been invalidated. Aborting
the distributed transaction. Transaction key ’%.*s.
Explanation: Adaptive Server could not perform the requested action. Check DTM
documentation for assistance.
Number Severity Text and Explanation
Server Error Messages 5700 - 5799
976
Server Error Messages 5700 - 5799
5631 16 Adaptive Server Internal Error. New transactional connection to server
’%S_SRVID’ is being passed while there is an existing transactional connection
to the same server in the same transaction. Aborting the distributed transaction.
Transaction key ’%.*s.
Explanation: Check error log and report the error to the System Administrator.
5632 16 This operation is invalid when the run value of configuration parameter ’enable xact
coordination’ is on. Please retry after disabling this configuration parameter.
Explanation: Adaptive Server could not perform the requested action.
Number Severity Text and Explanation
Number Severity Text and Explanation
5701 10 Changed database context to `%.*s'.
Explanation: Refer to the writeup for this error.
5702 10 The SQL Server is terminating this process.
Explanation: This informational message appears in conjunction with other errors such
as 813, 8211, or stack traces. Error 5702 indicates that Adaptive Server is terminating the
client process since the accompanying error was fatal. Check for and resolve the errors
raised in conjunction with the 5702 error. Check the Adaptive Server error log if the other
errors were not displayed on your screen.
5703 10 Changed language setting to `%.*s'.
Explanation: Adaptive Server sends this informational message to a DB-Library or CT-
Library client when the client logs in (the message displays the default language), and
when the client changes the current language. If you wish to suppress this message, add the
following line to your client's Adaptive Server message handler: if (msgno==5703) return
(0); This message cannot be suppressed on the Server side; it must be handled on the client
side.
5704 10 Changed client character set setting to `%.*s'.
Explanation: Refer to the writeup for this error.
CHAPTER 6 Adaptive Server Error Messages
977
Server Error Messages 5800 - 5899
Number Severity Text and Explanation
5803 10 Unknown config number in sysconfigures, config = %d.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
5804 16 The value for `%s' must not exceed `%s' or `%s'.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5805 16 Warning: The next configuration change will overwrite `%s'. To avoid this rename,
move, or delete old configuration files. See System Administration Guide for details.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5806 16 Warning: The file `%s' has been overwritten. To prevent this rename, move, or delete old
configuration files. See System Administration Guide for details.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5807 10 Invalid memory move request encountered for the ’%dK’ pool in cache ’%s’. Move
should equal at least 1 buffer of size ’%dK’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5808 10 WARNING: Dynamic loading of caches and pools through loading a new file are not
supported. However, the loadfile `%s' will be inspected for consistency. Refer to
`sp_cacheconfig' and `sp_poolconfig' to create or alter pools and caches.
Explanation: Refer to the writeup for this error.
5809 16 Less memory moved than requested in cache %s cache. Requested size = %d kb from
pool %d, actual memory moved = %d kb.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5810 16 new (%d) buffer pool of size %d for cache %s is being created
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5811 16 The new load file does not have the cache %s definition. Cache type, size and number of
caches should match the running values. Use sp_cacheconfig to determine the running
value
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
Server Error Messages 5800 - 5899
978
5812 16 The new load file has %d caches defined against running %d cache definitions.Cache
type, size and number of caches should match the running values. Use sp_cacheconfig to
determine the running value.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5813 16 The new load file has duplicate %s cache definitions, caches should be uniqueue.
Explanation: Refer to the writeup for this error.
5814 16 Must configure with at least %d engine on-line.
Explanation: Check the System Administration Guide for information about online
engines.
5816 16 Legal values for the number of remote logins are 0 or positive numbers.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5817 16 Legal values for the number of remote sites are 0 or positive numbers.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5818 16 Legal values for the number of remote connections are 0 or positive numbers.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5819 16 Legal values for the number of pre-read packets per remote connection are 0 or positive
numbers.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5820 16 Number of remote logins should be greater than the number of remote sites.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5821 16 Number of remote connections should be greater than the number of remote sites.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5822 16 Version number should be between 0 and 10000.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5824 16 Cannot reconfigure server to use sort order ID %d, because the row for its underlying
character set (ID %d) does not exist in syscharsets.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5825 16 Cannot reconfigure the server's sort order since the syscharsets table does not exist. You
must upgrade your server prior to attempting this.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
979
5826 10 You have just reconfigured SQL Server's default sort order. System table indexes will be
rebuilt when you reboot the SQL server.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5827 10 In changing the default sort order, you have also reconfigured SQL Server's default
character set.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5828 16 Legal values for number of user connections are 1 through %d.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5829 16 Do not recommend more than %d engines on-line. Use override option to force this
option.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5830 16 Must configure with at least %d engine(s) on-line.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5831 16 Cannot reconfigure the server's character set with out of bounds character set ID %d.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5832 10 The stack size must be a multiple of the page size. It has been rounded from %d to %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5833 16 Cannot reconfigure the server with an out-of-bound, illegal value for Systemwide
Password Expiration Interval.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5835 16 Cannot reconfigure the server with an out-of-range audit queue size. The valid range is
%d to %d inclusive.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5836 10 The additional network memory size must be a multiple of 2048 bytes. It has been
rounded down from %d to %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required.
5837 10 The default network packet size must be a multiple of 512. It has been rounded down
from %d to %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 5800 - 5899
980
5838 10 The maximum network packet size must be a multiple of 512. It has been rounded down
from %d to %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5839 16 The value of `max network packet size', `%ld', must be greater than or equal to the value
of the `default network packet size', `%ld'.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5840 16 Illegal value (%ld) specified for the number of large extents.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5841 16 Cannot reconfigure the server's sort order with an out of bounds sort order set ID %d.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5842 16 Number of cleanup blocks should be at least as great as the number of users. The number
of users currently configured is %d.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5843 16 Invalid Configuration: Cache alignment `%ld' is invalid. Alignment must be a power of
2 greater than or equal to 2048. Retry the command with a legal value.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5844 16 Cannot reconfigure the auto identity column size to be %d because the minimum
precision of a numeric is 1.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5845 16 Invalid value configured for lock promotion threshold = %d. Configured value must be
greater than or equal to %d.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5846 16 Illegal value `%ld' specified for configuration option `%s'. The legal values are between
`%ld' and `%ld'.
Explanation: Refer to the writeup for this error.
5847 16 Configuration Error: Configuration file `%s' does not exist or you do not have the
required read/write permission for the file.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5848 16 Warning: Unknown parameter `%s' found on line `%ld' of configuration file `%s'. This
parameter is ignored. Edit the configuration file to remove or correct this parameter.
Explanation: Refer to the writeup for this error.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
981
5849 16 Verification failed for parameter `%s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5850 16 Notification failed for parameter `%s'.
Explanation: Refer to the writeup for this error.
5851 16 Configuration Error: Configuration file `%s' has an unknown format on line %d.
Explanation: Refer to the writeup for this error.
5852 16 Changing the value of `%s' is not allowed since it is a static option.
Explanation: Refer to the writeup for this error.
5853 19 `%s' has been modified from `%ld' to `%ld' by the verification routine.
Explanation: Refer to the writeup for this error.
5854 18 Configuration Error: Cannot %s file ’%s’ due to system error ’%s’ (status = %d).
Explanation: Refer to the writeup for this error.
5855 16 Cannot change any of the configuration parameters since the `sysconfigures' table was
not updated during startup.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5856 16 The configuration parameter `%s' can only be changed via the stored procedure
`sp_configure'.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5857 16 Changing the value of `%s' is not allowed since its value is calculated.
Explanation: Refer to the writeup for this error.
5858 10 The configuration option `%s' has been changed by `%s' from `%ld' to `%ld'.
Explanation: This informational message is written to the Adaptive Server error log
when sp_configure is used to change the value of a configuration parameter. The
username of the person making the change and the old and new values are written out.
Note that the message is NOT written to the log when you edit the configuration file
directly.
5859 16 The configuration number `%d' is invalid.
Explanation: Refer to the writeup for this error.
5860 18 Invalid datatype encountered for parameter `%s'.
Explanation: Adaptive Server checks the datatype of a configuration parameter when
you use sp_configure to read or change the parameter value. This error indicates that the
datatype of the configuration parameter is invalid. Contact Sybase Technical Support with
the server version and SWR level, and the text of the command that raised the error.
Number Severity Text and Explanation
Server Error Messages 5800 - 5899
982
5861 16 The current ’max memory’ value ’%ld’, is not sufficient to change the parameter ’%s’
to ’%ld’. ’max memory’ should be greater than ’total logical memory’ ’%ld’
required for the configuration.
Explanation: Refer to the writeup for this error.
5862 18 Invalid portion encountered.
Explanation: Each ASE configuration parameter has certain attributes, called portions
(such as name, datatype etc) associated with it. If the server finds invalid attributes for a
parameter, this error is raised. Contact Sybase Technical Support with the server version
and SWR level, and the text of the command that raised the error.
5863 18 Invalid group encountered.
Explanation: Refer to the writeup for this error.
5864 18 Invalide option encountered in `%s'.
Explanation: Error occurred during validation of configuration parameters for async i/o
or online engines. Sybase Technical Support with the server version and SWR level, and
the text of the command that raised the error.
5865 18 error in os_get_cpu_count: %d
Explanation: Refer to the writeup for this error.
5866 10 Configuration file `%s' has been written and the previous version has been renamed to
`%s'.
Explanation: Refer to the writeup for this error.
5867 16 The wash size for the %dk buffer pool in cache %s has been incorrectly configured. It
must be a minimum of %d buffers and a maximum of %d percent of the number of buffers
in the pool.
Explanation: Refer to the writeup for this error.
5868 16 Invalid type configured for cache %s. Cache type may be one of mixed OR log only but
NOT both.
Explanation: Refer to the writeup for this error.
5869 16 Invalid buffer size of %dk for cache %s. Valid buffer sizes are powers of 2 between %dk
and %dk inclusive.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5870 16 An invalid buffer size of %dk was encounterd in cache %s. Valid buffer sizes for caches
are powers of 2 between %dk and %dk inclusive.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5871 16 Invalid pool size of %dk (%d buffers) encountered for the %dk pool in cache %s. Buffer
pools must have a minimum total size of %dk or %d buffers, whichever is greater.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
983
5872 16 The total size of the configured pools (%dk) in cache %s is greater than the total size
(%dk) of the cache.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5873 16 Invalid configuration for the default %dk pool in cache %s. The default %dk pool must
be a minimum of %dk.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5874 16 The total size of all configured caches (%dk) is greater than the memory available for
caches (%dk).
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5875 16 The cache type for the default data cache cannot be modified.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5876 16 Multiple pools containing buffer sizes of %dk encountered in cache %s. Buffer sizes in
a cache must be unique.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5877 16 Bad alignment value of %d encountered. Valid cache alignment values are powers of 2
in between %dK and %dK inclusive. The units of this value are in bytes.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5878 14 Permission denied. Only users with role ’%.*s’ can change configuration option ’%s’.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
5879 16 The `reconfigure' command is no longer needed and supported since its functionality has
been migrated into the `sp_configure' command'. Please refer to the Reference Manual for
details.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5880 16 Warning: The operating system setting for file descriptors, %d, is not large enough to
configure `user connections' to %d, `devices' to %d, and `remote sites' to %d.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5881 16 The value of `default network packet size', `%ld', must be less than or equal to the value
of the `max network packet size', `%ld'.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
Number Severity Text and Explanation
Server Error Messages 5800 - 5899
984
5882 16 A cache alignment factor of %dk was specified but no buffer pool containing %dk buffers
has been configured. An attempt will be made to create this pool with extra memory (%dk
bytes) from cache %s.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5883 16 The value of `number of locks', `%ld', is not enough to configure `user connections' to
`%ld'. `number of locks' should be at least twice the value of `user connections'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5884 10 %s
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5885 16 The 'lock promotion HWM'= '%d' cannot be less than 'lock promotion LWM'
Explanation: = '%d'. Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5886 16 The 'lock promotion LWM'= '%d', cannot be greater than the 'lock promot
Explanation: ion HWM'= '%d'. Command failed due to invalid or illegal request.
Check syntax, semantics, and permissions. Take any corrective action indicated by
message.
5887 16 Configuration Error: Duplicate Named Cache `%s' found around line `%ld' in the
configuration file.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5888 16 Configuration Error: Two Named Caches with the `cache status' defined as `default data
cache' is not allowed.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5889 16 Configuration Error: Unknown cache status `%s' defined for cache `%s'.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5890 16 Configuration Error: A Named Cache with `cache status=default data cache' does not
exist in the configuration file.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5891 16 Named cache `%s' has been configured too small. The minimum size of a named cache
is %d Kilobytes.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
985
Server Error Messages 5900 - 5999
5892 16 You cannot use `allow sendmsg' option because syb_sendmsg() builtin is not supported
on this platform.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5893 16 The sum, (%s) + (%s %s) + (%s) + (%s) + (%s) + (%s), must be no greater than ’%ld’.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5894 16 Configuration Error: Duplicate pool size definition of `%s' for Named Cache `%s'.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
5895 16 Configuration Error: Duplicate wash size definition of `%s' for Named Cache `%s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
5898 10 WARNING!!! %dK buffer pool has been deleted. The log I/O size for the following
databases have been set to %dk. You must change the log I/O size to an existing pool size.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
5899 16 The value of the ’max memory’ parameter (%ld) defined in the configuration file is not
high enough to set the other parameter values specified in the configuration file.
Explanation: Command failed. Check syntax and semantics. Check your configuration
file and any configuration parameters supplied.
Number Severity Text and Explanation
Number Severity Text and Explanation
5901 20 Was unable to get an alarm, the background checkpoint process is unable to run.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5902 20 Serious kernel error reported on upsleep call, unwilling to continue. Aborting the
background checkpoint process.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
5903 16 Unable to open database with id = %d, suspect inconsistency in sysdatabases table.
Explanation: Report this error to the System Administrator so dbcc diagnostics can be
run.
Server Error Messages 6000 - 6099
986
Server Error Messages 6000 - 6099
Number Severity Text and Explanation
6001 10 SHUTDOWN is waiting for %d process(es) to complete.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6002 10 A SHUTDOWN command is in progress. Please log off.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6003 10 This process terminated by SHUTDOWN command.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6004 14 Permission denied. Only users with System Administrator (SA) role can run the
SHUTDOWN command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
6005 10 A SHUTDOWN is in progress.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6006 10 Server SHUTDOWN by request.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6008 10 Unable to write statistics for object %ld in database %ld. Please run update statistics on
this table after boot-up or prior to accessing the table next time.
Explanation: This is an informational message but requires the specified followup
action.
6009 10 Unable to write statistics for all objects in database %ld. Please run update statistics on
all objects in this database after boot-up or after loading this database.
Explanation: This is an informational message but requires the specified followup
action.
6010 10 Unable to write statistics for index %ld of object %ld in database %ld. Please run update
statistics on this index after boot-up or prior to using this index.
Explanation: This is an informational message but requires the specified followup
action.
6011 10 Unable to write statistics for all indexes of object %ld in database %ld. Please run update
statistics on all indexes after boot-up or prior to using the indexes next.
Explanation: This is an informational message but requires the specified followup
action.
CHAPTER 6 Adaptive Server Error Messages
987
Server Error Messages 6100 - 6199
Number Severity Text and Explanation
6101 16 Process `%d' is not a valid process number. Choose a number between 1 and `%d'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
6102 14 Permission denied. Only users with System Administrator (SA) role can run the KILL
command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
6103 17 Unable to do cleanup for the killed process; received Msg %d.
Explanation: Refer to the writeup for this error.
6104 16 You cannot use KILL to kill your own process.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
6106 16 Process `%d' is not an active process number.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
6107 14 Only User processes can be KILLed or SYB_TERMINATEd.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
6108 16 Process `%d' is not sleeping under a valid KILL condition, and therefore cannot be
KILLed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
6109 16 The KILL command is not legal in a user transaction.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Server Error Messages 6200 - 6299
988
Server Error Messages 6200 - 6299
Number Severity Text and Explanation
6201 10 STEP %d
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6202 10 The type of query is SELECT (into Worktable%d).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6203 10 The type of query is %s.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6204 10 The update mode is direct.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6205 10 The update mode is deferred.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6206 10 GROUP BY
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6207 10 Vector Aggregate
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6208 10 Scalar Aggregate
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6209 10 This step involves sorting.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6210 10 Worktable%d created, in %s locking mode, for ORDER BY.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6211 10 Worktable%d created, in %s locking mode, for DISTINCT.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
CHAPTER 6 Adaptive Server Error Messages
989
6212 10 Worktable%d created for REFORMATTING.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6213 10 Worktable%d created for SELECT_INTO.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6214 10 TO TABLE
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6215 10 FROM TABLE
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6216 10 Worktable%d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6217 10 %.*s
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6218 10 DISJOINT TABLE : nested iteration.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6219 10 Nested iteration.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6220 10 EXISTS TABLE : nested iteration.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6221 10 Using GETSORTED
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6222 10 Using Dynamic Index.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6223 10 Table Scan.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6224 10 Using Clustered Index.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 6200 - 6299
990
6225 10 Index : %.*s
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6226 10 Index name not found.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6227 10 Log Scan.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6228 10 Cursor name `%.*s' is declared on procedure `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6229 10 Cursor name `%.*s' is declared at nesting level `%d'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6230 10 The cursor is positioned after the last row.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6231 10 The current cursor position has been deleted.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6232 10 The cursor is positioned before the next row.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6233 10 The cursor is positioned on a row.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6234 10 There have been %d rows read, %d rows updated and %d rows deleted through this cursor.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6235 10 The cursor is not open.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6236 10 The cursor will be closed if the current position is deleted.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6237 10 The cursor will be closed when a transaction is committed or rolled back.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
991
6238 10 The cursor will remain open when a transaction is committed or rolled back.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6239 10 The number of rows returned for each FETCH is %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6240 10 The cursor is read only.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6241 10 The cursor is updatable.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6242 10 There are %d columns returned by this cursor.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6243 10 The result columns are:
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6245 10 Name = `%.*s', `Expression Result', Type = %s, Length = %d (%S_MSG)
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6246 10 Name = `%.*s', Table = `%.*s', Type = %s, Length = %d (%S_MSG)
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6247 10 The cursor was opened with these parameters:
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6248 10 %s
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6249 10 There are no active cursors.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6250 10 There are no active cursors that match the search criteria.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 6200 - 6299
992
6251 10 This cursor is declared within a stored procedure. The cursor's memory usage cannot be
distinguished from that of the procedure as a whole.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6252 10 This cursor is declared on a stored procedure. It is presently using `%d' bytes. However,
the memory usage will increase when the cursor is opened because the query plan will be
associated with the cursor at that time.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6253 10 This cursor is declared on a stored procedure. It is using %ld bytes of memory. The
procedure's plan (%ld bytes) will be returned to the procedure cache when the cursor is
closed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6254 10 This cursor is using %ld bytes of memory.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6255 10 The cursor id is %ld.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6256 10 The cursor has been successfully opened %d times.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6257 10 The cursor was closed by a CLOSE CURSOR statement.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6259 10 The cursor was closed because its current scan position could not be maintained following
a delete, update or insert.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6260 10 The cursor was closed because it was declared on a join and its current position was
deleted.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6261 10 The cursor was closed due to an error on the OPEN CURSOR statement.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
993
6262 10 The cursor was closed because CLOSE ON ENDTRAN was SET ON and the transaction
containing the cursor ended.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6263 10 The cursor is read only because it is declared on a union.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6264 10 The cursor is read only because it is declared on a group by or its plan includes a group by
operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6265 10 The cursor is read only because it contains a DISTINCT.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6266 10 The cursor is read only because it contains an aggregate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6267 10 The cursor is read only because it contains an ORDER BY clause.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6268 10 Showplan output for the cursor:
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6269 10 The cursor is currently scanning at isolation level 0.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6270 10 The cursor is currently scanning at a nonzero isolation level.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6271 10 The cursor was compiled at isolation level %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6272 10 Using I/O Size %d Kbytes for index leaf pages.
Explanation: This is an informational message or a message header. No action is
required.
6273 10 With %S_MSG Buffer Replacement Strategy for index leaf pages.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 6200 - 6299
994
6274 10 Evaluate Grouped %s.
Explanation: This is an informational message or a message header. No action is
required.
6275 10 Evaluate Ungrouped %s.
Explanation: This is an informational message or a message header. No action is
required.
6276 10 Forward scan.
Explanation: This is an informational message or a message header. No action is
required.
6277 10 Backward scan.
Explanation: This is an informational message or a message header. No action is
required.
6278 10 Positioning at start of table.
Explanation: This is an informational message or a message header. No action is
required.
6279 10 Positioning at end of table.
Explanation: This is an informational message or a message header. No action is
required.
6280 10 Positioning by Row IDentifier (RID).
Explanation: This is an informational message or a message header. No action is
required.
6281 10 Positioning by key.
Explanation: This is an informational message or a message header. No action is
required.
6282 10 Positioning at index start.
Explanation: This is an informational message or a message header. No action is
required.
6283 10 Positioning at index end.
Explanation: This is an informational message or a message header. No action is
required.
6284 10 Scanning only the last page of the table.
Explanation: This is an informational message or a message header. No action is
required.
6285 10 Scanning only up to the first qualifying row.
Explanation: This is an informational message or a message header. No action is
required.
6286 10 Index contains all needed columns. Base table will not be read.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
995
Server Error Messages 6400 - 6499
6287 10 Keys are:
Explanation: This is an informational message or a message header. No action is
required.
6288 10 %.*s %S_MSG
Explanation: This is an informational message or a message header. No action is
required.
6289 10 QUERY PLAN FOR STATEMENT %u (at line %u).
Explanation: This is an informational message or a message header. No action is
required.
6290 10 MRU
Explanation: This is an informational message or a message header. No action is
required.
6291 10 LRU
Explanation: This is an informational message or a message header. No action is
required.
6292 10 Using %d Matching Index Scans
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
6401 16 Cannot rollback %.*s - no transaction or savepoint of that name found.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
6402 20 Inconsistency in rollback logic. ROLLBACK finds no matching SAVE TRANsaction or
BEGIN TRANsaction. ROLLBACK aborted.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
6403 20 No matching savexact record found when rolling back the subordinate transaction %.*s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Server Error Messages 6500 - 6599
996
Server Error Messages 6500 - 6599
6404 18 Process %d in database `%.*s' was aborted. The transaction was rolled back, but an
ENDXACT record was not written, probably because the log is full.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
6500 10 DB Mount: Unable to locate device with virtual device number %d in sysdevices table
of database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6501 10 DB Mount: Unable to locate a device ’%.*s’ in sysdevices table of database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6502 10 DB Mount: Unable to use database in boot sequence for database ’%.*s’ on the device
with virtual device number %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6503 10 DB Mount: Unable to open the table ’%.*s’ in database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6504 10 DB Mount: Unable to lock the sysusages table in database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6505 10 DB Mount: Unable to begin a transaction in database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6506 10 DB Mount: Unable to insert row in table ’%.*s’ of database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6507 10 DB Mount: Unable to update table ’%.*s’ of database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
CHAPTER 6 Adaptive Server Error Messages
997
6508 10 DB Mount: Unable to start transaction in database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6509 10 DB Mount: Unable to update the sysusages table during mount operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6510 10 DB Mount: Unable to update for database %d the sysattributes table of database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6511 10 DB Mount: Unable to recover or bring online the database ’%.*s’ after mount operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6512 10 DB Mount: The device name ’%.*s’ must be less than 23 characters.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6513 10 DB Mount: Unable to open the device ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6514 10 DB Mount: Unable to extract metadata from device ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
6515 10 DB Mount: No virtual devices are available.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6516 10 DB Mount: Unable to locate the master device in the virtual device number %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6517 10 DB Mount: Unable to locate master database in virtual device number %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6518 10 DB Mount: This option is not supported.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6519 10 DB Mount: Unable to find the database ’%.*s’ in mounted master ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6520 10 DB Mount: Not all devices needed for the database ’%.*s’ are active.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 6500 - 6599
998
6521 10 DB Mount: Performing initial disk init of device ’%.*s’ for metadata extraction required
for mount.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6522 10 DB Mount: Performing disk init of device as ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6523 10 DB Mount: Database of type master is mounted as ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6524 10 DB Mount: Unable to mount database ’%.*s’ of type master.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6525 10 DB Mount: Mounting all the databases in the database ’%.*s’ of type master.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6526 10 DB Mount: Mounting database ’%.*s’ from database ’%.*s’ of type master.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6527 10 DB Mount: Recovering all mounted databases in the database ’%.*s’ of type master.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6528 10 DB Mount: Recovering mounted database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6529 10 DB Mount: Recovery of mounted database ’%.*s’ is complete.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6530 10 DB Mount: Recovery of mounted database ’%.*s’ failed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6531 10 DB Mount: Starting failover of companion server.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6532 10 DB Mount: Mount of companion master successful.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
999
Server Error Messages 6700 - 6799
6533 10 B Mount: Mount of all the database in master_companion is complete.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6534 10 DB Mount: Failover of companion server is completed successfully.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6535 10 DB Mount: Mount of companion master failed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6536 10 DB Mount: Mount of database in master_companion failed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6537 10 DB Mount: Failover of companion server failed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6538 10 DB Mount: Unable to map %d from sysdevices table in ’%.*s’ to database ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6539 10 DB Mount: Mount of database ’%.*s’ is complete.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6540 10 DB Mount: Unable to read system tables.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
6541 10 DB Mount: Use database of ’%.*s’ failed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
6701 16 Could not open dbid %d, object %ld.
Explanation: Adaptive Server could not perform the requested action. Check your
command for missing or incorrect database objects, variable names, and/or input data.
Server Error Messages 6900 - 6999
1000
Server Error Messages 6900 - 6999
6702 20 Protection hash chain corrupt: element of type UNUSED found in hash chain (dbid %d,
object %ld, protection type %d, protection status %d, column map %ld)
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Number Severity Text and Explanation
Number Severity Text and Explanation
6901 21 Overflow on High component of timestamp occurred in database %d. Database table
possibly corrupt.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
6902 21 Page timestamp value falls between the old and new timestamps from log. Page #=%ld,
object id = %ld, page timestamp=%04x %08lx. Log: old timestamp=%04x %08lx, new
timestamp=%04x %08lx.
Explanation: Refer to the writeup for this error.
6903 21 High order of timestamp indicates that timestamp structure may be incorrect.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator so dbcc diagnostics
can be run. (Printed with trace output in Release 11.0 and higher.)
6904 21 Mismatch between database table passed and the one found in the system structure when
requesting new database timestamp. Database id passed in : %d. System database id : %d.
Explanation: Report the error to your System Administrator. Check system tables first.
(not raised in Release 11.0 and higher.)
6905 18 Value of Begin Timestamp=%04x %08lx of new transaction in object ’%.*s’ in Database
’%.*s’ is lesser than the Begin Timestamp=%04x %08lx of the last transaction in the
same database. Non transactional reads may miss some committed data.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
CHAPTER 6 Adaptive Server Error Messages
1001
6906 18 Value of Commit Timestamp=%04x %08lx in database ’%.*s’ is greater than the Begin
Timestamp=%04x %08lx of the completing transaction. If allowed, clients of Commit
Timestamp could have missed some committed data.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
6907 23 Value of Commit Timestamp=%04x %08lx in database ’%.*s’ is greater than Database
Timestamp=%04x %08lx. This can qualify some non committed data as committed, thus
leading to corruption.
Explanation: The database may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and DBCC diagnostics run.
6908 21 During redo the page timestamp value is less than old timestamp from log. Page #=%ld,
object id = %ld, page timestamp=%04x %08lx. Log old timestamp=%04x %08lx.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 7000 - 7099
1002
Server Error Messages 7000 - 7099
Number Severity Text and Explanation
7001 16 A transaction attempted on external table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7002 16 Attempt to open VOS file failed
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7003 16 Attempt to close VOS file failed
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7004 16 Attempt to sequential_read VOS file failed
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7005 16 Segment name must be non-null; holds fully qualified VOS file path name
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7006 16 External table file name error
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7007 16 Illegal datatype for external table
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7008 16 NULL not allowed for external table
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7009 16 Create unique index and create clustered index are not allowed for external tables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7010 16 No index named `%.*s' exists on the OS file for external table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7011 16 Attempt to get file status for external table failed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1003
7012 16 External table - skipped.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7013 10 Create database feature is disabled.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
7014 10 Drop database feature is disabled.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
7015 10 Alter database feature is disabled.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
7016 10 Only money(19, 4) is allowed for non-external tables.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
7017 10 The %s (%d) for column '%.*s' in external table '%.*s' must be within the range %d to %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
7018 20 Bad offset (%d) should be (%d) for external table column.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7019 20 No conversion buffer available for conversion, fatal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7020 16 Attempt to bulk copy into an external table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7021 16 The embedded_key index type must be used when creating a VOS index for external
tables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7022 16 Descending order not allowed in the VOS index used for external tables, use ascending
order.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7023 16 The argument duplicates_allowed must be true in the VOS index for external tables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7100 - 7199
1004
Server Error Messages 7100 - 7199
7024 16 The collation_code argument must be ascii or numeric when creating a VOS index for
extgernal tables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
7025 20 Process not running on engine with attached ports for external table during external table
scan.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7026 16 External tables index file name `%.*s' is too long. Maximum length is %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Number Severity Text and Explanation
7101 17 Unable to allocate new text value, dbid %d.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7105 22 TEXT/IMAGE page %d does not have a next page. Either there is a suspect text page
chain, or transaction isolation level ’read uncommitted’ has been set. Database %.*s,
table %.*s, first text page %d.
Explanation: Refer to the writeup for this error.
7109 22 Unexpected log record of type %d found while processing TEXT/IMAGE data.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
7112 17 Deadlock occurred while trying to lock page %ld, which is held by SQL Server process
%d.
Explanation: Retry the command.
7114 22 Page %ld is not a valid text page.
Explanation: Refer to the detailed writeup for Error 7114 in the chapter “Error Message
Writeups”.
7120 22 Log record %ld:%d was not found in the LOG.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
CHAPTER 6 Adaptive Server Error Messages
1005
7121 22 Free offset %d is invalid on page %ld.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
7123 16 Invalid text pointer value %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7124 16 The offset and length specified in the READTEXT command is greater than the actual
data length of %ld.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7125 16 Text pointer value %s conflicts with the column name specified.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7126 16 Text pointer value %s references a data page with an invalid text status.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
7127 16 Text pointer value %s references a data page with an invalid time stamp.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
7128 16 Text pointer value %s references a data page which is no longer allocated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
7129 16 Synchronization time stamp does not agree with text data page value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7130 16 WRITETEXT with no log is not valid at this time. Database %s must first be configured
for this.
Explanation: Refer to the writeup for this error.
7131 16 Invalid table and column name specified in textvalid function.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7132 16 Selection of TEXT and IMAGE datatypes require DBLIB 4.0 or greater.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
7133 16 NULL textptr passed to %s function.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7100 - 7199
1006
7134 16 The text table and the table referenced by the text pointer value %s disagree.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7135 25 Failed to acquire lock for objid %ld.
Explanation: Internal error. No user action ncessary.
7136 16 SQL Server is now using a multi-byte character set, and the TEXT character counts have
not been re-calculated using this character set for table '%.*s'. Use DBCC FIX_TEXT on
this table before running the query again.
Explanation: Take the corrective action before running queries.
7137 20 Textptr Write Failed: An error occured while attempting to write text/image replication
information for database %.*s, table %.*s, column %.*s. Please contact Sybase Technical
Support for assistance. ( page %ld, datapage %ld, datarow %d )
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7138 20 Text/Image Replication Failure: A memory allocation error occured during replication of
table %.*s, in database %.*s. Try restarting the Sql Server with a larger procedure cache,
or contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7139 16 Insert to a TEXT/IMAGE column from a non TEXT/IMAGE field which involves
internal worktable (eg. orderby, groupby) processing is not supported. Rewrite your query
to avoid conversion from non TEXT/IMAGE datatype to TEXT/IMAGE datatype.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7140 16 A deadlock was detected while attempting to lock the first text page for text pointer %s.
Explanation: A locking or deadlock error occurred during an attempt to update a
TEXT/IMAGE page. Retry the command.
7141 16 A lock request was interrupted while attempting to lock the first text page for text pointer
%s.
Explanation: A SQL command involving a TEXT page was interrupted by the user
with a control-c or equivalent.
7142 16 The text pointer %s refers to a TEXT/IMAGE page that has been allocated to a different
row. This occurred because the original row was updated or deleted during an internal
deadlock avoidance manuever.
Explanation: A locking or deadlock error occurred during an attempt to update a
TEXT/IMAGE page. Retry the command.
7143 18 The maxlen field of non-TEXT/IMAGE constant node is non-zero. Wrong data length
may be reported.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
(Not raised in Version 11.9.2)
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1007
7144 16 Mime pointer %s does not point to a multi-part message.
Explanation: Check input and syntax.
7145 16 Message pointed to by mime pointer %s has less than %d parts.
Explanation: Check command input.
7146 16 Non-zero starting offset can not be used with MIME type.
Explanation: Check command input.
7147 16 Retrieval of partial MIME messages is not supported.
Explanation: Check command input.
7148 16 Feature %s is not implemented.
Explanation: Invalid or illegal command.
7149 16 Invalid input value (%s) for parameter %s
Explanation: Check command parameters.
7150 16 MIME message malformed - can't find concluding boundary '--%.*s--'. Insert/Update is
aborted.
Explanation: Check command and input data.
7151 22 Selected message has %d bytes less than expected. Message is probably corrupt. Please
contact your system administrator.
Explanation: Report the error to your System Administrator. Adaptive Server must be
restarted.
7152 16 Boundary string specified in 'content-type' header is too long. Maximum allowable
length is 70 characters.
Explanation: Check query and input data.
7153 16 Received a premature end-of-message while reading text data from the network. Check
the status of the host program.
Explanation: Check command and input data.
7154 0 Unable to log the class/jar definition into the current database’s transaction log for
replication. Please check the space available in the transaction log.
Explanation: Check the space available in the transaction log.
7155 22 The st-node page linkage appears to be broken or corrupt. The command ’dbcc
rebuild_text (%ld, %d, %ld)’ can be executed to repair the st-node. (objid=%ld,
colid=%d, FTP=%ld).
Explanation: Report the error to your System Administrator. Adaptive Server must be
restarted.
7156 16 Cannot read text value starting on page %ld because it has a different character set than
is currently installed. This row needs to be re-inserted to convert it to the current character
set. (CSID from tipsa %d, current CSID %d).
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
Server Error Messages 7200 - 7299
1008
Server Error Messages 7200 - 7299
7157 16 You cannot run the non-logged version of dbcc rebuild_text in this database. Please
check with the DBO.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
7158 10 Non-logged version of dbcc rebuild_text is complete. Please dump your database to
ensure recoverability.
Explanation: This is an informational message. Follow the recommended course of
action.
7159 10 Completed rebuild_text for table ’%.*s’.
Explanation: This is an informational message.
Number Severity Text and Explanation
Number Severity Text and Explanation
7201 17 Can't open a connection to site `%S_SRVID' because there are no remote sites available.
Rerun when there are fewer active remote sites, or contact a user with System
Administrator (SA) role.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7202 17 Can't open a connection to site `%S_SRVID' because there are no available PSS structures.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7203 17 Can't open a connection to site `%.*s' because SQL Server is not configured for enough
user connections. See the error log file in the SQL Server boot directory.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7204 18 Can't open a connection to site `%.*s' because the site is already active.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7205 18 Can't open a connection to site `%S_SRVID'. See the error log file in the SQL Server boot
directory.
Explanation: Refer to the writeup for this error.
CHAPTER 6 Adaptive Server Error Messages
1009
7206 17 Can't open a connection to site `%S_SRVID' because all channel numbers are in use.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7207 17 Can't open a connection to site `%S_SRVID' because there are no remote connections
available. Rerun when there are fewer remote users and/or fewer local users making remote
accesses, or contact a user with System Administrator (SA) role.
Explanation: Refer to the detailed writeup for Error 7207 in the chapter titled “Error
Message Writeups”.
7208 17 Can't open a connection to site `%S_SRVID' because there are no remote logins available.
Rerun when there are fewer local users making remote accesses, or contact a user with
System Administrator (SA) role.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7209 17 Cannot open a connection to site `%S_SRVID' because %S_MSG buffer could not be
initialized.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7210 18 Can't open a connection to site `%S_SRVID' because `set up channel' message could not
be sent.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7211 18 Can't open a connection to site `%S_SRVID' because `set up channel' message was not
acknowledged.
Explanation: Refer to the detailed writeup for this message in the chapter titled “Error
Message Writeups”.
7212 11 Can't close connection %d on site `%S_SRVID' because it is not active.
Explanation: Refer to the writeup for this error.
7213 18 Can't remove site `%.*s' from list of active sites because it is missing.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7214 11 No site name received in server login packet. Server login rejected.
Explanation: Refer to the writeup for this error.
7215 18 Can't send to site `%S_SRVID'.
Explanation: Refer to the writeup for this error.
7216 18 Can't read from site `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 7200 - 7299
1010
7217 18 Echo failed from site `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7218 11 Site `%.*s' not found in sysservers.
Explanation: Refer to the writeup for this error.
7219 11 Site %d not found in sysservers.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
7220 11 Site `%s' not found in interfaces file.
Explanation: Refer to the writeup for this error.
7221 14 Login to site `%S_SRVID' failed.
Explanation: Refer to the writeup for this error.
7222 18 Received bad token 0x%x from site `%S_SRVID'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7223 16 Cannot %S_MSG site `%S_SRVID'.
Explanation: Refer to the writeup for this error.
7224 16 Unexpected end-of-message encountered in RPC response from site `%S_SRVID'.
Explanation: Failure in Remote Procedure Call (RPC). Check syntax. Check sending
and receiving Adaptive Server environments for remote access.
7225 16 Unknown datatype token %d `%s' encountered.
Explanation: Failure in Remote Procedure Call (RPC). Check syntax. Check sending
and receiving Adaptive Server environments for remote access.
7226 16 Alternate row received for id %d with no corresponding format information.
Explanation: Failure in Remote Procedure Call (RPC). Check syntax. Check sending
and receiving Adaptive Server environments for remote access.
7227 17 Can't open a connection to site `%S_SRVID' because SQL Server is not configured for
remote access. Ask a user with System Administrator (SA) role to reconfigure SQL Server
to allow remote access.
Explanation: Refer to the writeup for this error.
7228 18 Received a final DONE packet with DONE_ACK on site `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7229 18 Unable to obtain the remote Server's OS Session Label.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1011
7230 18 The OS Session Label of the remote Server process does not equal the connection level
assigned to it.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7231 18 The OS Session Label, curread and curwrite labels of the Client do not equal the
connection level for the remote Server.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7232 18 Internal MAC Subsystem error. OS Binary to Master SLID Conversion failed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7233 18 Internal MAC Subsystem error. Master SLID to OS Binary Conversion failed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7234 10 Failed to connect to remote server %s %s %s %s %s for site %s. Trying the next query
entry of this server, if any.
Explanation: Refer to the detailed writeup for Error 7234 in the chapter titled “Error
Message Writeups”.
7235 17 No other query entry found for the remote server %s - site %s. Aborting this site handler,
as no remote server responded. Please make sure the remote server is accepting
connections.
Explanation: Refer to the detailed writeup for Error 7235 in the chapter titled “Error
Message Writeups”.
7238 11 There was no security mechanism listed in Sysservers catalog for site %s.
Explanation: Command failed. Check your database for the object not found and re-enter
the command with the correct name.
7239 17 Failed to allocate a security session structure for site %s.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7240 18 Mechanism %s is not enabled for use for RPC Model B because the Security Control Layer
has not been initialized.
Explanation: Command failed due to internal Adaptive Server problem. Report the error
to your System Administrator.
7241 18 Security Session establishment failed during Secured RPC Model B login.
Explanation: Command failed due to internal Adaptive Server problem. Report the error
to your System Administrator.
7242 18 Security Negotiation failed during Secured RPC Model B login.
Explanation: Command failed due to internal Adaptive Server problem. Report the error
to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 7300 - 7399
1012
Server Error Messages 7300 - 7399
7243 16 Internal Limit reached. All local LOGCONN array segments are full. The following
display is accurate, but it does not contain all active LOGCONNs. Displaying %d active
LOGCONNs in %d local arrays.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message. (Not raised in 11.9.2).
Number Severity Text and Explanation
Number Severity Text and Explanation
7301 15 FOR UPDATE has been incorrectly specified for a READ ONLY cursor.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7302 15 The row number specification for a SET CURSOR ROWS statement must be an integer
value greater than 0.The given value is `%d'.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7303 15 FOR BROWSE can not be used in the declaration of a cursor.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7304 15 FOR READ ONLY can not be used in a SELECT which is not part of the declaration of
a cursor or which is not inside a stored procedure.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7305 15 FOR UPDATE can not be used in a SELECT which is not part of the declaration of a
cursor or which is not inside a stored procedure.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7307 15 COMPUTE clause can not be used in the declaration of a cursor.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7308 15 SELECT-INTO can not be used in the declaration of a cursor.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
CHAPTER 6 Adaptive Server Error Messages
1013
7309 10 SQL statement on line number %d contains %S_MSG. The error is caused due to the use
of %s.
Explanation: Check command syntax and semantics.
7310 10 SQL statement on line number %d contains %S_MSG. The error is caused due to the use
of non-ANSI option: %S_MSG.
Explanation: Check command syntax and semantics.
7311 10 Line number %d contains %S_MSG. The error is caused due to the use of Sybase
declared global/local variables.
Explanation: Check command syntax and semantics.
7312 10 Line number %d contains %S_MSG. The error is caused due to the use of Sybase built-
in function: %.*s.
Explanation: Check command syntax and semantics.
7313 10 Line number %d contains %S_MSG. The error is caused due to the use of non-standard
control flow: %s.
Explanation: Check command syntax and semantics.
7314 10 Line number %d contains %S_MSG. The error is caused due to the use of non-standard
transaction key word(s): %S_MSG.
Explanation: Check command syntax and semantics.
7315 10 Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI
conversion function(s).
Explanation: Check command syntax and semantics.
7316 10 Line number %d contains %S_MSG. The error is caused due to the use of database prefix.
Explanation: Check command syntax and semantics.
7317 10 Line number %d contains %S_MSG. The error is caused due to the use of %S_MSG
%S_MSG.
Explanation: Check command syntax and semantics.
7318 10 Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI
drop object functionality: %S_MSG.
Explanation: Check command syntax and semantics.
7319 10 Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI
operator: %S_MSG.
Explanation: Check command syntax and semantics.
7320 10 Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI
pattern matching character(s).
Explanation: Check command syntax and semantics.
7321 10 Line number %d contains %S_MSG. The error is caused due to the use of column
name(s) in a select list with aggregates but column name(s) not in group by list.
Explanation: Check command syntax and semantics.
Number Severity Text and Explanation
Server Error Messages 7300 - 7399
1014
7322 10 Line number %d contains %S_MSG. The error is caused due to the use of set operations
in an insert select: %S_MSG.
Explanation: Check command syntax and semantics.
7323 10 Line number %d contains %S_MSG. The error is caused due to the use of column
headings.
Explanation: Check command syntax and semantics.
7324 10 Line number %d contains %S_MSG. The error is caused due to the use of compute
statement.
Explanation: Check command syntax and semantics.
7325 16 Nulls not allowed in a primary key column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7326 10 Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI
escaping of `[` or `]' in a LIKE ESCAPE.
Explanation: Check command syntax and semantics.
7327 10 Length or precision specification %d is not within the range of 1 to %d.
Explanation: Check command syntax and semantics.
7328 10 Specified scale %d is not within the range of 0 to 255.
Explanation: Check command syntax and semantics.
7329 15 There are too many parameters given with function `%.*s'. The maximum number of
parameters allowed is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7330 15 Within %s, you are not allowed to specify the database name prefix for the new object
name in %s. All new objects must be created in the current database.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7331 15 Within %s, you can't create an object owned by another user. The specified object owner
is `%.*s', but the schema authorization id is `%.*s'.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
7332 15 %S_MSG is allowed only in %S_MSG
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7333 15 %s does not allow specifying the user name as a prefix to the object name.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1015
7334 16 Subqueries are not allowed in a RAISERROR.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7335 15 A SELECT statement that assigns a value to a variable must not be combined with a
COMPUTE clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7336 10 Line number %d contains non-ANSI identifier. Length of identifier `%.*s' is greater than
18.
Explanation: Check command syntax and semantics.
7337 10 FIPS WARNING: Truncation when inserting long char/varchar/unichar/univarchar into
shorter char/varchar/unichar/univarchar.
Explanation: Check command syntax and semantics.
7338 10 FIPS WARNING: Union of exact numeric with different precision or scale.
Explanation: Check command syntax and semantics.
7339 10 FIPS WARNING: Union of chars or of literals with different lengths.
Explanation: Check command syntax and semantics.
7340 10 FIPS WARNING: Union of chars with literal.
Explanation: Check command syntax and semantics.
7341 10 FIPS WARNING: Inserted approximate numeric into exact numeric.
Explanation: Check command syntax and semantics.
7342 15 Keyword SHARED can not be used in a SELECT statement which is not part of the
declaration of a cursor.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7343 15 The value (%d) given to the %S_MSG is not within the allowed range. The allowed
range is between %d and %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7344 16 DECLARE CURSOR must be the only statement in a query batch.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7345 16 SELECT is not allowed in a dynamic EXECUTE IMMEDIATE statement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7346 16 Invalid arguments for RAISERROR extended error data.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7300 - 7399
1016
7347 16 The IDENTITY function should be used only when the SELECT statement has an INTO
clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7348 16 Select expression results in more than one column having same name. Column name
`%.*s' is specified more than once
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7349 16 FIPS WARNING: Due to usage of the name of an expression in the ORDER BY clause
which has a correlation name in the select list
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7350 16 FIPS_WARNING: Use of implicit or explicit ALL in COUNT aggregate function. Only
COUNT(*) or COUNT( DISTINCT <expression> ) is allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7351 16 Local or global variables not allowed in view definition
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7352 16 The SET option with ARITH_OVERFLOW is allowed only in SET ARITHABORT or
SET ARITHIGNORE.
Explanation: See `set arithabort/arithignore' command restrictions.
7353 16 The SET option with NUMERIC_TRUNCATION is allowed only in SET
ARITHABORT.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7354 16 The SET can have option restrictions only when there is one option in the command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7355 16 Table (or view) `%.*s' created by SELECT INTO or CREATE VIEW results in a column
with no name. Please specify a column name for computed columns.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7356 16 Aggregates or subqueries are not allowed in check constraints.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7357 15 Label options (CURREAD, CURWRITE) cannot be used with non-label SET options in
a single SET commmand.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1017
7358 16 Invalid type argument specified for the %s builtin function. Argument must either be
SENSITIVITY or SENSITIVITY_BOUNDARY.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7359 16 SYB_IDENTITY is not allowed in READ or WRITE TEXTS commands.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7360 16 Explicit updates/inserts cannot be done on sensitivity or information columns.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7361 16 FIPS WARNING: GROUP BY clause specified when all the items in select list are
aggregate functions or none of the items in select list are aggregate functions.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7362 16 FIPS WARNING: Select list contains aggregate function(s) but GROUP BY clause not
specified.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7363 16 You can not have variable assignments in a SELECT statement with the UNION
operation.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7364 16 Tables `%.*s' and `%.*s' have same exposed names. Use correlation names to distinguish
them.
Explanation: Refer to the writeup for this error.
7365 16 A column in the FOR UPDATE OF list can only be qualified by a table or correlation
name. Column `%.*s' is qualified by an table owner and/or database name.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7366 16 A column in the FOR UPDATE OF list can only be qualified by an exposed table or
correlation name. `%.*s' is not an exposed name in the select statement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7367 16 Expected row size '%d' is not a valid value; expected row size must be greater th an 9 or
can be either 0 or 1.
Explanation: Check command parameters.
7368 16 Can not create column by name `SYB_IDENTITY_COL'. This name has special
meaning when `auto_identity' option is ON.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7300 - 7399
1018
7369 15 Procedure Grouping is not allowed.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7370 16 Specified precision %d is more than the maximum precision %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7371 16 Specified scale %d is more than the specified precision %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7372 15 Cursor FOR UPDATE cannot be specified at isolation level 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7373 15 Browse mode cannot be specified at isolation level 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7374 15 Invalid isolation level specified.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7375 15 SELECT INTO cannot be specified with isolation level clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7376 15 Select in a CREATE VIEW cannot be specified with isolation level clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7377 15 SELECT INSERT cannot be specified with isolation level clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7378 15 HOLDLOCK/NOHOLDLOCK/SHARED/READPAST conflicts with AT ISOLATION
LEVEL 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7379 14 Permission denied. You must have the `Replication' role to set %.*s ON or OFF. Please
contact a user with System Security Officer (SSO) role for help.
Explanation: Command failed. Certain SET commands require replication role.
7380 10 WARNING: Line %d. Invalid value for `%S_MSG' specified. This value will be
ignored, default value will be used instead.
Explanation: When you specify a prefetch size on select, update and delete statements,
but the value you specified is not available, the ASE Buffer Manager raises this warning
message. Processing continues with the prefetch size that the optimizer determines to be
the "best" value.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1019
7381 10 prefetch size
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7382 16 Subqueries are not allowed in an ORDER BY clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7383 16 Subqueries are not allowed in a GROUP BY clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7384 16 Subqueries are not allowed in a COMPUTE clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7385 16 The number of subqueries in the query exceeds the maximum allowed (%d).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7386 10 Set dup_in_subquery is no longer supported. To get similar performance and semantics,
rewrite the subquery as a join.
Explanation: The set_dup_in_subquery command existed in pre-11 server versions as
a temporary way to avoid changes needed for ANSI-compliant duplicate handling. It is
not supported as of version 11.0, which contains better subquery processing features.
Rewrite the subquery as a join.
7387 15 The maximum number of parameters in a dynamic SQL statement is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7388 16 An aggregate of an aggregate produces a scalar value. Any further nesting of aggregates
has no effect. Remove the aggregates beyond level two.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7389 16 A HAVING clause with aggregates of different levels is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7391 15 The table count specification for a SET TABLE COUNT statement must be an integer
value greater than 0. The given value is `%d'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
7392 15 Procedure Grouping is not allowed. Please contact a user with System Security Officer
(SSO) role for help.
Explanation: Command failed. Check syntax and semantics.
7393 16 The value of forced parallel degree cannot be negative.
Explanation: Check command parameters.
Number Severity Text and Explanation
Server Error Messages 7400 - 7499
1020
Server Error Messages 7400 - 7499
7394 15 Duplicate specification of '%S_MSG' clauses for one table is not allowed.
Explanation: Check command syntax.
7395 10 forced index
Explanation: This is informational text.
7396 10 forced parallel
Explanation: This is informational text.
7397 10 forced lru/mru
Explanation: This is informational text.
7398 10 forced prefetch
Explanation: This is informational text.
7399 15 Reserved page gap '%d' is not a valid value; reserved page gap must be between 0 and 255
Explanation: Command error. Check parameters.
Number Severity Text and Explanation
Number Severity Text and Explanation
7401 10 Could not allocate memory for the threshold task's argument list; threshold task cannot be
spawned for database %d, segment %d, free space %ld.
Explanation: Refer to the writeup for this error.
7402 10 Could not spawn the threshold handler procedure for database %d, segment %d, when
only %ld free pages were left in the segment.
Explanation: Refer to the writeup for this error.
7403 10 Threshold task could not use database %d, and so cannot execute the threshold procedure
for segment %d, free space %ld.
Explanation: Refer to the writeup for this error.
7404 10 Could not find row in systhresholds for database %.*s describing segment %d, free space
%ld.
Explanation: Refer to the writeup for this error.
7405 10 Threshold procedure name is missing from the systhresholds row in database %.*s for
segment %d, free space %ld.
Explanation: Refer to the writeup for this error.
7406 16 %s: unknown option: %.*s
Explanation: Refer to the writeup for this error.
CHAPTER 6 Adaptive Server Error Messages
1021
7407 10 Failed to execute the threshold procedure for database %d, segment %d, free space %ld.
Explanation: Refer to the writeup for this error.
7408 16 Could not find a dbtable for database %d.
Explanation: Refer to the writeup for this error.
7409 20 This task tried to sleep waiting for space to become available in the log, but could not. The
current command is being aborted because no further database changes can be logged.
Explanation: Refer to the writeup for this error.
7410 26 %s: function called with invalid argument.
Explanation: Refer to the writeup for this error.
7411 21 Table `systhresholds' in database `%.*s' is not in its correct sort order. Either the clustered
index is missing or there is data corruption in the table.
Explanation: Refer to the writeup for this error.
7412 10 Space available in the log segment has fallen critically low in database `%.*s'. All future
modifications to this database will be %S_MSG until the log is successfully dumped and
space becomes available.
Explanation: Refer to the writeup for this error.
7413 10 %d task(s) are sleeping waiting for space to become available in the log segment for
database %.*s.
Explanation: Refer to the writeup for this error.
7414 10 Threshold procedure `%.*s' returned an error indication (@status=%d) when called for
database `%.*s', segment `%.*s', free_space %ld.
Explanation: Refer to the writeup for this error.
7415 16 The transaction log in database %.*s is almost full. Your transaction is being %S_MSG
until space is made available in the log.
Explanation: Refer to the writeup for this error.
7416 20 Could not open Systhresholds table for database %.*s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
7417 21 The last chance threshold entry for logsegment is not present in threshold cache for
database '%S_DBID'. Please use 'dbcc thresholds' to see the threshold cache contents and
contact your system administrator.
Explanation: Adaptive Server encountered an internal error affecting all processes using
the current database. Report the error to your System Administrator. Adaptive Server must
be restarted and DBCC diagnostics run.
7418 22 The last chance threshold entry for logsegment is not present in systhresholds table for
database '%S_DBID'. Please contact your system administrator.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and DBCC diagnostics run.
Number Severity Text and Explanation
Server Error Messages 7400 - 7499
1022
7419 16 lct_admin(abort): Process %d that you are trying to abort is not a valid process. Choose a
process with id between %d and %d.
Explanation: Check command inputs and retry.
7420 16 lct_admin(abort): Cannot abort yourself. Your process id %d and the given process id %d.
Explanation: Check command inputs and retry.
7421 16 lct_admin(abort): Process %d is not an active process. Cannot abort it.
Explanation: Check command inputs and retry.
7422 16 lct_admin(abort): Process %d is not an user process. Only an user process waiting on log-
suspend mode can be aborted.
Explanation: Check command inputs and retry.
7423 10 lct_admin(abort): Process %d waiting on log-suspend state on database '%S_DBID is
being aborted.
Explanation: This is an informational message.
7424 16 lct_admin(abort): Cannot abort process %d, as it is not sleeping on log-suspend state in
database '%S_DBID'.
Explanation: Check command inputs and retry.
7425 16 lct_admin(unsuspend): This command is not supported anymore. If you want to abort the
tasks sleeping on log-suspend state, please consider using lct_admin(abort).
Explanation: Invalid command.
7426 16 lct_admin(abort): Database '%S_DBID' did not reach the last chance threshold. This
command will have no effect on the database.
Explanation: This is an informational message.
7427 10 Failed to complete LCT_ADMIN() function. Please look for any previous messages that
may help identify the cause.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
(Not raised in 11.9.2)
7428 17 Could not add the last chance threshold for database '%S_DBID'.
Explanation: Command did not execute due to potential resource problem.
7429 16 Database '%.*s' contains too many thresholds. It may contain at most %d thresholds. Drop
thresholds as required to bring the database below the limit.
Explanation: Take the corrective action indicated.
7433 10 Hit %s on database ’%S_DBID’ for %s segment during upgrade. Not spawning threshold
action procedure.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1023
Server Error Messages 7600 - 7699
7434 16 lct_admin('unsuspend') is no longer supported. We recommend that you use the KILL
command to stop suspended processes. You may wake individual processes using
lct_admin('w akeup', <spid>).
lct_admin('unsuspend') is no longer supported. We recommend that you use the KILL
command to stop suspended processes. You may wake individual processes using
lct_admin('w akeup', <spid>).
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
7435 16 lct_admin(abort): Process %d is a child-process. Cannot abort it.
Explanation: Command failed due to invalid or illegal request.
7436 18 lct_admin(abort): Unable to obtain DBTABLE for process %d. Cannot abort it.
Explanation: Command failed due to internal Adaptive Server problem. Report the error
to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
7601 14 Permission denied. System Security Officer (SSO) role is required to open an auditing
system table.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7602 16 There is no such audit option. If you received this message while executing a Sybase-
supplied auditing stored procedure, this is a system error, and you should contact a user
with System Administrator (SA) role.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7603 14 The ad_hoc_audit builtin function cannot be called directly. You must use
sp_addauditrecord to send an ad-hoc audit record.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
7604 20 An unknown audit event type was received. This is a system error. Contact a user with
System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Server Error Messages 7600 - 7699
1024
7605 20 An attempt to send a message to the audit process has failed. This is a system error.
Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7606 20 An attempt to allocate memory for the audit queue has failed. This is a system error.
Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7607 20 An attempt to establish a system mailbox for the audit process has failed. This is a system
error. Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7608 20 An attempt to open the sybsecurity database has failed. This is a system error. Contact
a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7609 20 An attempt to load the global audit options into sysauditoptions has failed. This is a
system error. Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7610 20 An attempt to open the sysaudits table has failed. This is a system error. Contact a user
with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7611 20 An attempt to awaken the server initialization process has failed. This is a system error.
Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7612 20 An attempt to get an audit record from the audit queue has failed. This is a system error.
Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7613 14 Permission denied. System Security Officer (SSO) role is required to create or drop the
sybsecurity database.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7614 14 Permission denied. System Security Officer (SSO) role is required to create an auditing
system table.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1025
7615 16 The auditing system tables can only be created in the sybsecurity database.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7616 16 You can only use SELECT or SELECT INTO with the sysaudits table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7617 20 An attempt to get a free audit record buffer from the audit queue has failed. This is a
system error. Contact a user with System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7618 20 The audit process is not currently active. Contact a user with System Administrator (SA)
or System Security Officer (SSO) role.
Explanation: Refer to the writeup for this error.
7619 20 An insert to the sysaudits table has failed. This is a serious error, and you should contact
a user with System Administrator (SA) or System Security Officer (SSO) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7620 14 You must use one of the Sybase-supplied auditing stored procedures to change audit
options.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
7623 20 Auditing: Fatal error - unable to get object owner name to fill in the audit record. This is
an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. A username could not be obtained for the audit record. Report the error to your
System Administrator.
7624 20 Auditing: Fatal error - unable to get audit creation flags in the database with dbid `%d'.
This is an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process when trying to update audit records. Report the error to your System
Administrator.
7625 20 Audit table number `%d' is invalid.
Explanation: Adaptive Server encountered an internal error affecting the current
process when trying to update audit records. Report the error to your System
Administrator.
7626 20 Auditing: Internal erorr - could not get the next audit table number.
Explanation: Adaptive Server encountered an internal error affecting the current
process when trying to update audit records. Report the error to your System
Administrator.
Number Severity Text and Explanation
Server Error Messages 7700 - 7799
1026
Server Error Messages 7700 - 7799
7627 20 Auditing: Fatal error - current audit table is full and server is configured to suspend
auditing when device is full, but it failed to suspend the audit process. This is an internal
error.
Explanation: Adaptive Server encountered an internal error affecting the current
process when trying to update audit records. Report the error to your System
Administrator.
7628 16 Invalid value for audit related configuration parameter because the audit subsystem is not
running. Contact a user with System Security Officer (SSO) Role.
Explanation: You attempted to change audit configuration without installing
sybsecurity database.
7629 18 Auditing: Internal error - current audit table config parameter value may not be updated
in the configuration file and in sysconfigures system table. Accurate value of this
parameter is in syscurconfigs system table. This is not a critical error.
Explanation: Adaptive Server encountered an error while attempting to change audit
table information. Report the error to your System Administrator.
7631 16 Current audit table can not be changed to `%d' because it is not empty.
Explanation: Adaptive Server encountered an error while attempting to change audit
table information. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
7701 16 Overflow when converting from char to type %s, value = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7702 16 Overflow when converting from numeric(%d,%d) to type %s'%.*s', value = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7703 16 Overflow when converting from decimal(%d,%d) to type %s'%.*s', value = `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7704 16 Truncation error when converting to exact numeric(%d,%d) from type %s'%.*s', value =
`%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1027
7705 10 Invalid pattern string. The character following the escape character must be percent sign,
underscore, left square bracket, right square bracket, or the escape character.
Explanation: Check command syntax and semantics.
7706 10 Pattern string is too long. The given pattern string `%.*s' is converted using the escape
character `%.*s'. The converted string is longer than %d bytes.
Explanation: Check command syntax and semantics.
7707 10 Illegal escape character found. There are fewer bytes than necessary to form a valid
character.
Explanation: Check command syntax and semantics.
7708 10 Pattern string is too complex. There are too many blocks requiring special attention for
right bracket (]), circumflex (^), or dash (-).
Explanation: Check command syntax and semantics.
7709 20 Server-initiated remote procedure call state error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7710 20 Attempt to retrieve a returned parameter length from a server-initiated stored procedure
without specifying the parameter name.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7711 20 Parameter not found while trying to retrieve the returned parameter length from a server-
initiated stored procedure.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
7712 16 Stored procedure `%.*s' may be run only in chained transaction mode. The `SET
CHAINED ON' command will cause the current session to use chained transaction mode.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7713 16 Stored procedure `%.*s' may be run only in unchained transaction mode. The `SET
CHAINED OFF' command will cause the current session to use unchained transaction
mode.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7714 16 In a CREATE SCHEMA statement, the authorization id must match the current user
name. The supplied authorization id, `%.*s', does not match the current user name, `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7715 18 Object `%d' specified as a rule for tabid `%d', colid `%d' does not have a variable node
in the tree.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 7700 - 7799
1028
7716 16 Cannot convert CHAR value to REAL. The CHAR value has incorrect syntax.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7717 20 Attempted to drop temporary table with object id %ld, which is not in the temporary
object lists for this task.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7718 16 The `%s' command is not allowed within a multi-statement transaction in the `%.*s'
database.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7719 17 There is no memory available to save the current sequencer state -- cannot continue
processing this query.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
7720 16 Update/Delete from a table which is the inner table of an outerjoin is not allowed.
Command aborted.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7725 16 Cursor `%.*s' was declared with a FOR UPDATE clause. This cursor was found to be
read only.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7726 16 Execute cursor `%.*s' is declared on a procedure which has more than one SQL statment.
For the declaration of this cursor to be legal the procedure should have a single SELECT
statement clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7727 26 An internal error occurred for the cursor variable `%.*s'. It could not be found on any
variable list of the procedure.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
7728 14 Permission denied. You must have the following role(s) to execute %.*s : `%.*s' . Please
contact a user with the appropriate role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7729 16 Invalid role string `%.*s' entered.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1029
7730 14 SET ROLE fails. The caller is not granted with the specified `%.*s' role. Please contact
a user with System Security Officer (SSO) role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7731 16 SET ROLE fails. The caller cannot assume the new user identity (uid) in the current
database. Please contact a user with System Security Officer (SSO) role for help.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7732 16 The UPDATE/DELETE WHERE CURRENT OF failed for cursor `%.*s' because the
cursor is read only.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7733 18 Unable to locate the base procedure header (Pss->phdr) which had been switched earlier.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7734 18 The search for table name when adding a resdom in s_addident() failed. The resdom for
the column `%.*s' did not contain the table name. This is an internal error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7735 16 The specfied row count `%d' for the cursor `%.*s' is invalid. The rowcount should always
be greater than zero.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7736 20 Unable to find lock request for tabid %ld dbid %d. This is an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7739 18 Internal error - SELECT INTO not found, perhaps tree corrupted.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7740 18 The declaration for cursor `%.*s' has the column `%.*s' in it's FOR UPDATE list which
is not part of the SELECT list for the cursor. Either select that column or remove it from
the FOR UPDATE list.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7741 18 Internal error - Both SHARED AND UPDLOCK have been set on table `%.s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 7700 - 7799
1030
7742 16 You must change your password using the sp_password system stored procedure before
you can continue.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7743 16 An explicit value for the identity field in table `%.*s' can only be specified in an insert
statement when a field list is used.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7744 16 Illegal attempt to update identity field `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7745 16 Attempting to add a new identity field to a table `%.*s', via select into, which would have
a field `%.*s' that inherits the identity property.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7746 16 Attempting to add more than 1 new identity field to a table `%.*s', via select into.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7747 16 Unable to SET IDENTITY_INSERT to ON for table `%.*s' because it is already on for
tabid %ld dbid %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7748 16 Pseudo-column `SYB_IDENTITY' used incorrectly. No table in the query has the
identity property.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7749 16 Pseudo-column `SYB_IDENTITY' used ambiguously. Multiple tables in the query have
the identity property.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7750 16 Argument type `%s' is invalid for argument %d of `%s' function.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7751 16 Unable to SET IDENTITY_INSERT to ON/OFF for table `%.*s' because the object
either does not exist or cannot be opened.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1031
7752 16 Unable to SET IDENTITY_INSERT to ON/OFF for table `%.*s' because you are neither
the DBO nor the object owner.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7753 16 Unable to SET IDENTITY_INSERT to ON/OFF for object `%.*s' because the object is
not a user table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7754 16 Operand data type `%s' is invalid for `%s' operator.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7755 18 Attempt to switch base procedure header (Pss->phdr) more than once.This is an internal
error.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7756 16 Unable to SET IDENTITY_INSERT to ON/OFF for table `%.*s' because the table does
not have the identity property.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7757 16 The order-by position number `%ld' is out of range of the number of items in the select-
list.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7758 16 The declaration for cursor `%.*s' has the column `%.*s' in it's FOR UPDATE OF list
which is not updatable after view resolution.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7759 16 The declaration for cursor `%.*s' has the column `%.*s' in it's FOR UPDATE OF list
which is not updatable because it has the identity property.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7760 16 Conversion of security label datatype to char/varchar datatype failed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7761 16 The data type `%s' is invalid for the %s function. Allowed types are: CHAR/VARCHAR
and SENSITIVITY/SENSITIVITY_BOUNDARY.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7700 - 7799
1032
7762 16 Trigger label configuration incompatible with user's profile.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7763 16 Procedure label configuration incompatible with user's profile.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7764 23 Sysobjects entry NOT found for procedure buffer entry.
Explanation: The database may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
7765 23 Invalid owner curread for view, procedure, or trigger in sysobjects entry.
Explanation: The database may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
7766 16 A conversion from `%s' label to character string resulted in an overflow.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7767 16 THe user's curread label does not dominate the converted label.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7768 16 Invalid label syntax.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7769 18 Internal conversion error detected while converting to/from `%s' label datatypes.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7770 10 Warning: There are other roles currently active.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7771 16 Insert into the sensitivity column of table `%.*s' attempted. Explicit inserts into the
sensitivity column are not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7772 18 Internal error encountered while processing @@update_mode global variable.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7773 16 Execute cursor `%.*s' is declared on a procedure which contains a non-SELECT or a
SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should
have a single SELECT statement without a COMPUTE clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1033
7774 16 The procedure `%.*s' contains a select statement with FOR UPDATE clause. This should
be the only statement in the procedure.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7775 16 The column `%.*s' in FOR UPDATE list is not part of the SELECT list. Either select that
column or remove it from the FOR UPDATE list.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7776 16 Transaction to update certification state of object %S_OBJID, database %S_DBID
failed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7777 16 Changing certification state of object %S_OBJID, database %S_DBID to SUSPECT
because of change in state of dependent object %.*s (previous object id %ld), database
%S_DBID.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7778 16 Suspect procedure %S_OBJID, database %S_DBID found. Cannot execute query.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7779 16 UNCERTIFIED object %S_OBJID, database %S_DBID accessed by CERTIFIED
object %S_OBJID, database %S_DBID. Cannot execute query.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7780 16 Procedure %S_OBJID, database %S_DBID with labels found UNCERTIFIED. Cannot
execute query.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7781 16 Suspect view %S_OBJID, database %S_DBID found. Cannot execute query.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7782 16 Remote procedure call from within CERTIFIED stored procedure %S_OBJID, database
%S_DBID not allowed. Cannot execute query.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
Number Severity Text and Explanation
Server Error Messages 7700 - 7799
1034
7783 10 Internal error -- server failed to do garbage collection on this procedure, id = %ld. Please
save the query tree and procedure text and inform the technical support. This is not a
critical error, so server continues processing.
Explanation: There was an error during procedure query tree compression. This is not
a critical problem as Adaptive Server can continue processing the procedure.
7784 16 Illegal escape character found. There are fewer bytes than necessary to form a valid
character.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7785 16 Attempting to create a table `%.*s', via select into, with column `%.*s' whose numeric
precision, %d, exceeds the maximum allowed precision (%d).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7786 16 Unable to turn role off since user is not a valid user in the current database.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
7787 16 Sensitivity column of view `%.*s' accessed. A view's sensitivity column is not user
accessible.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7788 10 WARNING: An explicit or implicit HOLDLOCK/NOHOLDLOCK was specified for
table `%.*s'; however, since this is an isolation level 0 scan, the
HOLDLOCK/NOHOLDLOCK is ignored.
Explanation: Refer to the writeup for this error.
7789 16 Unable to allocate work table for processing group by or distinct clause during query
optimization. Maximum limit (%d) of work tables is exceeded. Simplify the query and
retry.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7790 18 Internal error - Unable to remap cursors during recompilation. This is a non-fatal internal
error.
Explanation: During recompilation, Adaptive Server remaps declared cursors from the
old procedure header to the new header. This message means that an error is found during
remapping.
7791 16 Unable to remap lockid for table %.*s in database %S_DBID. Printing diagnostic
information: tobjp: 0x%x, lkr: 0x%x, rgtabid: %d.
Explanation: For temp tables and at times for user tables, the server needs to obtain the
object ID at run time when applying table locks. This error indicates that the server was
unable to obtain the ID for some reason.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1035
Server Error Messages 7900 - 7999
7792 16 An isolation level %d scan is being attempted on cursor `%.*s', but the cursor was
declared at isolation level %d. You must re-declare the cursor at isolation level %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7793 16 An isolation level '%d' scan is being attempted by an ad hoc query, but the query was
compiled in the batch at isolation level '%d'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7794 16 You cannot scan table '%.*s' at isolation level 0 because another process is running a
utility command that is incompatible with level 0 scans. Please retry later.
Explanation: Another process is running a DROP INDEX, ALTER TABLE,
TRUNCATE TABLE, REORG REBUILD, or CREATE CLUSTERED INDEX
command on the table.
7795 18 Internal error - Unable to process subqueries during transformations. Maximum limit
(%d) of subqueries is exceeded. Please save the DBCC TRACE(100) output and inform
technical support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7796 18 Internal error - Unable to process subqueries during transformations due to a corrupt
query tree. Please save the output from DBCC TRACE(100) and inform technical
support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Number Severity Text and Explanation
7901 16 Page %ld was expected to be the first page of a TEXT/IMAGE value.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7902 16 Data size mismatch occurred while checking TEXT/IMAGE values. The first page for
this value is: %ld. There were %ld bytes found, which is different from the expected data
length of %ld bytes.
Explanation: Refer to the writeup for this error.
Server Error Messages 7900 - 7999
1036
7903 16 Page %ld was expected to be a TEXT/IMAGE page. This occurred when link number
%ld was examined.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7904 10 The total number of TEXT/IMAGE pages in this table is %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7905 10 The number of rows in sysindexes for this table was %ld. It has been corrected to %ld.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7906 10 The number of data pages in sysindexes for this table was %ld. It has been corrected to
%ld.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7907 16 The status in the first page (%ld) of the no_log table %.*s and the status in the sysobjects
row, do not match.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7908 10 The table %.*s was created with the no_log option.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7909 10 A transaction involving the no_log table %.*s was undone. This may have left the table
in an inconsistent state. Rebuild the table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7910 16 Page %ld allocated (Alloc page: %ld Extent ID: %ld Alloc mask: 0x%x)
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7911 16 Page %ld deallocated (Alloc page: %ld Extent ID: %ld Alloc mask: 0x%x)
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7912 16 EXTID:%ld (Alloc page: %ld) is initialized. Extent follows:
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7913 16 PTNID=%d SPARE=%d OBJID=%ld RESERVE=0x%x FORWARD=0x%x
ALLOC=0x%x DEALLOC=0x%x IND ID=%d STATUS=0x%x
Explanation: This is an informational message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1037
7914 10 Allocation page %ld extid %ld is not referenced, but there are referenced pages within
this extent. Contact Technical Support for assistance on object %ld.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7915 10 Allocation page %ld extid %ld is referenced, but there are no referenced pages within
this extent. Contact Technical Support for assistnace on object %ld.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7916 10 Total (# alloc pages = %ld, # of alloc pages modified = %ld).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7917 16 Total (# pages allocated=%ld pages deallocated=%ld extents deleted=%ld).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7918 16 Alloc page %ld (pgs allocated=%ld pgs deallocated=%ld extents deleted=%ld).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7919 16 Fix_al not processed. Database needs to be in SINGLE USER mode.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7920 16 Processed %ld entries in the sysindexes for dbid %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7921 16 Found %ld bad entries in the sysindexes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7922 16 ***************************************************************
Explanation: This is an informational message or a message header. No action is
required.
7923 16 TABLE: %.*s OBJID = %ld
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7924 16 INDID=%ld FIRST=%ld ROOT=%ld SORT=%d
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7925 16 Indid : %d. %ld Index pages allocated and %ld Extents allocated.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 7900 - 7999
1038
7926 16 Data level: %d. %ld Data pages allocated and %ld Extents allocated.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7927 16 TOTAL # of extents = %ld
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7928 16 Index %.*s is not consistent; found %d leaf rows but %ld data rows. Drop and recreate
the index.
Explanation: Refer to the writeup for this error.
7929 16 Table has %d data rows.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7930 16 Table Corrupt: keys in left child do not precede the parent key; check left child page %ld.
Table Corrupt: keys in left child do not precede the parent key; check left child page %ld.
Explanation: Refer to the writeup for this error.
7931 16 Table Corrupt: keys in right child precede the parent key; check right child page %ld.
Explanation: There may be possible corruption in a database or a database object.
Consult the Error Messages and Troubleshooting Guide to see how to locate the table,
and run dbcc diagnostics.
7932 16 The indexes for `%.*s' are already correct. They will not be rebuilt.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7933 16 One or more indexes are corrupt. They will be rebuilt.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7934 16 The table `%.*s' has no indexes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7935 16 REINDEX received an exception - command aborted.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7936 10 Checktable on sysgams is not allowed.
Explanation: Check command syntax and semantics.
7937 16 The data in table `%.*s' is possibly corrupt - DBCC REINDEX aborted. Run DBCC
CHECKTABLE and report errors to a user with System Administrator (SA) role.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1039
7938 16 Table Corrupt: The oam entry for object %ld, indid %ld, alloc pg %ld, has a used count
of %d and an unused count of %d. The used count should be %d and the unused count
should be %d.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7939 16 Table Corrupt: The entry is missing from the OAM for object id %ld indid %d for
allocation page %ld.
Explanation: Refer to the writeup for this error.
7940 22 The counts in the OAM are incorrect. This implies that there are entries missing. Run
tablealloc utility with the FIX option on the table with the inaccurate OAM counts.
Explanation: Refer to the writeup for this error.
7941 16 Couldn't find table %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7942 10 The missing OAM entry has been inserted.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7943 10 Attempt to insert missing OAM entry failed.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
7944 10 *** NOTICE: Space used on the log segment is %s Mbytes, %s%%.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7945 10 *** NOTICE: Space free on the log segment is %s Mbytes, %s%%.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7946 10 *** NOTICE: Notification of log space used/free cannot be reported because the log
segment is not on its own device.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7947 16 The sortorder and character set ID's for index %d on this table were %d:%d in
sysindexes. They have been corrected to %d:%d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7900 - 7999
1040
7948 16 Page %ld, object %ld, index %d, level %d, was found with fixed-row status improperly
set. That status has been cleared by DBCC.
Explanation: This informational message is displayed by dbcc checktable or dbcc
checkdb (which calls dbcc checktable) when a page status bit in a page header is
set on when it should not be. This bit is normally set on when there are no
variable-length columns for this object (the rows are all fixed-length). If dbcc
checktable finds that this bit is set on and there are variable display rows, the bit
is turned off and the 7948 message is displayed. dbcc checktable (or dbcc checkdb)
corrects this problem so no further action is required.
7949 16 The number of pages used and unused for object %ld index %d on allocation page %ld
do not match the counts in the OAM entry.
Explanation: Refer to the writeup for this error.
7950 16 Unable to %.*s engine. Check sysengines count and max online engines config value.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7951 16 Data size mismatch occurred while checking a TEXT value. The first page for this value
is: %ld. There were %ld characters found, which is different from the expected length of
%ld characters.
Explanation: This error may be seen after upgrading from 11.x to 12.0 when tables
contain one or more text columns. Contact Sybase Technical Support to upgrade to a
version in which the problem is resolved.
7952 10 A TEXT value with an invalid MAGIC NUMBER has been found on page %ld. TEXT
values will no longer be checked for this table. Note because of this, the TEXT page count
will be inaccurate. Use DBCC FIX_TEXT to fix the TEXT values.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7953 10 Unable to acquire an exclusive lock on text page %ld. This text value has not been
recalculated. In order to recalculate those TEXT pages you must release the lock and
reissue the DBCC FIX_TEXT command.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7954 10 There are no TEXT pages in table %.*s to be updated.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7955 10 Not all of the TEXT pages in table %.*s have been successfully updated, however, DBCC
FIX_TEXT is restartable. Please issue the command again once any other errors have
been addressed.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1041
7956 16 Remapping utility - Column descriptor should have been remapped earlier. This is an
internal system error.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7957 25 Remapping utility - procedure is corrupted in Sysprocedures. Recreate this procedure.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7958 16 Remapping utility - a pointer exists in a tree when it should not.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7959 16 Remapping utility - unable to locate the given procedure %.*s in Sysprocedures.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7960 16 Remapping utility - Procedure needs to be recreated for this port.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7961 16 Remapping utility - Wrong kind of node passed to tree remapping. This is an internal
system error.
Explanation: Adaptive Server was unable to reclaim space following query remapping.
See the writeup for Error 7783 for more information.
7962 16 Upgrade requires the SQL Server to be booted in single user mode. Reboot the SQL
Server with the -m flag.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7963 16 Upgrade encountered a fatal error. Please check the SQL Server errorlog.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7964 14 Permission denied. You do not have the necessary role to run this command. Please
contact Sybase Technical Support for assistance in running this command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 7900 - 7999
1042
7965 10 The `fix' option has been ignored for this command. To use the `fix' option with system
tables, run the command from the database where the table is located. The database must
be in single user mode.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7966 20 The global space allocation report requires an exclusive lock on object 99. This process
does not hold this lock in database %d. This report is cancelled.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7967 20 Allocation page %ld in database %d does not hold the address lock required for
initializing the diagnostic bitmaps or correcting its allocation errors.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7968 20 The object allocation map for tabid %d indid %d is corrupt, therefore the optimized
report cannot be generated. Contact Technical Support for assistance.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7969 10 Allocation reports cannot be generated for object %ld in database %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7970 10 The default report option of %.*s is used for this run.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7971 10 The default fix option of %.*s is used for this run.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7972 10 The oam counts for objid %ld indid %d are corrected.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7973 10 The optimized report may generate erroneous messages due to the missing OAM entry.
Run the optimized report with the fix option, to correct this error.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
7974 16 ILLEGAL use of module %.*s. See the errorlog for detail information.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1043
7975 20 System catalog entrie(s) for Object %d, Database %d are corrupted.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7976 16 Object %d in database %d does not have any TEXT/IMAGE data.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7977 16 First page %ld and Root page %ld are not same.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7978 20 One or more text chain(s) for object %ld in database %ld is corrupt.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
7979 16 Text chain linkage corrupted for Page %ld of Object %ld.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7980 16 Unreferenced text chain found for page %ld, nextpage %ld, prevpage %ld.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
7981 16 The new transaction mode must be unchained, chained or anymode.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7982 16 The specified object `%.*s' is not a stored procedure in database `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7983 16 You must be either the system administrator (SA), the database administrator (dbo), or
the owner of this stored procedure to change its transaction mode.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
7985 16 Server name ’%.*s’ not found in system catalog.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 7900 - 7999
1044
7986 16 You can not change the mode of a remote stored procedure.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
7987 16 User named `%.*s' not found; check sysusers.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7988 16 The specified object `%.*s' is not found in database `%.*s'. Check sysobjects to make
sure you own the object.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7989 16 The serial allocation flag was found to be improperly set in allocation unit %ld, at extent
ID %ld, with alloc map = %d and objid = %ld. This flag has been cleared by DBCC.
Explanation: Refer to the detailed writeup for Error 7989 in the chapter titled “Error
Message Writeups”.
7990 16 Permission denied. User's operating system session label must dominate database
maxhold to use the DBCC command `%.*s'.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
7991 18 Label consistency check for database `%S_DBID' failed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7992 14 The user needs to be in the master database to execute this command.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
7993 18 Either the execution of the `DBCC SECURITY (LABEL_CHECK)' command failed or
one or more databases have been detected to have inconsistent security labels.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
7994 16 Database `%.*s' has references to other databases. Drop those references and try again
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
7995 14 Permission denied. Only the Database Owner (DBO) or a user with the System
Administrator (SA), System Security Officer (SSO), or Oper role can execute this
command for database `%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1045
7996 14 Permission denied. Object `%S_OBJID' not found.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7997 14 Permission denied. User's curwrite does not match the sensitivity label of object
`%S_OBJID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7998 14 Permission denied. Database `%S_DBID' not found.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
7999 14 Permission denied. User's curwrite does not match the sensitivity label of database
`%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 8000 - 8099
1046
Server Error Messages 8000 - 8099
Number Severity Text and Explanation
8002 15 Parameter number %d and subsequent parameters must be passed as `@name = value'.
Once the form `@name = value' has been used, all subsequent parameters must be passed
in the form `@name = value'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
8003 15 There are too many parameters in this CREATE PROCEDURE statement. The
maximum number is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
8004 16 Received an unrecognized datatype %d from TDS datastream.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
8005 15 Received a procedure name length of %d. The TDS datastream is incorrect.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
8006 20 SQL Server error detected by %S_MSG. Refer to the preceding %S_MSG message.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
8007 20 Unknown token returned by %S_MSG: %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
8008 16 Parameter no. %d, of type %d, did not have a valid value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
8009 16 Error encountered by %S_MSG. Please refer to %S_MSG messages for details.
Explanation: Refer to the detailed writeup for this message in the chapter titled “Error
Message Writeups”.
8010 16 datalen (%d) must be less than maxlen (%d) for rpc parameter %d
Explanation: Check your RPC parameters. There may be an inconsistency between
length and max length values.
8011 16 Parameter %d has datatype %s. This datatype is not valid for use in parameters for an
RPC.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1047
Server Error Messages 8200 - 8299
8012 16 Adaptive Server internal error: Received internal error %d from the remote server
’%S_SRVID’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
8013 16 A CTLIB operation failed during an RPC.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
8014 16 You cannot start a non-transactional RPC when the ’strict dtm enforcment’ option is
enabled for the session.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
8015 10 Adaptive Server has truncated parameter number %d passesd to rpc ’%.*s’ on server
’%.*s’. The remote server does not support character or binary data wider than 255 bytes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Number Severity Text and Explanation
8201 26 Keep count of descriptor (objid=%ld, dbid=%d) was expected to be %d. Instead %d was
found.
Explanation: Refer to the writeup for this error.
8203 26 Expected to find the descriptor for object %d in database %d in %s state.
Explanation: Refer to the writeup for this error.
8204 20 Expected to receive system catalog id. Instead %d was received.
Explanation: Refer to the writeup for this error.
8205 20 Invalid field token passed to descriptor (id = %d, field = %d).
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
8206 21 Object %d was not found in %s.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Server Error Messages 8200 - 8299
1048
8207 17 Couldn’t find an available descriptor for an object. Raise the value of the configuration
parameter ’number of open objects’ for more descriptors.
Explanation: Refer to the writeup for this error.
8208 21 Descriptor for object %d in database %d was notfound in the expected dbtable.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8209 26 Descriptor found was not expected to have %s state.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8210 21 Duplicate of work table descriptor found in the id hash table for temporary object %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8211 26 Mismatch found between the name and id descriptor hash table. Descriptor hashed by
name = 0x%0x and hashed by id = 0x%0x.
Explanation: Refer to the writeup for this error.
8213 20 Failed to acquire address lock on object %.*s
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
8215 14 An attempt was made to drop the DES of object %ld, which is not a user-defined object.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
8216 20 Failed to acquire table lock on object %.*s
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
8219 18 Couldn't compute lock promotion level in DES for object %d in database %d. Using
default level = %d.
Explanation: Refer to the writeup for this error.
8221 20 Couldn't find the identity column for object %.*s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
8222 20 Maximum rows per page value not found in the descriptor for table=%d, index=%d on
database %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run. (Not raised in 11.9.2)
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1049
8223 21 As part of a transaction rollback, an attempt was made to modify object '%S_OBJID ' in
database '%.*s', even though the current session is not holding an exclusive lock on that
object.
Explanation: The server encountered an internal error affecting all processes using this
database. Report the error to your SA.
8224 21 Internal error: could not save description of lightweight procedure '%.*s'.
Explanation: The server encountered an internal error affecting all processes using this
database. Report the error to your SA.
8225 16 Invalid object '%.*s' in dbid %d
Explanation: Check query and retry.
8226 16 Operation not allowed. System table '%.*s' cannot be bound/unbound.
Explanation: Invalid operation for this system table.
8227 16 Trying to bind/unbind an already bound/unbound object '%.*s' in database %d
Explanation: Illegal operation. Check object names in query.
8228 16 Cannot do an unbind at this time. The database %d is in use. Try doing unbind when there
are no users using the database.
Explanation: Illegal operation for a database in use.
8229 16 Trying to bind/unbind objects to dbid=%d. Bind/Unbind objects not allowed in master
and tempdb.
Explanation: Illegal operation for this database.
8230 16 Trying to turn on/off greedy allocation for object in database with dbid=%d. Turning
on/off greedy allocation for objects not allowed in databases master and tempdb.
Explanation: Illegal operation for this database.
8231 16 Operation not allowed. Cannot turn on/off greedy allocation for system table ’%.*s’.
Explanation: Illegal operation for this database.
8232 16 The server failed to record a version change for syscolumns in database ’%.*s’. The
version indicator should be %d. Due to this error, the database cannot be upgraded.
Explanation: Illegal operation for this database.
8233 16 %s operation is in progress on the object ’%.*s’ in database ’%.*s’. Please retry your
query later.
Explanation: Illegal operation for this database.
8234 16 %s operation is in progress on the object ’%.*s’ in database ’%.*s’. Please retry your
query later.
Explanation: Illegal operation for this database.
Number Severity Text and Explanation
Server Error Messages 8400 - 8499
1050
Server Error Messages 8400 - 8499
Number Severity Text and Explanation
8401 21 Object with id of %ld was not found in database number %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8402 21 Index row for object %ld (index id %d) was not found in database %d.
Explanation: Refer to the writeup for this error.
8403 21 Index tag structure doesn't contain the search mode executed.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
8404 21 Index tag structure indicates fast and slow search modes.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator.
8405 21 No modify lock was acquired for an index row %s.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8406 21 Insert of sysindexes row failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8407 21 Delete of sysindexes row failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8408 21 Didn't expect to find active modify lock for sysindexes.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8409 21 Invalid status found in sysindexes tag structure. Expected status: %s.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
CHAPTER 6 Adaptive Server Error Messages
1051
8410 21 Expected to find search lock during sysindexes scan.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8411 21 Invalid setup status found in sysindexes Manager during a call to: %s.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8412 21 No object id specified in sysindexes Manager call to: %s.
Explanation: This error is raised when the server routine identified in the message text
attempts to update the database’s sysindexes table but is unable to do so. Run dbcc
checktable on sysindexes. If the dbcc check shows errors, or if the 8412 error persists,
contact Sybase Technical Support.
8413 25 Update of sysindexes failed.
Explanation: Internal error only. No action required.
8414 21 Copy of sysindexes row failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8415 21 Unexpected value `%d' returned from lock manager after waiting for lock on page %ld,
dbid %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8416 20 Invalid scan type %d specified
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
8417 20 Internal error occurred while running the sysindexes exerciser.
Explanation: Internal error affecting the current process. Contact your SA.
8418 20 Invalid index descriptor field (%d) specified within sysindexes manager.
Explanation: Internal error affecting the current process. Contact your SA.
8419 21 Could not find index descriptor for objid %d, indid %d in dbid %d.
Explanation: Internal error affecting the current process. Contact your SA.
8420 20 Could not install index descriptor for objid %d, indid %d in dbid %d.
Explanation: Internal error affecting the current process. Contact your SA.
8421 20 Invalid input to sysindexes manager. Expected valid session descriptor for sysindexes
system table.
Explanation: Internal error affecting the current process. Contact your SA.
Number Severity Text and Explanation
Server Error Messages 8400 - 8499
1052
8422 21 Indid mismatch between index descriptor 0x%x (indid %d) and page 0x%x (indid %d)
for objid %d in dbid %d.
Explanation: Internal error affecting the current process. Contact your SA.
8423 21 Expected table descriptor to be set for objid %d in dbid %d.
Explanation: Internal error affecting the current process. Contact your SA.
8424 17 Cannot find an available index descriptor for an index. Increase the value of 'number of
open indexes'. If sp_configure fails due to lack of index descriptors, edit the configuration
file and restart the server.
Explanation: Check the installation and configuration guides for assistance with the
recommended task.
8425 21 Couldn't find an available index descriptor for system objects.
Explanation: Internal error affecting the current process. Contact your SA.
8426 26 Index descriptor 0x%x is already installed on the hash table for objid %d, indid %d in
dbid %d.
Explanation: Internal locking/synchronization rule was broken. Report the error to your
SA, and restart the server.
8427 20 Invalid input to sysindexes manager. Expected to have dbid or dbtable pointer set
Explanation: Internal error affecting the current process. Contact your SA.
8428 26 Unexpected keep count %d of index descriptor. Expected %d.
Explanation: Internal locking/synchronization rule was broken. Report the error to your
SA, and restart the server.
8429 20 Object with objid %d in dbid %d is not a table.
Explanation: Internal error affecting the current process. Contact your SA.
8430 10 Did not find table descriptor linked to process slot structure 0x%x when SQL Server tried
to release it.
Explanation: Internal error affecting the current process. Contact your SA.
8431 20 Invalid transaction descriptor passed to the sysindexes manager internal function
Explanation: Internal error affecting the current process. Contact your SA.
8432 20 Invalid object descriptor passed to the sysindexes manager internal function.
Explanation: Internal error affecting the current process. Contact your SA.
8433 20 Table descriptor (0x%x) for objid %d in dbid %d is already linked to another transaction.
Explanation: Internal error affecting the current process. Contact your SA.
8434 20 Invalid initialization flag %d specified within sysindexes manager.
Explanation: Internal error affecting the current process. Contact your SA.
8435 26 Expected to find the index descriptor for objid %d indid %d in dbid %d, in a %s state
(found state %d instead).
Explanation: Internal locking/synchronization error. Contact your SA and restart the
server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1053
Server Error Messages 8500 - 8599
8436 26 Index descriptor found was not expected to be in a %s state.
Explanation: Internal locking/synchronization error. Contact your SA and restart the
server.
8437 20 Update failed. SQL Server could not find field '%d' within index descriptor/buffer.
Explanation: Internal error affecting the current process. Contact your SA.
8438 21 Updating wrong indexrow in dbid %d. Objid for actual row updated is %ld, objid for
intended row was %ld. Index id for intended row was %d. Index page is %ld, field
updated is %d. Index row address is %0x, row number is %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
8439 16 Cannot install an index descriptor for an index for objid %d as a dbshutdown for the dbid
%d is in progress.
Explanation: Illegal operation for this database at this time. Retry later.
8440 21 Internal error. DBINFO update at offset %d bytes for length %d bytes will exceed the
current size, %d bytes, of DBINFO. DBINFO update in dbid %d failed.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
Number Severity Text and Explanation
8501 26 Object id's are not the same during an abort: %d and %d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8502 21 Invalid record type passed to abort: %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Server Error Messages 8600 - 8699
1054
Server Error Messages 8600 - 8699
Number Severity Text and Explanation
8601 20 Process %d tried to keep the PSS for process %d when it already had the PSS for process
%d kept.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
8602 16 Unable to initialize worker thread %x because parent %x has an invalid PSS.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
8603 16 Warning: worker thread %x already has a PSS allocated; initialization will proceed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
8604 16 An attention condition occurred in worker thread %x. The last return value is %d, and the
last recorded error was %d. Terminating the worker thread.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
8605 10 pss = 0x%lx is on the free list, but its p3stat flag (0x%x) does not have P3_PSS_FREE
bit on.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
8606 10 pss = 0x%lx is marked free but has a non zero value for pkspid (%d).
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
8607 10 Illegal value of pspid (%d) for pss = 0x%lx. pspid value should be between %d and %d.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
8608 18 pss=0x%lx has been marked sick. pss->p3stat=0x%lx pss->pspid=%d pss->pkspid=%d
pss->pmasterxact=0x%lx. There might be open xdes/sdes associated with the pss. Please
report this problem to Sybase Tech. Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
CHAPTER 6 Adaptive Server Error Messages
1055
Server Error Messages 8700 - 8799
Server Error Messages 8800 - 8899
Number Severity Text and Explanation
8701 26 Sitebuf has invalid state or keepcount. sitebuf=0x%lx, state=%d, keepcount=%ld.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8702 26 Sitebuf has invalid state. sitebuf=0x%lx, state=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8703 26 Invalid keep count in sitebuf. sitebuf=0x%lx, keepcount=%ld.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8704 26 Could not get the address lock. address=0x%lx, status=%d.
Explanation: Refer to the writeup for this error.
8705 26 Remotely started site handler.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8706 26 Invalid keep count in sitebuf. sitebuf=0x%lx, keepcount=%ld, lcfreed=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
8801 26 Logconn has invalid state or keepcount. logconn=0x%lx, state=%d, keepcount=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8802 26 Logconn has invalid state. logconn=0x%lx, state=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Server Error Messages 8900 - 8999
1056
Server Error Messages 8900 - 8999
8803 26 Missing sitebuf for siteid %d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8804 26 Packet acknowledgment is neither read nor write. rdwr=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8805 26 Invalid set parameter to lc_wconnstat. set=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8806 26 Corrupted pre-read data list in lc__flush. logconn=0x%lx, dtbeg=0x%lx, dtend=0x%lx.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
Number Severity Text and Explanation
Number Severity Text and Explanation
8901 26 Databuf has invalid state. databuf=0x%lx, state=%ld.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8902 26 Logconn has invalid state or keepcount. logconn=0x%lx, state=%d, keepcount=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8903 26 Invalid state in logconn. logconn=0x%lx, state=%d.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
8904 26 Invalid state in databuf or corrupted databuf chain. databuf=0x%lx, state=%ld,
dnext=0x%lx.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
CHAPTER 6 Adaptive Server Error Messages
1057
Server Error Messages 9000 - 9099
Number Severity Text and Explanation
9001 20 Process %d has requested a memory size %d that is greater than the memory size %d in
the disk buffer 0x%X, dbid %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9002 20 Process %d is accessing disk buffer 0x%X, in dbid %d that has been freed. The current
status of the DSKBUF is 0x%X.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9003 20 Could not start I/O for request %S_BLKIOPTR.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9004 20 I/O error detected on disk buffer 0x%X for page request %ld, dbid %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9005 20 Process %d is requesting an illegal I/O type of 0x%x.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9006 20 Process %d is attempting to free a disk buffer that is already freed. Disk buffer address
0x%X, dbid %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Server Error Messages 9100 - 9199
1058
Server Error Messages 9100 - 9199
Number Severity Text and Explanation
9101 16 The total size of all parameter values for stored procedure `%.*s' exceeds maximum size
(%d bytes) allowed for replication. Stored procedure `%.*s' is not replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9102 16 Failed to convert the %s log record into row format for database `%.*s', XACT ID
%S_RID, RID %S_RID. Information associated with the %s log record is not replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9103 16 Failed to send the %s log record for database `%.*s', XACT ID %S_RID, RID %S_RID.
Information associated with the %s log record is not replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9104 16 Cannot identify the object on the %s log record for database `%.*s', XACT ID %S_RID,
RID %S_RID. Information associated with the %s log record is not replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9105 16 A missing log record indicates a prematurely truncated log or a corrupt log. The %s log
record in database `%.*s', XACT ID %S_RID, is not replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9106 10 The deferred insert (INOOP) log record referenced by the insert indirect (INSIND) log
record was not found as expected at RID %S_RID.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9107 16 Unexpected function return value %d while processing the %s log record of database
`%.*s', XACT ID %S_RID, RID %S_RID. The %s log record may not have been
replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9108 10 Number of qualifiers supplied to the DBCC LOGTRANSFER command exceeds limit
of %d. The DBCC LOGTRANSFER command is not executed.
Explanation: Check command syntax and semantics.
CHAPTER 6 Adaptive Server Error Messages
1059
9109 10 Cannot find user name for user ID %d while sending the %s log record for database
`%.*s', XACT ID %S_RID, RID %S_RID. The user ID will be used instead of the user
name.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
9110 10 Found an ENDXACT log record before finding an expected INSERT log record in
database `%.*s', XACT ID %S_RID, RID %S_RID.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
9111 10 Failed to send the LTM truncation point information for database `%.*s'. The DBCC
GETTRUNC command fails during execution.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9112 16 The DBCC LOGTRANSFER command must be invoked with at least %d parameters.
The DBCC LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9113 16 `%.*s' is not a valid QUALIFIER for the DBCC LOGTRANSFER command. The
DBCC LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9114 16 `%.*s' is not a valid VERB for the DBCC LOGTRANSFER command. The DBCC
LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9115 16 `%.*s' is not a valid COMMAND for the DBCC LOGTRANSFER command. The
DBCC LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9116 16 `%d' is not a valid numeric value for the specified QUALIFIER. The DBCC
LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9117 16 The DBCC LOGTRANSFER command was invoked with an invalid combination of
QUALIFIERs. The DBCC LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9118 16 The specified COMMAND requires additional QUALIFIERS. The DBCC
LOGTRANSFER command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 9100 - 9199
1060
9119 17 Execution of the the %s command fails due to insufficient memory.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9120 16 The log transfer context for database `%.*s' has not been reserved with the DBCC
LOGTRANSFER (`reserve', `context') command. The specified DBCC command is not
executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9121 16 The log transfer context for the current database is already reserved by SQL Server
process %d. The log transfer context for the current database is not reserved.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9122 21 The log transfer process lost its connection to the LTM for database `%.*s'. Once the
LTM re-establishes the connection, replication will continue with no data loss.
Explanation: This is an informational message. The log transfer process encountered a
broken connection. The LTM will re-establish the connection and replication will
continue with no data loss.
9123 17 Unable to set a wakeup alarm for the log transfer process. The log transfer scan of
database `%S_DBID' will not honor the specified timeout of %d seconds.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9124 16 INTERNAL CODING ERROR. Log record ID %d is not valid. Please contact Sybase
Technical Support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9125 16 Usage: DBCC SETTRUNC(`ltm', { `valid' | `ignore' | `pageid', page number })
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9126 16 Usage: DBCC GETTRUNC()
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9127 16 INTERNAL CODING ERROR. The building of an internal data structure required more
memory than anticipated. Please contact Sybase Technical Support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9128 16 Ran out of memory trying to send an UPDATE command's DELETE/INSERT log record
pair for database `%.*s', XACT ID %S_RID, RID %S_RID. The %s log record is not
replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1061
9129 16 Unable to determine the end of the log for database `%.*s'. The log transfer scan of
database `%.*s' is aborted.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9130 16 The BEGINXACT log record referenced by the CHECKPOINT log record for database
`%.*s', XACT ID %S_RID, RID %S_RID, was not found at RID %S_RID as expected.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9131 21 The log transfer context for the current database is already reserved by your SQL Server
process. The DBCC LOGTRANSFER (`reserve', `context') command is ignored.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
9132 16 Failed to write the log record for the execution of stored procedure `%.*s' in database
`%.*s'. Stored procedure `%.*s' is not replicated.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9133 16 The SQL Server was not started with the proper command line option to enable
Replication Server support. The DBCC command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9134 16 The DBCC LOGTRANSFER (`setqual', ...) command was invoked with parameters of
incorrect type. The DBCC LOGTRANSFER (`setqual', ...) command is not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9135 16 Usage: DBCC LOGTRANSFER(`scan', { `normal' | `repeat' | `continue' })
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9136 16 Unable to find the RID of the last ENDXACT or CHECKPOINT log record. The log
transfer context for the current database is not reserved.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9137 16 LTM trunc. point not yet established with DBCC SETTRUNC(). Until the LTM trunc.
point is established, changes to the object `%.*s' may not be replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9138 16 Even though Replication Server support is disabled, database `%S_DBID' contains a
valid LTM trunc. point which prevents the complete truncation of all expendable log
pages.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
Server Error Messages 9100 - 9199
1062
9139 17 Failed to free allocated but unused memory in order to satisfy memory allocation request.
Memory allocation request fails.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9140 17 Memory allocator used for Replication Server support failed to fulfill memory allocation
request.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9141 16 The stored proc. `%.*s' associated with the %s log record in database `%.*s', XACT ID
%S_RID, RID %S_RID, was dropped after the log record was written. The %s log record
is not replicated.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9142 16 Usage: DBCC REPLICATE_TXTCOL (objid, colid, { always_replicate |
replicate_if_changed | do_not_replicate } )
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9143 16 `%.*s' is not a valid replication status. The DBCC REPLICATE_TXTCOL command is
not executed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9144 16 The requested column cannot be located. Check the objid and colid specified. The DBCC
REPLICATE_TXTCOL command is not executed.
Explanation: Check the column ID and object ID specified in the command.
9145 16 The datatype of the specified column must be TEXT, IMAGE, or offrow object. The
DBCC REPLICATE_TXTCOL command is not executed.
Explanation: Specified column is not TEXT or IMAGE. User should recheck the
column id specified.
9146 20 The excution of DBCC REPLICATE_TXTCOL failed due to an internal error. Please
contact your System Administrator (SA) for help.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9147 16 Replication Not Enabled: Replication on table %.*s in database %.*s, has not been
enabled yet. Run sp_setreplicate or sp_setrepcol before calling DBCC
REPLICATE_TXTCOL, the DBCC REPLICATE_TXTCOL command is not executed.
(objid %ld)
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1063
Server Error Messages 9200 - 9299
9148 20 Replication server could not send log records for log version change processing in
database `%.*s' because the log processing functions returned internal error %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9149 10 LTM Truncation point has not been established with DBCC SETTRUNC. Changes to the
objects in the database may not be replicated until the truncation point is set.
Explanation: This informational message requires corrective action as indicated.
9150 16 The log transfer context for the current database cannot be reserved because the current
database has been enabled for a Rep Agent Thread.
Explanation:
9151 16 Permission denied. User cannot execute the built-in function '%.*s' in database ' %d'.
Explanation: Check login/role permissions.
9152 16 The data at (%d, %d) has been truncated because the lti version level does not support
wider data.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
9153 16 The data at (%d, %d) is too wide to be handled by the current lti version level.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
9154 16 Skipping (%d, %d) because it contains data that is wider than the lti version level allows.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
9201 20 %S_REPAGNT: Could not map OAM Page (%d) to object id, current marker (%d, %d).
Explanation: Internal error, affects current process. Contact your SA.
9202 20 %S_REPAGNT: Nested replicated stored procedure detected. Transaction log may be
corrupt. Please contact SYBASE Technical Support. (current marker = %d, %d)
Explanation: Internal error, affects current process. Contact your SA.
Server Error Messages 9200 - 9299
1064
9203 20 %S_REPAGNT: Encountered an End Transaction that was not in abort state while locating
after image for Delete at (%d, %d), transaction = (%d, %d).
Explanation: Internal error, affects current process. Contact your SA.
9204 20 %S_REPAGNT: Could not locate schema for object with id = (%d), current marker (%d ,
%d).
Explanation: Internal error, affects current process. Contact your SA.
9205 20 %S_REPAGNT: A replicated End Stored Procedure Execution log record was found with
out a Begin. Transaction log may be corrupt. Please contact SYBASE Technical Support.
objid = (%d), current marker = (%d, %d)
Explanation: Internal error, affects current process. Contact your SA.
9206 20 %S_REPAGNT: Error initializing the Rep Agent. Could not set affinity to engine (% d).
Explanation:
9207 20 %S_REPAGNT: Could not re-read XCMDTEXT log record at (%d, %d), current marker
(%d , %d).
Explanation: Internal error, affects current process. Contact your SA.
9208 20 %S_REPAGNT: Update detected within a subscribable function. Transaction log may be
corrupt. Please contact SYBASE Technical Support. (current marker = (%d, %d)).
Explanation: Internal error, affects current process. Contact your SA.
9209 20 %S_REPAGNT: Missing datarow in TEXT/IMAGE insert log record. Transaction log may
be corrupt. Please contact SYBASE Technical Support. (current marker = (%d, %d)).
Explanation: Internal error, affects current process. Contact your SA.
9210 20 %S_REPAGNT: Fatal error from CT-Lib. (CT-Lib command = %s, return status = %d).
Explanation: Internal error, affects current process. Contact your SA.
9211 20 %S_REPAGNT: Received the following error message from the Replication Server: Msg
%ld. %.*s.
Explanation: Internal error, affects current process. Contact your SA.
9212 20 %S_REPAGNT: Received the following communications error message: Msg %s: %.*s.
Explanation: Internal error, affects current process. Contact your SA.
9213 16 %S_REPAGNT: The version of this Rep Agent, is not supported by the Replication Server
specified. After fixing this problem, restart the Rep Agent for this database. (Rep Agent
version = %d, Rep Server version = %d, Rep Server = %.*s).
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
9214 16 %S_REPAGNT: Failed to connect to Replication Server. Please check the Replication
Server, username, and password specified to sp_config_rep_agent. RepSvr = %.*s, user =
%. *s).
Explanation: Check your replication environment as recommended.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1065
9215 16 %S_REPAGNT: The Secondary Truncation Point is not valid. Please make sure that the
Secondary Truncation Point is valid, and then restart the Rep Agent Thread for this data
base.
Explanation: Take recommended action.
9216 10 %S_REPAGNT: The Rep Agent Thread will retry the connection to the Replication Server
every %d second(s). (RepSvr = %.*s).
Explanation: Informational message.
9217 10 %S_REPAGNT: Trace log file set to `%s'.
Explanation: Informational message.
9218 16 Database %S_DBID has not been enabled yet for an integrated Rep Agent Thread. Run
sp_enable_rep_agent() to enable the database.
Explanation:
9219 20 %S_REPAGNT: Internal coding error.
Explanation: Internal error, affects current process. Contact your SA.
9220 16 %S_REPAGNT: The Rep Agent Thread context for database %S_DBID has already been
reserved by another session.
Explanation:
9221 16 Parameter count/type mismatch. Please check the number and types of the parameters
passed to the builtin function, '%.*s'.
Explanation:
9222 16 You must be SA, DBO, or have REPLICATION role to execute the builtin function, '% .*s'.
Please check your current roles.
Explanation:
9223 16 Unknown operation, '%.*s', specified to builtin function rep_agent_admin(). Please check
parameter spelling and placement.
Explanation:
9224 16 Unknown category, '%.*s', specified to builtin function rep_agent_config(). Please check
parameter spelling and placement.
Explanation:
9225 16 Unknown property, '%.*s', specified to builtin function rep_agent_config(). Please check
parameter spelling and placement.
Explanation:
9226 16 Database %S_DBID has already been enabled to use a Rep Agent thread.
Explanation:
9227 17 %S_REPAGNT. Could not allocate memory to spawn Rep Agent thread. (size=%d)
Explanation:
9228 17 %S_REPAGNT. Could not spawn Rep Agent Thread.
Explanation: There may be a memory-related or other resource problem.
Number Severity Text and Explanation
Server Error Messages 9200 - 9299
1066
9229 16 %S_REPAGNT. Could not change to database, %S_DBID.
Explanation: Check syntax and input data.
9230 16 The Rep Agent Thread for database, %S_DBID, is not running. Please retry this command
after starting the Rep Agent Thread for this database.
Explanation:
9231 16 %S_REPAGNT. The Connect Dataserver name was not specified via 'sp_start_rep_agent
', nor was it found in sysattributes, or sysservers. Make sure that you have done a 'sp_ad
dserver <svr>, local'.
Explanation: When generating the 'connect source' command for Replication Server, the
connect dataserver attribute could not be determined. You can set connect dataserver
attribute directly with sp_start_rep_agent, or configure it via sp_config_rep_agent. This is
only necessary if the requested dataserver is other than the current dataservername. You
must also do an 'sp_addserver , local' in all cases.
9232 16 %S_REPAGNT. The Connect Database name was not found in sysattributes, or
sysdatabases.
Explanation: When generating the 'connect source' command for Replication Server, the
connect dataserver attribute could not be determined. You can set connect dataserver
attribute directly with sp_start_rep_agent, or configure it via sp_config_rep_agent. This is
only necessary if the requested dataserver is other than the current dataservername.
9233 17 %S_REPAGNT. Could not allocate %d bytes from the procedure cache. Please retry the
last operation when more memory is available, or re-configure the server with a larger
procedure cache.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9234 17 %S_REPAGNT. Could not start Rep Agent Thread.
Explanation:
9235 17 Could not allocate memory for gettrunc. Please retry gettrunc() later when more memory
is available, or re-configure the server with a larger procedure cache.
Explanation:
9236 11 Unknown dbid '%d' specified. Please check the dbid specified.
Explanation: Check the value of the database ID specified in the query.
9237 16 %S_REPAGNT. The row for %.*s could not be found in sysattributes. Please check the
configuration properties for this database with 'sp_config_rep_agent ' or
'sp_help_rep_agent'.
Explanation: This message is displayed when you have not configured a required
RepAgent attribute.
9238 16 Settrunc() is not permitted when a Rep Agent Thread is currently running on the database.
Explanation:
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1067
9239 17 %S_REPAGNT: Could not allocate a Procedure Cache for the Rep Agent Thread. Try
restarting the Rep Agent Thread after freeing up, or allocating a larger Procedure Cache.
Explanation:
9240 17 %S_REPAGNT: Could not allocate an alarm. Try restarting this Rep Agent Thread after
freeing up some alarms, or restart the server with more alarms allocated.
Explanation:
9241 20 %S_REPAGNT: Failure initializing the Rep Agent Context.
Explanation: Internal error, affects current process. Contact your SA.
9242 20 %S_REPAGNT: Underflow or overflow of state stack occurred.
Explanation: Internal error, affects current process. Contact your SA.
9243 20 %S_REPAGNT: Interface error with the Replication Server. The Rep Agent may not be
compatible with the Replication Server.
Explanation: Internal error, affects current process. Contact your SA.
9245 20 Failure during update/insert/delete from sysattributes.
Explanation: Report this error to the System Administrator so dbcc diagnostics can be
run.
9249 17 Failed to reserve context in shared mode.
Explanation: Replication error. Contact your SA.
9250 10 %S_REPAGNT Failed to open trace file, '%.*s'. Trace messages will go to stdout of the
server.
Explanation: Informational message.
9251 20 %S_REPAGNT Write to trace file, '%.*s', failed
Explanation: Internal error, affects current process. Contact your SA.
9252 20 Internal coding error in builtin function, '%.*s'.
Explanation: Contact Sybase Technical Support.
9253 20 Failed to get secondary truncation point.
Explanation: Internal error, affects current process. Contact your SA.
9254 20 %S_REPAGNT: Could not locate schema version for object id '%d' in the transaction log.
Explanation: Internal error, affects current process. Contact your SA.
9255 20 %S_REPAGNT: Rewrite of PREPARE log record failed at (%d, %d).
Explanation: Internal error, affects current process. Contact your SA.
9256 20 %S_REPAGNT: Could not read INOOP log record at (%d, %d), current marker (%d, %d).
Explanation: Internal error, affects current process. Contact your SA.
9257 20 %S_REPAGNT: Could not read ROWIMAGE log record at (%d, %d), current marker
(%d, % d).
Explanation: Internal error, affects current process. Contact your SA.
Number Severity Text and Explanation
Server Error Messages 9200 - 9299
1068
9258 20 %S_REPAGNT: Could not re-read EXECBEGIN log record at (%d, %d), current marker
(% d, %d).
Explanation: Internal error, affects current process. Contact your SA.
9259 20 %S_REPAGNT: Could not read TEXTINSERT/INOOPTEXT log record at (%d, %d),
current marker (%d, %d).
Explanation: Internal error, affects current process. Contact your SA.
9261 20 %S_REPAGNT: This Rep Agent Thread is aborting due to an unrecoverable
communications or Replication Server error.
Explanation: Internal error, affects current process. Contact your SA.
9262 16 Failed to start a Rep Agent Thread for the database specified because a Rep Agent Thread
is already running for that database.
Explanation: Check replication environment.
9263 10 %S_REPAGNT: Turning Batch mode on.
Explanation:
9264 10 %S_REPAGNT: Turning Batch mode off.
Explanation: This is an informational message.
9265 10 %S_REPAGNT: Ignoring LTL errors.
Explanation: This is an informational message.
9266 10 %S_REPAGNT: Error in passthru packet: '%.*s'.
Explanation:
9267 20 %S_REPAGNT: A security mechanism was specified, but no security service(s) were
specified. Please use 'sp_config_rep_agent' to specify which security service(s) to use
when connecting to the Replication Server.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9268 20 %S_REPAGNT: The security service '%.*s' was specified, but it is not supported by the
security mechanism. Please check the security service(s) and/or security mechanism
specified to sp_config_rep_agent. (CT-lib error %d).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9269 20 %S_REPAGNT: Failure initializing the security mechanism '%.*s'. Please check the
'security mechanism' specified to sp_config_rep_agent. (CT-lib error % d).
Explanation: Check the security mechanism that was specified for connections to the
Replication Server.
9270 10 %S_REPAGNT: Using default security mechanism.
Explanation: This is an informational message. No action is required.
9271 20 %S_REPAGNT: Failure initializing the default security mechanism. Please check that a
security mechanism has been properly configered. (CT-lib error %d)
Explanation: Check the default security mechanism set up for Replication Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1069
9272 20 %S_REPAGNT: Failure specifying the keytab filename. Please check that the keytab file
'%.*s', exists and is accessable. (CT-lib error %d).
Explanation: Check the Replication Server setup indicated in the message.
9273 10 %S_REPAGNT: Using default keytab file because security mechanism requir es a keytab
file, but the no keytab file was specified at server startup.
Explanation: This is an informational message. No action is required.
9274 16 Cannot disable the RepAgent thread for database %S_DBID, because the RepAgent is still
running. Please stop the RepAgent on that database with 'sp_stop _rep_agent' before re-
issuing 'sp_config_rep_agent disable'.
Explanation: Command failed due to invalid or illegal request. Take corrective action
indicated by the message.
9275 20 %S_REPAGNT: Could not locate the after image for the DELETE log record at (%d, %d).
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9276 20 Error executing the command 'set proxy %.*s'.
Explanation: Failure to execute the command 'set proxy %.*s' on the Replication Server.
Report the error to your System Administrator.
9277 20 %S_REPAGNT: The security mechanism configured requires a keytab file. Check that the
a keytab file was specified at server startup, and that 'use security services' has been
configured.
Explanation: The RepAgent is initializing security services, and the mechanism needs a
keytab file. However it cannot locate the keytab file, either because a keytab file was not
specified at server startup, or because 'use security services' has not been configured yet.
9278 0 %S_REPAGNT: Encountered a feature that cannot be supported by the current Replication
Server version. Upgrade the Replication Server version to a higher level, or use
sp_config_rep_agent to set the ’skip unsupported features’ option.
Explanation: This is an informational message. No action is required.
9279 0 %S_REPAGNT: Connecting to a Replication Server that supports a lower LTL version.
Features that are not supported by the lower LTL version may cause the RepAgent to
shutdown. Set the ’skip unsupported features’ configuration option to prevent shutdown.
Explanation: This is an informational message. No action is required.
9280 10 %S_REPAGNT: Unable to start RepAgent on database %S_DBID, because that database
has not been recovered and/or is not online. Please start the RepAgent manually using
sp_start_rep_agent when it is ready.
Explanation: This is an informational message. No action is required.
9281 10 %S_REPAGNT: The Replication Server LTL version should be at least %d for full support
of features. (Replication server LTL version %d, Rep Agent LTL version %d).
Explanation: This is an informational message. No action is required.
Number Severity Text and Explanation
Server Error Messages 9300 - 9399
1070
Server Error Messages 9300 - 9399
9282 20 %S_REPAGNT: No free file descriptors available.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9283 20 %S_REPAGNT: Aborting because a cross database stored procedure execution was
detected. This event needs to be manually applied, and skipped before restarting the
RepAgent. (sproc dbid %d, sproc objid %ld, current marker (%d, %d))
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9284 17 %S_REPAGNT. Could not allocate %d bytes from heap memory. You may need to re-
configure with more memory.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9285 17 %S_REPAGNT. The data at (%d, %d) is truncated because the Replication Server,
’%.*s’, cannot handle wide data. Check the ’data limits filter mode’ configuration
parameter.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9286 17 %S_REPAGNT. The data at (%d, %d) is too wide for the Replication Server, ’%.*s’, to
handle. Check the ’data limits filter mode’ configuration parameter.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9287 17 %S_REPAGNT. The data at (%d, %d) is skipped because it contains data wider than the
Replication Server, ’%.*s’, can handle. Check the ’data limits filter mode’ configuration
parameter.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
9301 23 Inconsistent SLID representation in object metadata.
Explanation: The database may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
CHAPTER 6 Adaptive Server Error Messages
1071
9302 18 Unexpected EX_CONTROL exception has been raised inside the Syslabels Manager:
error = %d, severity = %d, state = %d
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9303 18 Syslabels Manager: Insert into `%S_DBID.dbo.syslabels' failed during call to %s().
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9304 20 Internal MAC sub-system error. Corrupted master SLID value found. DO NOT USE THIS
SERVER AND ITS ASSOCIATED DEVICES UNTIL THE CAUSE OF THIS ERROR
HAS BEEN ELIMINATED.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9305 20 Internal MAC sub-system error. Corrupted database SLID value found in database `%d'.
DO NOT USE THIS DATABASE UNTIL THE CAUSE OF THIS ERROR HAS BEEN
ELIMINATED.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9306 20 Bad database id (`%d') found. Run DBCC checktable on sysdatabases and DBCC checkdb
on all databases used by this query.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9307 20 Internal MAC sub-system error. MSLID to DBSLID conversion failed in database `%d'.
DO NOT USE THIS DATABASE UNTIL THE CAUSE OF THIS ERROR HAS BEEN
ELIMINATED.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9308 20 Internal MAC sub-system error. DBSLID to MSLID conversion failed in database `%d'.
DO NOT USE THIS DATABASE UNTIL THE CAUSE OF THIS ERROR HAS BEEN
ELIMINATED.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9309 20 Internal MAC sub-system error. DO NOT USE THIS SERVER AND ITS ASSOCIATED
DEVICES UNTIL THE CAUSE OF THIS ERROR HAS BEEN ELIMINATED.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
Number Severity Text and Explanation
Server Error Messages 9300 - 9399
1072
9310 20 Internal MAC sub-system error. Label comparison failed. DO NOT USE THIS SERVER
AND ITS ASSOCIATED DEVICES UNTIL THE CAUSE OF THIS ERROR HAS BEEN
ELIMINATED.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9311 21 Syslabels Manager: Trying to boot the server without initializing values of Data_High and
Data_low.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
9312 21 Syslabels Manager: Current process label, or label of the MASTER DEVICE do not match
with value of Data_High stored in the server.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
9313 21 Syslabels Manager: Attempt to change values of Data_High and/or Data_Low is not
allowed.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
9314 14 Only a user with the System Administrator (SA), System Security Officer (SSO), or Oper
role or the Database Owner (DBO) can execute this command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
9315 18 Security label specified in the syslabels row with db_slid `%d' is not a valid label in the
underlying trusted OS.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9316 18 Security label specified in the syslabels row with db_slid `%d' is not dominated by Data
High.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9317 18 Security label specified in the syslabels row with db_slid `%d' does not dominate Data
Low.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9318 10 Database `%S_DBID' passed Syslabels Check.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1073
9319 10 Database `%S_DBID' passed Database Maxhold Consistency Check.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9321 18 Corrupt security label encountered in database `%S_DBID'. Marking database as having
inconsistent labels and checking the master database for possible related corruption.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9322 18 Maxhold inconsistency detected in database `%S_DBID'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9324 21 Corrupt security labels found in the master database. Shutting down the server.
Explanation: Adaptive Server encountered an internal error affecting all processes in the
current database. Report the error to your System Administrator. Adaptive Server must be
restarted and dbcc diagnostics run.
9325 18 Internal error. Failed to clear database `%S_DBID' of its security label inconsistency
status.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9326 18 Internal error. Failed to mark database `%S_DBID' as having inconsistent security labels.
Marking it as suspect instead.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9328 16 Inconsistency found in Syslabel Manager Cache. Contact a user with System
Administrator (SA) role.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9329 16 There are other current users of database `%S_DBID'. Discontinuing execution.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9330 16 Unsupported report or fix option requested. Available report options are: FULL,
NOREPORT. Available fix options are: FIX, NOFIX.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9331 18 Master SLID mismatch identified in syslabels row with db_slid `%d'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9332 10 Beginning security label consistency of database `%S_DBID'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 9500 – 9599
1074
Server Error Messages 9500 – 9599
9333 10 Security label consistency check of database `%S_DBID' done.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9334 10 Skipping checking of security label consistency for database `%S_DBID' as it hasn't been
initialized with the proper Data High and Data Low values.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9335 16 A security label consistency fix can only be performed on the master database if the server
was booted up in single-user mode.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9336 18 Row corruption detected in syslabels row with db_slid `%d'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
9501 10 Warning - null value eliminated in set function
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9502 16 Data exception - string data right truncated
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9503 14 You must have one of the following role(s) to execute this command/procedure: `%.*s'.
Please contact a user with the appropriate role(s) for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
9504 16 An isolation level 0 cursor scan has failed on an attempted restart for cursor `%.*s', table
`%.*s', index id `%d'. The cursor is being closed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9505 16 An isolation level 0 scan has failed on an attempted restart on table `%.*s', index id `%d'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1075
9506 10 Warning: Using only the first %d characters for password
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9507 18 The builtin function `syb_sendmsg' is not supported.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9508 16 The builtin function `syb_sendmsg' failed to send the message `%.*s' to the destination
address `%.*s' at port number %d, because the length of the Internet address is greater than
the server limits. Please provide a valid destination address and retry.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9509 16 The builtin `syb_sendmsg' failed to send the message `%.*s' to the destination address
`%.*s' at port number %d, because the port number is not valid. Please enter a valid
(positive integer value between 0 and 65535) port number and retry.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9510 16 The builtin function `syb_sendmsg' failed to send the message `%.*s' to destination `%.*s'
at port number %d because the Internet address is incorrectly formed or is non-existent.
Please enter the Internet address in its correct form and retry.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9511 18 The builtin function `syb_sendmsg' failed to send the message `%.*s' to the destination
address `%.*s' at port number %d due to an internal error which required the message to
be sent atomically. Please report this error to your Systems Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9512 18 The builtin `syb_sendmsg' failed to send the message `%.*s' to destination `%.*s' at port
number %d due to failure in opening or setting the socket to non-blocking mode. Please
report this internal error to your Systems Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9513 18 The builtin function 'syb_sendmsg' failed to send the message '%.*s' to the destination
address '%.*s' due to a failure to bind the socket to a local port number %d provided by
using dbcc tune. Please report this error to your Systems Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9514 18 The builtin function `syb_sendmsg' failed to send the message `%.*s' to the destination
address `%.*s' at port number %d due to an internal error while doing the actual send.
Please report this error to your Systems Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 9500 – 9599
1076
9515 16 The UPDATE/DELETE WHERE CURRENT OF to the cursor `%.*s' failed because the
isolation level is at 0.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9516 16 %d is an invalid spid. You could use sp_who to identify the correct spid.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9517 16 Table `%.*s' does not exist in the database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9518 17 Insert into work table (for deferred processing) failed while enforcing referential
constraints. Check previous errors for possible causes. dbname = `%.*s', table name =
`%.*s', constraint name = `%.*s'.%S_EED
Explanation: A worktable operation failed during processing. Check status of tempdb.
9519 18 Failed to update the identity pre-burn factor for field `%.*s' in table `%.*s'. Please re-try
the operation or contact your SA for details.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9520 18 Error occurred while creating the identity value for field `%.*s' in table `%.*s'. Please re-
try the operation or contact your SA for details.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9521 16 The parameter that specifies the number of rows in a SET CURSOR ROWS statement
must be an integer with a value greater than 0.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9522 16 The parameter that specifies the number of rows in a SET ROWCOUNT statement must
be an integer with a value greater than 0.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9523 18 The builtin `syb_sendmsg' is not currently enabled. Please contact your Systems
Administrator for more information.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
9524 16 SELECT is not allowed in a dynamic EXECUTE IMMEDIATE statement. This SELECT
may have been part of a stored procedure or a trigger.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1077
9525 16 A positioned update/delete on a row in table `%.*s' failed. This is because cursor `%.*s'
does not point to a valid row in an inner(outer) table of an outer(inner) join used in the
query.
Explanation: Attempted to delete or update a non-existent row in a table. Check join
statement in the named cursor targeting this table. Cursor fetch may have returned NULL
values due to no matching rows.
9526 16 The dynamic sql operation is not allowed with cursor `%.*s'.
Explanation: You cannot use a client cursor within a dynamically prepared statement.
9527 20 Attempt to acquire lock on wrong merge area during parallel merge. This is an internal
error. Contact a system administrator and SET PARALLEL_DEGREE 1 for this query.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9528 16 The optimizer could not find a unique index which it could use to scan table `%.*s' for
cursor `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message. Not raised in 11.9.2.
9529 20 Deadlock during parallel merge. This is an internal error. Use SET PARALLEL_DEGREE
1 to run this query, and contact Sybase Technical Support to report the problem.
Explanation:
9532 20 Internal error: unable to locate an extra SDES for cursor '%.*s'. The cursor was probably
compiled with the incorrect locking scheme for the target table.
Explanation:
9533 20 Internal error: unable to locate a temporary object during preprocessing.
Explanation:
9534 20 Interal error: could not determine the configuration value for parameter '%s'.
Explanation:
9536 18 Unable to obtain lock on system table.
Explanation: Command failed due to internal Adaptive Server problem. Save the query
and report the error to your System Administrator.
9537 17 Insufficient number of worker processes to execute this parallel query. Increase the value
of the configuration parameter 'number of worker processes'.
Explanation:
9538 17 Insufficient number of mailboxes to execute this parallel query. Increase the value of the
configuration parameter 'number of mailboxes'.
Explanation:
9539 17 Insufficient amount of memory per worker process to execute this parallel query. Increase
the value of the configuration parameter 'memory per worker process'.
Explanation:
Number Severity Text and Explanation
Server Error Messages 9500 – 9599
1078
9540 17 Insufficient number of messages to execute this parallel query. Increase the value of the
configuration parameter 'number of messages'.
Explanation:
9541 18 Worker Process API internal error %d. Consider running this query serially by setting the
session parameter 'parallel_degree' to 1. Please contact Sybase Technical SUpport
Explanation:
9543 16 Parameter passed to %s has an invalid type. It must be of type %s.
Explanation:
9544 16 Invalid time syntax in parameter for %s: '%.*s'.
Explanation:
9545 16 Invalid time value in parameter for %s: '%.*s'.
Explanation:
9546 10 AN ADJUSTED QUERY PLAN IS BEING USED FOR STATEMENT %d BECAUSE
Explanation: The remainder of this explanatory message appears in 9547.
9547 10 NOT ENOUGH WORKER PROCESSES ARE CURRENTLY AVAILABLE.
Explanation: The first portion of this explanatory message appears in 9546.
9548 10 ADJUSTED QUERY PLAN:
Explanation: This is a message header.
9549 17 Worker process (fid=%d, spid=%d) encountered error: %d, severity: %d, state: %d during
parallel query initialization. If the problem persists, consider setting the value of session
parameter 'parallel_degree' to 1 and rerunning the query.
Explanation: The message indicates a problem initiating a parallel query. fid is the family
id of the worker process. You can use set parallel_degree 1 to limit the session to serial
operation.
9550 16 The lightweight procedure ’%.*s’ cannot be executed because it does not exist.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9551 16 The specified password does not have any numeric characters. New passwords must have
at least one numeric character.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9552 16 The identity gap ’%d’ specified is too large for the identity column’s precision of ’%d’.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1079
9553 16 No Unicode character returned for the range 0xD800..0xDFFF (surrogates) because it is
not permitted to create Unicode expression with only half of a surrogate pair.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9554 16 No Unicode character defined for this integer expression.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9555 16 No Unicode scalar value returned for unmatched surrogate half.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9556 16 The position parameter passed in falls outside the source string.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9557 16 The server failed to create or update a row in table ’%.*s’ because a varying-length column
would start at offset %d. This starting location cannot be represented accurately in the
table’s row format.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9558 10 Character or binary data returned from Adaptive Server has been truncated. The client
application does not support more than 255 bytes of data as a result column or output
parameter.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9559 14 Table(s) in the current query have access rules but the row level access configuration
option is not enabled and ASE_ASM license is not available/enabled. Please enable row
level access option and the ASE_ASM license to run the query with access rules.
Explanation: Adaptive Server could not perform the requested action.
9560 10 The ordinal number of a column in the ORDER BY clause exceeds 255. The client
application does not support column numbers over 255.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
Number Severity Text and Explanation
Server Error Messages 9600 - 9699
1080
Server Error Messages 9600 - 9699
Server Error Messages 9700 - 9799
9561 20 An insert or update to table ’%.*s’ places column ’%.*s’ at offset %d,ending at offset %d.
The maximum permitted ending offset for this column is %d. This is a server internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
9601 10 A %.*s error occurred during %.*s cleanup. Cleanup will proceed for %.*s.
Explanation: This is an informational message or a message header. No action is
required.
9602 20 SQL Server has run out of CLEANUP ITEM BLOCKS. Re-run your command when
there are fewer active users, or contact a user with System Administrator (SA) role to
reconfigure SQL Server with more CLEANUP ITEM BLOCKS.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
9701 16 Parameter `%.*s' has an invalid type.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9702 16 Parameter `%.*s' is invalid.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9703 16 `%.*s' is not a valid account name.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1081
9704 16 Unable to get SQL Server security information.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
9705 16 Unable to set SQL Server security information.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
9706 16 SQL Server's user account cannot be modified.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
9707 16 No privilege to revoke.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
9708 16 The account name provided is a domain. Unable to grant privileges to a domain.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
9709 16 The account name provided is a deleted account. Unable to grant privileges to a deleted
account.
Explanation: Adaptive Server could not perform the requested action. The command
violates a permission or privilege restriction. Check the command and working database
context.
9710 16 There must be at least one account with `%.*s' privilege.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9711 16 There must be at least one account with `%.*s' privilege other than the `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9712 16 Access granted.
Explanation: This is an informational message or a message header. No action is
required.
9713 16 Access revoked.
Explanation: This is an informational message or a message header. No action is
required.
9714 16 login mode
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 9700 - 9799
1082
9715 16 default account
Explanation: This is an informational message or a message header. No action is
required.
9716 16 default domain
Explanation: This is an informational message or a message header. No action is
required.
9717 16 set host
Explanation: This is an informational message or a message header. No action is
required.
9718 16 key _
Explanation: This is an informational message or a message header. No action is
required.
9719 16 key $
Explanation: This is an informational message or a message header. No action is
required.
9720 16 key @
Explanation: This is an informational message or a message header. No action is
required.
9721 16 key #
Explanation: Informational header.
9722 16 name
Explanation: Header text.
9723 16 config_item
Explanation: Header text.
9724 16 standard
Explanation: Header text.
9725 16 integrated
Explanation: This is an informational message or a message header. No action is
required.
9726 16 mixed
Explanation: This is an informational message or a message header. No action is
required.
9727 16 unknown mode
Explanation: This is an informational message or a message header. No action is
required.
9728 16 true
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1083
Server Error Messages 9800 - 9899
9729 16 false
Explanation: This is an informational message or a message header. No action is
required.
9730 16 space
Explanation: This is an informational message or a message header. No action is
required.
9731 16 domain separator
Explanation: This is an informational message or a message header. No action is
required.
9732 16 null
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Number Severity Text and Explanation
9802 20 Deletion of row in SYSPARTITIONS failed. Database id %d, Object id %d, Partition
number %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
9803 21 Missing row in SYSPARTITIONS. Database id %d, Object id %d, Partition number %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
9805 10 Partition number %d for object id %d in database %d does not exist.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
9807 20 Process %d encountered deadlock while trying to lock control page %d of partition %d
for object id %d.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Server Error Messages 9800 - 9899
1084
9809 21 Control page %d specified for partition number %d of object id %d in database %d does
not exist.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
9810 21 Control page %d specified for partition number %d for object id %d in database %d is
corrupt.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
9814 21 SYSPARTITIONS table is missing in database %d.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
9816 17 Unable to allocate an in-memory partition structure for object id %d in database %d. To
increase the number of available partitions update the `partition groups' configuration
parameter.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9817 16 Invalid object ID %ld. Valid user object ID is a positive integer.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9818 16 Invalid partition number %d. Valid partition number is a positive integer.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
9819 11 Object ID %ld does not exist in database `%.*s'.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
9820 11 Partition number %d for object ID %ld in database `%.*s' does not exist.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
9821 12 The object `%.*s' is not a partitioned table.
Explanation: Command failed. Specify an object of the correct type.
9822 21 An error occured during an update to a control page. The old last page ID %d does not
match the last page ID of any partition for object `%.*s' (ID %d) in database `%.*s' (ID
%d) . The transaction is being rolled back.
Explanation: Adaptive Server encountered an internal error affecting all processes in
the current database. Report the error to your System Administrator. Adaptive Server
must be restarted and dbcc diagnostics run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1085
Server Error Messages 9900 - 9999
9823 20 Insert new partition row in SYSPARTITIONS failed for slice number %d. Database id
%d, Object id %d, Total number of slices %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9824 20 Update row in SYSPARTITIONS failed. Database id %d, Object id %d, Partition number
%d
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
9826 16 The number of data pages in partition number %d for table ’%.*s’ in database ’%.*s’
could not be determined because the table is currently being altered.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
9827 10 Warning: Control page %d upgrade for partition number %d for object ID %d in database
’%S_DBID’ may not have been done correctly. Please run sp_helpartition on this table
and, if necessary, correct the values with UPDATE PARTITION STATISTICS.
Explanation: A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
Number Severity Text and Explanation
9901 14 Permission denied. Only a user with curread set to @@data_high can perform the DBCC
command `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
9902 14 Only users with SA and SSO roles can run this dbcc dbrepair command for the database
%S_DBID.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
9903 14 Only users with SA and SSO roles having their curread dominating the maxhold of the
database can run this dbcc dbrepair command for the database `%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Server Error Messages 9900 - 9999
1086
9904 10 Total (# of text chains = %ld text pages = %ld) in this table.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9905 10 Processed %ld tables. Found %ld good text entries, %ld bad text entries in this database
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9906 16 Unrecognized option. Available options: dbcc engine(net, show, engine#), dbcc
engine(net, showall), dbcc engine(net, netengine)
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9908 16 Syspartitions system table does not exist in database id %S_DBID.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
9909 10 The total number of data pages in partition %d is %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9911 10 Object %ld has one row in Syspartitions
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9912 10 Object %ld has partition %ld instead of %ld in Syspartitions
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
9913 16 MAX_ROWS_PER_PAGE value of %d is invalid. It must be between 0 and %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9914 16 Amount of memory transferred (%dk) is less than the amount of memory requested (%dk).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9915 16 I/O size must be a power of 2.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9916 16 I/O size must be a power of 2.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9917 16 Can't find database id for %.*s. Check that this database exists and re-run the command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1087
9918 16 Encountered error using dbid %d.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
9919 16 Can't find object id for %.*s. Check the object name and re-run this command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9920 16 Index id %d not found for object id %d, dbid %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9921 16 Index %.*s not found for object id %d dbid %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9922 16 The first page %ld in sysindexes for table `%.*s' does not match with first page %ld for
the table's first partition in Syspartitions.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
9923 16 The first page %ld in syspartitions for partition %ld of table `%.*s' has previous page #
%ld in its page header. The previous page # should be NULL.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
9924 16 The last page %ld in syspartitions for partition %ld of table `%.*s' has next page # %ld in
its page header. The next page # should be NULL.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
9926 16 This option has been converted to the configuration parameter `%s'. Use `sp_configure' to
set it.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
9927 16 This option requries a table name as the third parameter. Use `sp_configure `%s'' to set the
option serverwide.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9928 16 This option has been disabled. Use `sp_poolconfig' instead.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 9900 - 9999
1088
9929 14 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can
run DBCC TEXTALLOC command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
9931 22 The %S_MSG page (%ld) found in the page chain does not match with the %S_MSG page
(%ld) found in the slice control page (%ld), for table `%.*s', on slice %ld. The table may
be corrupt.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
9932 22 The %S_MSG page (%d) found in the page chain doesn’t match with the %S_MSG page
(%d) stored in the Sysindexes for table ’%.*s’. The table may be corrupt.
Explanation: A table or index may be corrupt. Report the error to your System
Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
9933 16 The option max_rows_per_page cannot be set for a text/image index (%d) on table `%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message. Not raised in 11.9.2.
9934 16 Invalid index ID %d. Values for index ID must be between 0 and %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9935 10 SQL Server will not refresh index descriptor as the object descriptor for objid % ld in dbid
%d is not installed in cache.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
9936 20 Error while trying to refresh sysindexes row within index descriptor with indid % d objid
%ld and dbid %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
9938 16 Table with ID %d not found; check sysobjects.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9939 16 DBCC %s command is not supported anymore.
Explanation: Refer to the System Administration Guide for details on supported dbcc
commands and usage.
9940 16 The source text of object named '%s' with object id '%d' has already been hidden.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9941 16 The source text of object named '%s' with object id '%d' is missing and it is not hidden.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1089
9942 16 Failed to hide the source text.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9943 16 The hidden text of object named '%s' with object id '%d' does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
9944 10 Too many errors have been detected on device '%.*s' (physical device: %.*s). Page and
object checking on that device has been discontinued. (The CHECKSTORAGE operation
stops when more than 25%% of the checks are abandoned.)
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9945 10 Too many errors have been detected on table '%.*s' index '%.*s'. Checking for that object
will be discontinued. (The CHECKSTORAGE operation stops when more than 25 %% of
the checks are abandoned.)
Explanation: Run dbcc checktable to determine the state of this object.
9946 17 An attempt to reserve a %dK buffer failed. Increase the size of the %dK buffer pool in the
buffer cache ’%.*s’.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9947 17 An attempt to allocate memory failed due to insufficient SQL Server memory.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9948 17 The CHECKSTORAGE operation failed to cache a scan workspace row because of a
cache overflow. This is an internal error. Please contact Sybase Technical Support.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9949 24 An I/O in a workspace failed, page %d in database %d. Check your hardware for problems
that could cause I/O failures.
Explanation: Hardware error detected. Report the error to your System Administrator.
The database may have to be reloaded. It may be necessary to contact your hardware
vendor.
9950 17 Workspace '%.*s' is incorrectly allocated. Use sp_dbcc_createws to create a new
workspace.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
Server Error Messages 9900 - 9999
1090
9951 17 Workspace '%.*s' is too fragmented to be used. Use sp_dbcc_createws and
sp_dbcc_updateconfig to correct the problem.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9952 17 Workspace '%.*s' is too small to permit the CHECKSTORAGE operation to proceed. Use
sp_dbcc_alterws and sp_dbcc_updateconfig to correct the problem.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
9953 20 SQL Server failed to synchronize the activity of a worker process with the coordinating
process. This is an internal error. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9954 10 Storage checks for '%.*s' are complete. DBCC is now recording the results in the dbccdb
database.
Explanation: This is an informational message or a message header. No action is
required.
9955 20 A worker process could not access database '%.*s'. This is an internal error. Please contact
Sybase Technical support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
9956 10 A worker process failed to complete its assigned work during the scan phase. The results
of the CHECKSTORAGE operation will be incomplete.
Explanation: Informational message but may impact outcome of dbcc checkstorage.
9957 10 A worker process failed to complete its assigned work during the page chain check phase.
The results of the CHECKSTORAGE operation will be incomplete.
Explanation: Informational message but may impact outcome of dbcc checkstorage.
9958 10 A worker process failed to complete its assigned work during the OAM check phase. The
results of the CHECKSTORAGE operation will be incomplete.
Explanation: Informational message but may impact outcome of dbcc checkstorage.
9959 10 The CHECKSTORAGE operation has aborted.
Explanation: Problem impacts outcome of dbcc checkstorage.
9960 10 A non-recoverable error has occurred in the CHECKSTORAGE operation. The operation
has been aborted.
Explanation: Problem impacts outcome of dbcc checkstorage.
9961 17 DBCC failed to connect to the requested number of worker processes. The number of
workers configured is insufficient, or the number of workers exceeds 128. Use
sp_dbcc_updateconfig to reduce 'max worker processes' for this database.
Explanation: Problem impacts outcome of dbcc checkstorage.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1091
9962 17 Access to table '%.*s' index '%.*s' in the target database failed.
Explanation: Problem impacts outcome of dbcc checkstorage.
9963 16 An error occurred while attempting to insert a row into the dbcc_faults table or the
dbcc_fault_params table.
Explanation: Problem impacts outcome of dbcc checkstorage.
9964 16 Database '%.*s' was not found. Use sp_helpdb to list the available databases.
Explanation: Problem impacts outcome of dbcc checkstorage.
9965 16 The entries in dbcc_config for database '%.*s' are either missing or invalid. Use
sp_dbcc_evaluatedb to determine appropriate values for the entries and
sp_dbcc_updateconfig to set them.
Explanation: Problem impacts outcome of dbcc checkstorage.
9966 16 DBCC could not access the scan workspace '%.*s'. Verify that the workspace exists .
Explanation: Problem impacts outcome of dbcc checkstorage.
9967 16 DBCC could not access the text workspace '%.*s'. Verify that the workspace exists .
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9968 16 DBCC could not evaluate SQL Server's device configuration. Check the contents of the
dbcc_dev_info table.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9969 16 The operation sequence number update for database '%.*s' in the dbcc_config table failed.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9970 16 DBCC failed to either insert or update the row in the dbcc_operation_log table for this
check of database '%.*s'.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9971 20 DBCC failed to schedule work for the worker processes. This is an internal error. Please
contact Sybase Technical Support.
Explanation: Internal error affecting the current process. Contact your SA.
9972 16 An error occurred while inserting the results into the dbcc_counters table.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9973 16 An error occurred while inserting the results into the dbcc_operation_results table.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
Number Severity Text and Explanation
Server Error Messages 9900 - 9999
1092
9974 10 DBCC CHECKSTORAGE for database '%.*s' sequence %d completed at %s. %d faults
and %d suspect conditions were located. %d checks were aborted. You should investigate
the recorded faults, and plan a course of action that will correct them.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9975 10 DBCC CHECKSTORAGE for database '%.*s' encountered an error. Some results may not
be available. Correct the problems reported and reexecute the CHECKSTORAGE
command.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9976 10 There is an inconsistency between the dbcc_dev_info table and the sysdevices table. Use
DBCC CHECKDEVINFO to regenerate the dbcc_dev_info table.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9977 16 The cache '%.*s' specified in the dbcc_config table does not exist.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9978 16 The %dK buffer pool in the configured cache is too small. %dK is the minimum size .
Explanation: Check the System Administration Guide for assistance.
9979 10 Too many worker processes (%d) are configured for the available %dK buffer pool. This
buffer pool can only support %d workers.
Explanation: Check the SA Guide for assistance.
9980 10 %d text column values were not checked because the text workspace was too small. Use
sp_dbcc_alterws to increase its size by %dK.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9981 16 Correct syntax is:
dbcc createws({dbccdb|dbccalt}, segment name, workspace name, {scan|text}, size) dbcc
alterws({dbccdb|dbccalt}, workspace name, {scan|text}, size)
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
9982 16 The minimum size for a DBCC workspace is %d pages.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9983 16 DBCC failed to create the workspace '%.*s'.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9984 16 DBCC could not expand the size of workspace '%.*s' in database '%.*s' to %d pages .
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1093
9985 16 DBCC could not truncate the size of workspace '%.*s' in database '%.*s' by %d pages.
Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for
assistance.
9986 10 Suspect conditions are to be treated as faults if the same suspect condition persists in
subsequent CHECKSTORAGE operations, or if they are also detected by other DBCC
functions.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9987 16 DOL datapage %d of object %d does not have extended page header bits set correctly.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9988 16 NCFS value %ld in DOL datapage %ld is larger than available space %ld in the page
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9989 16 Number of deleted rows %ld in page header of DOL datapage %ld is incorrect. This value
cannot be negative.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9990 10 Insert free space value %ld in page header of DOL datapage %ld is greater than sum of cfs
and ncfs (%ld) in the page
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
9991 16 Orphan row at offset %ld in page %ld of object %ld must be marked committed delete and
is not
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9992 16 Actual #rows %ld in DOL datapage %ld and count of #rows - nextrno - %ld in page header
do not match
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9993 16 There is a mismatch between value of ncfs counter %ld in page header of DOL datapage
%ld and the actual amount of garbage %ld in the page
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9994 16 There is a mismatch between count of #deleted rows %ld in page header of DOL data page
%ld and the actual # deleted rows %ld in the page
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 9900 - 9999
1094
9995 16 There is a mismatch between value of insert free space %ld in page header of DOL
datapage %ld and actual value of insert free space %ld computed from the page with
expected row size as %ld
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9996 16 Keys of index id %d for table '%.*s' in %S_MSG not in proper order. Drop and recreate
the index. (index page %ld)
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9997 16 Root page %ld in index id %ld of object id %ld does not have BT_ROOT bit set
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9998 16 Index page %ld has object id %ld which is different from object id %ld
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
9999 16 Rids not in ascending order in index page %ld for row %ld at offset %ld (indid %l d, object
%ld). Drop and recreate the index.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1095
Server Error Messages 10100 - 10199
Number Severity Text and Explanation
10101 16 The object_type column cannot be NULL.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10102 16 The attrib_notify() function can only be used from a system stored procedure or with ad
hoc updates enabled.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10104 16 Class %d is not a valid attribute class.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10105 16 Attribute %d is not a valid attribute within class %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10106 16 Class cannot be NULL.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10107 16 Attribute cannot be NULL.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10108 16 The `action' parameter cannot be NULL.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10109 16 The value of the parameter `%s' is `%d'. The value should be between %d and %d.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
10110 10 The entry being added will have no effect due to precedence or scope rules.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
10111 10 The entry being dropped is preceded by another specification; dropping the entry will have
no effect.
Explanation: This is an informational message but may require follow-up action.
Contact your System Administrator.
Server Error Messages 10200 - 10299
1096
Server Error Messages 10200 - 10299
Number Severity Text and Explanation
10201 10 NESTING LEVEL %u SUBQUERIES FOR STATEMENT %u.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10202 10 QUERY PLAN FOR SUBQUERY %u (at nesting level %u and at line %u).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10203 10 Subquery under an IN predicate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10204 10 Subquery under an ANY predicate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10205 10 Subquery under an ALL predicate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10206 10 Subquery under an EXISTS predicate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10207 10 Subquery under an EXPRESSION predicate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10208 10 Correlated Subquery.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10209 10 Non-correlated Subquery.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10210 10 END OF QUERY PLAN FOR SUBQUERY %u.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10211 10 Run subquery %u (at nesting level %u).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
CHAPTER 6 Adaptive Server Error Messages
1097
10212 10 The cursor is read only because it contains a subquery.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10213 10 The update mode is deferred_varcol.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10214 10 The update mode is deferred_index.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10215 10 There have been %d scan fixups and %d matching search argument fixups for this cursor.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10216 10 The cursor is read only because it is referencing a dynamic table.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10217 10 Executed by coordinating process.
Explanation: This is an informational message or a message header. No action is
required.
10218 10 Executed in parallel by coordinating process and %ld worker processes.
Explanation: This is an informational message or a message header. No action is
required.
10219 10 Executed in parallel by %ld worker processes.
Explanation: This is an informational message or a message header. No action is
required.
10220 10 Executed in parallel with a %ld-way partition scan.
Explanation: This is an informational message or a message header. No action is
required.
10221 10 Executed in parallel by coordinating process and %ld worker processes.
Explanation: This is an informational message or a message header. No action is
required.
10222 10 Parallel work table merge.
Explanation: This is an informational message or a message header. No action is
required.
10223 10 Parallel network buffer merge.
Explanation: This is an informational message or a message header. No action is
required.
10224 10 Parallel result buffer merge.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 10200 - 10299
1098
10225 10 Auxiliary scan descriptors required: %ld
Explanation: This is an informational message or a message header. No action is
required.
10226 10 The specified spid value '%d' is out of range. It must be positive and not exceed the
maximum number of user connections.
Explanation: This is an informational message or a message header. No action is
required.
10227 10 There is no active server process for the specified spid value '%d'. Possibly the user
connection has terminated.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10228 10 The specified spid value '%d' applies to a server internal process, which does not execute
a query plan.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10229 10 The process with the specified spid value '%d' has not been assigned an sqltext structure.
Query plan retrieval cannot continue.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10230 10 The query plan for spid '%d' is unavailable. Possibly the query has not started or has
finished executing.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10231 10 The current batch id '%d' does not match the specified batch id '%d'. Specify just the spid
value to obtain the current batch id.
Explanation: This message is sent when the target process has received a new SQL batch
since the user executed sp_showplan.
10232 10 The current context id '%d' does not match the specified context id '%d'. Specify just the
spid value to obtain the current context id.
Explanation: This message is sent when the target process has invoked or returned from
a procedure since you executed sp_showplan. So the query plan may not correspond to
other information retrieved.
10233 10 The specified statement number '%d' is greater than the number of statements in the batch
or procedure. Specify just the spid value to obtain the current statement number.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10234 10 The SQL batch contains '%d' bytes. Text is '%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1099
10235 10 The cursor was closed because the object associated with it has been dropped.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10236 10 Executed by %ld worker processes.
Explanation: This is an informational message or a message header. No action is
required.
10237 10 Executed in parallel with a %ld-way hash scan.
Explanation: This is an informational message or a message header. No action is
required.
10239 10 With %S_MSG Buffer Replacement Strategy for data pages.
Explanation: Displays the buffer replacement strategy selected by the optimizer for the
data pages a given table.
10240 10 Using I/O Size %d Kbytes for data pages.
Explanation: Displays the I/O size of the data pages selected by the optimizer for a given
table.
10241 10 ASC
Explanation: This is informational text or header.
10242 10 DESC
Explanation: This is informational text or header.
10243 10 Index key order not found.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10244 10 Optimized using simulated statistics.
Explanation: This is informational text.
10246 10 Optimized using an Abstract Plan (ID : %d).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10247 10 Optimized using the Abstract Plan in the PLAN clause.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10248 10 Serial data merge.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10249 10 Parallel data merge using %d worker processes.
Explanation: This is an informational message or a message header. No action is
required.
10250 10 Worktable%d created for sort merge join.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 10300 - 10399
1100
Server Error Messages 10300 - 10399
10251 10 Merge join (outer table).
Explanation: This is informational text.
10252 10 Merge join (inner table).
Explanation: This is informational text.
10253 10 Serial data merge.
Explanation: This is informational text or header.
10254 10 Data copying.
Explanation: This is informational text or header.
10255 10 Text/Image column(s) deallocation.
Explanation: This is informational text.
10256 10 Catalog updates.
Explanation: This is informational text.
Number Severity Text and Explanation
Number Severity Text and Explanation
10301 14 Can't find database id for `%.*s'. Check that this database exists and re-run the command.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
10302 14 Only the DBO of database `%S_DBID' or a user with System Administrator (SA) role can
run this command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10303 14 Object named `%.*s' not found; check sysobjects.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
10304 14 Only the owner of object `%S_OBJID' or a user with System Administrator (SA) role can
run this command.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10305 14 Datatype named %.*s not found in database `%.*s'; check systypes.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
CHAPTER 6 Adaptive Server Error Messages
1101
10306 14 You do not have the permission to use datatype named %.*s in database %.*s.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10307 14 Curread should dominate the label being used.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10308 14 Supplied label is invalid.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10309 14 Curwrite is not equal to the label at which write is attempted.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10310 14 Session labels dominance relationship has been violated by the label being used.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10311 14 You must use one of the Sybase-supplied auditing stored procedures to change audit
options.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10312 14 The ad_hoc_audit builtin can only be called from the following stored procedures:
sp_addauditrecord, sp_bindmsg, sp_unbindmsg, sp_bindefault, sp_unbindefault,
sp_bindrule, sp_unbindrule, sp_addmessage, sp_dropmessage.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10313 14 The caller of the set_password builtin was not found! Password left unchanged.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10314 14 Only a person with System Security Officer (SSO) role can change another person's
password.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10315 14 Invalid caller's password specified, password left unchanged.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10316 14 New password supplied is the same as the previous password. Please supply a different
new password.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 10300 - 10399
1102
10317 14 The specified password is too short. Passwords must be at least %d character(s) long.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10318 14 Invalid user specified, password left unchanged.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10319 14 SET ROLE fails. The caller is not granted with the specified role. Please contact a user
with System Security Officer (SSO) role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10320 14 SET ROLE fails. The caller cannot assume the new user identity (uid) in the current
database. Please contact a user with System Security Officer (SSO) role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10321 14 Ad-hoc updates to system catalogs not enabled. A user with System Security Officer
(SSO) role must reconfigure system to allow this.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10322 14 In a CREATE SCHEMA statement, the authorization id must match the current user name.
The supplied authorization id, `%.*s', does not match the current user name, `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10323 14 You do not have the permission to use datatype id %d in database id %d.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10324 14 User `%.*s' not found in database `%S_DBID'.; check sysusers.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
10325 14 Database named %.*s not found; check sysdatabases.
Explanation: Command failed. Check your Adaptive Server environment for the object
not found and re-enter the command with the correct name.
10326 14 Suspect object %S_OBJID, database %S_DBID found. Cannot execute query.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10327 14 Procedure %S_OBJID, database %S_DBID with labels found UNCERTIFIED. Cannot
execute query.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1103
10328 14 UNCERTIFIED object %S_OBJID, database %S_DBID accessed by CERTIFIED object
%S_OBJID, database %S_DBID. Cannot execute query.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10329 14 Sysobjects entry NOT found for procedure buffer entry.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10330 14 %s permission denied on object %S_OBJID, database %S_DBID, owner %.*s
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10331 14 %s permission denied, database %S_DBID, owner %.*s
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10332 14 %s permission denied on column %.*s of object %S_OBJID, database %S_DBID, owner
%.*s
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10333 14 Incorrect DBCC command: Please see the Commands Reference Manual for DBCC
commands and options.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10334 14 Permission related internal error was encountered. Unable to continue execution.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10335 14 SET label (CURREAD, CURWRITE) failed because new value is an invalid label, or new
value doesn't satisfy the dominance relationships among session labels.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10336 14 Permission denied. Only the Database Owner (DBO) or a user with the System
Administrator (SA), System Security Officer (SSO), or Oper role can execute this
command for database `%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10337 16 Object `%S_OBJID' not found.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10338 14 Permission denied. User's curwrite does not match the sensitivity label of object
`%S_OBJID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 10300 - 10399
1104
10339 16 Database ’%S_DBID’ not found.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
10340 14 Permission denied. User's curwrite does not match the sensitivity label of database
`%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10341 14 Only users with SA and SSO roles can run this dbcc dbrepair command for the database
%S_DBID.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10342 14 Only users with SA and SSO roles can run this dbcc dbrepair command for the database
%S_DBID.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10343 14 Permission denied. Only a user with curwrite set to @@data_low can perform the
command `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10344 14 Permission denied. Only a user with curwrite set to @@data_high can perform the
command `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10345 14 Permission denied. The user cannot insert into the object `%S_OBJID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10346 14 Permission denied. The user cannot insert into the object `%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10347 14 Permission denied. The subject cannot see all the contents of the container object
`%S_OBJID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10348 14 Permission denied. The subject cannot see all the contents of the container object database
`%S_DBID'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1105
10349 14 Permission denied. Only a user with curread set to @@data_high can perform the
command `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10350 14 Permission related internal error was encountered. Unable to continue execution.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10351 14 Server user id %d is not a valid user in database `%.*s'
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10352 14 You can only use SELECT or SELECT INTO with the special table.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10353 14 You must have the following role(s) to execute this command/procedure: `%.*s' . Please
contact a user with the appropriate role for help.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10354 14 Permission denied. You must be either the system administrator (SA), the database
administrator (dbo), or the owner of this object to perform this operation.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10355 16 Changing certification state of object %S_OBJID, database %S_DBID to SUSPECT
because of change in state of dependent object %.*s (previous object id %ld), database
%S_DBID.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
10356 14 Illegal datatype encountered; check systypes.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10357 14 Permission denied. User's curwrite does not match the sensitivity label of datatype named
`%.*s' in database `%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10358 14 Curread cannot be set below the current database's hurdle.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
Server Error Messages 10300 - 10399
1106
10359 18 The curread and curwrite labels of the Client do not equal the connection level for the
remote Server.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
10360 18 Site `%.*s' not found in sysservers.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
10361 14 The attrib_notify() function can only be used from a system stored procedure or with ad
hoc updates enabled.
Explanation: Check that the function is called from the allowed procedure.
10362 14 The logschema() built-in function can only be called from the following stored procedures:
sp_rename, sp_setreplicate, sp_setreptable, sp_setrepproc.
Explanation: Check that the function is called from the allowed procedure.
10363 14 The built-in function '%.*s' can only be called from system stored procedures.
Explanation: Check that the function is called from the allowed procedure.
10364 14 Permission denied. You must either be the database/object owner or possess the following
roles in order to perform this operation: '%.*s'.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
10365 14 Permission denied. You must have '%s' access on the table to lock it in '%s' mode.
Explanation: Failure to execute command LOCK TABLE in either shared or exclusive
mode. Check permissions.
10366 14 System catalog updates are not allowed in transactions with %s as coordinator.
Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
10367 14 Permission denied on the %s ACF built-in.
Explanation: You do not have permission to execute this command. Have the object
owner or a user with the needed role run this command.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1107
Server Error Messages 10400 - 10499
Number Severity Text and Explanation
10401 10 additional network memory allocates additional memory for clients which request packet
sizes that are larger than the default packet size for the server.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10402 10 lock address spinlock ratio specifies the number of address lock buckets in the address
locks hash table which are protected by each spinlock (buckets per spinlock).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10403 10 allow nested triggers is a toggle that controls the use of nested triggers. When the value
is set to 1, data modifications made by triggers can fire other triggers.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10404 10 allow remote access determines whether users from remote servers can access this SQL
Server. The default is 1, to allow SQL Server to communicate with Backup Server.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10405 10 allow sql server async i/o is a toggle that enables SQL Server to run with asynchronous
disk I/O.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10406 10 allow updates to system tables allows system tables to be updated directly. The default is
0 (off).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10407 10 audit queue size determines the number of audit records that the audit queue can hold.
The default is 100.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10408 10 configuration file specifies the location of the configuration file you want to use.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10409 10 cpu accounting flush interval specifies how many machine clock ticks to accumulate
before adding cpu usage data to syslogins for use in chargeback accounting statistics.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Server Error Messages 10400 - 10499
1108
10410 10 cpu grace time specifies the maximum amount of time (in milliseconds) a user process
can run without yielding the CPU before SQL Server infects it.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10411 10 deadlock checking period specifies the minimum amount of time (in milliseconds) a
process must wait for a lock before SQL Server initiates a deadlock check.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10412 10 deadlock retries specifies the number of times a transaction will retry to acquire a lock
after it has become a deadlock victim.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10413 10 default character set id is the number of the default character set used by the server.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10414 10 default database size sets the default number of megabytes allocated to each new user
database. The default run value is 2 (megabytes)
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10415 10 default fill factor percent sets how full SQL Server makes each page when creating a new
index on existing data (unless user gives other value in create index statement).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10416 10 default language id is the number of the language that is used to display system messages
unless a user has chosen another language from those available on the server.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10417 10 default network packet size sets the default size of network packets for all users on SQL
Server.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10418 10 default sortorder id is the number of the current default sortorder on SQL Server. Do not
change this parameter. See the System Administration Guide for more information.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10419 10 disk i/o structures specifies the initial number of disk I/O control blocks SQL Server
allocates on startup.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1109
10420 10 event buffers per engine specifies the number of events per SQL Server engine that can
be simultaneously monitored. Events are used for observing SQL Server performance.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10421 10 executable code size reports the size of the SQL Server executable.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10422 10 freelock transfer block size specifies the number of locks moved between the engine
freelock cache and the global freelock list.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10423 10 housekeeper free write percent sets the maximum percentage that database writes can
increase because of free writes started by the housekeeper process.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10424 10 i/o accounting flush interval specifies how many disk I/Os to accumulate before flushing
the data to syslogins for use in chargeback accounting.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10425 10 i/o polling process count specifies the number of tasks the scheduler will run before
checking for disk and/or network I/O completions.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10426 10 identity burning set factor sets the percentage of potential IDENTITY column values
made available in each block.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10427 10 identity grab size allows each SQL Server process to reserve a block of IDENTITY
column values for inserts into tables that have an IDENTITY column.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10428 10 page lock promotion HWM sets the maximum number of page locks allowed before SQL
Server escalates to a table lock. The default value is 200.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10429 10 page lock promotion LWM sets the minimum number of page locks allowed before SQL
Server escalates to a table lock. The default value is 200.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 10400 - 10499
1110
10430 10 page lock promotion PCT sets the percentage of page locks allowed before SQL Server
escalates to a table lock. The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10431 10 lock shared memory disallows swapping of SQL Server pages to disk, and allowing the
operating system kernel to avoid the server's internal page locking code.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10432 10 max async i/o's per engine specifies the maximum number of asynchronous disk I/O
requests that can be outstanding for a single engine at one time.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10433 10 max async i/o's per server specifies the maximum number of asynchronous disk I/O
requests that can be outstanding for SQL Server at one time.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10434 10 max engine freelocks specifies the maximum number of locks available in an engine
freelock cache.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10435 10 max network packet size sets the maximum network packet size that a client program can
request.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10436 10 max number of network listeners specifies the maximum number of network listeners
that can be open at one time.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10437 10 max online engines controls the number of engines in a symmetric multiprocessor
environment.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10438 10 memory alignment boundary determines on which boundary buffer caches are aligned.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10439 10 min online engines is not currently used.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1111
10440 10 number of alarms specifies the number of alarms allocated by SQL Server. Alarms are
used with the Transact-SQL waitfor command.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10441 10 number of devices controls the number of database devices SQL Server can use. It does
not include devices used for database dumps.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10442 10 number of extent i/o buffers allocates the specified number of extents (8 data pages) for
use by create index. Do not set this value to more than 100.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10443 10 number of index trips specifies the number of times an aged index page recycles itself
onto the MRU chain.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10444 10 number of languages in cache is the maximum number of languages that can
simultaneously be held in the language cache. The default is 3.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10445 10 number of locks sets the number of available locks. The default run value is 5000.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10446 10 number of mailboxes sets the number of mailbox structures SQL Server allocates on
start-up. Mailboxes are use for process-to-process communication and synchronization.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10447 10 number of messages specifies the number of message structures allocated by SQL Server
at start-up time. Messages are used in conjunction with mailboxes for process-to-process
communication and synchronization.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10448 10 number of oam trips specifies the number of times an aged OAM page recycles itself onto
the MRU chain.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10449 10 number of open databases sets the maximum number of databases that can be open at one
time on SQL Server. The default run value is 12.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 10400 - 10499
1112
10450 10 number of open objects sets the maximum number of database objects that can be open
at one time on SQL Server. The default run value is 500.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10451 10 number of preallocated extents specifies the number of extent structures allocated in a
single trip to the page manager.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10452 10 number of remote connections controls the limit on active connections initiated to and
from this SQL Server. The default is 20.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10453 10 number of remote logins controls the number of active user connections from this SQL
Server to remote servers. The default is 20.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10454 10 number of remote sites controls the number of simultaneous remote sites that can access
this SQL Server. The default is 10.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10455 10 number of sort buffers specifies the number of buffers used to hold pages read from input
tables.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10456 10 number of user connections sets the maximum number of user connections that can be
connected to SQL Server at one time.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10457 10 page lock spinlock ratio specifies the ratio of spinlocks protecting the internal page locks
hash table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10458 10 page utilization percent controls when SQL Server performs an OAM (Object Allocation
Map) scan to find unused pages. The default run value is 95.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10459 10 partition groups sets how many partition groups to allocate for the server. Partition
groups are used by SQL Server to control access to individual partitions of tables.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1113
10460 10 partition spinlock ratio sets the number of partition caches each spinlock protects. These
spinlocks keep processes from using partition caches used by other processes.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10461 10 permission cache entries determines the number of cache protectors per task.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10462 10 print deadlock information enables printing of deadlock information to the error log.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10463 10 print recovery information determines what information SQL Server displays on the
console during recovery.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10464 10 procedure cache percent specifies the amount of memory allocated to the procedure
cache after SQL Server's memory needs are met. The default run value is 20.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10465 10 recovery interval in minutes sets the maximum time per database that SQL Server uses
to complete its recovery procedures in case of a system failure.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10466 10 remote server pre-read packets controls the number of packets that a site handler will pre-
read in connections with remote servers. The default is 3.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10467 10 runnable process search count specifies the number of times an engine will loop looking
for a runnable task before relinquishing the CPU.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10468 10 sort page count specifies the maximum amount of memory a sort operation can use.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10469 10 sql server clock tick length specifies the duration of the server's clock tick, in
microseconds.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10470 10 stack guard size specifies the size of the stack guard area.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 10400 - 10499
1114
10471 10 stack size sets the size of SQL Server's execution stack.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10472 10 systemwide password expiration is the number of days that passwords remain in effect
after they are changed. The default is 0 (passwords do not expire).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10473 10 lock table spinlock ratio specifies the number of table lock buckets in the table lock hash
table which are protected by each spinlock (buckets per spinlock).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10474 10 tape retention in days sets the number of days you want to retain each tape after it has
been used for a database or transaction log dump.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10475 10 tcp no delay disables TCP packet batching.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10476 10 time slice sets the number of milliseconds that SQL Server's scheduler allows a user
process to run. The default run value is 100 milliseconds.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10477 10 total data cache size represents the amount of memory currently available for use as a
data cache. It is a calculated value that is not directly user-configurable.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10478 10 The run value of ’total logical memory’ indicates the size of memory required to satisfy
the current configuration.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10479 10 upgrade version is changed by the upgrade program provided with new releases.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10480 10 user log cache size specifies the size (in bytes) for each user's log cache.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10481 10 user log cache spinlock ratio specifies the number of user log caches per user log cache
spinlock.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1115
10482 10 shared memory starting address determines the virtual address at which SQL Server
starts its shared memory region. Most users do not need to modify this.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10483 10 size of auto identity column sets the precision of IDENTITY columns automatically
created with the sp_dboption `auto identity' option.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10485 10 os file descriptors is a read-only parameter that indicates how many file descriptors have
been allocated to SQL Server. It is not user-configurable.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10486 10 Allow-limits allows the Resource Governor feature to be used by SAs. Default is 0 (off);
static.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10487 10 number of auxiliary scan descriptors sets the maximum number of auxiliary scan
descriptors that can be shared among all connections at one time. The default run value is
2 00.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10488 10 number of open indexes sets the maximum number of indexes that can be open at one time
on SQL Server. The default value is 500.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10489 10 open object spinlock ratio specifies the number of open objects protected by one spinlock.
The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10490 10 open index hash spinlock ratio specifies the number of internal hash tables for open
indexes protected by one spinlock. The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10491 10 open index spinlock ratio specifies the number of open indexes protected by one spinlock.
The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10492 10 enable cis specifies whether Component Integration Services is loaded when the server is
started. The default is 0 (do not load).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 10500 - 10599
1116
Server Error Messages 10500 - 10599
10493 10 cis connect timeout specifies the number of seconds to wait for a connect request to a
remote server to complete.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10494 10 cis bulk insert batch size specifies the number of rows in a bulk copy batch when
performing a SELECT INTO operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10495 10 max cis remote connections specifies the maximum number of connections to remote
servers that can be active at one time.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10496 10 max cis remote servers specifies the maximum number of remote servers that can be
accessed at one time.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10497 10 cis packet size specifies the maximum size of a network packet.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10498 10 cis cursor rows specifies the maximum number of rows that will be returned in response
to a single fetch operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10499 10 CIS idle timeout specifies the number of seconds to wait before terminating an idle
connection with a remote server.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
10501 16 Database '%.*s' not found; check sysdatabases.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
CHAPTER 6 Adaptive Server Error Messages
1117
Server Error Messages 10600 - 10699
10502 16 Internal error occurred. Unexpected value supplied. Please call Sybase Technical
Support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
10601 10 lock hashtable size specifies the number of buckets in the lock hash table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10602 10 the lock spinlock ratio specifies the number of page and row lock buckets in the lock hash
table which are protected by each spinlock (buckets per spinlock).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10603 10 row lock promotion HWM sets the maximum number of row locks allowed before SQL
server escalates to a table lock. The default value is 200.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10604 10 row lock promotion LWM sets the minimum number of row locks allowed before SQL
server escalates to a table lock. The default value is 200.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10605 10 row lock promotion PCT sets the percentage of row locks allowed before SQL Server
escalates to a table lock. The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10606 10 dump on conditions indicates whether the SQL Server will create a shared memory dump
file if any conditions configured using the sp_dumpconfig stored procedure occurs.
Possible values are 0 (not enabled) or 1 (enabled).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10607 10 enable SQL Server performance monitoring with Windows NT Perfmon.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Server Error Messages 10600 - 10699
1118
10608 10 enable unloading of a DLL after each execution of extended stored procedure.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10609 10 specify the extended stored procedure execution priority on the XP Server. The values
range from 0 to 15. The default value is 8.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10610 10 specify the extended stored procedure stack size on the XP Server. The values range and
the default value is platform dependent.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10611 10 restrict the client execution privileges of the OS command specified with xp_cmdshell.
Consult documentation for further details.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10612 10 enable start of Sybmail session with Windows NT mail subsystem with SQL Server
startup.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10613 10 enable SQL Server Error logging with Windows NT Event Viewer.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10614 10 enable SQL Server audit (logon success) logging with Windows NT Event Viewer.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10615 10 enable SQL Server audit (logon failure) logging with Windows NT Event Viewer.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10616 10 specify the computer name for centralized error logging with Windows NT Event
Viewer.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10617 16 cis rpc handling specifies whether Component Integration Services or a site handler is
used to send RPCs. The default is 0 (a site handler is used).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10618 16 This parameter is used to change the value of the maximum number of roles that can be
enabled by any user in a session.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1119
10619 10 number of large i/o buffers controls the number of extent size i/o disk buffers which are
allocated at server startup. These buffers are used by 'disk mirroring', 'load database' and
some dbcc commands.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10620 10 number of worker processes is the maximum number of worker processes that can be in
use Server-wide at any one time.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10621 10 memory per worker process is the additional amount of memory that will be allocated to
each worker process.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10622 10 max parallel degree is the maximum number of worker processes that can be used by a
given query at any one time.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10623 10 max scan parallel degree is the maximum number of worker processes that can be used
for a parallel scan against a non-partitioned object.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10624 10 When set to 1, the Server will allow ONLY those user connections which have already
been authenticated by the underlying security mechanism. Default is 0.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10625 10 When set to 0, the Server will not initialize the Security Control Layer (support for
security services is disabled). Default is 0.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10626 10 When this parameter is set to 1, the SQL Server will not allow any user connections
which are not using message confidentiality. Default value is 0.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10627 10 When this parameter is set to 1, the SQL Server will not allow any user connections
which are not using message integrity. Default value is 0.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 10600 - 10699
1120
10628 10 When set to 1, the Server will not allow any user connections which are not using
message replay detection checks. Default value is 0. When set to 0, the Server will allow
connections which use message replay as well as those which don't.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10629 10 When set to 1, the Server will not allow any user connections which are not using
message origin checks. Default value is 0. When set to 0, the Server will allow
connections which use message origin checks as well as those connections which don't.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10630 10 When set to 1, the Server will not allow any user connections which are not using
message out of sequence detection checks. Default value is 0.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10631 10 Each character from this string that appears in the principal name is mapped into the
DOLLAR sign. This is required to take care of those characters that may be valid in an
underlying security mechanism but not valid in the SQL Server name space.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10632 10 This login will be used by the SQL Server to let a user enter the SQL Server as a secure
default login if the user has already been authenticated by the underlying security
mechanism but does not have an entry in the syslogins table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10633 10 Each character from this string that appears in the principal name is mapped into the
POUND sign. This is required to take care of those characters that may be valid in an
underlying security mechanism but not valid in the SQL Server name space.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10634 10 Each character from this string that appears in the principal name is mapped into the
UNDERSCORE sign. This is required to take care of those characters that may be valid
in an underlying security mechanism but not valid in the SQL Server name space.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10635 10 determines whether users can modify their curread when a cursor is open. The default is
1 (allow users to modify their curread when a cursor is open).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1121
10636 10 enables/disables the grouping of stored procedures. The default is 1 (procedure grouping
allowed).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10637 10 enables/disables granting select to public to the text column of the syscomments table.
The default is 1 (grant select on syscomments.text to public).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10638 10 enables/disables the ability to send messages to internet addresses. The default is 0
(sendmsg not allowed).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10639 10 enables/disables auditing for the whole server. The default is 0 (auditing disabled).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10640 10 establishes where SQL Server writes audit records. Values can be 1 to 8, representing
sysaudits_01 through sysaudits _08; 0 means to set the current audit table to the next in
sequence. The default is 1.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10641 10 controls what happens when the audit table becomes full. Values are (1) suspend the audit
process and all auditable user processes (default), and (0) truncate the next audit table and
start using it as the current table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10642 10 indicates the default port number for sending internet messages.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10643 10 enables/disables character conversion before sending to or receiving from the client. The
default is 0 (SQL Server will convert characters before sending to or received from the
client).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10645 16 Maximum dump conditions indicates the maximum number of shared memory dump
conditions that can be configured on this server. The value of this field may be from 10
to 100. The default value is 10.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10646 16 This configuration option enables/disables the bidirectional index scans
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 10600 - 10699
1122
10647 10 enables/disables asynchronous prefetch server-wide. Sets the percentage of each buffer
pool in which prefetched but unused pages can be stored. If needed, this value can be
overridden for a pool with local async prefetch limit
Explanation: This is an informational message. No action is required.
10648 10 disable disk mirroring is a toggle that allows the user to utilize SQL Server disk mirroring.
Explanation: This is an informational message. No action is required.
10649 10 A transaction descriptor is used for each transaction started in a database by a user
connection. The number of transaction descriptors per process times the number of user
connections is the total number of transaction descriptors available.
Explanation: This is an informational message. No action is required.
10650 10 enables unicode-based character set conversions. When set to 1, enables conversions for
character sets not already in syscharsets. When set to 2, enables Unicode-based
conversions for all connections. The default is 0 (off).
Explanation: This message is generated from sp_configure when you ask for a
description of the 'enable unicode conversions' option.
10651 10 size of unilib cache sets the size of memory (in bytes) to be set aside for additional
Unicode-based conversions and collations.
Explanation: This is an informational message returned by sp_configure to describe
what the 'number of unilib buffers' option does.
10652 16 Configures cache partition server-wide. The global cache partition number must be power
of 2, between 1 to 64 and the partitioned buffer pool size must be at least 256P.
Explanation: This is an informational message.
10653 10 The value of ’number of ccbs’ is the number of Configurable Action Point Control Blocks
available to aid debugging.
Explanation: This message documents a feature introduced in Galaxy. However, the
config parameters and the message do show up in an 11.9 server. The parameters have no
effect on the 11.9 server though.
10654 10 The value of ’caps per ccb’ is the maximum number of Configurable Action Points that
can be configured at any one time within one Configurable Action Point Control Block.
Explanation: This message documents a feature introduced in Galaxy. However, the
config parameters and the message do show up in an 11.9 server. The parameters have no
effect on the 11.9 server though.
10655 10 The value of ’average cap size’ is a guess at how many bytes of memory will be required
to store the information associated with a typical Configurable Action Point.
Explanation: This message documents a feature introduced in Galaxy. However, the
config parameters and the message do show up in an 11.9 server. The parameters have no
effect on the 11.9 server though.
10656 16 enable java specifies whether Java Services are loaded when the server is started. The
default is 0 (not loaded).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1123
10657 16 Size of object heap is the per-process memory used for allocating Java objects.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
10658 16 Size of class heap is the memory used for Java classes and other such structures that are
shared between all processes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
10659 10 The 'license information' configuration parameter sets the number of user logins for
which Adaptive Server is licensed. When this count is exceeded, an informational
message is printed to the error log. Contact Sybase to purchase additional licenses.
Explanation: This is an informational message. No action is required.
10660 10 This configuration option ’enable xact coordination’ enables/disables Adaptive Server
distributed transaction coordination services.
Explanation: This is an informational message. No action is required.
10661 10 The configuration option ’xact coordination interval’ changes the distributed transaction
recovery interval.
Explanation: his is an informational message. No action is required.
10662 10 The configuration option ’number of dtx participants’ sets the maximum number of local
and remote distributed transaction participants that can be active at any instance of time.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10663 10 The configuration option ’strict dtm enforcement’ when enabled enforces that only
participants that can be managed through Adaptive Server distributed transaction
management protocol(s) can participate in a distributed transaction.
Explanation: This is an informational message. No action is required.
10664 10 The configuration option ’dtm lock timeout period’ sets the maximum time, in seconds,
a distributed transaction participant waits on a lock request after which the lock request
is timed out.
Explanation: This is an informational message. No action is required.
10665 10 Allow the query optimizer to consider sort-merge join and Join Transitive Closure(JTC).
The default is 0. By default, the optimizer does not evaluate sort-merge join and join
transitive closure, when generating query execution plans.
Explanation: This is an informational message. No action is required.
10666 16 Size of global fixed heap is the size of memory used by the Java subsystem for internal
data structures and other needs that are shared by all processes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 10600 - 10699
1124
10667 10 enable monitoring specifies whether the Adaptive Server will collect information for the
Monitoring and Diagnostic System.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10668 10 autostart collector indicates whether the Adaptive Server will start the Q Diagnsotics
Engine collector process on server startup.
Explanation: This is an informational message. No action is required.
10669 10 collector repository server specifies the name of the Q Diagnostics Engine repository
server.
Explanation: This is an informational message. No action is required.
10670 10 collector application host specifies the name of the Q Diagnostics Engine Application
Server host system.
Explanation: This is an informational message. No action is required.
10671 10 collector errorlog file specifies the directory in which the Q Diagnostics Engine Collector
process should place its errorlog file.
Explanation: This is an informational message. No action is required.
10672 10 collector failover file specifies the directory in which the Q Diagnostics Engine Collector
process should place it’s failover file
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10673 10 collection interval specifies the amount of time the Q Diagnostics Engine Collector
process waits between each data collection cycle.
Explanation: This is an informational message. No action is required.
10674 10 sql text pipe active indicates whether the Adaptive Server will collect historical sql batch
text information.
Explanation: This is an informational message. No action is required.
10675 10 sql text pipe max messages specifies the maximum number of messages that can be stored
for historical sql text.
Explanation: This is an informational message. No action is required.
10676 10 plan text pipe active indicates whether the Adaptive Server will collect historical plan text
monitoring information.
Explanation: This is an informational message. No action is required.
10677 10 plan text pipe max messages specifies the maximum number of messages that can be
stored for historical plan text.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10678 16 statement pipe active indicates whether the Adaptive Server will collect historical
statement level monitoring information.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1125
10679 10 statement pipe max messages specifies the maximum number of messages that can be
stored for historical statement text.
Explanation: This is an informational message. No action is required.
10680 10 errorlog pipe active indicates whether the Adaptive Server will collect historical errorlog
monitoring information.
Explanation: This is an informational message. No action is required.
10681 10 errorlog pipe max messages specifies the maximum number of messages that can be
stored for historical errorlog text.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
10682 10 deadlock pipe active indicates whether the Adaptive Server will collect historical
deadlock monitoring information.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10683 10 deadlock pipe max messages specifies the maximum number of messages that can be
stored for historical deadlock data.
Explanation: This is an informational message. No action is required.
10684 10 wait event timing specifies whether the Adaptive Server will collect monitoring data for
all wait events.
Explanation: This is an informational message. No action is required.
10685 10 process event timing specifies whether the Adaptive Server will collect monitoring data
on wait events for individual processes.
Explanation: This is an informational message. No action is required.
10686 10 object lockwait timing specifies whether the Adaptive Server will collect timing data on
lock requests.
Explanation:
10687 10 SQL batch capture indicates whether the Adaptive Server will collect sql batch text for
each process.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10688 16 tatement statistics active indicates whether the SQL Server will collect ad-hoc statement
monitoring information
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
10689 16 ’text prefetch size’ specifies the number of text pages to prefetch into the text read
pipeline.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 10600 - 10699
1126
10690 10 The ’default exp_row_size percent’ parameter reserves a specified percentage of page
size for expanding updates in data-only-locked tables. The default value is 5.
Explanation: This is an informational message. No action is required.
10691 10 ’enable housekeeper GC’ is a toggle that enables the housekeeper task to perform space
reclamation on data-only-locked tables. The default value is 1 (enabled).
Explanation: This is an informational message. No action is required.
10692 10 ’enable rep agent threads’ is a toggle that enables RepAgent threads within Adaptive
Server. The default value is 0 (disabled).
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10693 10 ’lock scheme’ sets the default locking scheme to be used by the create table and select
into commands when a lock scheme is not specified in the command. The default value
is allpages.
Explanation: This is an informational message. No action is required.
10694 10 ’lock wait period’ limits the number of seconds that tasks wait to acquire a lock on a table,
data page or data row. The default value is 2,147,483,647. At the default value, all tasks
wait indefinitely for locks.
Explanation: This is an informational message. No action is required.
10695 10 ’max SQL text monitored’ specifies the amount of memory allocated per user connection
for saving SQL text to memory shared by Adaptive Server. The default value is 0.
Explanation: This is an informational message. No action is required.
10696 10 ’read committed with lock’ determines whether an Adaptive Server using transaction
isolation level 1 (read committed) holds shared locks on rows or pages of data-only-
locked tables during select queries. The default value is 0 (off).
Explanation: This is an informational message. No action is required.
10697 10 maximum failed logins is the number of _consecutive_ failed login attempts permitted
before the targeted login is locked. It is set to zero after every successful login.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10698 10 minimum password length is the minimum number of characters a password must have
to be accepted for any new logins. Logins that were set up using the previously set
minimum password length can continue having fewer characters for their passwords.
Explanation: This is an informational message. No action is required.
10699 10 Setting configuration parameter ’check password for digit’ to 1 checks newly set
passwords for the presence of at least one digit. This parameter is off(set to 0) by default.
Explanation: This is an informational message. No action is required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1127
Server Error Messages 10700 - 10799
Number Severity Text and Explanation
10701 16 getMoreResults() is not allowed after executeQuery() or executeUpdate().
Explanation: This is an informational message or a message header. No action is
required.
10707 16 Unhandled Java Exception: %s.
Explanation:
10708 16 Class %.*s not found. Check and make sure that the class has been installed, and an entry
exists in Sysxtypes.
Explanation:
10709 16 Illegal reference to field ’%.*s’. Field accesses can only be performed on object-valued
expressions.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10710 16 No public non-static variable ’%.*s’ found in class ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10711 16 Cannot find a public method named ’%.*s’ in class ’%.*s’. Either the method does not
exist, or it is being called with the incorrect argument types.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10712 16 When using JDBC to execute a stored procedure, the results must be completely
processed before any other stored procedure can be executed. You attempted to execute
two procedures simultaneously.
Explanation: ommand failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10713 16 A JDBC query batch without any SQL statements was found. JDBC batches must contain
at least one SQL statement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10714 16 Illegal use of parameters in: %s. JDBC does not allow parameters in methods of
’statement’ objects.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10715 16 Parameter number %d is invalid for the current JDBC statement batch.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Server Error Messages 10700 - 10799
1128
10716 16 A SQL statement which produces a result set was submitted through a JDBC
executeUpdate() method. Use the JDBC execute() or executeQuery() methods.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10717 16 A single batch with SQL statements which produce multiple result sets was submitted
using the JDBC executeQuery() method. Use seperate batches or use the execute()
method.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10718 16 JDBC statement attempted to update a table which is already in use outside of the context
of the JAVA method which submitted the statement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10719 16 The %s command is not allowed in JDBC.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10720 16 A JDBC statement caused a trigger to fire which generates a result set. Result sets in
triggers are not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10721 16 Class %.*s does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10722 16 Package %.*s not found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message. C
10723 16 Class %.*s belongs to a jar. It cannot be independently removed or replaced.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10724 16 Jar %.*s does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10725 16 Class %.*s is in use. It cannot be removed.
Explanation: ommand failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10726 16 Cannot open file %.*s. If you’ve specified a relative pathname, re-try the command using
an absolute pathname.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1129
10727 16 Invalid text pointer specified.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10728 16 The specified file or image column contains a Java class. Java classes cannot be directly
installed. Enclose this class in a jar and re-try your command.
Explanation: ommand failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10729 16 The specified file or image column does not contain a valid jar. Install failed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10730 16 You’re attempting to install a jar that contains compressed classes. Re-create this jar
without using compression, and try the command again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10731 16 The specified jar contains a class whose name exceeds the server limits in length. Such
classes cannot be installed.
Explanation: Command failed due to invalid or illegal request.
10732 16 You’re attempting to install a class named %.*s. This class belongs to a package reserved
for system classes and cannot be installed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10733 16 Class %.*s cannot be replaced because it belongs to a different jar. Install failed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10734 16 Cannot run this command because Java services are not enabled. A user with System
Administrator (SA) role must reconfigure the system to enable Java.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10735 16 Jar ’%.*s’ not found. Check and make sure that the jar has been installed, and an entry
exists in Sysjars.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10736 16 Cannot convert datatype ’%s’ to datatype ’%s’. Either such conversion is not supported
or the datatype(s) is invalid.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10737 16 An internal conversion error was found while converting datatype ’%s’ to datatype ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 10700 - 10799
1130
10738 16 An overflow error was found while converting datatype ’%s’ to datatype ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10739 16 An underflow error was found while converting datatype ’%s’ type to datatype ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10740 16 Table %.*s does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10741 16 Arithmetic operations on extended type values are currently unsupported.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10742 16 You cannot do an update (INSERT, DELETE or UPDATE) from a JAVA method which
is invoked in a query already doing an update.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10743 16 The %s command is only allowed in JDBC if it does not change the current value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10744 16 You cannot use Java-SQL class datatypes in an ORDER BY clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10745 16 Conversion error detected while converting SQL data to Java data. Either the conversion
is not supported or the datatype(s) is invalid.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10746 16 No public field ’%.*s’ exists in the specified class ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10747 16 You tried to assign a value to a field in a NULL-valued object.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10748 16 You cannot create index on a column, ’%.*s’, that has a Java-SQL class datatype.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10749 16 Conversion error detected while converting Java data to SQL data. Either the conversion
is not supported or the datatype(s) is invalid.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1131
10750 16 You cannot use a Java-SQL class datatype in which the size of class is more than the
server limits in this aggregate expression.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10751 16 You cannot use a Java-SQL class datatype in this subquery or aggregate expression.
Explanation: ommand failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
10752 16 Instance methods can only be executed on object-valued expressions.
Explanation: ommand failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message. C
10753 16 Cannot find class ’%.*s’ in the database that matches the return datatype of the specified
method.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10754 16 Java datatype returned by a method cannot be mapped to SQL datatype.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10755 16 You cannot pass a SQL NULL value as an argument to a Java method.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10756 16 You cannot pass data that has a TEXT or IMAGE datatype as an argument to a Java
method.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10757 16 Java datatype returned by a field cannot be mapped to SQL datatype.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10758 16 The length of serialized object exceeds the maximum of %d bytes.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10759 16 Unable to load the class ’%.*s’ at execution time. The schema may have changed since
the command was compiled.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10760 16 Unable to load the method ’%.*s’ at execution time. The schema may have changed since
the command was compiled.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 10700 - 10799
1132
10761 16 You specified invalid datatypes in object comparison.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10762 16 Cannot initialize the Java Virtual Machine because the Java class library
($SYBASE/$SYBASE_ASE/lib/runtime.zip) is either missing, corrupted, or
incompatible with the current server release. Contact your System Administrator for help.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10763 16 Execution of remote procedure calls is not supported in JDBC.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10764 16 Cannot execute this operation due to insufficient memory in the Java heap(s). Increase the
value of the configuration parameters ’size of process object heap’ and/or ’size of shared
class heap’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10765 16 Cannot insert an object of class ’%.*s’ into a column because the object is not serializable.
An object is serializable if its class implements the ’java.io.Serializable’ or
’java.io.Externalizable’ interface.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10766 16 %s is not the acceptable URL for ASE JDBC driver.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10767 16 The wasNull() method failed, because there is no output parameter registered or no
parameter has been got from the engine.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10768 16 %s is not a valid value for a parameter index. Valid values are 1 to %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10769 16 Cannot get the value for parameter ’%s’ because it is not an out parameter.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10770 16 The connection has been closed or does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10771 16 %s is not a valid Column index value. Valid values are 1 to %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1133
10772 16 Cannot get data value or metadata from the result set because the result set has been
closed or does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10773 16 Cannot find column name ’%s’ in this result set.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10774 16 SQL statement execution error occurred, use catch statement to get the detailed
information.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10775 16 You cannot use the statement handle because it has been closed or does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10776 16 Parameter ’%s’ is registered as output parameter with ’%s’ type which is not compatible
with it’s in type ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10777 16 getColumnCount() failed because there is no valid column count for this query.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10778 16 getResultSetMetaData() failed because the query does not generate result set or the result
set does not exist.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10779 16 Cannot set java object at parameter ’%s’ because either no conversion is available to map
the object to any ASE SQL datatype or the java object is invalid.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10780 16 Either ’%s’ is not a valid JDBC datatype or no conversion is available to map the
JDBC/Java datatype to an Adaptive Server datatype.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10781 16 Cannot convert object to ’%s’ because either the conversion was attempted between an
illegal pair of object types or a format error was encountered in the conversion.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10782 16 Method ’%s’ is not supported in the ASE JDBC driver.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 10700 - 10799
1134
10783 16 %s is not a valid value for a parameter index because there is no parameter declared.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10784 16 Cannot convert object to any valid numeric data type because either the conversion was
attempted between an illegal pair of object types or a format error was encountered in the
conversion.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10785 17 A Java operation or conversion failed, most likely due to insufficient memory. Please
consult the errorlog for more information.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
10786 17 Insufficient system resources to execute this operation. Too many databases have been
opened in order to load classes. Please wait for a few processes to terminate before
retrying this command.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
10787 16 Cannot update or remove Java classes while the current process is still holding references
to objects.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10788 16 Operation failed because the object being deserialized belongs to class ’%s’ which is
incompatible with its declared class ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10789 16 There is already a class named ’%.*s’ in the database.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10790 16 There is already a jar named ’%.*s’ in the database.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10791 16 Process cannot update or remove class loader because Java Debugger is attached to the
process.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10792 16 Cannot invoke method ’%.*s’ on class ’%.*s’. Instance methods can only be invoked on
objects.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1135
Server Error Messages 10800 - 10899
10793 16 There is no class in a jar. Make sure that jar contains at least one class. Install failed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10794 16 Cannot pass NULL as the value for parameter number %d to the method ’%s’ in class
’%s’. The parameter is of a Java primitive datatype, and is non-nullable.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10795 16 The file ’%.*s’ contained in the jar does not represent a valid Java class file.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10796 10 Warning! Expecting file ’%s’ to contain Java class ’%s’. Instead, class ’%s’ was found.
Installing the class under the correct name ’%s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
10797 16 Cannot execute the prepared statement because the ’%s’ parameter has not been set.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10798 16 Cannot get the column value because the result set has not been opened yet. Use the
’next()’ function to open the result set before getting the column value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10799 16 Cannot get the column value because there are no more row in the result set.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Number Severity Text and Explanation
10801 16 Invalid type configured for cache %s. Cache type can be one of default OR mixed OR
log along with HK ignore but NOT just HK ignore alone.
Explanation: There may be possible corruption in a database or a database object. Take
any corrective action indicated by the message. Consult the Adaptive Server System
Administration Guide and the Troubleshooting Guide.
Server Error Messages 10800 - 10899
1136
10802 16 Configuration Error: Configuration Parameter `%s' cannot be changed to 1 when
parameter `evaluated configuration' is set to 1.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10803 16 Configuration Error: Cannot set configuration parameter `evaluated configuration' to 1.
Other Security related configuration parameters need to be set properly before this
parameter can be changed to 1. Please contact a user with SSO role for help.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10807 16 The value of `max parallel degree' (`%d') cannot be less than the value of `max scan
parallel degree' (`%d').
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10808 10 Use sp_configure to lower the value of `max scan parallel degree' or raise the value of
`max parallel degree'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10809 16 The value of `number of worker processes' (`%d') cannot be less than the value of `max
parallel degree' (`%d').
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10810 16 Use sp_configure to lower the value of `max parallel degree' or raise the value of `number
of worker processes'.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
10812 20 Auditing: Fatal erorr - could not truncate the audit table `%.*s'. This is an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
10813 16 Audit table cannot be changed because the log device in the sybsecurity database is full.
Explanation: SSO is trying to change the current audit table number but the log for
sybsecurity is full.
10814 20 Auditing: Fatal error - could not get the name of the audit table with the object id `%d' to
truncate it. This is an internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
10815 16 The lock hashtable size must be a power of 2. You have specified a size of %d, which is
not a power of 2. The next highest power of 2, %d, will be used instead.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1137
10816 16 The value of the `dump on conditions' configuration parameter must be either 0 or 1.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10817 16 Configuration Error: Unknown cache replacement policy `%s' defined for cache `%s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10818 10 Warning: the value provided for `parallel_degree' (`%d') was less than the value of
`scan_parallel_degree' (`%d'). The value of `scan_parallel_degree' has been adjusted to
`%d'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10819 10 The value of `scan_parallel_degree' (`%d') cannot be larger than the value of
`scan_parallel_degree' set by a calling procedure. The value `%d' is used.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10820 10 The configuration option `%s' has been changed by `%s' from `%s' to `%s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
10821 16 The configuration option `%s' requires a character string.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10822 16 The string size of the configuration option `%s' must be less than `%d'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10823 16 The specified memory, `%ldK', is not big enough to configure the configuration
parameter, `%s', to a valid value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10824 16 Illegal value `%s' specified for configuration option `%s'. The legal values are between
`%ld' and `%ld'.
Explanation: You tried to read in a configuration file which contains an alphanumeric
value for an integer configuration parameter. Correct the file entries.
10825 16 Configuration parameter, `%s', will consume more than %ld bytes of memory if
configured at %ld.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10826 16 The value of the ’max memory’ parameter ’%ld’ is not high enough to set the other
parameter values for the current SQL Server configuration.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 10800 - 10899
1138
10827 10 Warning: the value of the configuration parameter 'max scan parallel degree' has been set
to %d. For optimal performance, a value no larger than 4 is recommended.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10828 10 Consider increasing the value of configuration parameter ’max memory’ or decreasing
the value of configuration parameters causing significant memory consumption, such as
’number of user connections’.
Explanation: Refer to “Configuring Memory” in the System Administration Guide for
information on how Adaptive Server uses memory.
10829 16 Adaptive Server cannot estimate the memory requirement. See the System
Administration Guide for information about Adaptive Server memory requirement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10830 16 Configuration parameter '%s' can be only 0 or 1.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10831 16 Configured 'number of cache partitions' ('%d') is illegal in cache '%s'. The value must be
a power of '2' and between '%d' and '%d'.
Explanation:
10832 16 Each partitioned pool must be at least 256P. With the ’%d’ partitions we cannot configure
this value for buffer pool (%dk) in cache (%s). Please configure a bigger pool or reduce
the number of cache partitions.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10833 16 Cannot disable CIS Services as transaction coordination requires CIS Services to be
enabled. Please disable transaction coordination first.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10834 16 Configuration parameter ’%s’ can not be enabled without license ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10835 16 The license allows maximum %d engines only.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10836 16 Cannot ’enable ha’ as HA services require transaction coordination. Please enable
transaction coordination first.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1139
10837 16 Cannot ’enable ha’ as HA services require Omni services . Please enable Omni services
first.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10838 16 Server is currently HA cluster configured. ASE HA Services can not be disabled.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10839 16 The User Log Cache has been configured too small. The minimum size of a user log cache
is the max page size (in bytes) the server is using, which is %d Kilotyes for the current
server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10840 16 Memory grow failed for pool %s. Error code %d. This is possibly due to memory
fragmentation. This pool may grow on demand. Please increase ’max memory’ and retry
the configuration.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10841 16 The value of parameter ’max memory’ ’%ld’ cannot be less than the ’total logical
memory’ size ’%ld’. Please reconfigure ’max memory’ to be greater than or equal to the
total logical memory required.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10842 16 The value specified for configuration option ’%s’ ’%d’ may not be greater than the value
’%d’ specified for configuration option ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10843 16 The value specified for configuration option ’number of engines at startup’ ’%d’ may not
be greater than the number of available CPUs ’%d’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10844 16 Cannot enable ’use ssl client cert auth’ configuration parameter.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
10845 16 The maximum number of memory maps ’%d’ has been reached for ’%s’ pool. You will
have to reboot the server to reconfigure ’%s’. You may be able to reconfigure other
configuration parameters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 10900 - 10999
1140
Server Error Messages 10900 - 10999
10846 16 Overflow error: The ’total logical memory’ ’%d’ (2k pages) required for the
configuration exceeds the maximum size of memory available on a ’%d’ bit platform:
’%lu’ bytes. Please reduce the configuration values that are consuming large amounts of
memory.
Explanation: Take corrective action indicated by message. Check the System
Administration Guide for discussion of how Adaptive Server uses memory.
10847 16 The Adaptive Server Enterprise Small Business Edition does not allow you to set this
configuration parameter to a value higher than %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions.
Number Severity Text and Explanation
Number Severity Text and Explanation
10901 17 This query requires %d auxiliary scan descriptors, but currently there are only %d
auxiliary scan descriptors available. Either raise the value of the `number of auxiliary scan
descriptors' configuration parameter or try your query later.
Explanation: Command failed due to resource limitation. Retry when the resource is
available, or contact your System Administrator to address the resource problem.
10902 17 This query requires %d auxiliary scan descriptors, but the Server is configured with only
%d auxiliary scan descriptors. Raise the value of the `number of auxiliary scan
descriptors' configuration parameter before trying this query.
Explanation: Command failed due to resource limitation. Contact your System
Administrator to address the resource problem.
CHAPTER 6 Adaptive Server Error Messages
1141
Server Error Messages 11000 - 11099
Number Severity Text and Explanation
11001 10 Row count exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor were
exceeded.
11002 10 Estimated IO cost exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor were
reached.
11003 10 Actual IO cost exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor were
reached.
11004 10 Query batch running time exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor were
reached.
11005 10 Transaction's running time exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor were
reached.
11006 17 Unable to set a kernel alarm; timerange manager is unable to run.
Explanation: Resource Governor could not set an alarm. Check alarm resources.
11007 17 Unable to set a kernel alarm; time limit alarm cannot be set.
Explanation: Resource Governor could not set an alarm. Check alarm resources.
11008 20 An attempt to get a free cache member from the Resource Governor's pool has failed. This
is a system error -- contact a user with System Administrator (SA) role.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11009 16 Syntax error converting to DATETIME from BINARY/VARBINARY string.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11010 10 Unknown limit type %d encountered -- limit will be ignored.
Explanation: Illegal limit type was defined with Resource Governor.
11011 10 Unknown limit scope 0x%x encountered -- limit will be ignored.
Explanation: Illegal limit range was defined with Resource Governor.
11012 10 Unknown limit enforcement time %d encountered -- limit will be ignored.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
Server Error Messages 11000 - 11099
1142
11013 16 Correlated columns are not allowed in the outer join clause of the subquery.
Explanation: Refer to the writeup for Error 301.
11014 16 Insufficient worker processes available. Query executed using current available worker
processes. Inform the system administrator (SA) that the value of worker processes m ay
be too low.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
11015 16 Insufficient worker processes available. To execute, wait until the system is less busy or
set process_limit_action to quiet or warning, or increase the value of worker processes.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
11016 16 Cannot disable the role '%.*s' since you don't have it enabled.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
11017 20 DLL for the extended stored procedure '%1!' is not found. This is an internal error. Please
contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11018 10 XP Server must be up for ESP to execute.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
11019 16 Parameters to extended stored procedure must be passed all by name or all by position.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11020 16 Pseudo-column SYB_IDENTITY is referenced from a stored procedure after the identity
column has changed. Please drop/recreate the stored procedure.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11021 16 Function %s invoked with wrong number or type of argument(s).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11022 16 Internal structure for cursor ’%.*s’ could not be located. This is a severe error. Please
check for other errors preceding this one in the errorlog
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11023 16 An internal structure for the cursor could not be created. This is deemed to be a serious
error.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1143
11026 10 Warning: The statement on line %d uses the '%.*s' option with the view '%.*s'.
Performance hint options are valid only for tables. This hint will be ignored.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
11029 16 An index was found on table '%.*s' created via SELECT INTO. Parallel inserts into
indexed tables is unsupported. Drop the table and retry the command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11030 16 Execution of %S_MSG %.*s failed because the server was unable to change the owner
context in database %S_DBID when upgrading the compiled object.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11031 16 Execution of %S_MSG %.*s failed because of errors parsing the source text in
syscomments during upgrade. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11032 16 Execution of %S_MSG %.*s failed because the upgrade processing found incorrect
source text in syscomments. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11033 16 Execution of %S_MSG %.*s failed because the upgrade processing did not find source
text in syscomments. Please drop and recreate %.*s.
Explanation: ommand failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
11034 16 Execution of %S_MSG %.*s failed because the hidden source text could not be decrypted
during upgrade. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11035 16 Execution of %S_MSG %.*s failed because upgrade found no entry in syscomments for
this object. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11036 16 Your password will expire in %.*s days.
Explanation: This is an informational message or a message header. No action is
required.
11037 16 You specified an incorrect datatype for the variable containing the ’execute immediate’
command string.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 11000 - 11099
1144
11038 16 Your password will expire in %.*s days.
Explanation: This is an informational message or a message header. No action is
required.
11039 16 Another Execute Immediate statement cannot be executed inside an Execute Immediate
statement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11040 16 Adaptive Server cannot perform the requested action because column ’%.*s’ is not within
the scope of the joined table expression. Check your command for missing or incorrect
database objects, variable names, and/or input data.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11041 16 Adaptive Server cannot perform the requested action. Sybase outer joins and ANSI joins
cannot be mixed in the same query. Rewrite the command as specified in the error
message.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11042 18 Internal Error: Adaptive Server cannot find the ANSI outer join. The query tree may be
corrupted. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
11044 16 Warning: Ignoring rule/check constraint ’%.*s’ specified on table ’%.*s’ because it refers
to TEXT, IMAGE, or offrow Java datatype columns.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11045 16 %s command not allowed within the current running mode of the companion server
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11046 10 Warning: The results of the statement on line %d are join-order independent. Results may
differ on pre-12.0 releases, where the query is potentially join-order dependent.
Explanation: There may be a potential problem with a database or database object.
Contact your System Administrator.
11047 17 Insufficient number (%d) of ’worker processes’ available at execution time to alter %d-
way partitioned table ’%.*s’. Increase the number of ’worker processes’ or wait until the
system is less busy.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1145
11048 17 ALTER TABLE ’%.*s’ failed. Cursor ’%.*s’ is still open. Close this and any other open
cursors on this table before this schema change operation.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
11049 16 Cannot add column with duplicate name. A column with name ’%.*s’ already exists in
this table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11050 16 Adaptive Server cannot process this ALTER TABLE statement due to one or more
preceding errors. If there are no preceding errors, please contact Sybase Technical
Support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11051 20 ALTER TABLE ’%.*s’ failed. Table is currently being used by one or more other tasks.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11052 16 The ’select into’ database option is not enabled for database ’%.*s’. ALTER TABLE with
data copy cannot be done. Set the ’select into’ database option and re-run.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11053 16 Cannot alter table ’%.*s’ because the database option ’allow nulls by default’ has been
changed by concurrent users.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11054 16 The table ’%.*s’ is an inner member of an outer-join clause. This is not allowed if the
table also participates in a regular join clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11055 16 Query contains an illegal outer-join request.
Explanation: Refer to the writeup for Error 301.
11056 16 Exceeded tempdb space limit of %ld pages.
Explanation: Rewrite the query or contact your System Administrator to address the
resource limitation.
11057 16 Execute cursor ’%.*s’ may not be declared on a SQLJ procedure.
Explanation: Command failed due to invalid or illegal request.
Number Severity Text and Explanation
Server Error Messages 11100 - 11199
1146
Server Error Messages 11100 - 11199
11058 16 Statement contains ’%d’ columns/expessions in the target list. This exceeds the maximum
limit of ’%d’.
Explanation: Rewrite the query or split into multiple queries to conform to the server
limits.
11059 16 Too many tables in the query. The maximum allowable is %d.
Explanation: Rewrite the query or split into multiple queries to conform to the server
limits.
11060 16 This statement has exceeded the maximum number of recompilations (%d). This
indicates an internal error. Please note the error prior to this one and contact Sybase
Technical Support.
Explanation: Normally, a given statement in a stored procedure is recompiled only
once, but due to lack of resources or other factors, it might need to be recompiled more
than one time. This error is raised if the procedure is recompiled more than the specified
number of times, and is an indication of an internal error.
Number Severity Text and Explanation
Number Severity Text and Explanation
11101 16 Cannot grant the role '%.*s' because it contains role '%.*s' which is mutually exclusive
with role '%.*s' which is possessed by grantee '%.*s'. Remove the exclusivity and try
again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11102 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at activation
or membership level with role '%.*s' (contained by role '%.*s' which is the grantee role or
the ancestor role of grantee). Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11103 16 Cannot grant the roles '%.*s' and '%.*s' because they are mutually exclusive at activation
or membership level. Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11104 16 Cannot grant the role '%.*s' to role '%.*s' because it will result in cycle.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1147
11105 16 No such user/role '%.*s' exists.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11106 16 Failed to grant role '%.*s' to grantee '%.*s' because failed to expand the role to be granted.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11107 10 All the roles specified to be granted in the grant role statement have already been granted
to grantee '%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11108 10 The result of the REVOKE ROLE command will take effect once the user logs out and
then logs in again.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11109 14 You must have SSO authorization to grant/revoke user defined roles.
Explanation: You do not have permission to execute this command. Have the object
owner or a user with the needed role run this command.
11110 14 You must be in the master database to GRANT/REVOKE ROLE. Contact the System
Administrator (SA) if you do not have permission to run USE master.
Explanation: You do not have permission to execute this command. Have the object
owner or a user with the needed role run this command.
11111 16 No such role '%.*s' exists.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11112 16 You must have SSO authorization to create User Defined Roles.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11113 16 You must be in the master database to run CREATE ROLE command. Contact the System
Administrator (SA) if you do not have permission to run USE master.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11114 16 A role with name '%.*s' already exists in this server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11115 16 The role '%.*s' was not dropped because it still has privilege granted to it. Use the 'WITH
OVERRIDE' option to drop it.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 11100 - 11199
1148
11116 16 Cannot drop role '%.*s' because it does not exist in this server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11117 16 You must have SSO authorization to drop User Defined Roles.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11118 16 You must be in the master database to run DROP ROLE command. Contact the System
Administrator (SA) if you do not have permission to run USE master.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11119 16 The role '%.*s' was not dropped because it is one of the system roles.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11120 16 You must have SSO authorization to use ALTER ROLE to define roles exclusivity.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11121 16 You must be in the master database to run ALTER ROLE. Contact the System
Administrator (SA) if you do not have permission to run USE master.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11122 16 Cannot drop the '%.*s' exclusivity between role '%.*s' and '%.*s' since it does not exist in
this server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11123 16 Operation failed because the user '%.*s' has been granted both role '%.*s' and role '%.*s'.
Revoke one of the roles from the user and rerun this command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11124 16 Operation failed because role '%.*s' has been granted both role '%.*s' and role ' %.*s'.
Revoke one of the granted roles from role '%.*s' and rerun this command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11125 10 Warning: User '%.*s' (process ID '%d') has both roles '%.*s' and '%.*s' enabled. This
violates the '%.*s' exclusivity just added. Terminate the user's process to remove the
violation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
(Not raised in 11.9.2)
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1149
11126 16 Cannot add the '%.*s' exclusivity between role '%.*s' and role '%.*s' because it already
exists for this server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11127 16 The role named as '%.*s' does not exist for this server. Check the name and resubmit the
ALTER ROLE command
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11131 16 Failed to expand the role with srid '%d' because this exceeds the maximum role limit of
'%d'. Please revoke/disable roles you don't require and then rerun your command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11132 16 SQL Server failed to execute the built-in function %s because it failed to expand the role
'%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11133 16 %s: unknown option: '%.*s'. Use either '%s' or '%s' as an option value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11134 16 You already have the role '%.*s' active.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11136 16 You have reached the limit on the number of roles you can enable per session. Increase
the value of the configuration parameter 'max roles enabled per user' and rerun your
command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11137 18 Failed to add the role '%.*s' into the current database catalogs.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
11138 16 Failed to create role '%.*s', because this exceeds the maximum number roles limit of '%d'.
Please delete roles you don't need and rerun your command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11141 16 Password required to set role '%.*s' on.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 11100 - 11199
1150
11142 16 You specified the wrong password for enabling role '%.*s'. Try again with the correct
password.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11143 16 The password specified in CREATE/ALTER ROLE command is too short. The minimum
length of passwords is %d characters. Try again with a password that is %d or more
characters in length.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11145 16 Command failed because no password exists for role '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11146 16 Password already exists for role '%.*s'. Drop the existing password and then add the new
password.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11148 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at activation
or membership level with role '%.*s' (which is the ancestor of role '%.*s' in the hierarchy).
Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11149 16 Operation failed. Role '%.*s' is contained by/contains role '%.*s'. Revoke the granted role
from role '%.*s' or '%.*s' and rerun the command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11150 16 Operation failed. Role '%.*s' is mutually exclusive at membership or activation level with
role '%.*s'. Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11151 16 Cannot grant the role '%.*s' because it is mutually exclusive with role '%.*s' which is
possessed by grantee '%.*s'. Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11152 16 Operation failed. Role '%.*s' is mutually exclusive at activation or membership level with
role '%.*s' (contained by role '%.*s' which is the grantee role or the ancestor role of
grantee). Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1151
11153 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at
membership or activation level with role '%.*s'. Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11154 16 Operation failed. Role '%.*s' has not been granted to role '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11155 16 Operation failed. Role '%.*s' has not been granted to user '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11156 16 Operation failed. Role '%.*s' is mutually exclusive at activation or membership level with
role '%.*s' (which is the ancestor of role '%.*s' in the hierarchy). Remove the exclusivity
and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11157 16 Operation failed. Role '%.*s' is mutually exclusive at membership level with role '%.*s'
(which along with role '%.*s' has been granted to user '%.*s'). Remove the exclusivity and
try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11158 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at
membership level with role '%.*s' (which along with role '%.*s' has been granted to user
'%.*s'). Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11159 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at activation
or membership level with role '%.*s' (contained by role '%.*s'). Remove the exclusivity
and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11160 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at activation
or membership level with role '%.*s'. Remove the exclusivity and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11161 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at activation
level with role '%.*s' (contained by role '%.*s', which has already been enabled).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 11100 - 11199
1152
11162 16 Operation failed. Role '%.*s' (contained by role '%.*s') is mutually exclusive at activation
level with role '%.*s' (which has already been enabled).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11165 16 A user or group with the name '%.*s' already exists in this Server.
Explanation: Informational: A role name has to be unique across the entire database.
11166 16 User '%.*s' is currently logged in. The revocation of roles from users that are currently
logged in is not allowed.
Explanation: The revocation of roles from users that are currently logged in is not
allowed as these users may already have activated the roles being revoked in their current
login session.
11167 16 The role 'sybase_ts_role' cannot be granted to other roles.
Explanation: sybase_ts_role is not meant for general or widespread use. Only the SA or
another responsible user should use it, or permit its use, in limited situations and only as
recommended by Sybase.
11168 16 The role ’%.*s’ does not have a password. The value you specified for minimum
password length will be used when a password is added to the role.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11169 16 All overrides for the ’%.*s’ option have been removed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11170 16 Invalid value specified for ’%.*s’ attribute. Try again with a valid value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11171 16 The specified password does not have any numeric characters. New passwords must have
at least one numeric character.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11172 14 The role ’%.*s’ is locked. Contact a user with System Security Officer(SSO) role.
Explanation: You do not have permission to execute this command. Have the object
owner or a user with the needed role run this command.
11173 16 Your password will expire in %.*s days.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11174 16 Operation failed because it could not be performed on both companions. Retry later.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1153
Server Error Messages 11200 - 11299
Server Error Messages 11300 - 11399
11175 16 Operation failed because the limit for maximum number of roles that can be synchronized
on companions is ’%d’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Number Severity Text and Explanation
11201 -
11299
---
Explanation: See the chapter titled "Component Integration Services Error Messages"
for an explanation of these error messages.
Number Severit
y Text and Explanation
11302 20 Internal error: Lock structure overflowed while executing the built-in function logschema()
on object '%d' in database '%d'. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
11303 16 Failed to obtain locks while executing the built-in function logschema() on object '%d' in
database '%d'. Retry the operation.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Server Error Messages 11300 - 11399
1154
11304 20 Internal error: No free session descriptor is available for opening the user object '%d' in
database '%d' while executing the built-in function logschema(). Please contact Sybase
Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
11305 16 Failed to open the object '%d' in database '%d' while executing the built-in function
logschema(). Check if the object exists and retry the operation.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
11306 16 The object '%d' cannot be found in sysobjects in database '%d'. Check the value o f the
object ID and retry the operation.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
11307 16 The object '%d' in database '%d' is not a valid parameter for the built-in function
logschema(). The object must be a user table or a stored procedure.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
11308 20 Internal Error: There is no row in sysusers in database '%d' for user with user ID '%d'.
However, this user is the owner of the object '%d' in this database. Please contact Sybase
Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
11309 16 The built-in function logschema() failed for object '%d' in database '%d'. See the other
messages printed along with this message for more information.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
11310 20 Internal Error: The database '%d' in which the object '%d' resides and the database '%d' in
which the schema needs to be logged are different for a schema modification operation.
Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
11311 20 Internal Error: The column count in the XOBJINFO log record for object '%d' in database
'%d' is different from the number of XCOLINFO log records that are logged. Please contact
Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
Number Severit
y Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1155
Server Error Messages 11400 - 11499
11312 20 Permission denied. User cannot execute the built-in function logschema() on object '%d' in
database '%d'.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
11313 20 Failed to write the replication log record for the '%.*s' command for object '%.* s' in
database '%S_DBID'. The '%.*s' command is aborted.
Explanation: Adaptive Server encountered an internal error affecting the current process.
Reconnect to Adaptive Server. Report the error to your System Administrator so DBCC
diagnostics can be run.
11314 17 Failed to write the replication log record for the '%.*s' command in database '%S_DBID'.
The '%.*s' command will not be replicated.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severit
y Text and Explanation
Number Severity Text and Explanation
11400 11 Could not load library %s.
Explanation: Command failed. Check your database for the object not found and re-
enter the command with the correct name.
11401 10 The number of RPC parameters is %d.
Explanation: This is an informational message or a message header. No action is
required.
11402 10 DLL %s was successfully loaded.
Explanation: This is an informational message or a message header. No action is
required.
11403 16 Encountered an exception(%d) in ESP %s in DLL %s. If this is an user DLL check the
code else contact Sybase Technical Support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Server Error Messages 11400 - 11499
1156
11404 20 ESP %s not found in DLL %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11405 19 Illegal ESP priority specified. Setting it to previous value %d.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
11406 10 DLLname = %s.
Explanation: This is an informational message or a message header. No action is
required.
11407 10 ESPname = %s.
Explanation: This is an informational message or a message header. No action is
required.
11408 19 Illegal DLL file name length specified. Name will be truncated to %s.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
11409 19 Illegal ESP name length specified. Name will be truncated to %s.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
11410 20 Failed to register the XP Server log file %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11411 20 Failed to set specified STACK SIZE %d for XP Server. Check the valid range in the
documentation.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11412 20 Failed to set preemptive scheduling mode. Most probably Open Server does not support
it on this platform.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11413 10 %s just disconnected.
Explanation: This is an informational message or a message header. No action is
required.
11414 10 XP Server is shutting down.
Explanation: This is an informational message or a message header. No action is
required.
11415 10 XP Server is now running.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1157
11416 20 Failed to install the connection handler. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11417 20 Failed to install the disconnect handler. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11418 20 Failed to install the RPC handler. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11419 20 Failed to install the stop handler. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11420 20 Failed to get connection context. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11421 20 Failed to set version of Open Server. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11422 20 Cannot determine XP Server name. XP Server shutting down.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11423 10 The XP Server log file name exceeded the maximum limit of %d characters.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11424 20 Failed to set error handler for XP Server. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11425 20 Failed to initialize XP Server. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11426 20 Failed to register the Start Handler. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11427 20 Failed to run XP Server. Check the XP Server log file.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11428 10 Normal exit thru return from srv_run.
Explanation: Informational message.
Number Severity Text and Explanation
Server Error Messages 11400 - 11499
1158
11429 18 Failed to free CS_CONTEXT structure. Check the XP Server log file.
Explanation: Internal error affecting current process. Contact your SA.
11430 10 ESP priority set to %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11431 10 Default stack size for ESP is %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11432 10 XP Server name is %s.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11433 19 Invalid XP Server name length specified. This is an internal error. XP Server is shutting
down.
Explanation: Command failed when a non-configurable limit was exceeded. Reconnect
to Adaptive Server and report the error to your System Administrator.
11434 10 DLLs will be unloaded automatically.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11435 10 Client impersonation context set for ESPs.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11436 10 Entering main().
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11437 10 Debug mode detected.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11438 10 NT Service Option detected. Starting service.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11439 10 Attempting StartServiceCtrlDispatcher().
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11440 20 Could not start service. Failed in StartServiceCtrlDispatcher.
Explanation: Error affects XP Server operation. Contact your SA.
11441 16 Authentication failed. Connection denied. XP Server does not accept direct connection.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1159
11442 20 Invalid authentication. Please contact Sybase Technical Support.
Explanation: Error affects XP Server operation. Contact your SA.
11443 10 Authentication was successful.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11444 20 Failed to register the service control handler. You may start the XP Server through
command line interface.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11445 10 Entered xp_srv_service_main.
Explanation: Informational message.
11446 20 Failed to create the service thread.
Explanation: Error affects XP Server operation. Contact your SA.
11447 20 Failed to create the service event.
Explanation: Error affects XP Server operation. Contact your SA.
11448 20 %s: Operating System Error: %d: %s.
Explanation: Error affects XP Server operation. Contact your SA.
11449 20 %s: Open Server Error: %d/%d/%d: %s.
Explanation: Error affects XP Server operation. Contact your SA.
11450 18 %s: Fatal XP Server Error: %d/%d/%d: %s.
Explanation: Error affects XP Server operation. Contact your SA.
11451 16 %s: XP Server Error: %d/%d/%d: %s.
Explanation: Check command syntax/semantics.
11452 10 %s just connected.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11453 20 Could not get TDS version in connection handler. This is an internal error. Please contact
Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11454 20 Invalid client or SQL Server TDS version. TDS version 4.6 or higher required.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11455 20 Failed to get thread type for connection handler. This is an internal error. Please contact
Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Server Error Messages 11400 - 11499
1160
11456 20 Failed to get login authentication type. This is an internal error. Please contact Sybase
Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11457 17 Failed to get the time. Using random macro instead.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
11458 10 The DLL %s was successfully unloaded.
Explanation: Informational message.
11459 20 The system DLL %s was not successfully loaded.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11460 18 Sybmail configuration failed. Use xp_startmail with parameters to start the SQL Server
mail session.
Explanation: Problem affected XP Server operation. Take recommended action.
11461 18 ESP configuration failed. Default Values are used.
Explanation: Informational message.
11462 16 Could not load the DLL %s.
Explanation: Contact your SA.
11463 16 Invalid number of parameters specified. Check the documentation for minimum and
maximum number of parameters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11464 16 Invalid parameter value specified. Refer the documentation for the correct value( s).
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11465 18 Event Log configuration failed.
Explanation: Contact your SA to report the problem.
11466 10 Eventlog enable/disable flag is %d.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11467 20 Invalid SQL server name length (-a). Please check the documentation. XP Server is
shutting down.
Explanation: Error affects XP Server operation. Check the configuration guide.
11468 10 SQL Server name is %s.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1161
11469 20 Error condition in ESP. Refer to the XP Server log file for more information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11470 10 Stack size specified was too small. Using default size.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11471 20 Failed to set XP Server interfaces file %s. XP Server shutting down.
Explanation: Error affects XP Server operation. Contact your SA.
11472 20 The pathname specified for the interfaces file was too long. Check documentation for the
maximum value.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11473 10 Interfaces file %s is being referred by XP Server.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11474 20 XP Server can not determine the client type.
Explanation: Error affects XP Server operation. Contact your SA.
11475 10 Direct connection to the XP Server is not allowed.
Explanation: You must communicate with XP Server using Adaptive Server
commands.
11476 20 Could not install the signal handler for %s. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11477 16 A signal(%s) was raised while executing this ESP. If this is an user DLL check the code
else contact Sybase Technical Support.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11478 20 Failed to set the service status. This is an internal error. Please contact Sybase Technical
Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11479 20 NT service manager-related internal error.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11480 10 DLL for the extended stored procedure not found. Check entry in syscomments for this
ESP.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 11400 - 11499
1162
11481 10 Unable to start XP Server startup task. The server can continue running without this task,
however notify Sybase Technical Support for this error.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11482 17 Cannot allocate memory. Check the XP Server log file.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
11483 10 XP Server configuration failed.
Explanation: Error affects XP Server operation. Contact your SA.
11484 10 Sybmail configuration for XP Server failed.
Explanation: Error affects XP Server operation. Contact your SA.
11485 20 XP Server name is required to start XP Server. XP Server shutting down.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11486 10 Cannot unload DLL %s. Either there is an Operating System error while unloading or the
DLL was never loaded.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11487 10 Attempt to free DLL failed. Check XP Server errorlog file for more information.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11488 14 User access denied. Not a member of NT administrators group.
Explanation: Check login/role permissions.
11489 10 Event Log configuration for XP Server failed. Check XP Server errorlog file for more
information.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11493 14 User access denied. Failed to change the user context.
Explanation: You do not have the permission to execute this command. Have the object
owner or a user with the needed role run this command.
11494 16 Invalid Domain Name. PLease enter the correct Domain name and re-run the command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11495 16 Failed to synchronize with the SQL Server. Shutting down the XP Server.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1163
Server Error Messages 11500 - 11599
11496 16 Cannot %S_MSG site '%S_SRVID'. Please check the XP Server error log file for detailed
error description.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11497 20 Extended stored procedure %s in dll %s has bad linkage (should be __stdcall)
Explanation: Command failed due to invalid or illegal request.
Number Severity Text and Explanation
Number Severity Text and Explanation
11501 12 Invalid data type. An integer value must be supplied for error number.
Explanation: Command failed. Specify an object of the correct type.
11502 12 Invalid data type. A VARCHAR value must be supplied for message.
Explanation: Command failed. Specify an object of the correct type.
11503 12 Invalid data type. A VARCHAR value must be supplied for type.
Explanation: Command failed. Specify an object of the correct type.
11504 16 Error number must be equal to or greater than 50000.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11505 16 Type must be 'informational', 'warning' or 'error'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11506 17 Internal error: cannot allocate memory.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
11507 16 Invalid number of parameters. Error number and message must be provided.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11508 17 Event logging is not enabled. Cannot log event in event log.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Server Error Messages 11500 - 11599
1164
11513 10 Event log computer name is %s.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11514 17 Failed to log event in Event Log. The Event Log may be FULL.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
11515 18 Failed to initialize Event Log.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
11516 20 Failed to create mutex '%s' used by Sybmail. Refer to other error messages for possible
cause of the problem.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11517 20 The mail session was already active when %s was invoked. Invocation of this ESP will
have no effect.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11518 20 Sybmail encountered CMC Error: %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11519 20 The mail session was not active. Start the mail session using xp_startmail before calling
%s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11520 20 Failed to get the number of input parameters for %s. Please contact Sybase Technical
Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11521 20 The function %s received an invalid number of parameters (%d). Check user
documentation and re-enter command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1165
11522 20 The call to srv_descfmt() failed in %s. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11523 20 The call to srv_xferdata() failed in %s. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11524 20 The function %s expected some recipients, but none were found. Re-enter command with
a value for @recipient.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11525 20 Memory allocation in %s of size %d failed. Check that sufficient memory is available to
XP Server.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11526 20 No message retrieved and/or deleted because none found.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11527 20 The call to sm_bindparamdata() failed for parameter %s. Please contact Sybase Technical
Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11528 20 The call to sm_bindretprmdata() failed for parameter %s. Please contact Sybase Technical
Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11529 20 Failed to load CMC Library. Check that the library exists in a known location and re-enter
command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11530 20 Failed to get address of function '%s'.Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
Number Severity Text and Explanation
Server Error Messages 11500 - 11599
1166
11531 20 Invocation of function %s failed. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11532 20 Failed to create attach file. Error number from Win32 System Service is %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11533 20 Failed to write to attach file. Error number from Win32 System Service is %d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11534 20 Invalid parameter '%s' received. Check user documentation and re-enter command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11535 20 The data type of parameter %s is invalid. Check user documentation and re-enter
command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11536 20 The combination of input parameters %s is invalid. Check user documentation and re-
enter command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
11537 20 The value of parameter %s is invalid. Check user documentation for correct value.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11538 20 The result set obtained by executing the supplied query is invalid. Review the text of
query batch and re-enter command.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11539 20 Failed to get thread property in %s. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11540 20 Failed to obtain lock in function %s. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1167
11541 20 Failed to unlock mutex in function %s. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11542 20 Invalid mail profile name received. Check 'MailUserName' configuration parameter
value for SQL Server login 'sybmail'.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11543 20 The operation type passed to %s is invalid.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11544 20 There was an internal error during processing. Please refer to XP Server log file for more
information.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11545 20 The result set type '%d' obtained by executing the supplied query was invalid.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
11546 20 The parameter '%s' is not an output parameter.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
11547 20 The required parameter '%s' is missing. Check user documentation and re-enter
command.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
11548 20 Invalid event log computer name length (-l). XP Server shutting down.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
11549 20 Failed to access include file %s. Error number from file access call is %d.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
11550 20 Failed to start mail session. To use default parameter values for xp_startmail, add the
'sybmail' user account and configure 'start mail session' configuration parameter.
Explanation: A database maintenance operation failed. Restart Adaptive Server and
take any corrective action indicated by the message. Check the Adaptive Server error log.
Number Severity Text and Explanation
Server Error Messages 11600 - 11699
1168
Server Error Messages 11600 - 11699
Number Severity Text and Explanation
11601 18 Instance does not have any data pointers for counters. Restart SQL Server. If problem
persists, contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
11602 18 Failed to open file mapping in DLL to attach to SQL Server shared memory. SQL Server
may not be running or the machine is low on disk space. Otherwise, contact Sybase Tech
nical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
11603 18 Failed to MapViewOfFile of SQL Server shared memory file mapping. SQL Server may
not be running or the machine is low on disk space. Otherwise, contact Sybase Technical
Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
11604 20 Failed during signature verification of SYBPERF_ENV memory block of SQL Server.
Restart SQL Server. If problem persists, contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11605 20 Cannot allocate any more SYBPERF_COMPLEX_DEFs, array too small. Too many
SQL Server counter objects, counters, and instances. NT Performance Monitor will not
monitor this SQL Server. Please reduce number of counter objects, counters, instances.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11606 20 The performance monitor component of SQL Server is not initialized correctly.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
11607 10 NT Performance Monitor has started monitoring SQL Server.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11608 10 Monitor Group %s not found.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
CHAPTER 6 Adaptive Server Error Messages
1169
Server Error Messages 11700 - 11799
11609 10 Monitor Counter %s not found.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11610 10 SYBPERF_OBJECT_TYPE %s not found.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11611 10 No SQL Server is running with perform.exe integration; therefore, there is nothing to
monitor.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11612 10 %s.
Explanation: This is an informational message or a message header. No action is
required.
11613 20 The Sybperf DLL encountered a fatal exception when processing a %s request from the
Windows NT performance monitoring subsystem. The exception code was 0x%X.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
11701 15 CREATE for extended stored routine cannot contain statements after EXTERNAL
statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11704 16 The specified option '%.*s' is not valid for this command. The option is valid for the
LOAD TRANSACTION command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11706 16 Time value '%.*s' in the LOAD TRANSACTION UNTIL_TIME clause is not a legal
value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Server Error Messages 11700 - 11799
1170
11707 16 Incorrect time syntax in time string '%.*s' used in the LOAD TRANSACTION
UNTIL_TI ME statement. Correct format is month day, year
hour:minute:seconds:milliseconds[am | pm]
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11710 16 Subqueries are not allowed in a DEFAULT clause.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
11711 16 The REORG option '%.*s' requires a value greater than 0 to be specified.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11712 16 You cannot specify a value with the REORG option '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11713 16 Index name is not allowed in UPDATE PARTITION STATISTICS statement. Use
partition number instead.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11714 16 Partition number is not allowed in UPDATE STATISTICS statement. Use index name
instead.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11715 16 Options (index name, partition number) in UPDATE ALL STATISTICS statement are
ignored.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11717 16 The quoted identifier '%.*s' is illegal because its first character is '#', which is ambiguous.
Please use another character instead.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11718 16 %ld is not a valid partition number. Partition number must be greater than 0.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11719 16 Error converting %ld to IDENTITY_START value.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11720 16 %.*s' is not a REORG subcommand. The valid REORG subcommands are: REBUILD,
FORWARDED_ROWS, RECLAIM_SPACE, and COMPACT.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1171
11721 16 Global variables not allowed as defaults.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11722 15 The READPAST and HOLDLOCK object level locking options are incompatible.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11723 16 READPAST conflicts with AT ISOLATION LEVEL 3.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11724 15 Target variable '%.*s' may not appear in both the SET and WHERE clauses of the
UPDATE statement, nor in any subquery of the SET clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11725 15 All result expressions in a CASE expression must not be NULL.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11726 15 A single coalesce element is illegal in a COALESCE expression.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11728 15 SELECT INTO cannot be used in an INSERT statement to pull values from tables.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11729 15 The name '%.*s' is not a valid local variable name.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11730 15 The PROXY option cannot be used in conjunction with other options in a SET command.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11731 15 Duplicate option has been specified to UPDATE STATISTICS command. One or many
options have been repeated.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11732 10 Warning : Ambiguous correlation names in the set clause
Explanation: This warning is raised when the user use more than one correlated name
in the set clause at the left of the assign sign.
11733 10 Warning : Ambiguous table to update; Using the table specified in the update clause.
Explanation: This error is raised when Adaptive Server finds that the correlated name
of the table in the READ_CURSOR entry of the range is not used in the set clause to the
left of the assign sign.
Number Severity Text and Explanation
Server Error Messages 11700 - 11799
1172
11734 16 The quoted identifier '%.*s' is illegal because it contains an embedded period followed by
an embedded double quote. Please substitute another character in place of one of these
characters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11735 15 You specified an invalid password option.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11736 16 line %d: You cannot specify this command in an ’execute immediate’ context.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11737 16 You cannot specify outer joins in the HAVING clause of a query.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11738 16 Table name ’%.*s’ is reserved for internal use by Adaptive Server. Please use a different
name.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11739 15 The value specified for identity gap ’%d’ is not legal; identity gap must be greater than 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11740 16 UNICHAR and UNIVARCHAR datatypes are not supported when server’s default
character set is not UTF-8.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11741 15 Identity gap can be specified only for tables which have identity columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11742 15 language java’ and ’parameter style java’ clauses must be specified when creating sqlj
procedure/function.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11743 15 CREATE for extended stored routine cannot contain statement ’%s’; it can only contain
1 EXTERNAL statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11744 15 WITH CHECK OPTION is not allowed in the definition of a union view.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1173
Server Error Messages 11900 - 11999
11745 16 Function name ’%.*s’ is reserved for a T-SQL builtin function. Please use a different
name.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11746 16 Unable to create access rule. Please make sure the the row level access option is enabled
and ASE_ASM license is available and enabled.
Explanation: Command failed. Check execution environment as indicated in the
message.
11747 15 Java method ’%s’ has too many parameters. The maximum number is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11748 16 There are too many aggregates in the COMPUTE clause. The maximum number is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
11749 15 %s must be the only statement in a query batch.
Explanation: Command failed. Check syntax and semantics. Rewrite the command to
satisfy the condition indicated in the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
11901 16 Table '%.*s' was not found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11902 16 '%.*s' is not a table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11903 16 You cannot run REORG on a table which uses allpages locking.
Explanation: Tables that use data-only locking have unique space management needs.
The reorg utility reorganizes a table to reclaim unused space and improve clustering. Error
11903 is raised when you attempt to use reorg on an allpages locked table, since reorg
applies exclusively to tables that use the data-only locking scheme. Do not use the reorg
utility on an allpages locked table. You can use alter table to change the table’s
locking scheme to allow reorg, if desired.
Server Error Messages 11900 - 11999
1174
11904 16 You cannot specify an index with this REORG subcommand. Only the
RECLAIM_SPACE subcommand can be run on an index.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11906 16 You cannot use the RESUME or TIME options with the REBUILD subcommand.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11910 16 Index '%.*s' was not found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11911 10 Using time limit of %d minutes.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11913 10 Warning: The RESUME option was specified, but no valid restart point was found.
Starting from beginning of object.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11915 10 There are approximately %d pages to be processed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11916 10 %d pages have been processed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11917 16 REORG REBUILD of systabstats is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11918 16 You cannot run REORG REBUILD on '%.*s' because there are one or more isolation
level 0 scans active on the table.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11919 16 You cannot run REORG REBUILD in this database because the 'select into/bulkcopy'
option is off. Please check with the DBO.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11920 10 Beginning REORG %s of '%.*s'.
Explanation: This informational message is displayed when the REORG command
starts executing. The first parameter is the subcommand name, for example
RECLAIM_SPACE.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1175
11921 10 Beginning REORG RECLAIM_SPACE of index '%.*s' on table '%.*s'.
Explanation: This informational message is printed when the REORG
RECLAIM_SPACE command starts executing on an index.
11922 10 Resuming REORG %s of '%.*s'.
Explanation: This informational message is printed when the REORG utility starts
execution with the RESUME option. The first parameter is the subcommand name, for
example RECLAIM_SPACE.
11923 10 Resuming REORG RECLAIM_SPACE of index '%.*s' on table '%.*s'.
Explanation: This informational message is printed when the REORG
R E C L A I M _ S P A C E c o m m a n d s t a r t s e x e c u t i n g o n a n i n d e x , w i t h t h e R E S U M E o p t i o n .
11924 10 REORG %s of '%.*s' completed.
Explanation: This informational message is printed when the REORG command
completes execution. The first parameter is the subcommand name, for example
RECLAIM_SPACE.
11925 10 REORG RECLAIM_SPACE of index '%.*s' on table '%.*s' completed.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
11926 10 REORG %s of '%.*s' terminated due to error or user interrupt.
Explanation: This message is raised when the REORG utility encounters an error that
causes termination, or when the user terminates REORG.
11927 10 REORG RECLAIM_SPACE of index '%.*s' on table '%.*s' terminated due to error or
user interrupt.
Explanation: This message is raised when the REORG utility encounters an error that
causes termination, or when the user terminates REORG.
11928 16 Rebuild of index ’%.*s’ failed because the index is marked suspect.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
11929 16 Reorg cannot be run on proxy table ’%.*s’.
Explanation: Command failed due to invalid or illegal request for the object in
question.
Number Severity Text and Explanation
Server Error Messages 12000 - 12099
1176
Server Error Messages 12000 - 12099
Number Severity Text and Explanation
12001 16 Unable to find entry for class: %d, attribute: %d, value: %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12003 16 Unable to allocate shared memory dump condition. All conditions (%d) already
allocated.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12004 16 Empty shared memory dump condition list head passed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12005 16 Cannot free shared memory dump condition. Entry 0x%x not found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12006 16 An entry already exists for class: %d, attribute: %d, value: %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12007 16 Cannot set shared memory dump condition. An invalid attribute value was recevied: %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12008 16 Directory name too long. The maximum directory length is %d characters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12009 16 File name too long. The maximum length is %d characters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12010 16 Unable to set shared memory dump condition. Invalid record type: %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12011 16 Configuration of shared memory dump conditions is not available on this platform.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
CHAPTER 6 Adaptive Server Error Messages
1177
12012 16 Unable to perform this operation. The internal dump condition table was not allocated at
server startup time.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12013 16 Function ’%s’ expected %d parameters but received only %d. Retry the function with at
least the expected number of parameters.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12014 16 Parameter %d of function %s is too long. Maximum length is %d characters. Retry the
function with a shorter parameter.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12015 16 Unknown function %s. Check spelling of the function name.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12016 16 CAPs configuration table rebuild may be required: %s ’%s’ is missing from %s ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12017 16 Profile ’%s’, CAP ’%s’: Unknown CAP name. Check spelling.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12018 16 Not enough memory to %s %s ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12019 16 CCB ’%s’, profile ’%s’, CAP ’%s’: Too many actions. Only the first %d actions will be
configured.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12020 16 CAP ’%s’ in CCB ’%s’ not configured because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12021 16 Configuration of CCBs from tables in database ’%s’ aborted.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12022 16 Failed to lock %s ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12023 16 CCB ’%s’ not configured because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
Server Error Messages 12000 - 12099
1178
12024 16 CCB ’%s’ cannot be found because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12025 16 CAPs configuration table rebuild may be required: %s ’%s’ is missing.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12026 16 CCB ’%s’ CAP ’%s’ not activated because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12027 16 CCB ’%s’ CAP ’%s’ not destroyed because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12028 16 CCB ’%s’ CAP ’%s’ not deactivated because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12029 16 CCB ’%s’ not destroyed because %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12030 16 The CAPs facility is not active. Set the configuration parameter number of ccbs to 1 or
more.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12031 16 The CAPs facility is not active. See the error log for details.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12032 16 Capslib detected error: %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12033 16 Object can not be described because: %s.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1179
Server Error Messages 12100 - 12199
Number Severity Text and Explanation
12100 16 Cannot execute a LOCK TABLE command on table '%.*s', because this table does not
exist.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
12101 16 The object '%.*s' you've specified is not a user table. Executing the LOCK TABLE
command is only permitted on user tables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
12102 16 The table '%.*s' you've specified is a temporary table. Executing the LOCK TABLE
command is not permitted on temporary tables.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
12103 10 Table '%.*s' in database '%.*s' was not locked in '%.*s' mode because a covering lock in
'%.*s' mode was found.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12104 16 A LOCK TABLE command is not allowed outside the scope of a transaction on table '
%.*s' in the database '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
12106 16 Invalid parameter in LOCK TABLE syntax: '%.*s'.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
Server Error Messages 12200 - 12299
1180
Server Error Messages 12200 - 12299
Number Severity Text and Explanation
12201 20 Lock found in lock cache not on global lock chain: dbid %d, objid %d, locktype %d,
sufficiency class %d
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
12202 10 Could not initiate lock wait checking because Adaptive Server has run out of alarms. If
your application uses this feature, try rebooting the server.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12203 18 Lock cache entry not found for spid %d, lock 0x%lx, type %d, suff class %d. Please notify
your system administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12204 18 Attempted to redo deadlock search as a result of a lock upgrade. Found too many
SH_NKL lockrecs. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12205 17 Could not acquire a lock within the specified wait period. %s level wait period=%d
seconds, spid=%d, lock type=%s, dbid=%d, objid=%ld, pageno=%ld, rowno=%ld.
Aborting the transaction.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
12206 20 Internal Error in lock manager routine: Attempted lock anti-inheritance when the parents
sdes chain does not include the dbid and objid corresponding to the child thread which are
dbid=%d and objid=%d.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
12207 10 Could not acquire a lock within the specified wait period. %s level wait period=%d
seconds, spid=%d, lock type=%s, dbid=%d, objid=%ld, pageno=%ld, rowno=%ld.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
CHAPTER 6 Adaptive Server Error Messages
1181
Server Error Messages 12300 - 12399
Number Severity Text and Explanation
12300 20 Internal error: in table '%.*s', database %d, the forwarded row (%d, %d) pointed to by
(%d, %d) is invalid. Aborting the transaction.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12301 20 Internal error: the index (id = %d) and the data for row (%d, %d) in table '%.*s', database
%d are inconsistent; data is marked deleted but index is not. Aborting the tran saction.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12302 20 Internal error: deleted row (%d, %d) erroneously qualified for table '%.*s', database %d.
Terminating the scan.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12303 20 Internal error: invalid scan branch type. Aborting the transaction.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12304 10 Index id %d cannot be used to access table id %d as it is SUSPECT. Please drop and re-
create the index. Table-scan is being used instead.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12306 26 No table lock on object '%.*s' in database '%.*s'.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
12307 26 Row %d of Page %ld in table ’%.*s’ (id = %ld) in dbid %d is not locked.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
12308 21 Internal error : Invalid row id (Row %d, Page %ld) encountered in the table '%.*s ' in the
database '%.*s'.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
Server Error Messages 12300 - 12399
1182
12309 21 Expanding update on object ’%.*s’ in database ’%.*s’ cannot succeed on page %ld,
because the contiguous_free_bytes of %d is less than the difference of %d between new
rowlen and old rowlen. This is an internal error.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12310 21 Internal error: split or shrink propagation failed to commit after changing the page %ld of
index id %d of table ’%S_OBJID’ (id = %ld) in database ’%S_DBID’. Xactid is
(%ld,%d). Drop and re-create the index.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12311 20 Internal error: address lock request on page %ld of index id %d of table '%S_OBJID' (id
= %ld) in database '%S_DBID' failed with status %d. No need to drop the index.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12312 20 Index with id %d of table '%S_OBJID' (id = %ld) in database '%S_DBID' is already at
the maximum allowed height. It cannot grow any further. Try dropping and recreating the
index.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12313 21 Internal error: Insert into index id %d of table ’%S_OBJID’ (id = %ld) in database
’%S_DBID’ tried to replace undeleted RID (%ld,%d). Try dropping and recreating the
index.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12314 21 Bad child page pointer found on page %ld of index with id %d of table '%.*s' in database
'%.*s'. Expected child page pointer to be %ld but found %ld. Check if the index is
consistant using DBCC.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12315 21 Corrupt page, Internal error: Mismatch between tail timestamp '%04x' and the low two
bytes of timestamp in the page header '%04x' while accessing page '%ld' of object '%ld '
in database '%d'. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1183
12316 20 Internal error: Attempt to garbage collect a deallocated data page %d in table '% .*s',
database '%.*s'. Aborting the transaction.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12317 20 Internal error: Insert of a key of size %ld into page %ld of index id %d of table
'%S_OBJID' (id = %ld) in database '%S_DBID' failed because page has freespace of size
%ld . Try again or drop and recreate the index.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12318 20 Fatal internal error ecountered during scan on the index with id %d on table '%.* s' in
database '%.*s'. Isolation level is %d. Scan status is %ld. Current index scan page is %ld.
Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12319 20 Fatal internal error encountered during deferred dml on table '%.*s' in database '%.*s'. All
rows that qualified during the first phase were not visited during second phase of dml.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12320 21 Fatal internal error encountered when forwarding row (%d, %d) in table '%.*s', database
'%.*s' during update. Aborting the transaction.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12321 20 Internal error: No split point found for page %ld of index %d of object %ld. Old page :
%d entries, free space = %d. Split point information : <(%d), (%d), (%d, %d, %d)>.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12322 21 Row %d on DOL datapage %d in database '%.*s' has size %d and an invalid holesize %d.
Page is corrupted.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
Number Severity Text and Explanation
Server Error Messages 12400 - 12499
1184
Server Error Messages 12400 - 12499
Server Error Messages 12500 - 12599
12323 20 Internal error occured during rebuild of index id %d of table ’%S_OBJID’ (id = %ld) in
database ’%S_DBID’ while processing page %ld. Run dbcc checktable to see if the index
is consistent.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
12324 21 In database ’%S_DBID’, the server failed to open required table ’%.*s’. Please contact
Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
Number Severity Text and Explanation
Number Severity Text and Explanation
12400 20 Adaptive Server internal error: invalid input %d to syscoordinations manager.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
Number Severity Text and Explanation
12504 10 Timestamp mismatch error was not generated on page because page is marked for
deallocation. Page #=%ld, object id = %ld, page timestamp=%04x %08lx. Log old
timestamp=%04x %08lx.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
CHAPTER 6 Adaptive Server Error Messages
1185
12505 18 could not open table '%d' in database '%d' by id
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12506 18 sysstatistics upgrade error in table '%.*s' index '%.*s' distribution page %d - bad page
format - run update statistics on this table after upgrade
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12507 18 sysstatistics upgrade error in table '%.*s' index '%.*s' distribution page %d - nulls not a
beginning of page - run update statistics on this table after upgrade
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12508 18 sysstatistics upgrade error in table '%.*s' index '%.*s' distribution page %d - values not in
ascending order - run update statistics on this table after upgrade
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12509 18 sysstatistics upgrade error in table '%.*s' index '%.*s' distribution page %d - cannot
deallocate page - run update statistics on this table after upgrade
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12510 18 sysstatistics upgrade error in table '%.*s' index '%.*s' distribution page %d - cannot read
page - run update statistics on this table after upgrade
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12511 20 During recovery, quiescent last log marker was not found for database ’%.*s’. The
backward log scan was started on marker (%d, %d).
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12512 16 Database ’%.*s’ (dbid %d): has incomplete transactions. ONLINE DATABASE FOR
STANDBY_ACCESS cannot be completed successfully.
Explanation: A database maintenance operation failed. See the System Administration
Guide for a description of this command.
Number Severity Text and Explanation
Server Error Messages 12500 - 12599
1186
12513 10 Failed to delete the user specified recovery order for the dropped database '%.*s '. Inform
system administrator. During next bootup of server, this may turn off user specified
recovery order.
Explanation: his is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12514 10 Failed to read the user specified recovery order information. Inform system administrator.
The default dbid order will be used. To fix, delete all the user specified recovery order and
reinstall them using sp_setrecovery_order.
Explanation: his is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12515 18 sysindexes.distribution for table '%.*s index '%.*s' does not contain a valid distribution
page %d.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12516 21 During undo processing a CLR could not be logged. The internal error number is %d .
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12517 16 During transaction rollback a CLR could not be logged. The internal error number is
%d.This process will retry at intervals of one minute.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12518 20 Attempt to get an uninitialized page %d in database id %d during %s.
Explanation: This exception is raised when an uninitialized page is encountered during
recovery or undo operation when the page is expected to be allocated already.
12519 18 sysstatistics upgrade error in table '%.*s' index '%.*s' distribution page %d - exception
occurred - run update statistics on this table after upgrade
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12520 18 Recovery was unable to insert into the syscoordinations table. Please consult the Adaptive
Server errorlog for further information as to the cause. Please contact a user with System
Administrator (SA) role.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1187
12521 18 Recovery was unable to delete from the syscoordinations table. Please consult the
Adaptive Server errorlog for further information as to the cause. Please cont act a user
with System Administrator (SA) role
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12522 18 Recovery was unable to update syscoordinations table. Please consult the Adaptive
Server errorlog for further information as to the cause. Please contact a user with System
Administrator (SA) role
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12523 21 Recovery encountered an error in acquiring locks for reinstantiated transactions. Please
consult the Adaptive Server errorlog for further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12524 21 Recovery encountered an error while reserving space for log records for which space had
already been reserved during run time. Please consult the Adaptive Server errorlog for
further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12525 21 Recovery failed to open a session with the transaction log during transaction
reinstantiation. Please consult the Adaptive Server errorlog for further information as to
the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12526 21 Recovery detected an incorrect internal transaction state during transaction
reinstantiation. Please consult the Adaptive Server errorlog for further information as to
the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
12527 21 Recovery encountered an internal error during transaction reinstantiation. Please consult
the Adaptive Server errorlog for further information as to the cause.
Explanation: Adaptive Server encountered an internal error affecting all processes
using the current database. Report the error to your System Administrator. Adaptive
Server must be restarted and DBCC diagnostics run.
Number Severity Text and Explanation
Server Error Messages 12500 - 12599
1188
12528 18 The pre-%s log for database ’%.*s’ includes a CREATE INDEX incompatible with this
server version and operating environment. Only transactions completed before CREATE
INDEX will be recovered.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12529 10 Warning: A transaction ’%.*s’ that updated system tables was found to be in a prepared
state, and is being unconditionally rolled back. Please consult your System Administrator.
Explanation: his is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12530 16 Database ’%.*s’ was dumped on a version of Adaptive Server prior to 11.9 and cannot be
brought online in standby access mode. Please use the ONLINE DATABASE command
without any options.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12531 16 Cannot recover from log record %s at %S_RID affecting page %ld in ’%S_DBID’.
Reapply the log records using an earlier (pre-12.0) version of Adaptive Server, or contact
Sybase Technical Support for assistance.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12532 10 Redo pass of recovery has reinstantiated %d prepared transactions
Explanation: his is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12533 10 Undo pass of recovery has resolved %d prepared transactions
Explanation: his is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12534 10 During online of database ’%.*s’ an invalid cross-database reference with constraint id
%d was found in the ’sysreferences’ system catalog. The referencing and referenced
database ids are %d and %d respectively.
Explanation: his is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12535 18 Post-processing for system catalog ’%.*s’ could not be completed during online of
database ’%.*s’.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System
Administrator.
12536 16 Sysstatistics upgrade warning for table ’%S_OBJID’. New row-length after upgrade, %d,
(sequence no %d, format ID %d, column ID %d, %d columns) exceeds maximum limit
of %d. Run update statistics on this table after upgrade.
Explanation: Statistics for the object could not be updated during an upgrade. Take the
action recommended in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1189
Server Error Messages 12700 - 12799
12537 16 Database ’%.*s’ is in QUIESCE DATABASE state. It will recovered as for LOAD
DATABASE and left off line.
Explanation: This is an informational message showing how the specified database will
be treated upon server restart.
12538 10 Database ’%.*s’ is in QUIESCE DATABASE state, but the server is not booted with the
’-q’ flag. The QUIESCE DATABASE state will be ignored, and the database will be
recovered and brought on line normally.
Explanation: This is an informational message showing how the specified database will
be treated upon server restart.
12539 10 Database ’%.*s’ is a system database. Its QUIESCE DATABASE state will be ignored,
and the database will be recovered and brought on line normally.
Explanation: This is an informational message.
12540 10 Modified timestamp on page %ld of (%d, %d) which falls between log old ts (%d, %d)
and log new ts (%d, %d) during recovery of database id %d.
Explanation: This is an informational message.
12541 10 Modified timestamp on page %ld of (%d,%d) which is older than log old ts (%d, %d)
during recovery of database id %d.
Explanation: This is an informational message.
12542 16 Load the next transaction log in the load sequence, or use ONLINE DATABASE with
nooptions to end the load sequence.
Explanation: This informational message is displayed following a transaction load, and
requires one of the indicated actions.
12543 20 During recovery, quiescent first log marker was not found for database ’%.*s’. The
forward log scan was started on marker (%d, %d).
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
12700 18 Suspect Granularity: Bad suspect item type `%d' (`%d') due to an internal error. Please
contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Server Error Messages 12700 - 12799
1190
12701 10 Suspect Granularity: Command failed. No cached suspect list.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12702 18 Suspect Granularity: Unable to delete suspect information from master..sysattributes
table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12703 18 Suspect Granularity: Unable to start transaction to delete suspect information from
master..sysattributes table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12704 18 Suspect Granularity: Failed to access sysdatabases table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12705 18 Suspect Granularity: Failed to replace sysdatabases row.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12706 18 Suspect Granularity: Failed to end update on sysdatabases table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12707 18 Suspect Granularity: Adding suspect information rows is not allowed.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12708 18 Suspect Granularity: Failed to read or change a bit in status2 field of sysdatabases row.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12709 18 Suspect Granularity: Failed to clean up suspect information.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12710 18 Suspect Granularity: Command failed because of an unknown suspect attribute (`%d').
This is an internal error. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12711 18 Suspect Granularity: Command failed because cached suspect information is missing.
This is an internal error and can be a serious problem. You may need to restart SQL
Server. Contact your System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1191
12712 18 Suspect Granularity: Command failed because an invalid action (`%d')was detected.
This is an internal error. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12713 18 Suspect Granularity: Command failed because a suspect page-to-object map was not
available due to allocation page corruption. Contact your SystemAdministrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12714 18 Suspect Granularity: For the last suspect page in the object, the delete of the suspect
object entry failed but sp_forceonline_page was successful.Use sp_forceonline_object to
clean up the object information.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12715 18 Suspect Granularity: Command failed and the requested operation did not complete.
Inform your System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12716 17 Data unavailable: Unable to complete because the required data is currently unavailable.
The command failed and the transaction aborted.Try again later or contact your System
Administrator.
Explanation: Refer to the detailed writeup for Error 12716 in the chapter titled “Error
Message Writeups”.
12717 10 Suspect data encountered: Database `%.*s', object `%.*s'Index ID `%ld', page ID `%ld'.
Explanation: Refer to the detailed writeup for Error 12717 in the chapter titled “Error
Message Writeups”.
12718 10 Suspect data encountered: Database: `%.*s', Page: `%ld' (object information not
available).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12719 17 Suspect Granularity: Drop of object `%.*s' failed because master transaction is required
to update master..sysattributes table. Drop the table/index within a master database
transaction.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
12720 17 Suspect data encountered: Drop of object `%.*s' failed because it contains suspect data.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
Number Severity Text and Explanation
Server Error Messages 12700 - 12799
1192
12721 10 Suspect Granularity: Page `%ld' of database `%.*s' was made accessible to all users from
previous state `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12722 10 Suspect Granularity: The access state of page `%ld' of database `%.*s' was changed from
`%.*s' to `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12723 10 Suspect Granularity: Object `%ld' with index `%ld' of database `%.*s' was made
accessible to all users from previous state `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12724 10 Suspect Granularity: The access state of object `%ld' with index `%d' of database `%.*s'
was changed from `%.*s' to `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12725 18 Suspect Granularity: Transaction failed during commit (putxact).
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12726 17 Suspect Granularity: Dump database of `%.*s' failed because some of the data in this
database is suspect.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
12727 17 Suspect Granularity: Database `%.*s' has suspect data. Dump transaction with requested
options is disabled. Use dump transaction that saves the log OR SA can online all suspect
data (sp_forceonline_page) before performing this operation.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
12728 18 Suspect Granularity: Drop of object `%.*s' failed due to an internal error. Consult the
error log and Inform your System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12729 10 Suspect Granularity: WARNING: The drop of `%.*s' may fail if it has suspect pages
because it requires a transaction that started in the master database.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1193
12730 10 Suspect Granularity: Automatic truncation of log after checkpoint has been disabled
temporarily because some data in database `%.*s' is suspect. Either truncate log without
no_log or truncate_only option, or online all suspect pages/objects.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12731 17 Recovery (Suspect Granularity): Reached suspect threshold `%d' for database `%.*s'.
Increase suspect threshold using sp_setsuspect_threshold.
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
12732 18 Recovery (Suspect Granularity): Unable to mark suspect object `%ld'.Inform your
System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12733 18 Recovery (Suspect Granularity): Error in getting suspect information row from
master..sysattributes.Inform your System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12734 18 Recovery (Suspect Granularity): Failed to insert row into master..sysattributes table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12735 18 Recovery (Suspect Granularity): Failed to scan master..sysattributes table for suspect
information.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12736 10 Recovery (Suspect Granularity): Allocation page %ld is corrupted.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12737 18 Recovery (Suspect Granularity): Recovery aborted for database `%.*s' because the
suspect items cannot be isolated at this level.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12738 18 Recovery (Suspect Granularity): Failed to read suspect granularity from
master..sysattributes for database `%.*s'.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12739 10 Recovery (Suspect Granularity): Warning - suspect granularity defaulted to database
level for database `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 12700 - 12799
1194
12740 18 Recovery (Suspect Granularity): Failed to read suspect threshold from
master..sysattributes for database `%.*s'. Assumimg default (`%d' pages).
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12741 10 Recovery (Suspect Granularity): No transaction available to write to master..sysattributes
table.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12742 17 Recovery (Suspect Granularity): Warning: Memory not available to store suspect
information. Using default suspect granularity (database).
Explanation: Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
12743 10 Recovery (Suspect Granularity): Page/object suspect information has been deleted.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12744 10 Recovery (Suspect Granularity): Bad suspect granularity `%d' for database `%.*s'.This
is an internal error. Contact Sybase Technical Support.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12745 10 Recovery (Suspect Granularity): Warning - Failed to read error list for database:'%.*s'.
Continuing with hard coded error list.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12746 10 Recovery (Suspect Granularity): Warning - suspect granularity defaulted to page level.
Object level is disabled in this release.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12747 10 Recovery (Suspect Granularity): Suspect page encountered: database `%.*s', page `%ld',
session (%ld, %d), log row ID (%ld, %d).
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12748 10 Recovery (Suspect Granularity): Suspect object in database `%.*s', object `%.*s', index
`%ld'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12749 10 Recovery (Suspect Granularity): Suspect pages are present in database `%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1195
12750 10 Recovery (Suspect Granularity): Warning - Page to object translation failed.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12751 18 Recovery (Suspect Granularity): Failed to insert suspect informationrow into
master..sysattributes table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12752 18 Recovery (Suspect Granularity): Failed to write suspect list to master..sysattributes table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12753 18 Recovery (Suspect Granularity): Failed to write suspect attribute to master..sysattributes
table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12754 18 Recovery (Suspect Granularity): Failed to read suspect attribute from
master..sysattributes table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12755 18 Recovery (Suspect Granularity): Failed to read suspect list from master..sysattributes
table.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12756 18 Recovery (Suspect Granularity): Recovery aborted while reading master..sysattributes.
Inform your System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12757 18 Recovery (Suspect Granularity): Write of suspect information to master..sysattributes
failed. Inform your System Administrator.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by message. Report the error to your System Administrator.
12758 10 Recovery (Suspect Granularity): Settings for database '%.*s'- Suspect Granularity:
'%.*s', Suspect Threshold: %d, Online Option: '%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12759 10 Recovery (Suspect Granularity): Database `%.*s' - begin list of pre-recovery suspect
pages.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 12700 - 12799
1196
12760 10 Recovery (Suspect Granularity): Database `%.*s' - end list of pre-recovery suspect pages.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12761 10 Recovery (Suspect Granularity): Page '%ld' of database '%.*s' is removed from suspect
page list because it was unallocated at end of recovery due to page/extent deallocation.
This page is clean and no action is required.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12762 10 Recovery (Suspect Granularity): Recovery of database `%.*s' found %d suspect pages
belonging to %d suspect objects.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12763 10 Recovery (Suspect Granularity): Database `%.*s' is clean.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12767 10 Suspect data encountered: Database: `%.*s', Object: `%ld'
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
12768 10 Suspect Granularity: (for Testing only) Simulated error to create suspect pages. Objid:
'%ld', Indid: '%ld', Errtype: '%d', Logtype: '%d', Pagetype: '%d', PageNo: '%ld',
Simulation Type: '%.*s'.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
12769 10 Recovery (Suspect Granularity): The database '%.*s' will come online in read only mode
due to suspect pages/objects. Use sp_dboption to turn off read only mode.
Explanation: Check and resolve any problems with suspect pages and objects before
making the database available for use. For details, refer to the discussion of Recovery
Fault Isolation in the chapter Encyclopedia of Tasks.
12770 10 Suspect index encountered: database '%.*s', object '%.*s', index '%ld'.
Explanation: This is an informational message. Unless otherwise specified, no action
is required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1197
Server Error Messages 12800 - 12899
Number Severity Text and Explanation
12801 12 The object `%.*s' is not a partitioned table. UPDATE PARTITION STATISTICS can only
be run on partitioned tables.
Explanation: Command failed. Specify an object of the correct type.
12802 16 Invalid partition number %d. Valid partition number is a positive integer.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
12803 16 CREATE VIEW failed because column %d in the view definition has a null column name.
Column names cannot be null.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
12804 18 Unable to change the logversion from %d to %d on database ’%S_DBID’.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12805 18 Unable to bring the master database online due to lack for space. Please re-start the
previous of the server, add more space and then reboot the new version of the server.
Shutting down.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12806 18 cannot replace a tuple in sysstatistics
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12807 18 cannot delete a tuple in sysstatistics
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12808 18 Cannot write table '%.*s' statistics
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12809 16 Duplicate column listed in update statistics. Column name '%.*s' for table '%.*s' listed
more than once
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
Server Error Messages 12800 - 12899
1198
12810 16 Cannot resolve column name '%.*s' for table '%.*s'. This could be because the column does
not belong to the table or it has an unknown datatype or an internal error related to the
system catalogs has happened
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12811 16 Column name '%.*s' for table '%.*s' is one of TEXT, IMAGE or BIT datatype. This type
of column cannot be used in update statistics.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12813 18 Failed to start an internal transaction. This will prevent information for index '%.*s' on
table '%.*s' from being written out to SYSTABSTATS.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12814 18 Failed to write information in SYSTABSTATS.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12815 18 Failed to obtain lock on SYSTABSTATS.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12816 18 Failed to delete a row in SYSTABSTATS for table '%.*s', because the row could not be
located.
Explanation: Command failed due to internal Adaptive Server problem. Perform any
diagnostic action indicated by the message. Report the error to your System Administrator.
12817 16 This form of UPDATE STATISTICS on table '%.*s' does not support the CONSUMERS
option. Please rerun it without this option.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12818 16 Cannot create an object of this type in system-created proxy database.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12819 16 Cannot create a constraint on a column of TEXT, IMAGE, or off row Java datatype.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12820 16 Only the master database can be recovered when attempting to use the DISK REFIT
command. Restart the server using trace flag 3608.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12821 10 The result of the %s command has been truncated to %d bytes.
Explanation: This is an informational message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1199
Server Error Messages 12900 - 12999
12823 16 Command ’addcert’ failed to add certificate path %s, system error: %s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12824 16 Command ’dropcert’ failed to drop certificate path %s. %s
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12825 16 This operation is invalid when configuration parameter ’enable xact coordination’ is on.
Please retry after disabling this configuration parameter.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12826 16 Attempt to read certificate path from master database failed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions.
12827 16 Warning: command ’addcert’ adds certificate path %s with its common name field
different from server name.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12828 16 The datatype of a parameter marker used in the dynamic prepare statement could not be
resolved.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12829 16 Warning: command ’addcert’ adds certificate path ’%s’ that is not yet valid. Error ’%s’.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
12830 16 Warning: command ’addcert’ adds certificate path ’%s’ that has expired. Error %s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Number Severity Text and Explanation
12901 16 This command is not allowed on an offline database '%S_DBID'.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Server Error Messages 12900 - 12999
1200
12902 16 Mime page chain starting at page %d has %d parts in it's header %d parts were found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12903 16 Mime page chain starting at page %d has %d bytes in it's header %d bytes were found.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
12904 16 Cannot find object with ID '%d'. Check the object ID and retry the command.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12905 16 Index %ld of object %ld corrupt; key values in child page %ld inconsistent for parent
page %ld. Drop and recreate the index.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12906 16 Index %ld of object %ld has wrong level %d for page %ld, parent %ld is at level %d
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12907 16 The total number of data and control pages in this table is %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12908 16 Index %ld of object %ld has orphan leaf page %ld. Drop and recreate the index.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12909 16 Table with object id=%ld (name = %S_OBJID) inconsistent after Large Scale Allocation.
%ld pages in extent %ld were found reserved.
Explanation: Since 11.9.x, the Page Manager uses some bits in the allocation page
extent structure for internal bookkeeping, specially during operations like bcp that use
large scale allocation. These bits are called reserve bits. After you upgrade to 12.0, dbcc
checkalloc may report 12909 errors on your database if it finds reserve bits set (this may
happen if these bits were set during some page allocation but were not cleaned up).
Correct the error by running checkalloc with fix.
12910 16 Page %ld in extent %ld in Table with object id %ld (name = %S_OBJID) and index %ld
is in the process of being allocated. To verify if the page is indeed allocated, run
TABLEALLOC with the FIX option when there are no active transactions.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12911 10 The extended header bit is not set in page %ld of object '%.*s' (ID %d) in database '%.*s'
(ID %d).
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1201
12912 10 Incorrect offset entry(s) in the offset table of row %d in page %ld of object '%. *s' (ID
%d) in database '%.*s' (ID %d).
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12913 10 Incorrect column type in the offset table of row %d in page %ld of object '%.*s' (ID %d)
in database '%.*s' (ID %d).
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12914 16 EXP_ROW_SIZE value of %d is invalid. It must be between %d and %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12915 16 Invalid Cachelet ID %d. Valid Cachelet ID values are between %d and %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12916 16 Fixed spacebits (on allocation page) for DOL datapage %ld, with insfs %d and expected
row length %d. Were expected to be 0x%x, but were found to be 0x%x.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12917 16 Non-contiguous free space %d in page header of DOL datapage %ld is incorrect. This
value cannot be negative.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12919 10 Verifying faults for '%.*s'.
Explanation: This is an informational message. No action is required.
12920 16 The last completed DBCC CHECKSTORAGE for this database has been processed. You
must perform another DBCC CHECKSTORAGE before you can use CHECKVERIFY
or CHECKREPAIR. Use sp_dbcc_summary_report to view the DBCC operations
performed.
Explanation: Adaptive Server could not perform the requested action. A completed and
unverified CHECKSTORAGE operation must exist before CHECKVERIFY can
execute.
12921 16 A problem was encountered while accessing the faults recorded in the dbccdb database.
Please check the dbcc_faults and dbcc_fault_params tables in the dbccdb database.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
12922 16 A problem was encountered while updating the fault status in the dbcc_faults table. Please
check the dbcc_faults and dbcc_fault_params tables in the dbccdb database.
Explanation: Adaptive Server could not perform the requested action. Contact your
System Administrator.
Number Severity Text and Explanation
Server Error Messages 12900 - 12999
1202
12923 10 Failed to get an '%s' lock on table '%.*s'. The faults for this table will not be processed.
Explanation: dbcc checkstorage could not verify the faults for this table and its indexes
because it was unable to block updates to the table. Contact your System Administrator.
12924 10 DBCC CHECKVERIFY for database '%.*s' encountered an error. Correct the reported
problem reported and execute the CHECKVERIFY command again.
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12925 10 DBCC CHECKVERIFY for database '%.*s' sequence %d completed at %s. %d suspect
conditions were resolved as faults, and %d suspect conditions were resolved as harmless.
%d objects could not be checked.
Explanation: This is an informational message. No action is required.
12926 20 DBCC CHECKVERIFY could not acquire a lock on the target database.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
12927 10 Performing QUICK repairs to database '%.*s'.
Explanation: This is an informational message. No action is required.
12928 10 DBCC CHECKREPAIR with the QUICK_REPAIRS option does not accept an object
name. The parameter '%.*s' will be ignored.
Explanation: This is an informational message. The optional object parameter should
not be used with this command option.
12929 10 DBCC CHECKREPAIR for database '%.*s' sequence %d completed at %s. %d faults
were repaired, and %d faults were resolved without repair. %d objects could not be
processed and %d faults remain unrepaired.
Explanation: This is an informational message. No action is required.
12930 10 DBCC CHECKREPAIR for database '%.*s' encountered an error. Correct the problems
reported and execute the CHECKREPAIR command again.
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12931 10 The total number of empty pages (with all deleted rows) in this table is %ld.
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12932 10 The total number of pages which could be garbage collected to free up some space is %ld.
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12933 10 DBCC CHECKSTORAGE not supported in this release of Adaptive Server Enterprise.
Explanation: This dbcc feature is not supported in your version of Adaptive Server.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1203
12934 16 Page %ld of object %ld, indid %ld undergoing change. Some pages of indid %ld may not
be checked, retry the command later.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12935 16 Engine zero can not be offline.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12936 10 Failed to (re)build the st-node. Please issue the command ’dbcc rebuild_text (%ld, %d,
%ld)’ to (re)build the st-node. (objid=%ld, colid=%d, FTP=%ld).
Explanation: This is an informational message. The optional object parameter should
not be used with this command option.
12937 16 The text page back pointer on text page %d appears to be incorrect. Expected %d, byt got
%d.
Explanation: Report the error to your System Administrator so DBCC diagnostics can
be run.
12938 16 Engine number must be between %d and (maxonline - 1) %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12939 16 The minimum number of online engines is %d. No more engine can be offlined.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12940 16 Cannot find database ’%.*s’ for constraint ID %d in sysreferences.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
12941 16 Table ID %d, index ID %d in sysreferences does not have a matching entry in sysindexes
in database %d.
Explanation: Command failed due to invalid or illegal request.
12942 16 Table ID %d, column ID %d in sysconstraints does not have a matching entry in
syscolumns.
Explanation: Command failed due to invalid or illegal request.
12943 16 Mismatch found in an entry in sysreferences between the database ID %d and database
name ’%.*s’. The actual database ID is %d.
Explanation: Command failed due to invalid or illegal request.
12944 10 Insert free space value in page header of DOL datapage %ld has been corrected to %d.
Explanation: This is an informational message. Correct the problem indicated in the
preceeding messages or in the errorlog before re-executing the command. Contact your
System Administrator for assistance.
12945 16 Mismatch found. Current database ID %d, appears in sysreferences with database ID %d.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 12900 - 12999
1204
12947 16 Syslogs free space is currently %ld pages but DBCC counted %ld pages. This
descrepancy may be spurious if this count was done in multi-user mode. Please run
DBCC TABLEALLOC(syslogs, full, fix) to correct it.
Explanation: Take any corrective action indicated by the message.
12948 10 Syslogs free space count has been successfully recalculated. It has been corrected to %ld
pages.
Explanation: This is an informational message.
12949 16 This command is only allowed for databases having a separate log segment.
Explanation: For more information on this topic, see the writeup for Error 4205.
12950 10 The following task(s) will affect the offline process:
Explanation: This is an informational message.
12951 10 spid: %d has outstanding %s connections.
Explanation: This is an informational message.
12952 10 The total number of wrong st-node back references to first text page chains in this table
is %d.
Explanation: This is an informational message.
12953 16 Invalid external st-node first text page value %ld stored in first text page %ld.
Explanation: Command failed due to invalid or illegal request. Check syntax and
semantics.
12954 16 Invalid first text page value %d in data row text pointer %s for TEXT/IMAGE column
%d in row %d of page %d, object id %d.
Explanation: dbcc command found an error in an internal structure of the specified
object. Contact your System Administrator.
12955 16 Incorrect partition ID %d found in extent ID %d for object ID %d.
Explanation: dbcc command found an error in an extent for the specified object.
Contact your System Administrator.
12956 10 The reserved status was found to be improperly set in %ld pages. That status has been
cleared by DBCC.
Explanation: The dbcc command found and corrected the page status error.
12957 10 Start dbcc stacktrace...
Explanation: This is an informational message.
12958 10 dbcc stacktrace finished.
Explanation: This is an informational message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1205
Server Error Messages 13000 - 13099
Number Severity Text and Explanation
13001 10 data page
Explanation: This is an informational message or a message header. No action is
required.
13002 10 index page
Explanation: This is an informational message or a message header. No action is
required.
13003 10 leaf page
Explanation: This is an informational message or a message header. No action is
required.
13004 10 last
Explanation: This is an informational message or a message header. No action is
required.
13005 10 root
Explanation: This is an informational message or a message header. No action is
required.
13006 10 read from
Explanation: This is an informational message or a message header. No action is
required.
13007 10 send to
Explanation: This is an informational message or a message header. No action is
required.
13008 10 receive
Explanation: This is an informational message or a message header. No action is
required.
13009 10 send
Explanation: This is an informational message or a message header. No action is
required.
13010 10 read
Explanation: This is an informational message or a message header. No action is
required.
13011 10 wait
Explanation: This is an informational message or a message header. No action is
required.
Server Error Messages 13000 - 13099
1206
13012 10 A USE DATABASE statement
Explanation: This is an informational message or a message header. No action is
required.
13013 10 a procedure or trigger
Explanation: This is an informational message or a message header. No action is
required.
13014 10 A DISTINCT clause
Explanation: This is an informational message or a message header. No action is
required.
13015 10 a view
Explanation: This is an informational message or a message header. No action is
required.
13016 10 An INTO clause
Explanation: This is an informational message or a message header. No action is
required.
13017 10 An ORDER BY clause
Explanation: This is an informational message or a message header. No action is
required.
13018 10 A COMPUTE clause
Explanation: This is an informational message or a message header. No action is
required.
13019 10 a SELECT INTO statement
Explanation: This is an informational message or a message header. No action is
required.
13020 10 option
Explanation: This is an informational message or a message header. No action is
required.
13021 10 offset option
Explanation: This is an informational message or a message header. No action is
required.
13022 10 statistics option
Explanation: This is an informational message or a message header. No action is
required.
13023 10 parameter option
Explanation: This is an informational message or a message header. No action is
required.
13024 10 built-in function name
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1207
13025 10 field
Explanation: This is an informational message or a message header. No action is
required.
13026 10 parameter
Explanation: This is an informational message or a message header. No action is
required.
13027 10 convert specification
Explanation: This is an informational message or a message header. No action is
required.
13028 10 index
Explanation: This is an informational message or a message header. No action is
required.
13029 10 table
Explanation: This is an informational message or a message header. No action is
required.
13030 10 database
Explanation: This is an informational message or a message header. No action is
required.
13031 10 procedure
Explanation: This is an informational message or a message header. No action is
required.
13032 10 trigger
Explanation: This is an informational message or a message header. No action is
required.
13033 10 view
Explanation: This is an informational message or a message header. No action is
required.
13034 10 default
Explanation: This is an informational message or a message header. No action is
required.
13035 10 rule
Explanation: This is an informational message or a message header. No action is
required.
13036 10 system
Explanation: This is an informational message or a message header. No action is
required.
13037 10 unknown type
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 13000 - 13099
1208
13038 10 SET command
Explanation: This is an informational message or a message header. No action is
required.
13039 10 column
Explanation: This is an informational message or a message header. No action is
required.
13040 10 type
Explanation: This is an informational message or a message header. No action is
required.
13041 10 character string
Explanation: This is an informational message or a message header. No action is
required.
13042 10 integer
Explanation: This is an informational message or a message header. No action is
required.
13043 10 identifier
Explanation: This is an informational message or a message header. No action is
required.
13044 10 number
Explanation: This is an informational message or a message header. No action is
required.
13045 10 integer value
Explanation: This is an informational message or a message header. No action is
required.
13046 10 floating point value
Explanation: This is an informational message or a message header. No action is
required.
13047 10 object
Explanation: This is an informational message or a message header. No action is
required.
13048 10 column heading
Explanation: This is an informational message or a message header. No action is
required.
13049 10 constraint
Explanation: This is an informational message or a message header. No action is
required.
13050 10 Non-ANSI text
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1209
13051 10 ANSI text procesed in non-ANSI way
Explanation: This is an informational message or a message header. No action is
required.
13052 10 a non-ANSI data type usage
Explanation: This is an informational message or a message header. No action is
required.
13053 10 Non-standard datatype TIMESTAMP
Explanation: This is an informational message or a message header. No action is
required.
13054 10 Non-standard or user datatype:
Explanation: This is an informational message or a message header. No action is
required.
13055 10 ON <segment>
Explanation: This is an informational message or a message header. No action is
required.
13056 10 Alternate column names in CREATE VIEW
Explanation: This is an informational message or a message header. No action is
required.
13057 10 UNION in INSERT ... SELECT
Explanation: This is an informational message or a message header. No action is
required.
13058 10 FOR BROWSE
Explanation: This is an informational message or a message header. No action is
required.
13059 10 HOLD LOCK in SELECT statement
Explanation: This is an informational message or a message header. No action is
required.
13060 10 transaction name
Explanation: This is an informational message or a message header. No action is
required.
13061 10 Use of TRANSACTION key word instead of WORK
Explanation: This is an informational message or a message header. No action is
required.
13062 10 FROM clause in an UPDATE statement
Explanation: This is an informational message or a message header. No action is
required.
13063 10 More than one table in a from clause for DELETE statement
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 13000 - 13099
1210
13064 10 Named columns in an ORDER BY included in a UNION
Explanation: This is an informational message or a message header. No action is
required.
13065 10 Comparison operator !=
Explanation: This is an informational message or a message header. No action is
required.
13066 10 Comparison operator !<
Explanation: This is an informational message or a message header. No action is
required.
13067 10 Comparison operator !>
Explanation: This is an informational message or a message header. No action is
required.
13068 10 left equi-join operator
Explanation: This is an informational message or a message header. No action is
required.
13069 10 right equi-join operator
Explanation: This is an informational message or a message header. No action is
required.
13070 10 bitwise operator |
Explanation: This is an informational message or a message header. No action is
required.
13071 10 bitwise operator &
Explanation: This is an informational message or a message header. No action is
required.
13072 10 bitwise operator ^
Explanation: This is an informational message or a message header. No action is
required.
13073 10 bitwise operator ~
Explanation: This is an informational message or a message header. No action is
required.
13074 10 modulo operator %
Explanation: This is an informational message or a message header. No action is
required.
13075 10 temporary table usage
Explanation: This is an informational message or a message header. No action is
required.
13076 10 a statement with assigned variables in the select list
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1211
13077 10 aborted
Explanation: This is an informational message or a message header. No action is
required.
13078 10 data
Explanation: This is an informational message or a message header. No action is
required.
13079 10 log
Explanation: This is an informational message or a message header. No action is
required.
13080 10 A SYB_RESTREE statement
Explanation: This is an informational message or a message header. No action is
required.
13081 10 A CREATE SCHEMA statement
Explanation: This is an informational message or a message header. No action is
required.
13082 10 dynamic PREPARE statement
Explanation: This is an informational message or a message header. No action is
required.
13083 10 The untyped variable ?
Explanation: This is an informational message or a message header. No action is
required.
13084 10 in a WHERE clause or the SET clause of an UPDATE statement or the VALUES list of an
INSERT statement
Explanation: This is an informational message or a message header. No action is
required.
13085 10 Optional procedure number
Explanation: This is an informational message or a message header. No action is
required.
13086 10 Parameter declaration list
Explanation: This is an informational message or a message header. No action is
required.
13087 10 Procedure option
Explanation: This is an informational message or a message header. No action is
required.
13088 10 owner
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 13000 - 13099
1212
13089 10 object type
Explanation: This is an informational message or a message header. No action is
required.
13090 10 Backup Server
Explanation: This is an informational message or a message header. No action is
required.
13091 10 dump header
Explanation: This is an informational message or a message header. No action is
required.
13092 10 dump trailer
Explanation: This is an informational message or a message header. No action is
required.
13093 10 deadlock
Explanation: This is an informational message or a message header. No action is
required.
13094 10 user interrupt
Explanation: This is an informational message or a message header. No action is
required.
13095 10 suspended
Explanation: This is an informational message or a message header. No action is
required.
13096 10 explicit
Explanation: This is an informational message or a message header. No action is
required.
13097 10 implicit
Explanation: This is an informational message or a message header. No action is
required.
13098 10 A pseudo table
Explanation: This is an informational message or a message header. No action is
required.
13099 16 IDENTITY function
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1213
Server Error Messages 13100 - 13199
Number Severity Text and Explanation
13100 16 recalculating sysindexes.minlen
Explanation: This is an informational message or a message header. No action is
required.
13101 16 WITH <option> [=] <value>
Explanation: This is an informational message or a message header. No action is
required.
13102 10 remote server
Explanation: This is an informational message or a message header. No action is
required.
13103 10 primary
Explanation: This is an informational message or a message header. No action is
required.
13104 10 secondary
Explanation: This is an informational message or a message header. No action is
required.
13105 10 updatable
Explanation: This is an informational message or a message header. No action is
required.
13106 10 not updatable
Explanation: This is an informational message or a message header. No action is
required.
13108 10 AT ISOLATION
Explanation: This is an informational message or a message header. No action is
required.
13109 10 because table scans cannot be restarted
Explanation: This is an informational message or a message header. No action is
required.
13110 10 due to an internal error
Explanation: This is an informational message or a message header. No action is
required.
13111 10 initializing new column sysindexes.maxrowsperpage to zero
Explanation: This is an informational message or a message header. No action is
required.
Server Error Messages 13100 - 13199
1214
13112 10 checking database references in sysreferences
Explanation: This is an informational message or a message header. No action is
required.
13113 10 modifying index syscomments.syscomments
Explanation: This is an informational message or a message header. No action is
required.
13114 10 recalculating sysindexes.maxlen
Explanation: This is an informational message or a message header. No action is
required.
13115 10 dropping index
Explanation: This is an informational message or a message header. No action is
required.
13116 10 creating table
Explanation: This is an informational message or a message header. No action is
required.
13117 10 creating index
Explanation: This is an informational message or a message header. No action is
required.
13118 10 noting the present database upgrade level
Explanation: This is an informational message or a message header. No action is
required.
13119 10 adding column
Explanation: This is an informational message or a message header. No action is
required.
13120 10 changing column name
Explanation: This is an informational message or a message header. No action is
required.
13123 10 Initializing systimeranges
Explanation: This is an informational message or a message header. No action is
required.
13124 10 first
Explanation: This is an informational message or a message header. No action is
required. (Not raised in 11.9.2)
13125 16 forced index
Explanation: This is an informational message or a message header. No action is
required.
13126 16 forced parallel
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1215
13127 16 forced lru/mru
Explanation: This is an informational message or a message header. No action is
required.
13128 16 forced prefetch
Explanation: This is an informational message or a message header. No action is
required.
13134 10 initializing new column sysusers.sname
Explanation: This is an informational message or a message header. No action is
required.
13135 10 initializing new column sysalternates.sname
Explanation: This is an informational message or a message header. No action is
required.
13136 10 initializing the new column sysobjects.suid
Explanation: This is an informational message or a message header. No action is
required.
13137 10 initializing new column syscomments.hiddentext to NULL
Explanation: This is an informational message or a message header. No action is
required.
13138 10 initializing new column sysprocedures.version
Explanation: This is an informational message or a message header. No action is
required.
13139 10 Setting the value for the column to 1 for all system-defined roles so that they will be
enabled on login.
Explanation: This is an informational message or a message header. No action is
required.
13144 10 Checking database timestamps
Explanation: This is an informational message.
13145 10 Verifying page header information
Explanation: This is an informational message or a message header. No action is
required.
13146 16 Jar
Explanation: This is an informational message or a message header. No action is
required.
13147 16 JDBC
Explanation: This is an informational message or a message header. No action is
required.
13148 10 checking SQL states in sysmessages
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Server Error Messages 13200 - 13299
1216
Server Error Messages 13200 - 13299
Number Severity Text and Explanation
13200 10 executing SQL statement
Explanation: This is an informational message or a message header. No action is
required.
13201 10 initializing partition IDs for each extent
Explanation: This is an informational message or a message header. No action is
required.
13202 10 initializing partition statistics for each partitioned table
Explanation: This is an informational message or a message header. No action is
required.
13203 15 Variable
Explanation: This is an informational message or a message header. No action is
required.
13204 15 Aggregate function
Explanation: This is an informational message or a message header. No action is
required.
13205 15 check constraint
Explanation: This is an informational message or a message header. No action is
required.
13206 10 changing name of system table
Explanation: This is an informational message.
13207 10 new name:
Explanation: This is an informational message or a message header. No action is
required.
13208 10 standby-mode log
Explanation: This is an informational message or a message header. No action is
required.
13209 10 Begin upgrade of distribution pages
Explanation: This is an informational message or a message header. No action is
required.
13210 10 Initialize systabstats with valid statistics
Explanation: This is an informational message. No action required.
13211 10 Checking indstatus2 in sysindexes and correcting it if required
Explanation: This is an informational message or a message header. No action is
required.
CHAPTER 6 Adaptive Server Error Messages
1217
Server Error Messages 13900 - 13999
13212 10 Creating/Updating the last chance threshold for logsegment.
Explanation: This is an informational message or a message header. No action is
required.
13214 10 insert rows into sysusrpartitions for each system table and index.
Explanation: This is an informational message or a message header. No action is
required.
13216 10 Upgrade SARGs in SYSINDEXES to 2-byte column IDs.
Explanation: This is an informational message or a message header. No action is
required.
13217 16 Reconcile (delete obsolete, add new) messages in SYSMESSAGES.
Explanation: This is an informational message or a message header. No action is
required.
13218 10 Load initial set of attribute-definition rows into SYSATTRIBUTES.
Explanation: This is an informational message or a message header. No action is
required.
13219 16 Upgrade colidarray in sysstatistics to 2-byte column IDs.
Explanation: This is an informational message or a message header. No action is
required.
13220 16 Initialize disk and create empty allocation units on master device.
Explanation: This is an informational message or a message header. No action is
required.
13221 16 Bootstrap basic system catalogs in database.
Explanation: This is an informational message or a message header. No action is
required.
Number Severity Text and Explanation
Number Severity Text and Explanation
13900 10 Warning: a default (object id %ld) is defined on column ’%.*s’ being modified. Check the
validity of the default value after this ALTER TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Server Error Messages 13900 - 13999
1218
13901 10 Warning: a rule or constraint is defined on column ’%.*s’ being modified. Verify the
validity of rules and constraints after this ALTER TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13902 10 Warning: Column ’%.*s’ being modified is a key in one or more indexes. Verify the
validity of these indexes after this ALTER TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13903 10 Warning: primary or foreign keys are defined on column ’%.*s’ being modified. Verify
the validity of the RI constraint after this ALTER TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13904 10 Warning: A logical RI constraint, using sp_primarykey/sp_foreignkey exists on column
’%.*s’ being modified. Verify the validity of the logical RI constraint after this ALTER
TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13905 10 Warning: no columns to drop, add or modify. ALTER TABLE ’%.*s’ was aborted.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13906 10 ALTER TABLE ’%.*s’ failed. You cannot add new non-NULL text/image column
’%.*s’. Such columns may only be added as NULL columns.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13907 16 ALTER TABLE ’%.*s’ failed. You cannot modify column ’%.*s’ to text/image type.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13908 16 ALTER TABLE ’%.*s’ failed. You cannot add off-row Java/text/image column in
conjunction with either dropping or modifying such a column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13909 16 ALTER TABLE ’%.*s’ failed. You cannot drop text/image column ’%.*s’ in conjunction
with modifying column ’%.*s’ to text/image type.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13910 10 Warning: since data is not copied when altering table ’%.*s’, the specified
’exp_row_size’ value will not be honored. Use sp_chgattribute to change the
’exp_row_size’ value after this ALTER TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1219
13911 10 Warning: when modifying column ’%.*s’, user specified NULL type overrides the
NULL type of user defined datatype ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13912 10 Warning: when modifying column ’%.*s’, the NULL type of the user-defined datatype
’%.*s’ will be applied to the column.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13913 10 Warning: column ’%.*s’ is referenced by one or more rules or constraints. Verify the
validity of the rules/constraints after this ALTER TABLE operation.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13914 16 ALTER TABLE ’%.*s’ failed. You cannot drop column ’%.*s’ which is referenced in one
or more rules/constraints. Drop the rules/constraints before dropping the column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13915 16 ALTER TABLE failed. You cannot add table-level constraints when the operation on
table ’%.*s’ requires data copy. Add the constraints in a separate ALTER TABLE
statement.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13916 16 ALTER TABLE ’%.*s’ failed. You cannot add column-level constraints, such as
referential integrity or primary key/unique constraints, when the operation requires data
copy.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13917 16 ALTER TABLE ’%.*s’ failed. You cannot alter a data-only locked partitioned table with
a clustered index when the operation requires data copy. Drop the index and try again.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13918 16 ALTER TABLE ’%.*s’ failed. Default cannot be an expression when adding non-NULL
column ’%.*s’. Use a default value instead.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13919 16 ALTER TABLE ’%.*s’ failed because the table definition has been changed.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13920 16 ALTER TABLE ’%.*s’ failed. Lock change operation cannot be supported with other
operations that do not require data copy.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
Server Error Messages 13900 - 13999
1220
13921 16 ALTER TABLE ’%.*s’ failed. You cannot drop column ’%.*s’ on which a
primary/foreign key constraint is defined using sp_primarykey or sp_foreignkey. Drop
the key definitions before dropping the column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13922 16 ALTER TABLE ’%.*s’ failed. You cannot modify timestamp column ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13923 16 ALTER TABLE ’%.*s’ failed. You cannot modify the datatype of column ’%.*s’ to
timestamp.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13924 16 ALTER TABLE ’%.*s’ failed. You cannot modify a primary key column to NULL.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13925 10 Warning: ALTER TABLE operation did not affect column ’%.*s’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13926 16 ALTER TABLE ’%.*s’ failed. A table with a clustered index cannot be altered if the
operation includes a lock scheme change.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13927 16 ALTER TABLE ’%.*s’ failed. You cannot add an identity column to a partitioned table
when the operation requires data copy.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13928 16 ALTER TABLE ’%.*s’ failed. You cannot specify a default clause when adding identity
column ’%.*s’.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13929 16 ALTER TABLE ’%.*s’ failed. You cannot drop identity column ’%.*s’ when
’identity_insert’ is on. Set this option off before dropping the identity column.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13930 16 The procedure ’%.*s’ contains an ALTER TABLE statement requiring data copy. This
should be the only statement in the procedure.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1221
13931 16 ALTER TABLE ’%.*s’ failed. Internal error detected while trying to update
SYSCOLUMNS with text/image replication status.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13932 16 ALTER TABLE ’%.*s’ failed. You cannot modify column ’%.*s’ to type ’%.*s’ which
has identity property.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13933 16 ALTER TABLE ’%.*s’ failed. You cannot modify identity column ’%.*s’ whose
datatype is user-defined.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13934 16 ALTER TABLE ’%.*s’ failed. You cannot modify column ’%.*s’. You cannot modify a
Java column or modify a column to type Java ADT.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13935 16 ALTER TABLE ’%.*s’ failed. You cannot add new non-null Java column ’%.*s’. Such
columns may only be added as NULL columns.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13936 16 ALTER TABLE ’%.*s’ failed. You cannot alter a partitioned table that has Java columns
when the operation requires data copy. To alter the schema, unpartition the table, then
repartition it.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
13937 10 Warning: The schema for table ’%.*s’ has changed. Drop and re-create each trigger on
this table that uses the ’if update(column_name)’ clause.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
13938 16 ALTER TABLE ’%.*s’ failed. You cannot drop column ’%.*s’ because it is part of the
partition key.
Explanation: Command failed. See the command syntax in the Reference Manual for
details.
13939 16 ALTER TABLE ’%.*s’ failed. You cannot modify column ’%.*s’ because it is part of the
partition key.
Explanation: Command failed. See the command syntax in the Reference Manual for
details.
Number Severity Text and Explanation
Server Error Messages 14000 - 14099
1222
Server Error Messages 14000 - 14099
13940 16 One or more column names in the specified table contain reserved words or special
characters, for example ’%.*s’. Set the QUOTED_IDENTIFIER option to handle the
column(s) and re-run the command.
Explanation: Adaptive Server could not perform the requested action. Rewrite the
command to conform to the requirement specified in the error message.
Number Severity Text and Explanation
Number Severity Text and Explanation
14000 10 per object statistics active determines whether the Adaptive Server will collect
monitoring information on a per object basis
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
14001 10 per object statistics active determines whether the Adaptive Server will collect
monitoring information on a per object basis
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14002 16 The configuration option ’dtm detach timeout period’ specifies the timeout period in
minutes, for detached transactions. Transactions that are detached longer than this
timeout period will be rolled back.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions.
14003 10 The ’abstract plan load’ option enables the server wide Abstract Plan LOAD mode from
ap_stdin.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14004 10 The ’abstract plan dump’ option enables the server wide Abstract Plan DUMP mode to
ap_stout.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14005 10 The ’abstract plan replace’ option enables the server wide Abstract Plan REPLACE sub-
mode.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
CHAPTER 6 Adaptive Server Error Messages
1223
14006 10 The ’abstract plan cache’ option enables the server wide Abstract Plan EXISTS CHECK
cache sub-mode.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14007 10 ’enable HA’ lets you enable or disable HA services in Adaptive Server. The default value
is 0 (disabled). This is a static option, meaning that you have to restart the server after
changing the value.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14008 10 Enables Unicode data to be normalized, that is re-written in canonical form. Once
disabled, cannot be re-enabled. Default is enabled.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14009 10 Changes the default sort order for Unicode (unichar/univarchar) data. Default is ’binary’.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14010 10 number of open partitions sets the maximum number of partitions that can be open at one
time on Adaptive Server. The default value is 500.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14011 10 open partition hash spinlock ratio specifies the number of internal hash table for open
partitions protected by one spinlock. The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14012 10 open partition spinlock ratio specifies the number of open partitions protected by one
spinlock. The default value is 100.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14013 10 Enables processing of Unicode surrogates, guaranteeing the integrity of surrogate pairs.
When disabled, surrogates are ignored. Default is disabled.
Explanation: This is an informational message about a unicode configuration option.
Unless otherwise specified, no action is required.
14014 10 max memory sets the maximum size of memory, in 2K units, that ASE can allocate.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14015 16 procedure cache size specifies the amount of memory allocated to the procedure cache.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Number Severity Text and Explanation
Server Error Messages 14000 - 14099
1224
14016 16 dynamic allocation on demand specifies whether ASE memory can be allocated on
demand due to reconfiguration of dynamic configuration parameters.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
14017 16 allocate max shared memory specifies whether ASE allocates all the memory specified
by ’max memory’ at any one time.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14018 16 number of engines at startup specifies the number of engines ASE brings online during
the startup process.
Explanation: This is an informational message. Unless otherwise specified, no action is
required.
14019 10 The amount of heap memory in bytes for each user connection.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Refer to the System Administration Guide for details.
14020 10 Enables row level access control facility. Default is disabled.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
14021 10 Enables SSL facility. Default is disabled.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
14022 16 total physical memory is a read-only parameter that indicates the size of the physical
memory allocated by ASE so far. It is not user-configurable.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Contact your System Administrator about any warning issued in the message.
Refer to the System Administration Guide for details.
14023 10 The ’number of histogram steps’ option specifies the default number of histogram steps
for update statistics and create index.
Explanation: This is an informational message. Unless otherwise specified, no action is
required. Refer to the Performance and Tuning Guide for details.
Number Severity Text and Explanation
CHAPTER 6 Adaptive Server Error Messages
1225
Server Error Messages 14100 - 14199
Number Severity Text and Explanation
14101 21 Insert of syspartition row failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14102 21 Delete of syspartitions row failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14103 21 Invalid setup status found in syspartition Manager during a call to: %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14104 21 No object id specified in syspartitions Manager call to: %s.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14105 21 Update of syspartitions failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14106 21 Copy of syspartition row failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14115 21 Object with objid %d in dbid %d is not a table.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
14116 21 Did not find table descriptor linked to process slot structure 0x%x when SQL Server tried
to release it.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
diagnostics can be run.
Server Error Messages 14200 - 14299
1226
Server Error Messages 14200 - 14299
14122 21 Update failed. SQL Server could not find field ’%d’ within partition descript or/buffer.
Explanation: Adaptive Server encountered an internal error during a partitioning
operation affecting the current process. Reconnect to Adaptive Server. Report the error to
your System Administrator so diagnostics can be run.
14123 21 Updating wrong ptnrow in dbid %d. Objid for actual row updated is %ld, objid for
intended row was %ld. Partition id for intended row was %d. Partition page is %ld, field
updated is %d. Partition row address is %0x, row number is %d.
Explanation: Adaptive Server encountered an internal error during a partitioning
operation affecting the current process. Reconnect to Adaptive Server. Report the error to
your System Administrator so DBCC diagnostics can be run.
14125 21 Internal error occurred while running the sysindexes exerciser.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.
Number Severity Text and Explanation
Number Severity Text and Explanation
14200 16 The specified java signature is invalid.
Explanation: Refer to the writeup for this error.
14201 16 Return type of the java method for a SQLJ procedure must be void or int.
Explanation: Command failed due to invalid or illegal request. Check syntax and
semantics.
14202 16 The Java ’main’ method cannot return result sets.
Explanation: Command failed. Check application code.
14203 16 Invalid mapping between the SQLJ procedure signature and the signature of the Java
command line ’main’ method.
Explanation: Command failed. Check application code.
14204 16 The specified return type does not map to the java method return type.
Explanation: Command failed. Check application code and function definition.
14205 16 The Java ’main’ method cannot be used in CREATE FUNCTION.
Explanation: Command failed. Check function definition.
CHAPTER 6 Adaptive Server Error Messages
1227
14206 10 Warning: SQLJ procedure is trying to return more result sets than were specified in
DYNAMIC RESULT SETS clause (%d). Only %d result sets are returned.
Explanation: This is an informational message but may require follow-up action.
14207 16 Incorrect number of parameters for SQLJ function ’%.*s’.
Explanation: Command failed. Check syntax and semantics.
14208 16 Unable to execute SQLJ function ’%s’. The function schema may have changed since the
query was compiled.
Explanation: Check the function, methods and any other dependent code.
14209 16 Unable to load the method ’%.*s’ for SQLJ function ’%s’ at execution time. The method
schema may have changed since the function was compiled.
Explanation: Check the function, methods and any other dependent code.
14210 16 SQLJ functions do not support TEXT/IMAGE return types. Use the ADT type
java.io.InputStream.
Explanation: Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by the message.
14211 16 The method signature of Java method ’%s’ exceeds the maximum size of %d.
Explanation: Command failed due to invalid or illegal request. Check syntax.
14212 16 Cannot find a public method named ’%.*s, ResultSets[], ...)’ in class ’%.*s’. Either the
method does not exist, or it is being called with incorrect argument types.
Explanation: Check the function, methods and any other dependent code.
14213 16 Java method ’%s’ has too many parameters. The maximum number is %d.
Explanation: Check SQLJ application code.
14214 16 SQLJ procedures cannot return a result set from temporary tables to the ASE JDBC client.
Explanation: Check SQLJ application code.
14215 16 SQLJ procedures can only return result sets created with ASE JDBC driver.
Explanation: Check SQLJ application code.
14216 16 Function ’%.*s’ not found. If this is a SQLJ function, use sp_help to check whether the
object exists (sp_help may produce a large amount of output).
Explanation: Check function definition as directed.
Number Severity Text and Explanation
Server Error Messages 14300 - 14399
1228
Server Error Messages 14300 - 14399
Number Severity Text and Explanation
14300 16 Cannot use duplicate column names in partition key list. Column name ’%.*s’ listed
more than once.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14301 16 Column ’%.*s’ -- Cannot partition on a column of TEXT or IMAGE data type.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14302 16 Column ’%.*s’ -- Cannot partition on a column of BIT data type.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14303 16 Column ’%.*s’ -- Cannot partition on a column that has a Java-SQL class datatype.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14304 16 Partition ’%.*s’ -- Partition condition not in incremental order.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14305 16 Partition ’%.*s’ -- #%d upperbound value overflow.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14306 16 Partition ’%.*s’ -- #%d upperbound value underflow.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
14307 16 Partition ’%.*s’ -- %d upperbounds expected, but %d specified.
Explanation: Adaptive Server could not perform the requested action. Modify your
command to meet the Adaptive Server requirement for the objects or variables shown in
the error message.
CHAPTER 6 Adaptive Server Error Messages
1229
Server Error Messages 14400 - 14499
Server Error Messages 17000 - 18999
Messages in the 17xxx and 18xxx series are informational and error messages
returned by stored procedures. For help with a system procedure message, refer
to the discussion of that procedure in the "System Procedures" section of the
Adaptive Server Reference Manual. ASE functions and commands used in a
stored procedure may generate their own error messages, with an error number
below 17xxx and severity of 10 or higher; for help with those messages, refer
to the appropriate error number in this chapter.
14308 20 Attempt to insert a row in syspartitionkeys failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
diagnostics can be run.
14309 20 Attempt to delete a row in syspartitionkeys failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
diagnostics can be run.
14310 20 Attempt to drop a partition condition failed.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
diagnostics can be run.
Number Severity Text and Explanation
Number Severity Text and Explanation
14400 10 number of HBC connections setts the maximum number of simultaneous Host Based
Communication connections.
Explanation: This is an informational message about a configuration parameter.
Server Error Messages 17000 - 18999
1230
Number Severity Text and Explanation
17000-
18999
0 See above comment on this series of messages.
1231
Glossary
allocation pages Database-wide pages Adaptive Server uses to maintain the information
about how each unit of 256 contiguous database pages is used.
buffer A buffer is a structure that Adaptive Server uses to store physical disk
pages while they are in memory. When a page is read into memory from
disk, a buffer header is assigned to it. The header tracks the usage and the
contents of the page image. Together, the page and the buffer header
define a buffer.
clustered index An index in which the physical order of the data and the logical (indexed)
order of the data is the same. Only one clustered index can exist on a table.
See also “leaf level.”
dbtable A dbtable is a memory structure that tracks information about a database;
for example whether the database is currently in use, whether it is in
single-user mode, and and other data needed by a server task accessing the
database.
error log The Adaptive Server error log file includes:
• Adaptive Server restart messages (including database recovery
messages)
• Fatal error messages
• Error messages from the kernel
The name of this file varies; see the Adaptive Server installation and
configuration guide for details.
The Backup Server has its own error log file where Backup Server error
messages are written. Refer to “Backup Server Error Logging” in the
System Administration Guide for details.
The SQL Monitor Server has its own error log file where SQL Monitor
Server error messages are written. Refer to the Monitor Server
Supplement for your platform for details.
The Replication Server has its own error log file where Replication Server
error messages are written. Refer to the Replication Server Administration
Guide for details.
1232
The Navigation Server has its own error log file where Navigation Server error
messages are written. Refer to the Navigation Server Reference Manual for
details.
extent Every 256-page allocation unit is divided into 32 structures called extents, each
containing 8 contiguous pages. Each extent contains information about those 8
contiguous pages, including a bitmap showing pages in use and a bitmap
showing pages to be deallocated.
foreign key In a table, a column whose data values correspond to the values of a key
column in another table.
index ID The number Adaptive Server uses to uniquely identify (within a database) an
index. The following table shows the index types:
leaf level The bottom of a clustered or nonclustered index. In a clustered index, the leaf
level contains the actual data pages of the table.
logical page The unique address for pages in the context of each database.
MASS Buffers are grouped together to form Memory Address Space Segments
(MASSes). A buffer cache consists of MASSes linked in MRU/LRU (most
recently used/least recently used) chains.
nonclustered index An index that stores key values and points to data. The leaf level points to data
rows rather than containing the data itself.
Object Allocation
Map (OAM) An Object Allocation Map (OAM) contains information about how space is
allocated for Adaptive Server objects. A single OAM page holds information
about up to 250 allocation pages (248 if the object is an IDENTITY column).
Each allocation page for an object has an entry in the OAM pages for that table
or index. The OAM entry for each allocation page stores the number of used
and unused data and index pages on that allocation page.
A maximum of 263 OAM pages are allowed, supporting a maximum of 65,535
allocation units for an object.
Index ID Meaning
0 Actual table data
1 Clustered index
2-250 Nonclustered indexes
255 Text or image page
1233
object ID The number Adaptive Server uses to uniquely identify (within a database) an
Adaptive Server object. If you know an object ID and you know the database
the object is in, you can determine the object name. System tables have an
object ID that is less than 100 and user tables have an object ID that is 100 or
greater.
primary key The column or combination of columns that uniquely identify a row.
remote procedure
call (RPC) A procedure executed on a different Adaptive Server from the Adaptive Server
the user is logged into.
session descriptors The data structures used to manage access to Adaptive Server objects. Session
descriptors exist in three forms: user session descriptors (including worktable
session descriptors), system session descriptors, and worktable session
descriptors (separate from user session descriptors).
system table One of the data dictionary tables. System tables have an object ID that is less
than 100. The system tables keep track of information about the Adaptive
Server as a whole and about each user database. The master database contains
some system tables that are not in user databases. The “Sybase Adaptive Server
System Tables Diagram,” available through Sybase Customer Support, shows
which system tables are in master only and which system tables are in all
databases. For details about each system table, refer to the Adaptive Server
Reference Supplement.
timestamp Timestamps are an attribute of each database. Each entry in the database
transaction log is associated with a unique timestamp. Timestamps are used to
order database activity; however, timestamps are not time-dependent.
transaction log A system table (syslogs) in which all changes to the database are recorded.
virtual page Actual offset on a device for a page within a database.
Note For a more complete set of definitions, see the glossary in the Adaptive
Server System Administration Guide.
1234
1235
Symbols
%S_MSG
explanation 367
Numerics
102 error 142
107 error 143
11018 error 630
1105 error 281
1108 error 289, 379
1120 error 290
11203 error 632
1124 error 291
1127 error 292
1129 error 294
1131 error 296
1133 error 297
1141 error 298
1142 error 300
1143 error 304
11903 error 631
1203 error 306
1204 error 306
1205 error 308
1243 error 310
1249 error 311
1265 error 312
12716 error 633
12717 error 634
1279 error 313
12818 error 636
14200 error 637
1501 error 315
1505 error 316
1508 error 318
1509 error 319
1510 error 321
1514 error 322
1530 error 323
1531 error 324
1601 error 326
1602 error 327
1603 error 329
1605 error 330
1608 error 333
1613 error 334
1621 error 335
1622 error 336
1623 error 337
1702 error 339
1732 error 339
17461 error 639
17715 error 640
17716 error 640
17737 error 641
17870 error 641
17871 error 642
17872 error 642
17873 error 643
17874 error 643
17875 error 644
17903 error 644
17904 error 645
17905 error 645
17906 error 645
17910 error 646
1803 error 340
18031 error 646
18032 error 647
18033 error 647
1808 error 342
1809 error 343
18097 error 648
1810 error 344
18123 error 648
1813 error 344
18145 error 649
Index
Index
1236
1820 error 345
18750 error 649
1902 error 346
1903 error 347
1916 error 348
and 1508 error 319
1928 error 349
195 error 145
207 error 147
208 error 148
2110 error 349
213 error 150
216 error 151
2243 error 352
225 error 153
226 error 154
229 error 155
232 error 156
233 error 157
2401 error 353
2402 error 354
2409 error 355
241 error 159
247 error 160
2501 error 357
2502 error 358
2503 error 359
2506 error 361
2507 error 362
2509 error 364
2510 error 366
2511 error 367
2513 error 368
2514 error 369
2517 error 371
2520 error 372
2521 error 373
2524 error 377
2525 error 378
2529 error 381
2540 error 382
2546 error 386
2547 error 390
2550 error 392
2558 error 394
cause 396
prevention 398
2559 error 401
257 error 162
2572 error 403
2573 error 404
2574 error 405
2575 error 406
2578 error 407
2582 error 408
2583 error 410
259 error 163
2591 error 412
2596 error 413
2601 error 416
2610 error 416
2615 error 418
2619 error 419
2620 error 420
2626 error 422
2628 error 424
265 error 165
266 error 166
268 error 169
and sp_helpsort 169
2714 error 426
2729 error 427
2753 error 427
2762 error 428
277 error 171
2805 error 431
2806 error 432
2811 error 433
and 1105 error 433
2812 error 433
2824 error 436
2835 error 437
301 error 172
3019 error 438
3020 error 439
3105 error 440
311 error 172
3120 error 441
313 error 174
314 error 176
3201 error 442
3203 error 443
Index
1237
3211 error 444
3212 error 445
3216 error 446
3225 error 446
3230 error 447
3233 error 448
3240 error 449
3301 error 450
3307 error 451
3401 error 454
3403 error 455
3404 error 456
3414 error 457
3418 error 458
3425 error 459
3429 error 459
3434 error 461
3445 error 462
3446 error 463
3447 error 464
3452 error 465
3454 error 465
3470 error 467
3604 error 469
3621 error 469
3626 error 471
3701 error 473
3702 error 474
3703 error 475
3704 error 476
3731 error 477
3904 error 479
3905 error 480
3906 error 481
3908 error 483
3917 error 484
4001 error 487
4002 error 488
4020 error 491
403 error 178
404 error 178
414 error 179
4204 error 493
4205 error 497
4207 error 497
4216 error 498
4221 error 500
4222 error 501
428 error 180
4305 error 502
4322 error 503
4716 error 505
4801 error 506
4806 error 506
4951 error 508
4953 error 508
4954 error 509
4956 error 510
4964 error 510
5006 error 512
5013 error 513
5018 error 515
5034 error 517
511 error 181
5115 error 519
512 error 181
5123 error 521
5142 error 523
515 error 183
530 error 185
539 error 185
540 error 186
546 error 187
547 error 188
551 error 190
5602 error 524
5701 error 525
5704 error 525
5808 error 527
5824 error 528
584 error 191
5846 error 529
5847 error 530
5848 error 531
5849 error 532
5850 error 532
5851 error 533
5852 error 534
5853 error 535
5854 error 536
5857 error 537
5859 error 538
Index
1238
5861 error 538
5863 error 539
5865 error 541
5866 error 542
5867 error 542
5868 error 543
5893 error 544
601 error 192
603 error 193
605 error 195, 653
6103 error 546
6107 error 547
611 error 198
614 error 199
622 error 202
623 error 202
624 error 204
625 error 207
629 error 210
631 error 211
644 error 215
678 error 216
6901 error 548
6902 error 549
691 error 216
692 error 218
693 error 219
694 error 220
695 error 222
696 error 223
697 error 224
701 error 225
702 error 227
703 error 229
706 error 230
707 error 231
709 error 231
7101 error 552
7105 error 553
7114 error 555
7130 error 556
7134 error 558
7201 error 560
7205 error 561
7207 error 562
7211 error 563
7212 error 565
7214 error 566
7215 error 567
7218 error 568
7220 error 569
7221 error 571
7223 error 574
7227 error 575
7234 error 576
7235 error 577
7380 error 579
7401 error 580
7402 error 581
7403 error 582
7404 error 583
7406 error 584
7407 error 585
7408 error 586
7409 error 586
7410 error 587
7411 error 588
7412 error 589
7413 error 589
7414 error 590
7415 error 591
7618 error 592
7783 error 594
7788 error 595
7901 error 597
7902 error 598
7928 error 601
7930 error 602
7939 error 603
7940 error 605
7949 error 607
7989 error 609
8006 error 610
8009 error 611
803 error 232
804 error 234
806 error 235
813 error 237
820 error 238
8201 error 613
8203 error 613
8204 error 615
Index
1239
8207 error 616
821 error 240
8210 error 617
8211 error 618
8219 error 619
822 error 241
823 error 243
832 error 245
834 error 246
835 error 248
840 error 248
8402 error 621
8419 error 622
842 error 249
847 error 250
849 error 251
852 error 253
855 error 254
8601 error 625
861 error 255
863 error 256
8704 error 626
9004 error 627
903 error 257
905 error 258
906 error 260
908 error 261
911 error 85, 262
9122 error 628
913 error 263
916 error 264
921 error 266
924 error 267
925 error 268
926 error 270
930 error 272
935 error 273
940 error 275
941 error 276
945 error 277
950 error 279
A
Access errors 192
Error 601 192
Error 603 193
Error 605 195
Error 611 198
Error 614 199
Error 622 202
Error 623 202
Error 624 204
Error 625 207
Error 631 211
Error 644 215
Error 678 216
Error 691 216
Error 692 218
Error 693 219
Error 694 220
Error 695 222
Error 696 223
Error 697 224
Access Method errors 191
Account
locked, and 4002 error 488
Adaptive Server
character set support error 654
does not start 4, 17
rebuilding manually 17
resetting to default configuration 39
returning to multi-user mode 34
starting in single-user mode 33
starting with trace flags 80
Adjust table
and 2506 error 361
Allocation
1108 error 289
3403 error 455
7989 error 609
structure 386
Allocation errors
and single-user mode 90
detecting early 89
explanation of 86
fixing with the fix option 86
Allocation hints space
and 1732 error 339
Allocation pages
and 1129 error 295
Index
1240
and 1131 error 296
allow remote access
and 7221 error 572
allow updates
and 259 error 164
allow_dup_row
and 1508 error 318
and 1916 error 348
create index option 318
alter database
and 1808 error 342
and 2558 error 399
and 3225 error 447
for load 273
when database full 512
alter database errors 512
Error 5006 512
Error 5013 513
Error 5018 515
Error 5034 517
alter table
and 3703 error 475
alter table errors 508
Error 4951 508
Error 4953 508
Error 4954 509
Error 4956 510
Error 4964 510
and expression limit 178
Arithmetic overflow
and 232 error 156
ASTC errors
Error 5602 524
Asynchronous I/O
Sun systems 244, 521
Auditing errors 592
Error 7618 592
B
Backup Server
accessing after recovery 40
and sp_volchanged system procedure 446
setting default manually in Adaptive Server 40
basis_daioconfig error 651
bcp
use to shrink database 441
bcp
and 4207 error 498
fast mode 507
bcp errors 505, 506
Error 4801 506
Error 4806 506
Buffer
mismatch 653
Buffer Manager Errors
Error 832 245
Buffer Manager errors 231, 232
Error 803 232
Error 804 234
Error 806 235
Error 813 237
Error 820 238
Error 821 240
Error 822 241
Error 823 243
Error 834 246
Error 835 248
Error 840 248
Error 842 249
Error 847 250
Error 849 251
Error 852 253
Error 855 254
Error 861 255
Error 863 256
Buffer mismatch error 653
buildmaster 26
and 5013 error 514
C
Cache management problems 653
character set
how to find 65
how to view existing 65
Character set conversion errors 353
Error 2401 353
Error 2402 354
Error 2409 355
Index
1241
Character set error 654
Character set support error 654
checkpoint
and 3401 error 454
and 623 error 203
and 624 error 205
and 631 error 214
and 7413 error 589
checkpoint
and 822 error 281
Client process
333
Clustered index 400
and duplicate values 418
one per table 347
wrong page 210
Column
limit on tables 339
name rules 339
Command aborted
and 3621 error 469
Comments xxv
Commit and abort errors 449, 450
Error 3301 450
Error 3307 451
Composite index
definition 347
Configuration errors 527, 629
Error 5808 527
Error 5824 528
Error 5846 529
Error 5847 530
Error 5848 531
Error 5849 532
Error 5850 532
Error 5851 533
Error 5852 534
Error 5853 535
Error 5854 536
Error 5857 537
Error 5859 538
Error 5861 538
Error 5863 539
Error 5865 541
Error 5866 542
Error 5867 542
Error 5868 543
Error 5893 544
Configuration parameters
calculated 537
read-only 537
Configured sockets
and 1605 error 330
Corrupt index 215, 366
Corrupted
index, how to fix 75
table, rescuing data from 78
Corrupted index
on system tables, repairing 75
Could not create shared memory error 655
create database
and 1808 error 342
and 1809 error 343
and 1810 error 344
and 1813 error 344
and 2558 error 398
and 3225 error 447
and 906 error 260
and size of model 344
create index
and 1505 error 316
and 1510 error 321
and 1530 error 323
and 1531 error 324
and 1928 error 349
clustered index 1508 error 318
exclusive option error 348
failure on duplicate key 316
failure on duplicate row 318
ignore_dup_key option 469
options and Error 1916 319
create table
and 1702 error 339
create trigger
and 2110 error 350
Create Utilities errors
Error 2753 427
Create utilities errors 339, 424, 426
Error 12818 636
Error 1702 339
Error 1732 339
Error 1803 340
Index
1242
Error 1808 342
Error 1809 343
Error 1810 344
Error 1813 344
Error 1820 345
Error 1902 346
Error 1903 347
Error 1916 348
Error 1928 349
Error 2110 349
Error 2714 426
Error 2729 427
Error 2762 428
Creating error messages 138
CSMD Dump 132
current number online engines configuration parameter.
See sp_configure
Current process infected with %d error 655
D
Data
and log mapping 397
cache, sizing 226
page 367
Data on log error 397
data_pgs 300
Database
configured size 440
dropping when drop database fails 84
dump Error 3201 442
failed recovery and suspect status 457, 459
failure during recovery 207
full 282
loading after corruption 207
maintenance 230
matching to physical devices 125
model and 1105 error 286, 288
naming conventions 148
no chkpt on recovery option 288
no performance benefit on a single device 512
page, matching to object 93
recovery 205
shrinking 440
single-user option 288
sort order 441
suspect 207, 266, 270
suspect, how to reload 84
Database owner.
See dbo
dataserver
and 1623 error 337
dataserver errors 487
Error 4001 487
Error 4002 488
Error 4020 491
Datatype
storage size. 347
Datatype conversion
and 247 error 161
dbcc
printing output to screen 93
dbcc checkalloc
and 2525 error 379
and 2546 error 386
and 2558 error 395
and 2572 error 403
and 2583 error 410, 411
and 7939 error 603
and 7940 error 605
and 7949 error 608
and single-user mode 86
dbcc checkalloc with fix option
syntax 92
dbcc checkcatalog
and 2514 error 369
and 2517 error 371
and 2520 error 372
and 2550 error 393
dbcc checkdb
and 2501 error 357
and 2506 error 361
and 2507 error 362
and 2509 error 364
and 2520 error 372
and 2524 error 377
and 605 error 195
and 7902 error 598
and 7930 error 602
and 7948 error 1040
dbcc checkstorage
Index
1243
analyzing faults 69
and other dbcc errors 70
faults due to sp_placeobject 73
dbcc checktable
and 2501 error 357
and 2506 error 361
and 2507 error 362
and 2509 error 364
and 2524 error 377
and 2582 error 409
and 2596 error 413
and 7902 error 598
and 7930 error 602
and 7948 error 1040
dbcc dbrepair
and 2520 error 372
dbcc dbrepair
and 2573 error 404
and 3702 error 474
dbcc errors 357, 597
2591 error 412
Error 2501 357
Error 2502 358
Error 2503 359
Error 2506 361
Error 2507 362
Error 2509 364
Error 2510 366
Error 2511 367
Error 2513 368
Error 2514 369
Error 2517 371
Error 2520 372
Error 2521 373
Error 2524 377
Error 2525 378
Error 2529 381
Error 2540 382
Error 2546 386
Error 2547 390
Error 2550 392
Error 2558 394
Error 2559 401
Error 2572 403
Error 2573 404
Error 2574 405
Error 2575 406
Error 2578 407
Error 2582 408
Error 2583 410
Error 2596 413
Error 7901 597
Error 7902 598
Error 7928 601
Error 7930 602
Error 7939 603
Error 7940 605
Error 7949 607
Error 7989 609
dbcc fix_text
and 2501 error 357
dbcc indexalloc
and 7940 error 605
dbcc indexalloc
and 2583 error 410
and 7939 error 603
and 7949 error 608
dbcc page 93
and 806 error 235
dbcc pglinkage 211
dbcc reindex
and 2501 error 357
dbcc tablealloc
and 2501 error 357
and 2583 error 410
and 7939 error 603
and 7940 error 605
and 7949 error 608
dbo
and 208 error 148
and 2812 error 434
and 4806 error 506
and select into/bulkcopy option 506
dbo
and 268 error 169
dbwritetext
and 268 error 170
and 7130 error 556
Deadlock
and 1205 error 308
and long-running transaction 309
DECnet protocol
Index
1244
and user connections 327
default character set
changing manually 58
Deleting duplicate rows 324
Delimited identifiers 147
Descriptor Manager errors 613
Error 8201 613
Error 8203 613
Error 8204 615
Error 8207 616
Error 8210 617
Error 8211 618
Error 8219 619
Device
finding virtual device number 108
lost, with pieces of tempdb 14
moving using disk mirroring 100
offline 241, 242, 249, 447
removed 241, 249
renamed 241, 249
dinit kernel error message 243
Disaster recovery 1
Disk errors 515, 519
Error 5115 519
Error 5123 521
Error 5142 523
disk init
failure 519
failure and Error 5123 521
size 519, 522
vdevno 520
Disk Manager errors
Error 9004 627
Disk mirroring
I/O error on primary device 679
I/O error on secondary device 679
disk refit 36
disk reinit 36
disk remirror 680
Distributed database network errors 560
Error 7201 560
Error 7205 561
Error 7207 562
Error 7211 563
Error 7212 565
Error 7214 566
Error 7215 567
Error 7218 568
Error 7220 569
Error 7221 571
Error 7223 574
Error 7227 575
Error 7234 576
Error 7235 577
Distribution page 380
dopen error 657
dpages 831
drop database
failure procedure 84
drop errors 473
Error 3701 473
Error 3702 474
Error 3703 475
Error 3704 476
Error 3731 477
drop index
and 3703 error 475
drop table
and 3731 error 477
drop trigger
and 3703 error 475
Dstart I/O request repeatedly delayed error 659
dump and load errors 438, 493
Error 3019 438
Error 3020 439
Error 3105 440
Error 3120 441
Error 3201 442
Error 3203 443
Error 3211 444
Error 3212 445
Error 3216 446
Error 3225 446
Error 3230 447
Error 3233 448
Error 3240 449
Error 4204 493
Error 4205 497
Error 4207 497
Error 4216 498
Error 4221 500
Error 4222 501
Index
1245
Error 4305 502
Error 4322 503
dump database
and 3211 error 444
and 3212 error 445
and 3240 error 449
dump transaction
and 4204 error 493
and 4207 error 498
and 4222 error 501
with no_log 240
Duplicate key
and create index 316
Duplicate rows
deleting 324
E
Error
243
creating error messages 138
faxing log fragments 140
hard 605 195
read Error 822 241
reporting to Sybase 138
system procedure 639
transient 605 195
variables in error message text 136
write Error 822 241
Error 102 142
Error 107 143
Error 10841 629
Error 11018 630
Error 1105 281
and 2558 error 395
Error 1108 289
Error 1120 290
Error 11203 632
Error 1124 291
Error 1127 292
Error 1129 294
Error 1131 296
Error 1133 297
Error 1141 298
Error 1142 300
Error 1143 304
Error 11903 631
Error 1203 306
Error 1204 306
Error 1205 308
Error 1243 310
Error 1249 311
Error 1265 312
Error 12716 633
Error 12717 634
Error 1279 313
Error 12818 636
Error 14200 637
Error 1501 315
Error 1505 316
Error 1508 318
Error 1509 319
Error 1510 321
and 1105 error 321
Error 1514 322
Error 1530 323
Error 1531 324
Error 1601 326
Error 1602 327
Error 1603 329
Error 1605 330
Error 1608 333
Error 1613 334
Error 1621 335
Error 1622 336
Error 1623 337
Error 1702 339
Error 1732 339
Error 17461 639
Error 17715 640
Error 17716 640
Error 17737 641
Error 17870 641
Error 17871 642
Error 17872 642
Error 17873 643
Error 17874 643
Error 17875 644
Error 17903 644
Error 17904 645
Error 17905 645
Index
1246
Error 17906 645
Error 17910 646
Error 1803 340
Error 18031 646
Error 18032 647
Error 18033 647
Error 1808 342
Error 1809 343
Error 18097 648
Error 1810 344
Error 18123 648
Error 1813 344
Error 18145 649
Error 1820 345
Error 18750 649
Error 1902 346
Error 1903 347
Error 1916 348
Error 1928 349
Error 195 145, 245
Error 207 147
Error 208 148
and 229 error 149
Error 2110 349
Error 213 150
Error 216 151
Error 2243 352
Error 225 153
Error 226 154
Error 229 155
Error 232 156
Error 233 157
Error 2401 353
Error 2402 354
Error 2409 355
Error 241 159
Error 247 160
Error 2501 357
Error 2502 358
Error 2503 359
and 605 error 359
Error 2506 361
Error 2507 362
Error 2509 364
Error 2510 366
Error 2511 367
Error 2513 368
Error 2514 369
Error 2517 371
Error 2520 372
Error 2521 373
Error 2524 377
Error 2525 378
Error 2529 381
Error 2540 382
and 7939 error 604
Error 2546 386
and 7939 error 604
Error 2547 390
Error 2550 392
Error 2558 394
Error 2559 401
Error 2572 403
Error 2573 404
Error 2574 405
Error 2575 406
Error 2578 407
Error 2582 408
Error 2583 410
Error 259 163
Error 2591 412
Error 2596 413
Error 2601 416
Error 2610 416
Error 2615 418
and 1916 error 418
Error 2619 419
Error 2620 420
Error 2626 422
Error 2628 424
Error 266 166
Error 268 169
and sp_help 169
and sp_helpsort 169
Error 2714 426
Error 2729 427
Error 2753 427
Error 2762 428
Error 277 171
Error 2805 431
Error 2806 432
Error 2811 433
Index
1247
Error 2812 433
Error 2824 436
Error 2835 437
Error 301 172
Error 3019 438
Error 3020 439
Error 3105 440
Error 311 172
Error 3120 441
Error 313 174
Error 314 176
Error 3201 442
Error 3203 443
Error 3211 444
Error 3212 445
Error 3216 446
Error 3225 446
Error 3230 447
Error 3233 448
Error 3240 449
Error 3301 450
Error 3307 451
Error 3401 454
Error 3403 455
Error 3404 456
Error 3414 457
Error 3418 458
Error 3425 459
Error 3429 459
Error 3434 461
Error 3445 462
Error 3446 463
Error 3447 464
Error 3452 465
Error 3454 465
Error 3470 467
Error 3604 469
Error 3621 469
Error 3626 471
Error 3701 473
and 2714 error 473
Error 3702 474
Error 3703 475
Error 3704 476
Error 3731 477
Error 3904 479
Error 3905 480
Error 3906 481
Error 3908 483
Error 3917 484
Error 4001 487
Error 4002 488
Error 4020 491
Error 403 178
Error 404 178
Error 414 179
Error 4204 493
Error 4205 497
Error 4207 497
Error 4216 498
Error 4221 500
Error 4222 501
Error 428 180
Error 4305 502
Error 4322 503
Error 4716 505
Error 4801 506
Error 4806 506
Error 4951 508
Error 4953 508
Error 4954 509
Error 4956 510
Error 4964 510
Error 5006 512
Error 5013 513
Error 5018 515
Error 5034 517
Error 511
and 1708 error 181
Error 5115 519
Error 512 181
Error 5123 521
Error 5142 523
Error 530 185
Error 539 185
Error 540 186
Error 546 187
Error 547 188
Error 551 190
Error 5602 524
Error 5701 525
Error 5704 525
Index
1248
Error 5808 527
Error 5824 528
Error 584 191
Error 5846 529
Error 5847 530
Error 5848 531
Error 5849 532
Error 5850 532
Error 5851 533
Error 5852 534
Error 5853 535
Error 5854 536
Error 5857 537
Error 5859 538
Error 5861 538
Error 5863 539
Error 5865 541
Error 5866 542
Error 5867 542
Error 5868 543
Error 5893 544
Error 601 192
Error 603 193
Error 605 195
and 2502 error 358
Error 6103 546
Error 6107 547
Error 611 198
Error 614 199
Error 622 202
Error 623 202
Error 624 204
Error 625 207
Error 631 211
Error 644 215
Error 678 216
Error 6901 548
Error 6902 549
Error 691 216
Error 692 218
Error 693 219
Error 694 220
Error 695 222
Error 696 223
Error 697 224
Error 701 225
Error 702 227
Error 703 229
Error 706 230
Error 707 231
Error 709 231
Error 7101 552
Error 7105 553
Error 7114 555
Error 7130 556
Error 7134 558
Error 7201 560
Error 7205 561
Error 7207 562
Error 7211 563
Error 7212 565
Error 7214 566
Error 7215 567
Error 7218 568
Error 7220 569
Error 7221 571
Error 7223 574
Error 7227 575
Error 7234 576
Error 7235 577
Error 7380 579
Error 7401 580
Error 7402 581
Error 7403 582
Error 7404 583
Error 7406 584
Error 7407 585
Error 7408 586
Error 7409 586
Error 7410 587
Error 7411 588
Error 7412 589
Error 7413 589
Error 7414 590
Error 7415 591
Error 7618 592
Error 7783 594
Error 7788 595
Error 7901 597
Error 7902 598
Error 7928 601
Error 7930 602
Index
1249
Error 7939 603
Error 7940 605
Error 7949 607
Error 7989 609
Error 8006 610
Error 8009 611
Error 803 232
Error 804 234
Error 806 235
Error 813 237
Error 820 238
Error 8201 613
Error 8203 613
Error 8204 615
Error 8207 616
Error 821 240
Error 8210 617
Error 8211 618
Error 8219 619
Error 822 241
Error 823 243
Error 834 246
Error 835 248
Error 840 248
Error 8402 621
Error 8419 622
Error 842 249
Error 847 250
Error 849 251
Error 852 253
Error 855 254
Error 8601 625
Error 861 255
Error 863 256
Error 8704 626
Error 9004 627
Error 903 257
Error 905 258
Error 906 260
Error 911 85, 262
Error 9122 628
Error 913 263
Error 916 264
Error 921 266
Error 924 267
Error 925 268
Error 926 270
Error 930 272
Error 935 273
Error 940 275
Error 941 276
Error 945 277
Error 950 279
Error and exception handling errors 467, 469
Error 3604 469
Error 3621 469
Error 3626 471
Error log 135
monitoring 127
Operating System 131
script for checking 127
Error severity levels 135
Errors
access method 191
alter database 512
alter table 508
auditing 592
Buffer Manager 231
character set conversion 353
commit and abort 449
configuration 527
create utilities 339, 424
dataserver 487
dbcc 357, 597
Descriptor Manager 613
disk 515
distributed database network 560
dump and load 493
dump and load 438
error and exception handling 467
Fault Isolation Utility 633
initialization 325
insert 416
kernel 651
Lock Manager 304
Memory Manager 216
Open Client 525
Open Database Manager 256
Parser 141, 579
Procedure Manager 431
process kill 546
Process Status Structure 625
Index
1250
query processor 171
recovery 452
remote create 631
RPC 610
Sequencer 147, 594, 630, 637
Site Buffer Manager 626
Sort Manager 313
sysindexes Manager 621
Text Manager 552
threshold 580
timestamp 548
Transaction 479
Execution plan
and 225 error 153
Expression limit on queries 178
Extent 386, 394
F
Failed to open device error 663
Fast bcp method 507
Fault Isolation Utility errors 633
Error 12716 633
Error 12717 634
File already in use error 664
forceindex
and 313 error 176
and 314 error 176
Foreign key 180
and 547 error 189
G
Guardword 675
H
Hard 605 195
Help xxviii
High Availability errors
Error 2243 352
holdlock
595
and 1205 error 309
I
I/O
Error 5115 519
Error 822 241
Error 823 243
Identifiers
delimited 147
ignore_dup_key
and 3604 error 469
ignore_dup_key 469
and 1916 error 348
ignore_dup_row
and 1508 error 318
and 1916 error 348
create index option 318
Index
clustered 210, 400
clustered index and sorted_data 323
composite index 347
corrupt 205, 215, 366
corrupted, how to fix 75
corruption 75
deleting duplicate index values 317
deleting duplicate rows 419
determining type 1232
distribution page 380
duplicate values 416, 418
finding name from object ID and index ID 94
finding name from page number 93
index ID 215
page 367
page number 215
single clustered index limit 347
unique index and 2601 error 416
unique index and duplicate values 469
Information sources
xxvii
Initialization errors 325, 326
Error 1601 326
Error 1602 327
Error 1603 329
Error 1605 330
Index
1251
Error 1608 333
Error 1613 334
Error 1621 335
Error 1622 336
Error 1623 337
insert
and 1203 error 306
and 2620 error 421
Insert errors
2626 error 422
Error 2601 416
Error 2610 416
Error 2615 418
Error 2619 419
Error 2620 420
Error 2628 424
insert errors 416
installmaster
and 2812 error 434
and permissions error 435
executing 35
installmodel
executing 35
Interfaces file
and 1602 error 328
and 1605 error 330
and 7220 error 569
and 7221 error 572
and kernel message 667
isql
-J flag 654
J
Join operation limits 227
K
Kernel errors 651
basis_daioconfig 651
buffer mismatch 653
character set 654
could not create shared memory 655
current process infected with %d 655
dopen 657
dstart I/O request repeatedly delayed 659
failed to open device 663
file already in use 664
memory too fragmented 665
memory usage in procedure headers 666
network information 667
no more alarms available 668
open objects parameter may be too low 669
os_attach_region 670
os_create_region 671
read-write error 673
server is unnamed 674
stack guardword 675
t_rcvconnect 678
udunmirror errors 678
ueoffline 680
Kernel message
device full 512
stack guardword and 3626 error 471
L
lct_admin
and 17716 error 640
and 7406 error 584
and 7408 error 586
Leaf page 367
Limit
and or or expressions 178
on joins 227
on search conditions 227
load database
and 631 error 212
load database
and 3105 error 440
and 3225 error 447
and 3240 error 449
and 4322 error 503
failure 272
when sort orders differ 441
Loading a database
after corruption 207
Lock
on an object 308
Index
1252
Lock Manager errors 304, 306
Error 1203 306
Error 1204 306
Error 1205 308
Error 1243 310
Error 1249 311
Error 1265 312
Error 1279 313
lock promotion hwm configuration parameter.
See sp_configure
lock promotion lwm configuration parameter.
See sp_configure
lock promotion pct configuration parameter.
See sp_configure
Locks
and 1265 error 312
and 1510 error 321
and holdlock 309
running out of 307
running out of locks and Error 1510 322
Log
and data mapping 397
full 282
suicide 51, 56
Log on data 397
Log Transfer errors
Error 9122 628
Log version
and 3445 error 462
Logical page 235
Logical page number
in Adaptive Server error messages 93
Logical Volume Manager 245
Login request
rejected, 4002 error 488
Logins
reestablishing 37
Long-running transactions
causes of 109
detecting and clearing 109
LTM
and 834 error 247
LVM 245
M
Mail address
tsg@sybase.com xxv
Maintenance Token 95
master database
and 1809 error 343
and 4322 error 503
corrupt 4, 7
error when extending 513
loading from backup 36
putting in single-user mode 33
rebuilding 27
restoring system catalogs 36
returning to multi-user mode 34
Master device
building new 25
going bad 16
restoring lost device 8
restoring with valid dump 8
restoring without valid dump 12
master..sysmessages 135
Maximum
bytes per index 348
clustered indexes on a table 347
columns in a table 339
Memory
and lock scheme conversion 511
insufficient for login 231
maximum amount 229
too fragmented 665
Memory Manager errors 216, 225
Error 701 225
Error 702 227
Error 703 229
Error 706 230
Error 707 231
Error 709 231
Memory too fragmented error 665
min online engines configuration parameter.
See sp_configure
Minimally logged operation
and dumping to transaction log 171
Mirroring
using to move a Sybase device 100
model database
altering 39
Index
1253
how to check size 341, 344
installing 35
lost or corrupted 13
rebuilding 39
Multiuser mode
returning Adaptive Server to 34
N
Naming conventions 148, 434
Network
1602 error 328
1605 error 330
1608 error 333
1613 error 334
information message 667
No more alarms available error 668
Non-logged operation 507
and 268 error 169
Novell
starting Adaptive Server with trace flags 82
number of devices parameter
altering manually 38
number of locks configuration parameter.
See sp_configure
number of open databases configuration
parameterSee sp_configure
number of open objects configuration parameter.
See sp_configure
number of remote connections
and 7221 error 572
number of remote connections configuration
parameter
See 7207 error
number of remote logins configuration parameter
See 7207 error
number of remote sites
and 7221 error 572
number of sort buffers configuration parameter.
See sp_configure
O
OAM entry 292, 410, 605, 608
OAM page 301
and 1133 error 297
Object
finding name from page number 93
Object Allocation Map
and 1129 error 295
and 1131 error 296
and 1133 error 297
and 1142 error 300
and 1143 error 304
and 7939 error 603
Object does not exist 148
Object name 148
object_name function 94
Offset table
and 2507 error 362
and 2620 error 421
online database
and 3446 error 464
and 3452 error 465
and 3454 error 466
Online Recovery 49
and Recovery Fault Isolation 51
Open Client errors 525
Error 5701 525
Error 5704 525
Open Database Manager errors 256, 257
Error 903 257
Error 905 258
Error 906 260
Error 911 262
Error 913 263
Error 916 264
Error 921 266
Error 924 267
Error 925 268
Error 926 270
Error 930 272
Error 935 273
Error 940 275
Error 941 276
Error 945 277
Error 950 279
open objects configuration parameter.
See sp_configure
Open objects parameter may be too low error 669
Index
1254
Optimizer problems
getting help with 116, 125
preparing for analysis of 116, 125
or expression limit 178
OS/2
starting Adaptive Server with trace flags in 83
os_attach_region error 670
os_create_region errors 671
P
Page
chain 359, 373, 386
distribution 380
incorrect free byte offset 413
linkage error 359
not found 381
offset table inconsistencies 421
See Also Allocation 383
Page Manager errors 281
Error 1105 281
Error 1108 289
Error 1120 290
Error 1124 291
Error 1127 292
Error 1129 294
Error 1131 296
Error 1133 297
Error 1141 298
Error 1142 300
Error 1143 304
Parser Errors 142
Error 102 142
Error 107 143
Error 195 145
Parser errors 141, 579
Error 7380 579
Partitioned table
and 1928 error 349
and 4716 error 505
Partitioning a table
and 4953 error 509
Password
incorrect, and 4002 error 488
Permissions
and 229 error 155
Prefetch size
and 7380 error 579
and 855 error 254
Preparing for database recovery 1
probe
and 3429 error 460
Procedure cache
and 701 error 225
shortage 225
sizing 225
procedure cache percent configuration parameter
See and 701 error
See and 709 error
Procedure Manager errors 431
Error 2805 431
Error 2806 432
Error 2811 433
Error 2812 433
Error 2824 436
Error 2835 437
Process
killed, cleanup and Error 6103 546
Process kill errors 546
Error 6103 546
Error 6107 547
Process Status Structure errors 625
Error 8601 625
memory usage error 666
Q
Query plan 225, 229
Query Processor Errors
Error 301 172
Error 546 187
Query Processor errors 171
Error 311 172
Error 313 174
Error 314 176
Error 403 178
Error 404 178
Error 414 179
Error 428 180
Error 511 181
Index
1255
Error 512 181
Error 515 183
Error 530 185
Error 539 185
Error 540 186
Error 547 188
Error 551 190
Error 584 191
Query tree 229
R
Raw partitions
correct use of 97
getting information about 99
Read
Error 822 241
Error 823 244
Rebuilding Adaptive Server 17
Recovery
and 3301 error 450
and 3403 error 455
and 631 error 212
and 906 error 257, 260
errors 205
preparing for database 1
Recovery errors 452, 454
Error 3401 454
Error 3403 455
Error 3404 456
Error 3414 457
Error 3418 458
Error 3425 459
Error 3429 459
Error 3434 461
Error 3445 462
Error 3446 463
Error 3447 464
Error 3452 465
Error 3454 465
Error 3470 467
Recovery Fault Isolation 51
advantages 54
and 12716 error 633
and 12717 error 634
example 56
implementing 55
Recursive calls 676
Remapping all objects in a database 114
remote create errors 631
Error 11203 632
Error 11903 631
Remote Procedure Call
and 7215 error 567
and 7218 error 568
and 7220 error 569
and 7221 error 571
and 7227 error 575
Remote procedure call 667
and 7205 error 561
and 7211 error 563
no site name received error 566
reorg utility
and 11903 error 1173
Reporting errors to Sybase 138
Reproducing problems for Technical Support 141
reserved_pgs 300
Restoring master device 8
with valid dump 8
without valid dump 12
Restoring system catalog information 36
RID.
See Row ID
Row
maximum length 181
Row compare
and 1509 error 319
Row ID 203, 205
rowcnt 300
RPC
can't open connection 575
can't send to site error 567
login to site failed error 571
site not found error 568, 569
RPC errors 610
Error 8006 610
Error 8009 611
Runserver
sample file 33
runserver file
modifying for Digital OpenVMS 81
Index
1256
modifying for UNIX 80
S
sdes 232, 234
Search condition limits 227
Segment
default 395
log 396
mapping 394
system 395
select
and 1203 error 306
select into
and 4207 error 498
select into/bulkcopy
how to activate 170
Sequencer Errors 147
Error 195 159
Error 207 147
Error 208 148
Error 213 150
Error 216 151
Error 225 153
Error 226 154
Error 229 155
Error 232 156
Error 233 157
Error 257 162
Error 259 163
Error 265 165
Error 266 166
Error 268 169
Error 277 171
Sequencer errors 594, 630, 637
Error 11018 630
Error 14200 637
Error 247 160
Error 7783 594
Error 7788 595
Server is unnamed error 674
servername global variable
and 'Server is Unnamed' error 675
servername global variable
and 7214 error 566
Session descriptors 232, 234
and 603 error 193
system 193
user 193
worktable 193
set showplan on 121
set statistics io on 122
set statistics time on 124
Severity levels 135
Shrinking a database 440
shutdown
and 631 error 214
Single-user mode
and 924 error 267
starting Adaptive Server in 33
Site Buffer Manager errors 626
Error 8704 626
Sort failure
and 1510 error 321
Sort Manager Errors 315
Error 1501 315
Error 1505 316
Error 1508 318
Error 1509 319
Error 1510 321
Error 1514 322
Error 1530 323
Error 1531 324
Sort Manager errors 313
Sort order
and 2714 error 426
and dump/load 441
changing 441
sort order
changing manually 58
how to view existing 65
sorted_data
and 1530 error 323
and 1531 error 324
sp_addlogin 38
sp_addmessage 138
sp_addsegment
and 2558 error 399
sp_addserver 674
and 7214 error 566
and 7221 error 572
Index
1257
sp_addthreshold
and 17870 error 641
and 17871 error 642
and 17872 error 643
and 17874 error 643
and 17875 error 644
and 18031 error 646
sp_bindcache
and 861 error 255
sp_cacheconfig
and 5868 error 543
sp_configure
stack size configuration parameter 472
sp_configure
and 1510 error 322
and 18123 error 648
and 2812 error 434
and 5847 error 530
and 5849 error 532
and 5850 error 532
and 5851 error 534
and 5852 error 535
and 5853 error 535
and 5854 error 536
and 5859 error 538
and 5861 error 539
and 5863 error 540
and 5866 error 542
current number online engines configuration
parameter 541
devices parameter, altering manually 38
lock promotion hwm configuration parameter
619
lock promotion lwm configuration parameter
619
lock promotion pct configuration parameter 619
min online engines configuration parameter 541
number of locks configuration parameter 307
number of open databases configuration
parameter 258
number of open objects configuration parameter
153, 616
number of sort buffers configuration parameter
316
number of user connections configuration
parameter 326
running out of locks 307
total memory configuration parameter 226, 539
sp_dboption
and 226 error 155
and 268 error 169
and 2762 error 429
and 4207 error 498
and 4806 error 507
and 924 error 268
and dbo 169
enabling select into/bulkcopy 170
sp_diskblock (user must add) 674
sp_diskdefault
and 1808 error 342
sp_dropsegment
and 2550 error 393
and 2558 error 399
sp_dropthreshold
and 17871 error 642
and 17875 error 644
and 17903 error 644
and 17904 error 645
and 17905 error 645
and 18031 error 646
sp_extendsegment 59
and 2558 error 399
sp_help 121
and 268 error 169
and 2812 error 434
sp_helpdb
and sysusages 399
sp_helplog
checking log location 502
sp_helpserver
checking Adaptive Server status 667
sp_helpsort
and 268 error 169
sp_helpthreshold
and 17910 error 646
sp_logdevice
and 2558 error 399
and 4222 error 501
sp_modifythreshold
and 17870 error 641
and 17871 error 642
and 17872 error 643
Index
1258
and 17874 error 643
and 17875 error 644
and 17904 error 645
and 18031 error 646
and 18032 error 647
and 7403 error 582
sp_placeobject
and 17737 error 641
sp_poolconfig 542
and 18145 error 649
and 852 error 253
sp_procqmode
and 18097 error 648
sp_volchanged
and 3216 error 446
sp_who
and 924 error 267
output 95
Stack guardword 471
Stack guardword error 675
Stack size 472
and stack guardword error 676
stack size configuration parameter.
See sp_configure
Stored procedures
and 913 error 263
compilation 229
creating system procedures 434
maintenance 230
query plan 225, 229
query tree 229
resolution 229
Style conventions xxvii
Sun systems
asynchronous I/O 244, 521
Suspect database 266, 270
and 3414 error 457, 459
and 624 error 207
and 822 error 242
and 840 error 249
and dbcc dbrepair 404
how to reload 84
resetting suspect status 242, 249, 302
Suspect status
marking a database with 103
resetting a database's 105
SYB_BACKUP
manually setting 40
sybinit
and 3452 error 465
and 3454 error 466
Syntax
dbcc checkalloc with fix option 92
style conventions xxvi, xxvii
sysalternates
and 916 error 264
sysaudits
and 7618 error 592
syscharsets
and 2409 error 355
and 605 error 196
syscolumns
and 2514 error 369
sysconfigures
and 5859 error 538
sysconstraints
and 3703 error 475
sysdatabases
and 1813 error 345
and 2520 error 372
and 3418 error 458
and 911 error 262
and 913 error 263
sysindexes
and 1133 error 297
and 691 error 217
and 903 error 257
and 906 error 260
and allocation Error 2525 379
sysindexes
and 8402 error 621
sysindexes Manager errors 621
Error 8402 621
Error 8419 622
syslogins
and 4002 error 488
syslogs
and 1105 error 282
and 3301 error 450
and 3403 error 455
and 4216 error 499
sysobjects
Index
1259
and 2501 error 357
and 2517 error 371
and 3703 error 475
and 906 error 260
finding system tables with ID value 164
sysprocedures
and 2517 error 371
and 2806 error 432
and 2811 error 433
and 2835 error 437
sysreferences
and 3703 error 475
sysremotelogins
and 4002 error 488
sysservers
and 7214 error 566
and 7218 error 568
and 7220 error 569
System Administrator 135
System catalogs
restoring information in 36
System memory 225
System procedure errors 639
Error 17461 639
Error 17715 640
Error 17716 640
Error 17737 641
Error 17870 641
Error 17871 642
Error 17872 642
Error 17873 643
Error 17874 643
Error 17875 644
Error 17903 644
Error 17904 645
Error 17905 645
Error 17906 645
Error 17910 646
Error 18031 646
Error 18032 647
Error 18033 647
Error 18097 648
Error 18123 648
Error 18145 649
Error 18750 649
System table 367
errors 366
syscolumns 369
sysmessages 135
sysusages 398
systhresholds
and 17870 error 641
and 17903 error 644
and 17910 error 646
and 601 error 192
and 7404 error 583
and 7407 error 585
systypes
and 2514 error 369
sysusages 398
and 2550 error 393
sysusers
and 916 error 264
T
t_rcvconnect error 678
Table
column limit 339
column name rules 339
corrupt error 369
corrupted, how to fix 126
corrupted, rescuing data from 78
finding name from page number 93
master..sysmessages 135
Table corrupt error
2503 error 359
2525 error 378
2540 error 382
2546 error 386
Technical Support
reproducing problems 141
tempdb
altering 39
and 216 error 153
and 806 error 236
and select into/ bulkcopy option 169, 430
and select into/bulkcopy option 430
device lost 14
log full 284
rebuilding 39
Index
1260
reducing the size of 111, 114
Temporary tables
and 208 error 148
and 2714 error 426
Test cases 141
Text Manager errors 552
Error 7101 552
Error 7105 553
Error 7114 555
Error 7130 556
Error 7134 558
Threshold errors 580
Error 7401 580
Error 7402 581
Error 7403 582
Error 7404 583
Error 7406 584
Error 7407 585
Error 7408 586
Error 7409 586
Error 7410 587
Error 7411 588
Error 7412 589
Error 7413 589
Error 7414 590
Error 7415 591
Time out
process times out 667
Timestamp
and 4305 error 502
Timestamp errors 548
Error 6901 548
Error 6902 549
total memory configuration parameter
and 701 error 226
and 709 error 232
Trace flag
302 125
310 125
3601 141
3604 93
Trace flags
how to start Adaptive Server with 80
using in Novell 82
using in NT 83
using in OS/2 83
Transaction
long transactions and deadlocks 309
Transaction Coordinator errors
Error 5602 524
Transaction errors 479
Error 3904 479
Error 3905 480
Error 3906 481
Error 3908 483
Error 3917 484
Transaction log
and 3301 error 450
and 3403 error 455
Transactions, long-running
causes of 109
detecting and clearing 109
Transact-SQL
syntax conventions xxvi, xxvii
Transient 605 195
truncate table errors 505
Error 4716 505
tsg@sybase.com mail address xxv
Two-phase commit
and 3429 error 460
Type ID mismatch problems 369
U
udstartio 242
udunmirror errors 678, 679
ueoffline error 680
unique
and create index 317
UNIX
asynch I/O and 5115 error 521
Unpartitioning a table
and 4954 error 509
update
and 1203 error 306
used_pgs 300
User connections
327
and 1605 error 330
and 701 error 226
running out of 326
Index
1261
usertype problems 369
V
Variables in error messages 135
vdevno 38
Virtual device number 38, 520, 522
Virtual disk number 673
Virtual page 235
Virtual sockets
and 1605 error 330
W
where clause limitations 178
Windows NT
starting Adaptive Server with trace flags in 83
Write
Error 822 241
writetext
and 268 error 169
and 7130 error 556
X
XP Server 73
Index
1262

Navigation menu