volume 3: sybase adaptive server™ enterprise ...dis.unal.edu.co/~icasta/man_sybase/svrtsg3.pdf ·...

Volume 3: Sybase® Adaptive Server™Enterprise Troubleshooting and ErrorMessages Guide

Document ID: 39994-01-1192-01Last Revised: January 1999Copyright © 1989-1999 by Sybase, Inc. All rights reserved.

This publication pertains to Sybase database management software and to any subsequent release until otherwiseindicated in new editions or technical notes. Information in this document is subject to change without notice. Thesoftware described herein is furnished under a license agreement, and it may be used or copied only in accordancewith 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 faxnumber. All other international customers should contact their Sybase subsidiary or local distributor. Upgradesare 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, withoutthe prior written permission of Sybase, Inc.

Sybase, the Sybase logo, PowerBuilder, Powersoft, Replication Server, S-Designor, SQL Advantage, SQL Debug,SQL SMART, Transact-SQL, VisualWriter are registered trademarks of Sybase, Inc. Adaptable WindowingEnvironment, Adaptive Server, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, AnswerBase,Application Manager, AppModeler, Backup Server, Client-Library, Client Services, CodeBank, Connection Manager,DataArchitect, Database Analyzer, DataExpress, Data Pipeline, DataWindow, DB-Library, Designor, DevelopersWorkbench, Dimensions Anywhere, Dimensions Enterprise, Dimensions Server, DirectCONNECT, Easy SQR,Embedded SQL, EMS, Enterprise CONNECT, Enterprise Manager, Enterprise SQL Server Manager, Enterprise WorkArchitecture, Enterprise Work Designer, Enterprise Work Modeler, EWA, Gateway Manager, GeoPoint, InfoMaker,InformationCONNECT, InternetBuilder, iScript, KnowledgeBase, MainframeCONNECT, Maintenance Express, MAP,MetaWorks, MethodSet, Movedb, MySupport, Navigation Server Manager, Net-Gateway, NetImpact, Net-Library,ObjectCONNECT, ObjectCycle, OmniCONNECT, OmniSQL Access Module, OmniSQL Server, OmniSQL Toolkit,Open Client, Open ClientCONNECT, Open Client/Server, Open Client/Server Interfaces, Open Gateway, OpenServer, Open ServerCONNECT, Open Solutions, Optima++, PB-Gen, PC DB-Net, PC Net Library, PowerBuilt,PowerBuilt with PowerBuilder, PowerScript, PowerSocket, Powersoft Portfolio, PowerWare Desktop, PowerWareEnterprise, ProcessAnalyst, Replication Agent, Replication Driver, Replication Server Manager, Resource Manager,RW-Library, SAFE, SDF, Secure SQL Server, Security Guardian, SKILS, smart.partners, smart.parts, smart.script, SQLAnywhere, SQL Central, SQL Code Checker, SQL Edit, SQL Edit/TPU, SQL Remote, SQL Server, SQL Server/CFT,SQL Server/DBM, SQL Server Manager, SQL Server SNMP SubAgent, SQL Station, SQL Toolset, StarDesignor,Sybase Client/Server Interfaces, Sybase Development Framework, Sybase Dimensions, Sybase Gateways, SybaseIQ, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase User Workbench,SybaseWare, SyBooks, System 10, System 11, SystemTools, Visual Components, VisualSpeller, Warehouse WORKS,Watcom, Watcom SQL, Watcom SQL Server, web.sql, WebSights, WebViewer, WorkGroup SQL Server, XA-Library,XA-Server, and XP Server are trademarks of Sybase, Inc. 1/99

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 respectivecompanies.

Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) ofDFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.

Sybase, Inc., 6475 Christie Avenue, Emeryville, CA 94608.

Table of Contents

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985

Chapter 4: Backup Server Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987

Commonly Encountered Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987“No language handler installed” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987LOGCONN Errors in Adaptive Server After Using Backup Server. . . . . 988load {database | transaction} with listonly Locks Database . . . . . . . . . . . . . . . . . 988Some Messages from Backup Server Are Lost . . . . . . . . . . . . . . . . . . . . . . . . 988dump database on Digital OpenVMS Alpha/Digital UNIX Raises Error . 989Error 5704 in the OpenVMS Backup Server error log . . . . . . . . . . . . . . . . . . 989Unable to use Async IO when dumping to disk on HP-UX . . . . . . . . . . . . 990Maximum Number of DBPROCESSes Already Allocated . . . . . . . . . . . . . 991

Error Conditions Without Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991

Errors in Backup Server Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992Net-Library routine net_dict_open failed in srv__open_dictionary . . . . . . . . 992Net-Library routine net_listen failed in srv_start_net . . . . . . . . . . . . . . . . . . . 992Net-Library routine net_init failed in srv__init_net . . . . . . . . . . . . . . . . . . . . 993No driver of the requested protocol class is available . . . . . . . . . . . . . . . . . 993Net-lib protocol driver call to connect two endpoints failed . . . . . . . . . . . 993

Open Server Error Messages Related to Backup Server . . . . . . . . . . . . . . . . . . . . . . . . . 993Error 5704.10.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993Error 16240.20.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994

A Listing of All Backup Server Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994Error Number Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994List of Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996

Backup Server Error Messages 1.1.2 — 1.63.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997

Backup Server Error Messages 2.1.2 — 3.55.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008


Backup Server Error Messages 4.76.3 — 4.147.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030



979

Table of Contents

Chapter 5: Component Integration Services Error Messages . . . . . . . . . . . . . . . . . . . . 1057

Component Integration Services Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058

Chapter 6: Adaptive Server Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069

Working with Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069

Server Error Messages 1 - 199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071

Server Error Messages 200 - 299 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085








Server Error Messages 1100-1199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168








Server Error Messages 2000–2099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229










Server Error Messages 3000 — 3099 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281

980

Table of Contents









Server Error Messages 3900 – 3999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
























981

Table of Contents
























Server Error Messages 10100 — 10199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584









982

Table of Contents





















983

Table of Contents

984

About This Book

The Sybase Adaptive Server Troubleshooting and Error Messages Guide isa three-volume set. The first volume contains guidelines for systemdatabase recovery and other troubleshooting procedures. The secondvolume contains detailed error message descriptions. This third volumeincludes 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, relateddocuments, other sources of information, conventions used in this manual,and help, please refer to “About This Book” in Volume 1.

985

About This Book

986

Chapter 4

Backup Server Error Messages

This chapter discusses Backup Server errors and Open Server errors relatedto 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 ErrorsFollowing are descriptions of some problems that commonly occur whenyou use Backup Server.

“No language handler installed” MessageIf you connect directly to the Backup Server with isql and attempt to issue acommand, you will get messages like the following:

1> dump database master to tapedump12> go

No language handler installed.Language cmd: dump database master to tapedump1

This is expected behavior because Backup Server is not a stand-aloneAdaptive Server. It is an Open Server application, is not intended toaccept direct commands, and, therefore, has no way of parsing them. Allcommands to the Backup Server, such as shutdown or dump and load, can beissued only from a running Adaptive Server.

987

Chapter 4 Backup Server Error Messages

LOGCONN Errors in Adaptive Server After Using BackupServerThe Adaptive Server site handler reports this error when the server hasunexpectedly lost contact with another site. If the other site is a BackupServer, then a dump or load session has prematurely completed. This errormessage 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 abortedby a user interrupt (such as Ctrl-c), the message should be treated as aninformational message.

This error can also be reported if the Adaptive Server unexpectedlyloses contact with the Backup Server. In this case, the error should beinvestigated.

load {database | transaction} with listonly LocksDatabaseA 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 withlistonly. To work around load with listonly locking an active database, create adummy database and do the load with listonly into that database instead ofthe database you do not want to have locked.

Some Messages from Backup Server Are LostMessages initiated by a threshold procedure may be lost if the bootwindow is not present. Adaptive Server has no mechanism for interceptinga Tabular Data Stream (TDS) received from other servers; the TDS ismerely passed on to the client. Threshold procedures have no “client,” somessages from Backup Server to these tasks will not appear unless youspecify otherwise.

You must specify notify=operator_console if the dump is invoked by a storedprocedure, including sp_thresholdaction; this is an issue for volume changeprompts, for example, to which you cannot respond if you never see them.

988

Commonly Encountered Errors

dump database on Digital OpenVMS Alpha/Digital UNIXRaises ErrorAttempting to use dump database when your database devices are on rawpartitions (DEC HSC [mscp] devices) raises the following error:

Backup Server: 4.80.2.1: Server, device /dev/44a0e: Youmust 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 devicedriver that causes Backup Server to fail to identify the HSC device type.Digitals's CLD #00266 states that such devices return 0 when queriedwith “MTIOCGET ioctl.”

WARNING! Sybase currently supports only SCSI devices on Digital UNIX.

Error 5704 in the OpenVMS Backup Server error logError 5704: "Changed client character set setting to '%.*s'” appears in theSystem 11 Backup Server error log on OpenVMS, even when the charactersets and language of the Backup Server and the Adaptive Server appearthe same. The errors are written every time a dump or load command isissued. Logging in to the Backup Server and immediately exiting generatesthis 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 AdaptiveServer appear to be identical, they are not so to the backupserver.exeprogram. OpenVMS DCL Command Language Interpreter converts

989


command string tokens, except the strings enclosed in double quotes, touppercase before returning the parsed commands to the calling programs.

Consequently, to log into the Adaptive Server you must specify your username in quotes as in the following command:

isql/ user_name ="sa".

Similarly, the strings 'us_english' and 'iso_1' seen above in single quotesare converted to uppercase. This causes backupserver.exe to interpret thesestrings 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 thetwo strings in double quotes as follows:

/LANGUAGE="us_english" -/CHARACTER_SET="iso_1"

Unable to use Async IO when dumping to disk on HP-UXWhen trying to dump a database to disk on HP the following error occurs:

Backup Server 4.86.2.1: Unable to use Async IO onthe database device 'disk device specified'.

Backup Server must use Async IO on a block special devicesbecause SQL Server is doing the same. Refer to the serverrelease 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 occursbecause of a problem in locking shared memory.

Adaptive Server, when using Async IO on HP, needs to lock its sharedmemory into physical memory so that processing an Async IO requestwill never have to wait for memory areas to be moved from swapspaceto 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 physicalmemory left for the Backup Server.

990

Error Conditions Without Messages

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.

• Change the HP-UX kernel parameter UNLOCKABLE_MEM. By default,this is 0 which signifies the aforementioned 75% - 25% ratio. ConsultHP technical support before changing this parameter.

Maximum Number of DBPROCESSes Already AllocatedTwo scenarios could result in this error. They are summarized in thefollowing table:

Scenario Action

The Backup Server runserver file, theinterfaces file, and the sysservers table in themaster database do not have a consistentname for the Backup Server.

Verify that all three locations containthe same Backup Server name. Payattention to case sensitivity.

You have hit a network limit for theBackup Server process. Typically, thislimit is set to 25.

Start Backup Server with the -Nnn flag tochange the network limit. For example,-N30 increases the limit to 30.

Error Conditions Without MessagesA programming error may occur that causes the Backup Server to hangwithout issuing a message. Follow these steps:

• Determine whether the entire Adaptive Server is hung or just a singlesession.

• Terminate the hung session with keyboard interrupt or quit.

At this point, on a UNIX machine, it is necessary to check for I/Osubprocesses that remain alive, holding open dump devices. Performthis check with the ps command and use kill (default signal) to kill thesybmultbuf processes whose command lines contain device names usedby the terminated session. Be careful to kill only those processes thatuse the devices involved.

Each device is controlled by a pair of processes, and each pair of processescontrols just one device. Therefore, the presence of a device name in a

991


command line is sufficient to identify the subprocess to kill. dump and loaddata from an aborted session or Server are not usable.

The Backup Server can exit abnormally without killing its subprocesses. Inthis case, use kill to clean up the sybmultbuf processes before restarting theBackup Server; otherwise, the devices involved may not be usable.

Errors in Backup Server Error LogThe following error messages may appear in the Backup Server error log.

Net-Library routine net_dict_open failed insrv__open_dictionary

Net-library routine net_dict_open() failed insrv__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 thefile exists and the permissions are set correctly.

Net-Library routine net_listen failed in srv_start_netNet-Library routine net_listen() failed in srv__start_net.Network error: status = 12 - Net-lib protocol driver call toregister 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, justas with Adaptive Server. Check to be sure this privilege is setappropriately.

• If this fails to help, try using DECnet object names instead of objectnumbers. If this works, then report to Sybase Technical Support thatyou have encountered bug 51237.

992

Open Server Error Messages Related to Backup Server

Net-Library routine net_init failed in srv__init_netNet-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 loadingan incompatible Sybase product release into the same $SYBASE directoryas the Backup Server. Be sure the entire release directory is up to date andthat you have not accidentally renamed or deleted localization files.

No driver of the requested protocol class is availableNo driver of the requested protocol class is available.

This message indicates that the entry in the interfaces file for the requestedBackup Server is wrong. Refer to the System Administration GuideSupplement for your platform to find out the correct interfaces file entries.

Net-lib protocol driver call to connect two endpointsfailed

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 theAdaptive Server's network address is correct in the interfaces file.

Open Server Error Messages Related to Backup ServerFollowing are some Open Server error messages that can appear when youare using Backup Server.

Error 5704.10.0Open Server Error: 5704.10.0: Changed client character setsetting to 'cp850'Open Server Session Fatal Error: 16227.15.0: Unknown token TDS streamreceived by spid 5

This message can appear if a user, who succeeds in executing a local dumpdatabase, tries to dump to a remote Backup Server.

993


Check your default character set. If the default character sets for the remoteBackup Server and Adaptive Server are different, change the BackupServer's default character set, restart the Backup Server, and rerun the dump.

Error 16240.20.0Many error conditions are associated with this Open Server error,differentiated by the accompanying messages. The following errors beginwith the phrase “Open Server Fatal Error 16240.20.0”:

Net-Library routine net_address_get() failed in srv__start_netNetwork error: status = 12 - Specifiedserver name attribute could not be foundBackup 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 interfacesfile.” The Backup Server will not start. Check to be sure the name of theserver you are trying to start is in the interfaces file, and remember thatserver names are case-sensitive.

SYB_BACKUP is the logical name of the Backup Server. It may also be thephysical name, but it need not be.

Under normal circumstances, sybinit sets up the Backup Server, but if yourBackup Server name has been edited or deleted from the interfaces file, addit again with sp_addserver, as follows:

1> sp_addserver SYB_BACKUP, NULL, physical-name2> go

The specified physical-name is the name to use, both in the interfaces file andwhen you do a dump or load with the at option.

A Listing of All Backup Server Error MessagesThis section lists the text and gives a brief explanation for Backup Servererrors.

Error Number FormatA Backup Server error number has four components:

994

A Listing of All Backup Server Error Messages

major.minor.severity.state

major numbers map to functional areas as follows:

MajorNumber

Description

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

minor numbers order the errors within a major category. There is no specialmeaning to these numbers; they serve only to distinguish between errors.

severity codes are as follows:

Severity Code Description

0 Internal informational message, usually a component ofanother 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 allof usage, environment, or internal logic.

This severity consists of two levels, which indicate whetheror not the session must exit. 2 indicates the session mustexit. 3 indicates the session may or may not exit.

4 An unexpected condition, fatal to the executionof the Backup Server, has occurred. The sessionmust exit immediately.

state codes have a one-to-one mapping to instances of the error reportedwithin the code.

995


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 Serverand Backup Server can run without being swapped.

996

Backup Server Error Messages 1.1.2 — 1.63.2

Backup Server Error Messages 1.1.2 — 1.63.2Number Severity Text and Explanation

1.1.2 2Memory allocation failed in %1! for a %2!allocation. This DUMP or LOAD session must exit.

Explanation: Indicates shortage of virtual memory on the machinerunning Backup Server. User should terminate unnecessary processes.

1.2.0 0WAIT

Explanation: This informational text may be a component of anothermessage. No action is necessary.

1.3.0 0NOWAIT


1.4.0 0PROCEED


1.5.4 4Failed to install CS-Library message callbackroutine.

Explanation: Backup Server's attempt to install an event handler failed.Backup Server cannot run.

1.6.0 0RETRY


1.7.1 1Cannot allocate the locale info of the task. Usethe Backup Server default language % ` 1!' instead.

Explanation: The local structure for the client connection to BackupServer could not be allocated, and the thread property for the local

information could not be captured. Refer to the Backup Server errorlog for more information.

1.8.0 0ABORT

Explanation: This informational text may be a component of another

message. No action is necessary.

997


Number Severity Text and Explanation

1.9.0 0Backup Server


1.10.0 0DUMP


1.11.0 0LOAD

Explanation: This informational text may be a component of another

message. No action is necessary.

1.12.0 0volume


1.13.0 0OPERATOR


1.14.2 2Unrecoverable I/O or volume error. This DUMP orLOAD session must exit.

Explanation: This message is usually preceded by a more specificmessage describing a fault encountered in the lower I/O layers. One

exception: this message is the only error indication when the BackupServer fails to start the multi-buffering subprocess that it uses to performbackup I/O.Reasons for this failure are the non-existence of the sybmultbuf

program in the standard locations (-M option argument, Backup Server'scurrent 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 4UNRECOVERABLE CONDITION: ALL SESSIONS WILL TERMINATEABNORMALLY. THE BACKUP SERVER MUST EXIT.

Explanation: This message is preceded by other messages describing

the failure.

998



1.16.2 2Error (major = %1!, minor = %2!) raised withunknown severity %3!.n

Explanation: Indicates a programming bug in an instance of errorreporting.

1.17.2 2Major = %1!, Minor = %2!, Severity = %3!, state =%4!: error text is missing.

Explanation: Indicates that localization files are out-of-date with thecode. Check installation with Sybase Technical Support.

1.18.1 1WARNING: Requested %1! file descriptors, wasallocated %2!; Backup Server will run out of filedescriptors if this number is less than the numberof database devices plus twice the number of stripesin concurrent use.

Explanation: The Backup Server attempts to obtain the highest number

of file descriptors allowed to a user program. This message indicatesthat the Backup Server found a lower quota. Concurrent activity mustbe restricted as directed or the platform administrator can increase theHDESLIM.

1.19.4 4Cannot allocate the configuration structure

Explanation: Indicates either a basic Open Server failure or an extremeshortage of memory and swap space.

1.20.4 4CS_CONTEXT allocation failed.

Explanation: The context allocation routine failed when it tried to load

localization files. The SYBASE environment variable is set incorrectly orthe localization files are missing.

1.21.2 2Unable to configure the maximum number of userevents to %1!.

Explanation: An error occurred when you tried to configure the OpenServer's run-time maximum number of application-specific definedevent types. Refer to the Open Server Server-Library Reference Manual foran explanation of events. Refer to the Backup Server error log for moreinformation, and contact Sybase Technical Support.

999



1.22.2 2Unable to configure the maximum number of SRV_PROCSto %1!.

Explanation: An attempt to configure the Open Server run-time valuesto allow the specified number of Server threads failed. Backup Server

uses one thread per dump or load connection plus an additional threadfor each stripe. Use the -P option to increase the number of threads.

1.23.2 2Unable to configure the maximum number of networkread buffers to %1!.

Explanation: An attempt to configure the Open Server run-time valuesto allow the specified number of network read buffers failed. Thesebuffers are used for Server to Server connections, and the configurationvalue is hard coded to 10.

1.24.2 2Unable to configure the maximum number ofconnections to %1!.

Explanation: Attempt to configure the Open Server run-time values to

allow the specified number of network connections failed. The valueof the -C option (/connections in Digital OpenVMS) to the backupserver

command is used for the configurable value. Check the line in yourRUN_servername file and see the entry for backupserver in Adaptive Server

Utility Programs for your platform.

1.25.1 1Logging Backup Server messages in file % ` 1!'\n

Explanation: Indicates that Backup Server messages are being writtento the file named.

1.26.1 1Unable to open Backup Server message log file

%` 1!'\n

Explanation: Check the path to the message log file. Make sure that theSYBASE environment variable is set correctly.

1000



1.27.1 1Operating system swap space is low. The operatingsystem 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.

1.28.2 2Open Server routine %1! failed. See Backup Servererror log for additional information. \n

Explanation: Internal error, contact Sybase Technical Support. This isa catch-all message for any Open Server function that raises an errorfor which Backup Server has determined the affected routine but notthe exact error.

1.29.2 2Unable to start the Backup Server. See BackupServer 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 OpenServer messages that are displayed.

1.30.2 2Backup Server encountered error freeing memory.\n

Explanation: Internal error, contact Sybase Technical Support. An erroroccurred when an attempt was made to free a block of memory from

Backup Server's run-time heap. Either the memory was previouslyfreed or there is another error in the Open Server routines for freeingmemory. Check the Backup Server error log for any Open Servermessages pertinent to this problem.

1.31.2 2Unable to configure the maximum number of networkconnections to %1!. The number of networkdump/load stripes that the Backup Server can runsimultaneously is %2!.

Explanation: Attempt to set the maximum number of networkconnections (DBPROCESSes) that the Server can originate failed. Referto the usage of the -N command line option. It may be too large forDB-Library to handle.

1001



1.32.2 2Unexpected failure in c ` s_strcmp()' routine.

Explanation: Internal error, contact Sybase Technical Support. An erroroccurred when comparing two strings to see if they are equal, greaterthan, or less than each other. The cause of the error could be an illegalstring in length or content or that the character sets of the two stringsare incompatible for comparison.

1.33.0 0Backup Server Internal Error

Explanation: This informational text may be a component of anothermessage.

1.34.1 1Unable 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>


1.36.1 1Unable to configure Async IO. If Adaptive Server isusing Async IO on block special devices, then dumpand loads may be inconsistent. Refer to the serverrelease notes.

Explanation: HP only: could not initialize and configure theasynchronous I/O system to be used when accessing database devices.Check the Backup Server error log and contact Sybase TechnicalSupport.

1.37.4 4Could 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 aninternal error.

1002



1.38.4 4Could not get master lock on server name, server%1!: code %2! message %3!.

Explanation: Digital OpenVMS only: an attempt to obtain a lockidentifying this as the “master” Backup Server failed for the reason

specified in %3!. Backup Server cannot start.

1.39.4 4This backup server is unnamed, and so cannot acquirethe master lock it needs to boot successfully.Backup Server must shut down.

Explanation: Digital OpenVMS only: no Server name was given whenattempting 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 logicalname.

1.41.4 4A server named %1! is already running. Could notobtain stop-lock.

Explanation: Digital OpenVMS only: another Backup Server with thesame logical name is already running. This Backup Server cannot start.

1.42.4 4STOP semaphore failed, code %1! message %2!.

Explanation: Digital OpenVMS only: failed to queue the lock requiredto shut down Backup Server via stopserver. Backup Server cannot start.

1.43.4 4Failed getting system information: sys$getsyifailed, code %1! message %2!.

Explanation: An unexpected condition, fatal to the execution of theBackup Server, has occurred. The session must exit immediately.

1.44.1 1Backup Server could not set the server language to

%` 1!'. The specified language may not be a validlanguage, 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 specifiedlanguage may not be a valid language, or the language may not beinstalled under $SYBASE/locales.

1003



1.45.1 1Backup Server could not set the server characterset to % 1!'. The specified character set may notbe a valid character set, or the character set maynot be installed under $SYBASE/locales. The defaultcharacter 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 specifiedcharacter set may not be a valid character set or the character set maynot be installed under $SYBASE.

1.46.1 1CSLIB routine %1! failed. See Backup Server errorlog for additional information.

Explanation: This is the catch-all message for CS-Library (Client/ServerLibrary) functions that return an error. Currently, the only reference to

this error occurs when Backup Server is attempting to configure thelocalization properties of the process. Refer to the Backup Server errorlog for more information. There could be something wrong with thespecified language or character set, for example the specified characterset is not valid for the specified language. Contact Sybase TechnicalSupport if a resolution cannot be determined.

1.47.1 1Backup Server could not set the serverlanguage/character set to % ` 1!/%2!'. Thespecified language/character set combination may notbe valid, or the language/character set combinationmay not be installed under $SYBASE/locales. Thedefault language/character set is in use.

Explanation: Attempt to set the Backup Server's language and characterset failed. Refer to the Backup Server error log for more information.

The specified language or character set may not be valid or the languageor character set may not be installed under $SYBASE/locales.

1.48.2 2Attempt to dispatch Backup Server by Service ControlManager 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 NTspecific message.

1004



1.49.2 2Attempt to register Service Control Handler returnedoperating 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 NTspecific message.

1.50.2 2Attempt to set Control Status returned operatingsystem error = %1!(%2!).


1.51.2 2Service Control Handler received an invalid controlcode = %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 NTspecific message.

1.52.1 1Backup Server terminating because of system shutdown

Explanation: Information, no user action necessary.

1.53.2 2Attempt to create thread returned operating systemerror = %1!(%2!).


1.54.2 2Attempt to connect to registry returned operatingsystem 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.

1005



1.55.2 2Attempt to open registry key returned operatingsystem error = %1!(%2!).


environment, or internal logic. The session must exit. This is an NTspecific message.

1.56.2The SYBASE environment variable must be set.


environment, or internal logic. The session must exit. Follow anyinstructions given.

1.57.2 2Backup Server encountered an error while attemptingto create a message queue. The Open Serverroutine srv_createmsgq failed. This session cannotcontinue.

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 2Error: Unable to disable the % ` 1!' systemregistered procedure.


environment, or internal logic. The session must exit.

1.59.2 2Error: Unable to spawn thread to drop thedisallowed system registered procedures.


1006



1.60.2 2Unable 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 numberof message queues exceed the allowed maximum. Restart the BackupServer with reduced values for these parameters.

1.61.2 2The 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 anyinstructions given.

1.62.2 2Unable to load the Sytos DLL that SYTAPE is set to.


1.63.2 2Unable to configure %1! connections and %2!service threads which requires %3! messages. Themaximum number of messages is %4!.

Explanation: The value of the -C and -P option are such that the numberof message queues exceed the allowed maximum. Restart the BackupServer with reduced values for these parameters.

1007



2.1.2 2Open Server initialization failed. Unable to start%1!.

Explanation: The user should check the installation. This error can alsoarise from memory and swap space shortage.

2.2.4 4Open Server Server Fatal Error: %1!.%2!.%3!: %4!

Explanation: This indicates a fault within the Open Server layer thatforces program exit. The error code placeholder should be matched to

the Open Server error codes for diagnosis. Check installation.

2.3.2 2Open Server Session Fatal Error: %1!.%2!.%3!: %4!

Explanation: Interpret as for 2.2.4, except only the session exits, notthe whole Server.

2.4.2 2Open Server Error: %1!.%2!.%3!: %4!

Explanation: Interpret as for 2.2.4, except Server and session processingcontinue. Example: missing localization file.

2.5.2 2Couldn't define %1! event; Backup Server must exit.


2.6.2 2Login information unavailable.

Explanation: The Backup Server could not access the session logininformation to perform authentication due to unauthorized sessioninitiator or programming bug. Contact Sybase Technical Support.

2.7.2 2Remove server TDS version must be equal to orgreater than 4.6. This session must exit.

Explanation: Connection was attempted with an obsolete TDS version.Backup Server communicates reliably only with System 10 AdaptiveServers and other Backup Servers.

1008



2.8.2 2Couldn't create semaphore for session %1!. Thissession must exit.

Explanation: Indicates Open Server MUTEX initialization failure orsession limit reached.

2.9.4 4The 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 yourRUN_servername file.

2.10.2 2A 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 theline in your RUN_servername file.

2.11.2 2Failed 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 (mutuallyexclusive object) which only one user at a time can lock. Refer to theBackup Server error log for more information.

2.12.2 2The diagnostic option specifier must be an integer.Option is % 1!'


2.13.2 2Unable to get connection endpoint.srv_thread_props() returned an error.


has occurred. Error may have occurred with any or all of usage,environment, or internal logic. The session must exit.

1009



2.14.2 2Unable to determine connection type. fstat()returned an error: %1!



2.15.2 2Connection refused. The owner id of the connectionnamed pipe is not the same user id as that of theBackup Server process.


2.16.2 2Error: unable to disable registered procedures.


2.17.2 2Unrecognized security option % ` 1!'.


2.18.4 4The number of service threads must be a positiveinteger up to the maximum of %1!. Specified valuewas %` 2!'.

Explanation: The value specified for -P option is invalid. Restartbackup server with a valid value.

2.19.2 2Invalid verbosity level: A verbosity levelspecifier must be an integer from 0 to 3.



1010



3.1.2 2Unrecognized RPC received--ignored.

Explanation: The session initiator sent an unrecognized RPC. Indicatesad hoc RPC was sent, or a programming bug in Adaptive Server orBackup Server. Contact Sybase Technical Support.

3.2.2 2Symbol %1! not found in TDS table.

Explanation: Internal message; customers will likely never see it; it isonly included here for completeness.

3.3.2 2%1!: May not specify Backup Server scanning orfree-page clearing for a secondary phase.

Explanation: Internal error, contact Sybase Technical Support. Theseerrors indicate a violation of the dump synchronization protocol of theRPC API.

3.4.2 2%1!: Must specify Backup Server scanning in orderto clear free pages at LOAD time.

Explanation: Internal error, contact Sybase Technical Support. These

errors indicate a violation of the dump synchronization protocol of theRPC 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 onephase may be active at a time.

Explanation: Internal error, contact Sybase Technical Support. Violationof the dump synchronization protocol of the RPC API.

3.7.2 2%1!: phase %2! already concluded.


1011



3.8.2 2%1!: May not begin phase %2! before completingan earlier phase, number %3!, for which there isuncompleted work.


3.9.2 2%1!: May not initiate Backup Server scanning for aphase for which run-lists have been queued.


3.10.2 2%1!: phase %2! not active.


3.11.2 2%1! SANITY: PHASE for phase no. %2! not at headof list.


3.12.2 2May not submit RPC %1! unless performing a DUMP.


3.13.2 2%1!: Illegal phase number %2!.


3.14.2 2Logical page %1! is not in the given database map.


3.15.2 2The disk piece for page %1! does not belong tophase %2!.


1012



3.16.2 2%1!: There is no session of id %2! in progress.


3.17.2 2Pathname parameter must specify an absolutepathname. Rejected value: %1!

Explanation: Adaptive Server sent its present working directory to theBackup Server and that directory was not recognized as an absolutepath specifier.

3.18.2 2Adaptive Server Enterprise did not specify absolutepathname root before sending the relative devicepathname %1!.

Explanation: Adaptive Server sent a device specification that was notrecognized as an absolute path specification, and had not previouslysent its present working directory.

3.19.2 2Combining device pathnames %1! and %2! exceeds themaximum pathname length.

Explanation: The combination of Adaptive Server's present working

directory and the relative device name is too long for Backup Server'sinternal 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 expectedfor that RPC. If you are sending Backup Server the RPC via your owncustomized mechanism, check that mechanism for the correct RPCcount. 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 willexceed the size used to store the run lists internally within BackupServer. If you are sending Backup Server the RPC via your owncustomized mechanism, check that mechanism for the correct size of therun lists. Otherwise, contact Sybase Technical Support.

1013



3.22.2 2%1!: Session %2! does not exist.


3.23.2 2%1!: Could not queue run list for session %2!.


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 whichBackup Server conducts the scan.


3.26.2 2%1! SANITY: parameter data overflows I/O block.

Explanation: Internal error, contact Sybase Technical Support. Errorwith dump header or trailer processing in either Server. The totalparameter sizes are defined to equal the I/O block size.

3.27.2 2Invalid RPC sequence at RPC %1!.

Explanation: Internal error, contact Sybase Technical Support. Error in

the session initiator (Adaptive Server or Backup Server), a violationof the RPC API.

3.28.2 2Non-contiguous database map, session %1!, lpn %2!.

Explanation: Internal error, contact Sybase Technical Support. These

errors indicate an Adaptive Server programming bug, defectivedatabase disk mapping information sent.

3.29.2 2No virtual mapping for logical page %1!.

Explanation: Internal error, contact Sybase Technical Support. Theseerrors indicate an Adaptive Server programming bug, defective

database disk mapping information sent.

1014



3.30.2 2Bs_normdbmap received an overlapping disk piece.

Explanation: Internal error, contact Sybase Technical Support. Theseerrors indicate an Adaptive Server programming bug, defectivedatabase disk mapping information sent.

3.31.2 2Improper parameter count %1! for RPC %2!.

Explanation: Internal error, contact Sybase Technical Support. Error inthe session initiator (Adaptive Server or Backup Server), a violationof the RPC API.

3.32.2 2Incorrect type for parameter #%1! for RPC %2!;expected %3! got %4!.


3.33.2 2SANITY: premature last run list.

Explanation: Internal error, contact Sybase Technical Support.

3.34.2 2SANITY: more stripes than extents.


3.35.2 2RPC %1! refused following previous FAILURE return.



3.36.2 2RPC %1!: parameter %2! may not be NULL.



3.37.2 2SANITY: RPC %1!: expected parameter %2! gotparameter %3!.


1015



3.38.2 2There is no primary phase %1! for secondary phase%2!.


3.39.2 2RPC %1! can only be executed in a slave server.

Explanation: These errors indicate an Adaptive Server programmingerror, violation of the RPC API.

3.40.2 2Illegal length for parameter #%1! for RPC %2!;expected %3! got %4!.



3.41.2 2Illegal max-length for parameter #%1! for RPC %2!;expected %3! got %4!.


3.42.1 1%1! is complete (database %2!).

Explanation: Informational message that Backup Server processing forthe session is complete (the dump or load command may continue torun, for example, to clear the region of the loaded database above thedump-time high page).

3.43.1 1Dump phase number %1! completed.

Explanation: Informational message that a dump synchronizationphase has completed.

3.44.2 2The Backup Server is already performing a deferredshutdown; only one may be active at a time.

Explanation: Shutdown is in progress and will occur when all dumpsand loads have completed.

1016



3.45.1 1Attention received: cancelling deferred shutdown.


3.46.2 2Deferred shutdown wait failed, cancelling deferredshutdown.


3.47.2 2The Backup Server is undergoing shutdown. Yoursession will terminate immediately. Pleasereattempt connection later.

Explanation: This message is issued in response to a dump or loadcommand after a shutdown request has been sent but before the BackupServer has actually shut down.

3.48.1 1The Backup Server will go down immediately.Terminating sessions.

Explanation: This is the final message sent to the session that issued theshutdown command.

3.49.2 2RPC %1! does not allow option %2!.

Explanation: An RPC inconsistency was detected. This could be causedby incompatible releases of Backup Server and Adaptive Server.

3.50.2 2Non-privileged connection is not authorized toexecute privileged RPC % ` 1!'.

Explanation: Some RPCs are “privileged,” that is, they can only occurin the context of an Adaptive Server-initiated dump. Users who attemptto programmatically duplicate one of these RPCs are prevented from

doing so.

3.51.2 2Database device #%1!, name %2! has already beendeclared as #%3!, name %4!.

Explanation: Internal error, contact Sybase Technical Support. Thedump or load command as translated by Adaptive Server does notmake sense. The sysdevices table may be corrupt.

1017



3.52.2 2Database device #%1! has not been declared.

Explanation: Internal error, contact Sybase Technical Support. Thedump or load command as translated by Adaptive Server does notmake sense. The sysdevices table may be corrupt.

3.53.2 2Malformed option list received, RPC: %1!.

Explanation: Internal error, contact Sybase Technical Support. Thedump or load options as passed from Adaptive Server do not makesense. The problem may be possible to work around by rearranging,adding or removing options to the dump or load command.

3.54.1 1Waiting 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 nowaitwas not specified.

3.55.2 2RPC %1!, parameter % 2!': %` 3!' is an invalidvalue.

Explanation: Internal error, contact Sybase Technical Support. AdaptiveServer requested an unknown function.

1018



4.1.2 2Device %1!': volume % ` 2!' appears to contain datawritten in a format that the Backup Server doesnot recognize. Please use a different volume, orinitialize 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 canbe overwritten. Will be followed by an additional operating systemmessage elaborating on the situation.

4.2.3 3Adaptive Server Enterprise sent an overlapping diskpiece.

Explanation: Database is corrupt. Run dbcc diagnostics on yourdatabase and refer to Adaptive Server Error Messages for correctivemeasures.

4.3.2 2Device %1! is not in use by any session on thisserver.

Explanation: Indicates user addressed sp_volchanged execution to an

inactive device. Check parameters.

4.4.2 2Device %1! does not belong to session <%2!>.Notification failed.

Explanation: Indicates a device specified in an sp_volchanged executiondoes not belong to the named session. Check parameters.

4.5.2 2Notification attempt failed--message channel forsession <%1!> is closed.

Explanation: Indicates user addressed sp_volchanged execution to anonexistent session. Check parameters.

4.6.2 2Failed to create or attach shared tape i/o buffers.

Explanation: Indicates unavailability of shared memory on theplatform, possibly caused by memory shortage or kernel configurationlimit reached. Check resource availability. This is probably a BackupServer problem.

1019



4.7.2 2Device %1! already in use.

Explanation: A session attempted to use an archive device owned byanother session. Select a different archive device.

4.8.2 2Mirror 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 2Label validation error: read returned %1! readinglabel. Read:n%2!

Explanation: These errors indicate a mislabeled or illegal-formatarchive volume. User should use offline commands to verify that thetape contains Sybase information. The following commands submittedrepeatedly in order will display the beginning and ending labelcharacters 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 onthe tape.

4.10.2 2Label validation error: first label not VOL1.

Explanation: Same as Error # 4.9.2

4.11.2 2Label validation error: seek to %1!s failed, %2!.


4.12.2 2Label validation error: %1! label not found.


4.13.2 2Device %1!': can't determine how to set density onchannel %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.

1020



4.14.2 2Label validation error: too many header labels.

Explanation: Errors similar to 4.9.2–4.12.2.

4.15.2 2Label validation error: seek to trailer labelsfailed.


4.16.2 2Label validation error: read of tape mark failed.


4.17.2 2The stripes on the specified devices have completed,but more dump stripes exist.

Explanation: This message arises when loading from fewer stripes thanthe number used at dump time. At load time, there must be at least oneinstance of every device type used at dump time.

4.18.2 2Unsupported device type. The stat() system callreturned type '%1!' for '%2!'. Refer to youroperating 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 2Label validation error: too many trailer labels.


4.20.2 2Device %1!': I/O error, write of tape mark failed.


4.21.2 2Device %1!' should be marked l ` ist only', but isnot. Cannot continue this command.


4.22.1 1Option %1! is not valid for device % ` 2!'.

Explanation: Indicates a device option not appropriate for the device

type. Review legal options for device types.

1021



4.23.2 2%1!: read %2!: %3!.

Explanation: Indicates a read or write system call error on a disk orfile device. Investigate possible causes (for example, out-of-spacecondition.) 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 orfile device. Investigate possible causes (for example, out-of-spacecondition.) This error aborts the dump or load.

4.25.2 2Device %1!': %2! is an inappropriate densityvalue for this device.

Explanation: Digital OpenVMS only: the density value specified inthe dump or load command is not valid. Expected values are: nonespecified, 800, 1600, 6250, 6666, 10000, and 38000.

4.26.2 2Volume validation error: failed to obtain deviceinformation, device: %1! error: %2!.

Explanation: Backup Server is unable to sense the type of a givendevice. Verify that the device is of a legal type and that the BackupServer process has operating system permission to access it.

4.27.2 2Volume validation error: attempt to close %1!returned %2!.

Explanation: A UNIX file failed to close. The first parameter is the filename and the second is the UNIX error message that was returned.

4.28.2 2Device %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 2Device %1!': sense mode failed on channel %2!;status = 0x%3!.

Explanation: Digital OpenVMS only: could not sense devicecharacteristics. The “status” line will contain the operating systemerror code.

1022



4.30.2 2Volume validation error: attempt to open %1!returned %2!.

Explanation: Indicates an error opening or closing a database device.

4.31.2 2Device %1!': failed to skip back to beginning oftape 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 2Failed to allocate memory for tape i/o buffer.


environment, or internal logic. The session will exit.

4.33.2 2Header labels of rejected volume:

Explanation: Display of the data Backup Server found where it expectedANSI volume labels. Verify that the proper volume is loaded.

4.34.1 1Device %1!':\nVolume name:'%2!'\n


4.35.1 1Device %1!':\t\nLabelname:\t'%2!'\nVolume id:\t'%3!'\nAccesscode:\t'%4!'\nReserved:\t'%5!'\nOwnerid:\t'%6!'\nReserved:\t'%7!'\nLabelingversion:\t%8!\n


4.36.1 1Device %1!':\t\nFile name:\t'%2!'\nCreate date& time:\t%3!, %4!\nExpiration date & time:\t%5!,%6!\nDatabase name:\t'%7!'\n


1023



4.37.1 1Device '%1!':\t\nLabel id:\t'%2!'\nFilename:\t'%3!'\nStripe count:\t%4!\nDevicetypecount:\t%5!\nArchive volume number:\t%6!\nStripeposition:\t%7!\nGeneration number:\t%8!\nGenerationversion:\t%9!\n


4.38.1 1Device %1!':\nLabel id:\t'%2!'\nRecordformat:\t'%3!'\nMax. bytes/block:\t%4!\nRecordlength:\t%5!\nBackup formatversion:\t%6!\nReserved:\t'%7!'\nDatabasename:\t'%8!'\nBuffer offsetlength:\t%9!\nReserved:\t'%10!'\n


4.39.1 1Device %1!': illegible file date & time found;continuing.

Explanation: This error is raised when Backup Server attempts to listthe 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 1Creating new disk file %1!.

Explanation: This message occurs when attempting to dump to anon-existent disk FNAME.

4.42.2 2Couldn't obtain channel to multibufferingsubprocess, error: %1!

Explanation: An attempt to fork a subprocess failed.

4.43.2 2Couldn't create multibuffering subprocess.

Explanation: Backup Server was unable to complete start-up of themultibuffering subprocess. File descriptors may be exhausted (Error4.42). Retry session when Backup Server activity is lower. Possiblevirtual memory shortage (Error 4.43).

1024



4.45.2 2The maximum number of %1! stripe devices has beenexceeded.

Explanation: A single dump or load session may use a maximum of 32archive stripes. Reduce the number of archive devices in the dump or

load command.

4.46.2 2Length error on I/O -- transferred %1! bytes,expecting to transfer %2! bytes.

Explanation: Digital OpenVMS only: Backup Server requested theoperating system to read or write %2 bytes and only %1 bytes wereactually transferred. Probably device or media failure.

4.50.2 2Device %1!: The blocksize %2! of the dump file isnot 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 2Archive devices % ` 1!' and % 2!' do not belong tothe same file group.

Explanation: Internal error, contact Sybase Technical Support. Thetapes/devices do not belong to the same archive group. To the BackupServer, it appears that “tapes” from two different dumps are mountedin devices requested by the current load.

4.52.2 2There should be %1! load stripes, but the commandonly specifies %2!. One or more required deviceshave been omitted from the command line.

Explanation: Backup Server supports database loads on fewer devicesthan 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 verifiesthat a load command specifies all needed device types. If it does not,this error is raised.

1025



4.53.2 2The 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. BackupServer cannot load from more stripes than were used for the original

dump.

4.54.2 2The 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 theload command

4.55.2 2Device validation error: couldn't open raw device%1!, error: %2!

Explanation: These errors denote failure to obtain hardwarecharacteristics after establishing the device type. Check permissions onthe device special file, investigate the returned operating system errormessage.

4.56.2 2Device validation error: couldn't obtain tape drivecharacteristics for device %1!, error: %2!


4.57.2 2Device validation error: couldn't obtain disk drivecharacteristics for device %1!, error: %2!


4.58.1 1Database %1!: %2! kilobytes %3!ed.

Explanation: This message conveys the progress of the dump or loadsession. %3 is “DUMP” or “LOAD”.

1026



4.59.3 3Archive device %1! must either be a STRIPE orMIRROR.

Explanation: Internal error, contact Sybase Technical Support. Thiserror can occur only if Adaptive Server incorrectly translated a dump

command.

4.60.2 2Archive device %1! does not support a validtapemark.

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 2Archive device %1! does not support %2! operation.


4.62.3 3Multibuffering subprocesses died, archive %1!.

Explanation: This error message may indicate that the Backup Servercannot find the sybmultbuf program. Check $SYBASE/bin to see ifsybmultbuf is there.This can also happen if the Backup Server cannotlocate the sybmultbuf binary because it has received an incorrectparameter.The correct use of the -M flag is: $SYBASE/bin/backupserver-M$SYBASE/bin/sybmultbuf A third possibility is that the BackupServer has had trouble forking the sybmultbuf process. Check theBackup 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.

1027



4.63.2 2End-of-volume reading labels, archive %1!.

Explanation: Backup Server encountered a tape file mark whenattempting to read the ANSI labels. Indicates validation attempt on ablank tape (not an error), a non-ANSI tape or programming error. Thetape volume should be examined off line with the commands givenabove. If the volume was the final volume of the load and the I/O hasproceeded 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 3SANITY: Scheduled ACK events exceed stripe count.


4.67.2 2Device %1!: This tape device requires the CAPACITYoption.

Explanation: Backup Server does not know how to detect end-of-tapeon this device. Therefore capacity must be specified on dump, or youmust specify the device as a logical device name from sysdevices.

4.68.2 2Write data to a network device (slave site: %1!,device: %2!) failed.

Explanation: This messages are self-explanatory. Further details willappear in a 4.82.2 message, which will immediately follow this message.

4.69.2 2Read data from the network device (slave site: %1!,device: %2!) failed.


4.70.2 2Device %1!: Unable to query ODM database for deviceattributes. ODM error code = %2!.

Explanation: RS6000 only: Since Backup Server has failed to determinedevice characteristics, it cannot ensure that the device is configured forextended file marks.

1028



4.71.2 2Device %1!: Is not configured for extended filemarks.

Explanation: RS6000 only: Multi-file devices must be reconfigured withextended tape marks. This is so that tape marks can be overwritten

on multi-file dumps.

4.72.2 2Write data to the archive device % ` 1!' failed. I/Oerror: %2!


4.73.2 2Read data from the archive device % ` 1!' failed.I/O error: %2!


4.74.2 2Unable 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 isworld-writable, has sufficient space, and contains no unused files ofthe form BS_servername.number.

4.75.3 3Device %1!: %2! is not a legal virtual disknumber.

Explanation: Internal error, contact Sybase Technical Support. BackupServer cannot determine what portions of the specified database deviceshould be backed up because information about the device sent fromAdaptive Server does not correspond with the actual physical device.

1029



4.76.3 3Device %1!: %2! is not a legal virtual blocknumber.

Explanation: Internal error, contact Sybase Technical Support. BackupServer cannot determine what portions of the specified database deviceshould be backed up because information about the device sent fromAdaptive Server does not correspond with the actual physical device.

4.77.2 2Device %1! may not be used: minimum blocksize forI/O exceeds device maxiumum of %2!.

Explanation: Backup Server requires tape devices to support an I/Osize of at least 2K. The tape device found has a maximum I/O size lessthan 2K. This message should never appear. If it does, user should checkdevice name specification. If correct, user must use another device.

4.78.2 2Option %1!: illegal value %2!.

Explanation: This indicates the user has supplied an illegal value for adevice option. Review the device options and legal values.

4.79.2 2Server %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 sizethat exceeds the available buffer size.

4.80.2 2Server %1!, device %2!: You must use theno-rewind-on-close tape device.

Explanation: Backup Server requires all tape devices to use theno-rewind-on-close option, so that it can fully control tape positioning.

4.81.2 2Server %1!: device %2! is open for writing; youmay not specify the @fname parameter when changingvolumes.

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.

1030



4.82.2 2Operating system error, server %1! device %2!:code %3! message %4!.

Explanation: This message appears when a system call (perhapsperformed as part of a higher-level operation) has failed. It is intended

primarily for diagnostic use and should be interpreted in the context ofimmediately preceding messages.

4.83.2 2Device %1!: The specified blocksize %2! is notwithin the range of %3! to %4!.

Explanation: The user-specified block size is out of range. Respecifyblock size within the listed limits.

4.84.1 1Device %1!: The specified blocksize of %2! will betruncated to %3! which is a multiple of %4!.

Explanation: The user-specified block size was truncated to be amultiple of 2048.

4.85.1 1Device %1!: Disk model %2! does not exist in the/etc/disktab file. Using default values for thisdevice.

Explanation: The disk device is not configured in /etc/disktab, so adefault disk block size will be used.

4.86.2 2Unable to initialize Async IO on the database device%1!. Backup Server must use Async IO on a blockspecial devices because Adaptive Server Enterpriseis doing the same.

Explanation: This is an HP-specific error. If Adaptive Server Enterpriseis using asynchronous I/O for a block special device, then backup Server

must do the same in order to guarantee disk coherency. Block I/Owithout asynchronous isa buffered I/O operation. With asynchronousI/O, it is not buffered. If two processes access the same disk, one usingbuffered I/O and the other using nonbuffered I/O, the current image ofa disk page may be ignored by one of the processes.

1031



4.87.2 2Device %1!: uname() failed with error: %2!.

Explanation: HP only: Backup Server is trying to identify the machineas an HP 800 or HP 700. The uname call (which gets this information)failed.

4.88.2 2Device %1!: Could not determine device type dueto unknown machine model. Expected models areHP9000/800 & 700 series.

Explanation: Related to Error 4.87.2. After getting the machine namewith the uname call, Backup Server could not identify the device typebecause it could not identify the machine type. Only 800 and 700 seriesmachines are expected.

4.89.2 2Allocation of Resource Tag failed.

Explanation:

4.90.2Allocation of Resource Tag for tape i/o failed.


4.91.2 2Registering of application failed. OS errorreturned %1!.


has occurred. Error may have occurred with any or all of usage,environment, or internal logic.

4.92.2 2Unregistering of application failed. OS errorreturned %1!.


4.93.2 2Read from %1! failed: OS error returned %2!, errno%3!.


environment, or internal logic.

1032



4.94.2 2Write to %1! failed: OS error returned %2!, errno%3!.



4.95.2 2Unable to expand file %1!. OS error returned %2!.


4.96.2 2Unable to set end of file for %1!. OS errorreturned %2!.


4.97.2 2Asynchronous I/O failed for %1!. OS error returned%2!.


4.98.2 2Unable to reserve device %1! in Control Mode. OSerror returned %2!.


4.99.2 2Open unable to mount media for device %1! : OSerror returned %2!.


1033



4.100.2 2Unable to dismount media for device %1! : OS errorreturned %2!.



4.101.2 2Unable to reserve device %1! in IO Mode. OS errorreturned %2!.


4.102.2 2Unable to locate device %1! in the Media Managerdatabase.


4.103.2 2Requested seek type %1! is invalid.


4.104.2 2Memory Allocation for I/O buffer failed.


4.105.2 2Received invalid return code %1! in I/O completionstatus.


has occurred. Error may have occurred with any or all of usage,environment, or internal logic.

1034



4.106.2 2Unable to forward a file mark: OS error returned%1! .



4.107.2 2Error in forwarding %1! file marks.


4.108.2 2Unable to back over a file mark: OS error returned%1! .


4.109.2 2Error in backing over %1! file marks.


4.110.2 2Attepmt to write EOF on device %1! failed. OSerror returned %2! .


4.111.2 2Unable to rewind device %1!: OS error returned %2!.


4.112.2 2Unable to unload media in device %1!.


1035



4.113.2 2Unable to go to end of media.


4.114.2 2Unable to retension device.


4.115.2 2Open of %1! failed, unable to expand device name tofullpath.


4.116.2 2Open of %1! failed, unable to determine volumenumber. Volume = %2! Fullpath = %3!.


4.117.2 2Unable to get volume mapping information for volume%1! in path %2!.


4.118.3 3Unable to detect database device %1!


4.119.2 2Unable to release device %1!


1036



4.120.3 3Unable to locate state information for this stripe.


4.121.3 3Local semaphore handle is NULL for asynchronous diski/o.


4.122.2 2Unable to allocate semaphore for disk operations ondevice %1!.


4.123.2 2Operating system error, server %1! device %2!errcode %3!.


4.124.2 2Archive API error for device='%1!': Vendorapplication name=%2!, Library version=%3!, APIroutine=%4!, Message=%5!


4.125.1 1Archive API information for device='%1!': Vendorapplication name=%2!, Library version=%3!,Message=%4!.


1037



4.126.3 3Unable to get current date and time. Internalerror.



4.127.2 2Internal Error on device %1!: Attempting todetermine if device is non-rewinding. Failed to getthe OS version when converting data returned fromuname(2).


4.128.2 2Failed to start multibuffering subprocesses forarchive device % ` 1!'. Look at the Backup Servererror log for more information.

Explanation: Either the sybmultbuf process was not created successfullyor the sybmultbuf process died immediately after creation. Check thebackup server error log for any error message from the sybmultbufprocess.

4.129.2 2Device %1! may not be used with physical blocksizeconfigured as %2!. In order to be usable by BackupServer a device's blocksize must be configured to beboth less than or equal to %3! and to be an evendivisor of that value.


4.130.2 2Device: $ 1!'. The stream identifier % ` 2!'contains invalid characters. The valid characterare, alphabetic, numeric, and underscore.


1038



4.131.2 2Device: % 1!'. The stream identifier % ` 2!' has anincorrect length. A valid length is from 1 to 30bytes long.


4.132.1 1Attempting to open bytestream: % ` 1!'


4.132.1 1Attempting to open byte stream device: % ` 1!'


4.133.2 2Invalid path or no execute permission formultibuffering subprocess binary: %1!

Explanation: The sybmultbuf binary could not be found. Checkthe pathname in the -M option or $SYBASE/bin for the existence ofsybmultbuf binary (in NT sybmbuf.exe). Also, check if the binary hasexecute permissions.

4.134.2 2Invalid Device: you cannot dump to or load from thenull device, '%1!'.

Explanation: You cannot dump to null device since you cannot recoverthe dump from it. Select a device of a legal type.

4.135.2 2Invalid Device: you cannot dump to or load from adirectory, '%1!'.

Explanation: The specified archive device is a directory name. Specify a

device name or a disk file name.

4.136.2 2uname failed with OS error '%1!'.



1039



4.137.2 2Invalid OS release number '%1!'


4.138.2 2Device '%1!': operating system call 'readlink'failed with error '%2!'.


4.139.2 2[%1!] The '%2!' call failed for device '%3!' witherror number %4! (%5!). Refer to your operatingsystem documentation for further details. Look for'%6!' in the backup server errorlog for additionalinformation from SYBMULTBUF.

Explanation: The message has 93 secondary state values used todetermine where a failure occurred in sybmultbuf.

4.140.2 2[%1!] The '%2!' call failed with error number %3!(%4!). Refer to your operating system documentationfor further details. Look for '%5!' in the backupserver errorlog for additional information fromSYBMULTBUF.


4.141.2 2[%1!] The '%2!' call failed for device '%3!' witherror number %4! (%5!). Refer to your operatingsystem documentation for further details.


4.142.2 2[%1!] The '%2!' call failed with error number %3!(%4!). Refer to your operating system documentationfor further details.


1040



4.143.2 2[%1!] A failure occurred for device '%2!'. Lookfor '%3!' in the backup server errorlog foradditional information from SYBMULTBUF.


4.144.2 2[%1!] A failure occurred. Look for '%2!' in thebackup server errorlog for additional informationfrom 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 todetermine where a failure occurred in sybmultbuf..

4.147.2 2Operating system error. Code %1! message %2!.


1041



5.1.2 2The mirror devices (site: %1!) and the primarydevice(site: %2!) must reside at the same site.

Explanation: This message is part of the uncompleted dump mirroringfeature. All mirrors for a stripe must reside on the same host.

5.2.2 2Cannot allocate the login record.

Explanation: This error occurs when the dblogin call fails, probablydue to a memory resource problem.

5.3.2 2Cannot open a connection to the slave site % ` 1!'.

Explanation: An attempt to connect to a remote Backup Serverencountered this failure. Look for:Memory or swap space shortageNo remote Backup Server running

Wrong listening address

5.4.2 2RPC ( %` 1!') initialization fails.

Explanation: Internal error, contact Sybase Technical Support. Failurein dbrpcinit.

5.5.2 2Cannot add a parameter to the RPC ( % ` 1!') call

Explanation: Internal error, contact Sybase Technical Support. Failurein dbrpcparam.

5.6.2 2Cannot send the RPC ( % 1!').

Explanation: Check to see that the local or remote Backup Server isstill available.

5.7.2 2RPC ( %` 1!') execution failed.

Explanation: These messages point to difficulties in issuing an RPC to aremote Backup Server. Probable cause is an Open Server programmingerror.

1042



5.8.2 2RPC as_cmd execution failed - slave server: %1!,device: %2!, command type: %3!.

Explanation: These messages point to difficulties in issuing an RPC to aremote Backup Server. Probable cause is an Open Server programming

error.

5.9.2 2RPC as_pagerun execution failed - slave server:%1!, device: %2!.

Explanation: These messages point to difficulties in issuing an RPC to aremote Backup Server. Probable cause is an Open Server programmingerror.

5.11.2 2RPC bs_end_load execution failed - slave server:%1!, device: %2!.

Explanation: These messages indicate failure to deliver the namedRPCs to the remote Backup Server. Adjacent messages provide moredetail. Probable causes are sudden death of the remote Backup Server,

or a programming error.

5.12.2 2Missing device name parameter @devname, RPC: %1!,command: %2!.

Explanation: Internal error, contact Sybase Technical Support. Checkthe compatibility of local and remote Backup Servers.

5.13.2 2Received an unknown command. RPC: %1!, command:%2!.


5.14.2 2Cannot set the value of an RPC return parameters,RPC: %1!


5.15.2 2Slave server received %1! bytes of data that ismore than @count %2! specified in as_pagerun.

Explanation: Internal error, contact Sybase Technical Support. Violationof the RPC API.

1043



5.16.2 2DB-Library error, error number %1!, severity %2!:%3!

Explanation: The installed DB-Library error handling function returnsthis error. Adjacent messages provide more detail.

5.17.2 2Cannot get the character set currently in use.

Explanation: The remote Backup Server could not set the character setto its default setting for the initial connection from a client of the localBackup Server.

5.18.2 2Cannot set character set % ` 1!' in the login record.

Explanation: The remote Backup Server could not set the character setto the set specified by the remote connection.

5.19.2 2Cannot get the language currently in use.

Explanation: The remote Backup Server could not set the language toits default setting for the initial connection from a client of the localBackup Server.

5.20.2 2Cannot set language %` 1!' in the login record.

Explanation: The remote Backup Server could not set the languagespecified by the remote connection.

5.21.2 2Remote DUMP/LOAD is not allowed when interfacing toa stripe for device % ` 1!'.


1044



6.28.1 1Dumpfile name % 1!' section number %2! mounted on%3! %` 4!'

Explanation: This message has a critical role. It contains the file nameassigned 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 inpersistent storage and specify it at load time in order to locate the filefor loading from the multifile archive. If the dumpfile name is lost, itwill be necessary to scan the tape offline with the commands givenunder message 4.12.2 to locate the dumpfile name.

6.29.1unnamed dumpfile, section number %1! mounted ondevice % 2!'

Explanation:

6.30.1 1Device %1!: Volume cataloguing complete.

Explanation: This is an informational message indicating that the

load with listonly command has completed successfully for the specifiedarchive device.

6.31.2 2Volume rejected.

Explanation: Backup Server refuses to use the mounted volume.

Adjacent messages provide more detail. The volume either hasnon-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. Ifyou are loading, use another volume. If you are dumping, user mayoverwrite.

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 wasspecified in the capacity clause.

1045



6.34.2 2\n%1!\n%2!\n%3!


6.35.2 2Volume 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 2Header labels of rejected volume:

Explanation: Preamble message to display labels of rejected volume.

6.37.2 2Volume 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 1Header labels of volume on % ` 1!':


6.39.0 0tape drive

Explanation: Internal informational message, usually a component ofanother message. No user action necessary.

6.40.0 0disk


6.41.1 1Header labels of mounted volume:

Explanation: Preamble message to display labels of mounted volume.

6.42.0 0disk file


1046



6.43.0 0floppy disk


6.44.0 0device


6.45.1 1Be sure to remove the tape/floppy from drive %1!(server: %2!, session id: %3!).

Explanation: Reminder message appears when nounload (default) isspecified for an unloadable device.

6.46.1 1%1!: Mount the next volume to read.

Explanation: Requests mounting of the next volume in sequence forload.

6.47.1 1%1!: Mount the next volume to write.

Explanation: Requests mounting of the next volume in sequence tocontinue dump.

6.48.1 1%1!: Volume on device %` 2!' has restricted access(code %3!).

Explanation: Reports ANSI restricted-access code in label prior toconfirming overwrite request.

6.49.1 1%1!: Volume to be overwritten on % ` 2!' has notexpired: creation date on this volume is %3!,expiration date is %4!.

Explanation: Requests verification of overwrite of unexpired volume.

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 correctvolume.

1047



6.51.1 1%1!: Mount the next volume to search.

Explanation: Reports that the requested dumpfile (specified by the fileoption) was not found on the volume.

6.52.1 1%1!: Volume to be overwritten on % ` 2!' hasunrecognized 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 forwrite access. Mount another volume.

Explanation: Check write protection.

6.54.1 1%1!: Volume on device %` 2!' is expired and will beover written.

Explanation: A single dump file device has media with expired dumpdata on it. The user is prompted whether the data is to be overwritten.

6.55.1 1The volume mounted on % 1!' does not belong to thesame archive as other, previously mounted volumes.

Explanation: The creation time of this volume does not match the othervolumes or stripes.

6.56.2 2The volume mounted on device %` 1!' could not bepositioned to append another dump file. This dumpdevice may only support one dump file per volumeset.

Explanation: The mounted volume is either full, or can only hold onedump file.

6.57.1 1Device %1!' supports one dump file per volume set.


6.58.1 1Device %1!' supports multiple dump files pervolume set.


1048



6.61.2 2Volume validation error: Volume change request notallowed on non-mountable devices, device name: %1!.

Explanation: Requests mounting of next volume in sequence to locaterequested dump file.

6.65.2 2Volume validation error: illegal volume change,device %1!: volume for stripe %2! mounted whilestripe %3! loading still in progress.

Explanation: Reminds user that all volumes of a dump-time stripemust complete loading on the device before the first volume of anotherdump-time stripe may begin loading.

6.66.2 2Volume validation error: illegal volume change,device %1!: volume mounted out of order, expectedvolume %2!, got volume %3!

Explanation: Volumes must be loaded in the same order in which theywere dumped.

6.78.1 1EXECUTE 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 meanscontinue operation with the currently mounted volume. retry meansredo the validation check that led to the prompt (presumably on a newvolume). abort means abort the entire dump or load session.

6.80.2 2Session %1! is exiting by request fromsp_volchanged.\nData written in this sessionare incomplete and invalid.\nAborting session.

Explanation: The user requested an abort through sp_volchanged.

6.81.2 2Unrecognized volume change prompt id (internalerror); task must exit.

Explanation: Indicates a Backup Server programming error. Retry thedump or load command, avoiding unnecessary volume manipulations.

1049



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.

6.83.2 2Volume validation error: Volume name mismatch,volume name %1!, expected volume name %2!.

Explanation: Volumes within a stripe must have the same name inthe ANSI VOL1 label. It is possible for a user to execute the dumpcommand properly and still receive this error at load time, if the firstvolume was overwritten using the dumpvolume option and the second

volume, with a different name, was appended to.

6.84.2 2Volume validation error: illegal volume change,device %1!: stripe %2! is already loaded.

Explanation: User remounted a tape for a stripe that has already beenloaded.

6.85.0 0byte stream


6.86.2 2Unexpected error reading from volume change responsemessage 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 orexchange it for another.

1050



6.88.1 1Volume on device % 1!' has unrecognized format ornot formatted.

Explanation: The mounted volume is not ready for use. Format it orexchange it for another.

6.89.2 2The SYTAPE environment variable must be set.

Explanation: The SYTAPE environment variable must be set beforecontinuing.

1051



7.1.2 2Memory 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 2Option %1!': %2! is an invalid value; value mustbe an even multiple of %3!.

Explanation: Illegal value for a dump or load option.

7.3.2 2Option error: when you specify %1!, you may notspecify %2!.

Explanation: Illegal combination of options in a dump or loadcommand.

7.4.2 2Option %1!': %` 2!' is an invalid value -- checkthe documentation for allowable values.

Explanation: Unrecognized value specified for a dump or loadcommand.

7.5.2 2%` 1!' is a badly formed value string.

Explanation: Syntax error in dump or load command option.

7.6.2 2Option %1!': %` 2!' is an invalid volume label.The maximum length is %3!.

Explanation: Volume label is longer than 6 characters.

7.7.2 2Option %1!' is not valid.

Explanation: Unrecognized dump or load option.

7.8.2 2Option %1!' may not be negated.

Explanation: You cannot use no with this option.

7.9.2 2Option %1!' does not take any value; remove = ` '.

Explanation: This option does not allow you to specify a value.

1052



7.10.2 2Option %1!' may not have more than one value.

Explanation: User specified more than one value after “=”, and theoption only permits one value.

7.11.2 2Option %1!' may not take a value when it isnegated.

Explanation: User specified an option with a value and no. Thecombination is illegal for this option.

7.12.2 2Option %1!' requires a value, but none wasspecified.

Explanation: You must specify a value for these options: density,

blocksize, capacity, dumpvolume, retaindays, or file.

7.13.2 2Option %1!': %` 2!' is not unique -- supply morecharacters.

Explanation: User abbreviated a keyword following a value, and theabbreviation is ambiguous.

7.14.2 2Option error: when you specify %1!, you must alsospecify %2!.

Explanation: Invalid combination of options.

7.15.2 2Option %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 0and


7.17.0 0or


1053



8.1.2 2Device %1!: Failure to open for read/write.Operating system message: % ` 2!'.



8.2.2 2Device %1!: Failure to rewind tape device.


8.3.2 2Device %1!: Failure to write minimum block size of%2! bytes.


8.4.2 2Device %1!: Auto-configuration failure. This tapedevice is not supported.


8.5.1 1Warning, 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. Thisinformational message is printed if the configuration file does not existalready and hence it is about to create one.

8.6.1 1Warning, the format of the device configuration %1!file is invalid. Configuration information will notbe saved.


1054



8.7.1 1Warning, unable to open device configuration file%1! for writing. Operating system error %2!.Configuration information will not be saved.


8.8.1 1Warning, unable to write to device configurationfile %1!. Operating system error %2!.Configuration information will not be saved.


8.9.1 1Warning, unable to close device configuration file%1!. Operating system error %2!. Configurationinformation will not be saved.


8.10.2 2Device %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 thebackup 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 thedata on the tape.

8.11.1 1Device %1!: Will be auto-configured and theresults saved in the configuration file %2!. Theconfiguration will take additional time.


8.12.2 2Device %1!: the operating system device type isdifferent than what is in the configuration file%2!. Please remove entry for this device in theconfiguration file and reconfigure the device byissuing a DUMP with the INIT qualifier.


1055



8.13.2 2Device %1!: the operating system file mark type isdifferent than what is in the configuration file%2!.

Explanation: The operating system file mark type is different than whatis specified in the configuration file.

8.14.1 1Backup Server tape configuration file %1! revisionis not compatible.


8.15.1 1Device %1!: not found in tape configuration file.Tape configuration will be attempted.


8.16.2 2Device %1!: Auto-configuration failure. The devicefunctions as rewind on close. Please specifiy theno rewind on close device interface.


8.17.2 2Device %1!: Auto-configuration failure. Internalor system call error encountered while checking forrewind on close.


1056

Chapter 5

Component Integration Services Error Messages

This chapter gives the error number, message text, and a brief explanationfor Component Integration Services error messages.

1057

Chapter 5 Component Integration Services Error Messages

Component Integration Services Error MessagesNumber Severity Text and Explanation

11201 16A remote table definition must be defined before the

e` xisting' option is used (object % ` .*s').

Explanation: Use sp_helpobjectdef to compare the table name on theremote server with the remote table name mapped to the table in yourcommand. If the remote table does not exist, first create the table onthe remote server or use create table.

11202 16Unable to create table % ` .*s' because it has noremote storage location defined. Creation of localuser tables is allowed only in the master and tempdbdatabases.

Explanation: Define the remote storage location using sp_addobjectdef,then rerun this command.

11203 16The command %` s' is not legal when the remote object(%.*s) has been defined as an RPC.

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 15There is an error in the syntax of the objectdefinition % ` .*s'.

Explanation: Command failed. Check syntax and semantics of yourobject definition and rewrite the command.

11205 16Datatype % s' is unsupported for server % ` .*s'.

Explanation: The datatype is not supported by the server where theremote object is located. Rewrite the command using a valid datatype.

11206 16Unable 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.

1058



11207 10Warning, table definition does not contain allcolumns found in remote object % ` .*s'; (defined: %dfound: %d)

Explanation: This is an informational message. Contact the ObjectOwner about the warning issued in this message.

11208 16No 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 16Column type mismatch in remote object % ` .*s' forcolumn %` .*s'; (defined: %d found: %d).

Explanation: Refer to the writeup “Problem Retrieving Data FromRemote Objects” in Appendix A “Troubleshooting” of the Component

Integration Services User's Guide.

11210 16Column length mismatch in remote object % ` .*s' forcolumn %` .*s'; (defined %d found: %d).

Explanation: Refer to the writeup “Problem Retrieving Data FromRemote Objects” in Appendix A “Troubleshootin ” of the Component


11211 16Handling of null values in remote object % ` .*s' forcolumn %` .*s' differs from that defined; (defined:

%` s' found: %` s').



11212 16Identity attribute mismatch for column % ` .*s';(defined: %` s' found: %` s').



1059



11213 16Column count mismatch in remote object % ` .*s';(defined: %d found %d).



11214 16Remote object % .*s' does not exist.

Explanation: If the syntax is correct, refer to the writeup “Unableto Access Remote Object” in Appendix A “Troubleshooting” of theComponent Integration Services User's Guide.

11215 16Remote object % .*s' not uniquely identified; %dobjects with the same name and owner were found.

Explanation: The remote server contains more than one object with thename specified by sp_addobjectdef. Use sp_dropobjectdef to drop the object,and reenter the object definition with an owner name or database nameto further qualify the remote object.

11216 16Internal Ct-Lib/Cs-Lib error %d: % ` .*s'.

Explanation: Command failed due to an internal Adaptive Serverproblem. Report the error to your System Administrator.

11217 10Entered passthru mode to server % ` .*s'.

Explanation: This is an informational message. No action is required.

11218 10Exited passthru mode from server % ` .*s'.


11219 17Cannot open a connection to site % ` .*s' becausethere are no free remote descriptors (RDES).Increase the configuration parameter for userconnections 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.

1060



11220 16Parameter cannot be NULL.

Explanation: Adaptive Server could not perform the requested action.Rewrite the command with an entry for the parameter.

11221 16No 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 externallogin using sp_addexternlogin.

11222 12Parameter %d must be datatype CHAR or VARCHAR.

Explanation: Command failed. Specify an object of the correct type.

11223 17Insufficient memory is available to allocatestructures needed to access a remote site.

Explanation: Command failed due to resource limitation. Modify thecommand to fit available resources, retry when the resource is available,or contact your System Administrator to address the resource problem.

11224 16Cannot open a connection to site % ` .*s' because itdoes not have PASSTHRU or RPC capabilities.

Explanation: Use sp_helpobjectdef to verify the object is mapped to aremote server. If the server is remote, have the System Administratorreconfigure it to allow passthrough connections.

11225 16Server 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 SystemAdministrator correct the entry.

11226 16Server class (%d) for server % ` .*s' is notsupported.

Explanation: An invalid server class has been defined for the remoteserver. Use sp_helpserver to check the server definition, and have yourSystem Administrator correct the entry.

1061



11227 16Statement % s' is unsupported by % ` .*s'.

Explanation: The SQL statement uses a datatype or syntax that is notsupported by the server class of the server where the remote objectresides. Rewrite the command using correct syntax or a valid datatype.

11228 18Remote text/image data length less than expected forcolumn %` .*s'.

Explanation: Command failed due to internal Adaptive Server problem.Report the error to your System Administrator.

11229 16Unable to commit transaction on remote server %.*s.

Explanation: During a transaction involving multiple servers, the localserver was unable to broadcast a commit request to a remote server.Work done locally as part of the transaction will be rolled back.

11230 16Unable to prepare transaction on remote server %.*s.

Explanation: During a transaction involving multiple servers, the localserver was unable to broadcast a prepare request to a remote server.A rollback request has been sent to all remote servers involved in thetransaction. Work done locally as part of the transaction will be rolledback.

11231 16Unable to rollback transaction on remote server%.*s.

Explanation: During a transaction involving multiple servers, the localserver was unable to broadcast a rollback request to a remote server.Work done locally as part of the transaction will be rolled back.

11232 18Unable to access cursor process status structure(PSS); update cannot be completed.


1062



11233 16Column mismatch in remote object % ` .*s' for column

%` .*s'; (column must be defined with length >= 10 oras DATETIME).


Integration Services User's Guide









11236 16Update or c omplex INSERT' of non-NULL TEXT/IMAGEdata is unsupported by server % ` .*s'. Use WRITETEXTinstead.

Explanation: Adaptive Server could not perform the requested action.Modify your command as shown in the error message.

11237 16TEXT/IMAGE value too long for INSERT/UPDATE onserver % .*s'. Use WRITETEXT instead.


11238 16Complex INSERT of TEXT/IMAGE data is not supported.Use WRITETEXT instead.


1063



11242 10Component Integration Services recovery started.


11243 10Component Integration Services recovery complete.


11244 10Deallocating text/image data for external object

%` .*s'.


11245 10Checking external objects.


11246 16Precision or scale mismatch in remote object % ` .*s'for column % .*s'; (defined: %d,%d found: %d,%d).



11247 16Scale mismatch in remote object % ` .*s' for column

%` .*s'; (defined: %d found: %d).



11248 14Remote server % .*s' is currently configured as readonly.

Explanation: You do not have permission to execute this command.

Contact the System Administrator to change permissions.

11249 10Executing Partial Query Remotely

Explanation: This is an informational message generated by showplan.No action is required.

11250 10EXISTS TABLE: Executing Query Remotely


1064



11251 10Dynamic Update


11252 10Select for Update


11253 10Dynamic Delete

Explanation: This is an informational message generated by showplan.

No action is required.

11254 10Select for Delete


11255 10Remote Cursor Operation


11256 10%.*s


11257 10%.*s


11258 11No 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 10Warning, no mapping for remote column named % ` .*s'in local object % ` .*s'.

Explanation: This is an informational message. Contact the ObjectOwner about the warning issued in this message.

1065



11263 10Server Name: %.*s


11264 10Text of generated SQL:


11265 10Executing Query Remotely

Explanation: This is an informational message generated by showplan.


11266 16The sp_columns result set returned by the remoteserver is incomplete. Each row must contain atleast %d columns, but only %d are present.

Explanation: Command failed due to remote server problem. Reportthe error to your System Administrator.

11267 16Unable to create table '%.*s' on remote server; thisserver not configured for heterogeneous data access.

Explanation: Command failed. Contact your System Administrator toinstall the Extended Enterprise Option of Adaptive Server Enterpriseprior to accessing remote servers that are not server class sql_server.

11268 16Unable to insert into a text/image column becausethe table does not contain a unique index.

Explanation: Command failed. The table must have a unique index toexecute a select...into or insert...select command, since the table has text orimage columns and is owned by a server of class direct_connect or sds.

11269 16The optimizer could not find a unique index which itcould 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 indicatedby message.

1066



11270 16Column '%.*s' does not allow NULL. Any columndefined as a parameter column for RPC tables mustallow NULL. A parameter column is a column whosename 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 16Column '%.*s' must precede all parameter columns. Aparameter column is a column whose name begins withan underscore.

Explanation: Adaptive Server could not perform the requested action.Rewrite the command and put result column definitions beforeparameter column definitions-all column names that begin with an

underscore must appear at the end of the list.

11272 16Action requested is not valid for remote tables(%.*s).

Explanation: Command failed due to invalid request. You cannot enterthis command using proxy tables (the command can only be used withlocal tables).

11273 10Encounter %d conversion errors during processing ofexternal statistics; some rows have been ignored.

Explanation: update statistics cannot generate complete statistics becausethe proxy table has columns with datatypes or widths that are differentfrom the corresponding column at the remote location.

1067


1068

Chapter 6

Adaptive Server Error Messages

This chapter contains the text of all the numbered Adaptive Server errormessages through 18406. Each message is followed by a short explanationand brief instructions on what to do when you see the error.

Since dbcc checkstorage faults are somewhat different in concept fromother error messages, they do not appear in this chapter. For a listing ofdbcc checkstorage faults, see “How to Analyze dbcc checkstorage Faults” in“Encyclopedia of Tasks”.

Working with Error MessagesThis chapter shows all numbered messages applicable to Adaptive ServerVersions 11.0.x through 11.9.2. The message text itself corresponds tothe Version 11.9.2 text. Accordingly, specific messages may or may notappear in your server version, and the message text may differ from whatis shown here.

WARNING! If your site utilizes any applications based on Adaptive Server errormessages, note that characteristics such as the text of a message, itsseverity, and so on are subject to change from one version to the next.Messages may also be withdrawn or replaced by new messages. Exercisecaution, therefore, in using the existence, or any other characteristics ofa message, as the basis for your applications.

Use this chapter as an error reference. Look up the error number and notethe severity. Then use the accompanying explanation (available for most,though not all, messages) to determine your next course of action. If theerror is one of the commonly occurring server messages documented inthe chapter “Error Message Writeups,” the explanation will refer you tothat chapter. In other cases, it gives you guidance on the nature of theerror and what to do next.

1069

Chapter 6 Adaptive Server Error Messages

Generally speaking, the severity level of a message corresponds to the typeand severity of the problem that the server encountered. For a completedescription of severity levels, see “Adaptive Server Error Logging” in theSystem Administration Guide.

1070

Server Error Messages 1 - 199

Server Error Messages 1 - 199Number Severity Text and Explanation

21 10WARNING - Fatal Error %ld occurred at %S_DATE.Please note the error and time, and contact a userwith System Administrator (SA) authorization.

Explanation: This is an informational message. Unless otherwisespecified, no action is required. Contact your System Administratorabout any warning issued in the message.

101 15Line %d: SQL syntax error.

Explanation: Command failed. Check syntax and semantics.

102 15Incorrect syntax near % ` .*s'.

Explanation: Refer to the writeup for Error 102.

103 15The %S_MSG that starts with % ` .*s' is too long.Maximum length is %d.

Explanation: Command failed. Check syntax and semantics. Rewritethe command to satisfy the condition indicated in the message.

104 15Order-by items must appear in the select-list if thestatement contains set operators.


105 15Unclosed quote before the character string % ` .*s'.


106 16Too many table names in the query. The maximumallowable is %d.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicated

by message.

1071



107 15The column prefix %` .*s' does not match with a tablename or alias name used in the query. Either thetable is not specified in the FROM clause or it hasa correlation name which must be used instead.


108 15The order-by position number % ` ld' is out of rangeof 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 15There are more columns in the INSERT statement thanvalues specified in the VALUES clause. The numberof values in the VALUES clause must match the numberof columns specified in the INSERT statement.


110 15There are fewer columns in the INSERT statement thanvalues specified in the VALUES clause. The numberof values in the VALUES clause must match the numberof columns specified in the INSERT statement.


111 15%s must be the first command in a query batch.


112 15Variables are not allowed in %s statement.


113 15Missing end comment mark '*/'.


1072



114 15%` .*s' is not a recognized DUMP DATABASE/TRANSACTION

truncation option.


115 15The offset % d' given in a CONTROLROW command doesnot correspond to the beginning of a statement.


116 15The symbol * ' can only be used for a subqueryselect list when the subquery is introduced withEXISTS or NOT EXISTS.



117 15The %S_MSG name %` .*s' contains more than themaximum number of prefixes. The maximum is %d.


118 15%` s' option name length plus value string length

must total less than %d characters.


119 15Must pass parameter number %d and subsequentparameters as @ name = value'. Once the form @ ` name= value' has been used, all subsequent parametersmust be passed in the form @ ` name = value'.


1073



120 15The SELECT list for the INSERT statement containsfewer items than the INSERT list. The numberof SELECT values must match the number of INSERTcolumns.


121 15The SELECT list for the INSERT statement containsmore items than the INSERT list. The number ofSELECT values must match the number of INSERTcolumns.


122 15The debug option % d' is larger than the maximumallowed. The highest option available is %d.

Explanation: Command failed due to invalid or illegal request.Adaptive Server cannot perform the requested action.

123 15Must attach a value to the binary prefix 0 ` x';zero-length binary value is not allowed.


124 15CREATE PROCEDURE contains no statements.

Explanation: Command failed. The CREATE PROCEDURE commandmust contain at least one SQL statement.

126 15Cannot nest CREATE PROCEDURE statements.


127 15This CREATE may only contain 1 statement.


1074



128 15The name %` .*s' is illegal in this context. Onlyconstants, constant expressions, or variablesallowed here. Column names are illegal.


129 15Fillfactor % ` d' is not a valid percentage;fillfactor must be between 1 and 100.


130 15The comparison operator = ` ALL' is not currentlysupported.

Explanation: Command failed due to invalid or illegal request.

Adaptive Server cannot perform the requested action.

131 15The size (%d) given to the %S_MSG %` .*s' exceeds themaximum. The largest size allowed is %d.


132 15The label % .*s': has already been declared. Labelnames must be unique within a query batch or storedprocedure


133 15A GOTO statment references the label % ` .*s' but thelabel has not been declared.


134 15The variable name % .*s' has already been declared.Variable names must be unique within a query batchor stored procedure.


1075



135 15Cannot use a BREAK statement outside the scope of aWHILE statement.


136 15Cannot use a CONTINUE statement outside the scope ofa WHILE statement.


137 15Must declare variable % ` .*s'.



138 15Illegal correlation clause in a subquery.

Explanation: Command failed due to invalid or illegal request.Adaptive Server cannot perform the requested action. (This error is notraised in Release 11.0 and higher.)

139 15Cannot assign a default value to a local variable.


140 15Can only use IF UPDATE within a CREATE TRIGGER.


141 15A SELECT statement that assigns a value to avariable must not be combined with data-retrievaloperations.


1076



143 15A compute-by item was not found in the order-bylist. All expressions in the compute-by list mustalso be present in the order-by list


144 15Cannot use an aggregate in an expression used forthe by-list of a GROUP BY clause.


145 15A subquery with no aggregate functions may onlycontain expressions in its GROUP BY clause that arein the select-list.


146 15Cannot perform an aggregate function on a columnfrom a table not declared in the same subquery.


147 15An aggregate function may not appear in a WHEREclause unless it is in a subquery that is in aHAVING clause, and the column being aggregated isin a table named in a FROM clause outside of thesubquery.


148 15Incorrect time syntax in time string % ` .*s' usedwith WAITFOR.


1077



149 15Time value % .*s' used with WAITFOR is not a legalvalue. Check date/time syntax.


150 15Both terms of an outer join must contain columns.


151 15%` .*s' is an invalid money value.


152 15Subqueries that use DISTINCT with a GROUP BY clauseare not currently supported.

Explanation: Command failed due to invalid or illegal request.Adaptive Server cannot perform the requested action. (This error is notraised in Release 11.0 and higher.)

153 16Variables/Parameters are not allowed in the ORDER BYclause.

Explanation: Adaptive Server could not perform the requested action.Rewrite the command to conform to the requirement specified in theerror message.

154 15%S_MSG is not allowed in %S_MSG.


155 15%` .*s' is not a recognized %s option.



156 15Incorrect syntax near the keyword % ` .*s'.


1078



158 15Too many ORDER BY expressions. The maximum is %d.


159 15For DROP INDEX, must give both the table and theindex name, in the form tablename.indexname


160 15Rule does not contain a variable.


161 15Rule contains more than one variable.


162 15The select list item identified by the order bynumber %` ld' is a * ` ', rather than a column name.When ordering by column number, a column name mustappear in the select list position that correspondsto the order by number.


163 15The COMPUTE BY list does not match the ORDER BYlist.


164 15GROUP BY expressions must refer to column names.


1079



165 16Privilege %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 thecommand and working database context.

166 15%s does not allow specifying the database name as aprefix to the object name.


167 16May 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, variablenames, and/or input data.

168 15The %S_MSG %` .*s' is out of the range of machinerepresentation (%d bytes).


169 15Expression % d' and % d' in the ORDER BY list aresame. Expressions in the ORDER BY list must beunique.


171 15Can't use SELECT INTO in Browse Mode.


172 15Can't use HOLDLOCK in Browse Mode


173 15The definition for column % ` .*s' must include adatatype.


1080



174 15The function %` .*s' requires %d arguments.


175 15Functions may only be nested to level %d.


176 15Function % .*s' is not yet implemented.



177 15%s cannot create a temporary object (with # ` ' as thefirst character name.


178 15A RETURN statement with a return status may only beused in a stored procedure.


179 15Can't use the OUTPUT option when passing a constantto a stored procedure.


180 15There are too many parameters in this CREATEPROCEDURE statement. The maximum number is %d.


181 15Can't use the OUTPUT option in a DECLARE statement.



1081



182 15Table and column names must be supplied for theREADTEXT or WRITETEXT utility.


183 15The scale (%d) for column % ` .*s' must be within therange %d to %d.


184 15Invalid money datatype specification for column

%` .*s'. Only money(19, 4) is allowed fornon-external tables.



185 15Data stream is invalid for WRITETEXT command in bulkform.


186 15Data stream missing from WRITETEXT command.

Explanation: Command failed. Check the syntax of the WRITETEXTcommand.

187 15Odd number of bytes in IMAGE data.

Explanation: While inserting text/image data, an upper limit on thesend may have been reached. Check the data sent and consider using

ct_command or other alternative.

188 15Can't specify a log-device in a CREATE DATABASEstatement without also specifying at least onenon-log-device.


1082



189 15Function % .*s' requires %d to %d arguments.


190 15Can not update the global variable % ` .*s'.


191 15Some part of your SQL statement is nested toodeeply. Please re-write the query or break it upinto smaller queries.



192 15Can't create a view inside a stored procedure.


193 15The object or column name starting with % ` .*s' istoo long. The maximum length is %d characters.


195 15%` .*s' is not a recognized %S_MSG.


196 15SELECT INTO must be the first query in a SQLstatement containing set operators.


197 15Set operators may not appear within the definitionof a view.


1083



198 15Browse mode is invalid for statements containing setoperators.


199 15An INSERT statement may not contain a SELECTstatement that assigns values to a variable.


1084



201 16Procedure %.*s expects parameter %.*s, which was notsupplied.


202 11Internal error -- Unable to open table at queryexecution time.

Explanation: Command failed. There may be a Adaptive Serverproblem. Contact Sybase Technical Support. (This error is not raised inRelease 11.1 and higher.)

203 16The name %` .*s' is not a valid identifier.


204 20Normalization error; node %s

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics can be run.

205 16All queries in a SQL statement containing setoperators must have an equal number of expressionsin their target lists.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby message.

206 16Operand type clash: %s is incompatible with %s


207 16Invalid column name %` .*s'.


1085



208 16%.*s not found. Specify owner.objectname or usesp_help to check whether the object exists (sp_helpmay produce lots of output).


209 16Ambiguous column name %.*s

Explanation: Command failed. Check syntax and semantics. A column

name may need the full table specification or alias.

210 16Syntax error converting DATETIME fromBINARY/VARBINARY string.


211 16Syntax error converting SMALLDATETIME fromBINARY/VARBINARY string.


212 16Expression result length exceeds maximum: max - %dfound - %d


213 16Insert error: column name or number of suppliedvalues does not match table definition.


214 16Cannot convert parameter %.*s to type %.*s expectedby procedure.


by message.

1086



216 20Attempt to automatically drop temporary tablefailed.


217 16Maximum 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 theobjects or variables shown in the error message.

218 16Given parameter %.*s is too large; maximum size forthis parameter is %d bytes.

Explanation: Adaptive Server could not perform the requested action.Modify your command to meet the Adaptive Server requirement for theobjects or variables shown in the error message.

219 16Print format failed to match with a result column.


220 16Arithmetic overflow error for type %s, value = %ld.


221 16Column of type (%s) does not allow nulls. It maynot be compared with null.


222 20Unintelligible query plan step encountered.


1087



223 11Object %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 notfound and re-enter the command with the correct name.

224 11Object %d specified as a rule/check constraintfor tabid %d, colid %d is missing or not of typedefault.


225 11Cannot run query--referenced object (name %.*s)dropped during query optimization.


226 16%s command not allowed within multi-statementtransaction.


227 16Arithmetic overflow error ocurred while convertingthe string %` .*s' to type %s.


228 14Query is based on a view that no longer exists (id= %ld)--cannot run.

Explanation: Command failed. Check your Adaptive Serverenvironment for the object not found and re-enter the command withthe 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


1088



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 11Getdefault: no such default. id=%ld dbid=%d


232 16Arithmetic overflow error for type %s, value = %f.


233 16The column %.*s in table %.*s does not allow nullvalues.%S_EED


234 16There is insufficient result space to convert MONEYvalue to CHAR.


by message.

235 16Precision error during %S_MSG conversion of %s value

%` s' to a %s field.


236 16The conversion from CHAR to MONEY resulted in aMONEY overflow error.


1089



237 16There is insufficient result space to convert MONEYvalue to %s.


by message.

238 16There is insufficient result space to convert %svalue (= %d) to MONEY.


239 16Table %.*s' does not exist. Please refer tosysobjects for correct name.


240 16There is insufficient result space to convertDATETIME value to CHAR.


241 16Scale error during %S_MSG conversion of %s value



242 16The conversion of CHAR to DATETIME resulted in aDATETIME value out of range.



1090



243 16Type %` .*s' is not a defined system type.


244 16The conversion of CHAR value % ` .*s' overflowed anINT1 field, use a larger integer field.


245 16Domain error during %S_MSG conversion of %s value



246 16The conversion of CHAR value % ` .*s' overflowed anINT2 field, use a larger integer field.


247 16Arithmetic overflow during %S_MSG conversion of %svalue %s' to a %s field .


248 16The conversion of CHAR value % ` .*s' overflowed anINT4 field. Maximum integer value exceeded.


1091



249 16Syntax error during %S_MSG conversion of %s value



by message.

251 16Unable to allocate ancillary table for queryoptimization. Maximum number of tables in a query(%d) exceeded.


252 16Can't group by a bit field.


253 16Maximum number of group-by expressions exceeded (31max, %d found).


254 16Maximum number of columns in a work table (%d)exceeded.


255 16Maximum row size (%d) for a work table exceeded.


1092



256 16The data type % s' is invalid for the %sfunction. Allowed types are: CHAR/VARCHAR andBINARY/VARBINARY.


257 16Implicit conversion from datatype % ` s' to % s' isnot allowed. Use the CONVERT function to run thisquery.


258 20Database %.*s' missing during query recompile.


259 16Ad-hoc updates to system catalogs not enabled. Auser with System Security Officer (SSO) role mustreconfigure system to allow this.


261 16%` .*s' is not a recognized global variable.


by message.

262 16%s permission denied, database %S_DBID, owner %.*s


1093



263 16Must specify table to SELECT * FROM.


264 16Column name %.*s appears more than once in theresult column list.


265 16Insufficient result space for %S_MSG conversion of%s value %s' to a %s field.


266 10Transaction count after EXECUTE indicates that aCOMMIT or ROLLBACK TRAN is missing. Previous count= %ld, Current count = %ld.

Explanation: Check command syntax for missing COMMIT orROLLBACK TRANSACTION. Use @@trancount in stored proceduresto check transaction count.

266 16Transaction count after EXECUTE indicates that aCOMMIT or ROLLBACK TRAN is missing. Previous count= %ld, Current count = %ld.

Explanation: Check command syntax for missing COMMIT orROLLBACK TRANSACTION. Use @@trancount in stored proceduresto check transaction count.

267 16Object % .*s' cannot be found.



1094



268 16You can't run SELECT INTO in this database. Pleasecheck with the Database Owner.


269 16NULL value cannot be specified for conversion fromdatatype % s' to % s'.



270 16Table %.*s' can't be modified.



272 16Can't update a TIMESTAMP column.


by message.

273 10Warning: A non-null value cannot be insertedinto a TIMESTAMP column by the user. The databasetimestamp value has been inserted into the TIMESTAMPfield instead.


274 20A SYSTEM exception was raised with an unrecognizedminor number %d.


1095



276 16The parameter % .*s' in the procedure % ` .*s' was notdeclared 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 16There was a transaction active when exiting thestored procedure % ` .*s'. The temporary table % ` .*s'was dropped in this transaction either explicitly orimplicitly. This transaction has been aborted toprevent database corruption.


278 16TEXT and IMAGE datatypes may not be used in a GROUPBY clause.


Rewrite the command to conform to the requirement specified in theerror message.

279 16TEXT and IMAGE datatypes are invalid in thissubquery or aggregate expression.


280 16Only TEXT and IMAGE datatypes are valid with theTEXTPTR 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 fromDATETIME to a character string.


1096



282 10Procedure % .*s' attempted to return a status ofNULL, which is not allowed. A status of 0 will bereturned instead.


283 16You can't use browse mode with DBLIB 2.0 -- you mustupgrade to DBLIB 4.0 in order to run this query.


284 16Rules may not be bound to TEXT or IMAGE datatypes.


285 16READTEXT and WRITETEXT commands may not be used withviews.


286 16The logical tables INSERTED and DELETED may not beupdated.


287 16%s command not allowed within a trigger.


1097



288 16The PATINDEX function operates on CHAR, VARCHAR, andTEXT datatypes only.



290 16Trace 3604 is illegal within a stored procedure.


291 16Access to sysgams is disallowed.


292 16There is insufficient result space to convertSMALLMONEY value to CHAR.


294 16The conversion from CHAR to SMALLMONEY resulted in aSMALLMONEY overflow error.


296 16The conversion of CHAR to SMALLDATETIME resulted ina SMALLDATETIME value out of range.



1098



297 16There is insufficient result space to convertSMALLDATETIME 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 16The conversion from DATETIME to SMALLDATETIMEresulted in a SMALLDATETIME overflow error.


1099



301 16Query contains an illegal outer-join request.


303 16The table % .*s' is an inner member of an outer-joinclause. This is not allowed if the table alsoparticipates in a regular join clause.

Explanation: Semantic error in query. Inner join and outer join weremixed.

304 16The table % .*s' is outer-joined with itself.


305 16The column %.*s' (user type:%.*s) is joined with

%` .*s' (user type:%.*s). The user types are notcompatible: underlying types must be identical inorder to join.


306 16TEXT and IMAGE datatypes may not be used in a WHEREclause, except with the LIKE expression.


307 10Index %.*s' specified as optimizer hint in the FROMclause of table % ` .*s' does not exist. Optimizerwill choose another index instead.

Explanation: This is an informational message but may requirefollow-up action. Contact your System Administrator.

1100



308 20Table not open for range table entry % ` d', objid

%` ld', dbid % ` d'.


309 20Wrong sdes for range table entry % ` d'. Expectedobject % ld', dbid % ` d', got object % ` ld', dbid

%` d'.


310 10Index id %d on table id %d cannot be used in theoptimization of a query as it is SUSPECT. Pleasehave the SA run DBCC REINDEX on the specified table.

Explanation: There may be a potential problem with a database ordatabase object. Contact your System Administrator.

311 16The optimizer could not find a unique index which itcould use to scan table % ` .*s' for cursor % ` .*s'.


312 16Index id %d on table % ` .*s' is explicitly specifiedin cursor % .*s' declared for update. This index iseither not unique or its key includes a column inthe for update of list. This cursor my be closed onan update or a delete.


313 16The optimizer could not find a unique index which itcould use to perform an isolation level 0 scan ontable % .*s'.


1101



314 16WARNING: A non-unique clustered index has beenforced on an isolation level 0 scan on table

%` .*s'. If the scan must restart, the scan willbe repositioned at the beginning of the duplicatekey group. Thus, it is possible that this caninfinitely loop.


315 16Internal error - The SQL Server was unable to finda join order to run this query. Please informtechnical su pport.

Explanation: Internal Adaptive Server error. A table may be circularlydependent upon itself. Contact Sybase Technical Support.

316 17Cannot compile the query because the space requiredfor the search arguments (%d bytes) exceeds themaximum amount of memory that can be granted. Tryreducing the number of search arguments.

Explanation: Reduce number of sargs. Try breaking up the query intomultiple queries.

317 16A subquery in this query is correlated to an innertable of an outerjoin. This is not allowed in TSQLsemantics.


318 18sysstatistics catalog was read and an inconsistencywas found, please run update statistics and contactSybase Technical Support

Explanation: There was an internal Adaptive Server problem. Performthe diagnostic action indicated in the message. (Version 11.9.2 andhigher.)

319 18Statistics 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.)

1102



320 10Index id %d on table id %d cannot be used in theoptimization of a query as it is SUSPECT. Pleasedrop and recreate the index on the specifiedtable.

Explanation: Use sp_helpindex to obtain index information, then dropand recreate the index. (Version 11.9.2 and higher.)

321 18Internal statistics calculation inconsistency.Please contact Sybase technical support

Explanation: (Version 11.9.2 and higher.)

322 18Internal error: systabstats statistics could not beread, please contact Sybase Technical Support.


323 10WARNING: Edited statistics are overwritten. Table:'%.*s' (objectid %ld), column: '%.*s'.


324 10Invalid simulated value (%ld) ignored for %S_MSG'%.*s'. Actual value (%ld) used instead.


1103



401 16Unimplemented command or expression %s.


403 16Invalid operator for datatype op: %s type: %s.


404 19Too many ANDs or ORs in expression (limit %d perexpression level). Try splitting query or limitingANDs and ORs.


405 20Cannot route query results - query internalrepresentation corrupted.


406 23Ord_needed: Can't find index for varno=%d,objid=%ld.

Explanation: The database may be corrupt. Report the error to yourSystem Administrator. Adaptive Server must be restarted and dbccdiagnostics run.

407 19You query creates too many internal work tablesand/or user tables: the maximum is %d. Simplifythe query and try again.

Explanation: Command failed when a configurable limit wasexceeded. Reconnect to Adaptive Server and perform any correctiveaction indicated by the message. Report the error to your System

Administrator.

1104



408 20Is_var: Unknown data type %d.


409 16The %s operation cannot take a %s datatype as anargument.


410 20Compute clause #%d, b y' expression #%d is not inthe order-by list.


411 20Compute clause #%d, aggregate expression #%d is notin the select list.


412 16Cannot update more than 1 sysindexes row at a time.


413 17Maximum procedure %s count exceeded. Limit is %d.Modify the procedure to use fewer %ss.



1105



414 16The current query would generate a key size of%d for a work table. This exceeds the maximumallowable limit of %d.


415 16The current query would require an index on awork table to be built with %d keys. The maximumallowable number of keys is %d.


416 16Create of work table failed because row size wouldbe %d. This exceeds the maximum allowable size of arow in a table, %d.


418 20Can't find the real column name corresponding to thecolumn heading % .*s'.


420 16TEXT and IMAGE datatypes may not be used in an ORDERBY clause.

Explanation: Check query syntax.

421 16TEXT and IMAGE datatypes may not be selected asDISTINCT.


1106



422 19Too many nested expressions or logical operators tocompile. Try splitting query or limiting ANDs andORs.

Explanation: Command failed when a configurable limit wasexceeded. Reconnect to Adaptive Server and perform any correctiveaction indicated by the message. Report the error to your SystemAdministrator.

423 20Table referenced in a foreign key constraint ismissing, database = % ` S_DBID', table = % ` S_OBJID'.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error to

your System Administrator so dbcc diagnostics can be run.

424 20Failed to enforce a referential constraint, database= %` S_DBID', table = % ` S_OBJID'.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so DBCC diagnostics can be run. (This erroris not raised in Adaptive Server 11.1 and higher.)

425 20Referencing table in a foreign key constraint ismissing, database = % ` S_DBID', table = % ` S_OBJID'.



426 20Primary key column referenced in a foreign keyconstraint is missing, database = % ` S_DBID', table =

%` S_OBJID'.


1107



427 20Referencing column in a foreign key constraint ismissing from system catalog, database = % ` S_DBID',table = % S_OBJID'.


428 20There are more than %d referential constraints ontable %.*s. Please reduce the number of referentialconstraints before trying this query.


429 18Invalid constraint type passed to compilereferential 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 toyour System Administrator.

430 18Constraint id info in the resvar for checkconstraints is missing. This is an internal error,database = % S_DBID', table = % ` S_OBJID'.


431 26Node 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 restartAdaptive Server.

432 16Security Label datatypes may not be used in an ORDERBY clause.


1108



433 17Unable to allocate work table to process referentialconstraint. Query exceeds the maximum limit (%d) ofwork tables. Either simplify the query or reducethe number of referential constraints on the tablesinvolved in the query.

Explanation: Resource error while trying to allocate worktable toprocess deferred update on a table with referential constraints. Takecorrective action described in message.

434 16Work table cannot be allocated for processing theorder by clause which requires a sort. Maximumlimit (%d) of work tables is exceeded whileprocessing this query. Simplify the query andretry.


435 16Database %.*s' is not available. The % ` s'statement will not be executed because thecross-database referential constraint on table

%` .*s' cannot be enforced. Contact your SystemAdministrator about the availability of database

%` .*s'.


436 16The %` s' statement will not be executed becausethe cross-database referential constraint on table

%` .*s' cannot be enforced. A table or constraintdefinition is missing in database % ` .*s'. Contactyour System Administrator.


1109



441 18Deadlock occurred in SQL Process %d, While accessingreferencing 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 16Maximum number of user tables under all sides of aUNION statement can not exceed %d. Please simplifythe query and retry.


444 16The index %d for the table %ld was not found indatabase %d. The index may have been dropped whilethis query was being compiled.

Explanation: Adaptive Server could not perform the requested action.Contact your System Administrator.

1110



501 20There is no result-list for a SELECT statement.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator.(Not raised in Adaptive Server 11.0 and higher.)

502 18Internal error encountered in merging rows; resubmitquery batch.

Explanation: Command failed due to internal Adaptive Server problem.

Perform any diagnostic action indicated by message. Report the error toyour System Administrator.

504 11Stored procedure %` .*s' not found.


508 20No begin-row pointer found in plan.


509 11User name %` .*s' not found.

Explanation: Command failed. Check your Adaptive Serverenvironment for the object not found and re-enter the command withthe correct name.

510 20Bad eop type 0x%x .


511 16Updated or inserted row is bigger than maximum size(%d bytes) allowed for this table.


1111



512 16Subquery returned more than 1 value. This isillegal when the subquery follows =, !=, <, <= , >,>=, or when the subquery is used as an expression.


513 16A column insert or update conflicts with a ruleimposed by a previous CREATE RULE command. Thecommand was aborted. The conflict occurred indatabase %S_DBID', table % ` S_OBJID', column %` .*s'

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby message. (Not raised in Release 11.0 and higher.)

514 20Expression stack overflow. Usually this is becausebuilt-in functions have been nested too deeply.Try to rephrase the query using less deeply nestedfunctions.



515 16Attempt to insert NULL value into column % ` .*s',table % .*s'; column does not allow nulls. Updatefails.%S_EED


516 18Attempt to get system date/time failed.


517 16Adding a value to a %s field caused overflow.


1112



518 16Cannot convert type % ` s' to type % ` s'.


519 16Overflow resulted from MONEY multiplication.


520 16Overflow resulted from MONEY division.


521 16Overflow resulted from MONEY addition.


522 16Overflow resulted from MONEY subtraction.



523 16Overflow resulted from %s minus operation.



524 16Overflow resulted from MONEY remainder (modulo)operation.


1113



526 18SQL Server has run out of alarms. Re-run yourcommand when there are fewer users running WAITFOR.

Explanation: You can increase the configuration parameter n` umberof alarms'.

527 20Cannot remove alarm.


528 20System error detected during attempt to use upsleepsystem call.


529 16Explicit conversion from datatype % ` s' to % s' isnot allowed.

Explanation: Command failed due to invalid request. Consult theAdaptive Server Reference Manual for information on datatypeconversions.

530 16Attempt to insert NULL value into column %d in worktable (table id %ld); column does not allow NULLS.UPDATE fails.


532 16The timestamp (changed to %.*s) shows that the rowhas been updated by another user.

Explanation: The command failed and no data was updated in thedatabase because an integrity check or other semantic check on thedata failed.

533 20Can't find a range table entry for range %d.


1114



534 16TEXT and IMAGE datatypes require DBLIB version 4.0or greater.


by message.

535 16Difference of two datetime fields caused overflow atruntime.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. The result of the DATEDIFFfunction may be too large.

536 16Invalid length parameter passed to the substringfunction.

Explanation: Check command syntax. There may be more constraintsto report than sp_helpconstraint can fit.

537 16Overflow resulted from a SMALLMONEY remainderoperation.


Check your command for missing or incorrect database objects, variablenames, and/or input data.

538 16%` .*s' cannot be found. This language might have

been dropped. Please contact a user with SystemAdministrator (SA) role.



539 20Unexpected internal access methods error %d,state %d. Please report to Technical Supportthe following inform ation: spid=%d, dbid=%d,objectid=%ld, curcmd=%d (%s), plasterror=%ld,pstat=0x%x, p2stat=0x%x, xactid=(%ld, %d).


1115



540 16Schema for table %` .*s' has changed sincecompilation of this query. Please re-execute query.


by message.

541 18An unknown arithmetic exception type was reported.The transaction has been aborted. This is aninternal system error. Please contact a user withSystem Administrator (SA) role.


542 16An invalid datetime value was encountered. Valueexceeds year 9999.


543 18Constraint id information not found upon constraintviolation, dbname = % ` S_DBID', table name = % ` .*s'.This is an internal error.


544 16Unknown Constraint violation occurred, database= %` .*s', table name = % ` .*s', constraint name =

%` .*s'.


1116



545 18Constraint violation occurred, entry for theconstraint missing from system catalog, database= %` .*s', table name = % ` .*s', constraint name =

%` .*s'.



546 16Foreign key constraint violation occurred, dbname= %` .*s', table name = % ` .*s', constraint name =

%` .*s'.%S_EED


547 16Dependent foreign key constraint violation in areferential integrity constraint. dbname = % ` .*s',table name = % .*s', constraint name = % ` .*s'.%S_EED


548 16Check constraint violation occurred, dbname =

%` .*s', table name = % ` .*s', constraint name =%` .*s'.%S_EED


549 18Constraint violation occurred, bad constraint typepassed to the exception handler.



1117



550 16The attempted insert or update failed because thetarget view was either created WITH CHECK OPTION orspans another view created WITH CHECK OPTION. Atleast one resultant row from the command would notqualify under the CHECK OPTION constraint.


551 20An unknown EVAL was sent to the execution module.


552 16A column insert or update conflicts with a rulebound to the column. The command is aborted. Theconflict occured in database % ` .*s', table % ` .*s',rule % .*s', column % ` .*s'.%S_EED


553 16The number of parameters/variables in the FETCHINTO clause does not match the number of columns incursor % .*s' result set.


554 16The UPDATE/DELETE WHERE CURRENT OF to the cursor

%` .*s' failed because the row has changed since itwas fetched.


1118




%` .*s' failed because the key of the row used inidentifying the row changed since it was fetched.


556 16The table referenced in the UPDATE/DELETE WHERECURRENT OF is not part of the result set tables ofcursor % .*s'.


557 16The cursor % .*s' can not be used as it could notbe found. It is possible that either it was notdeclared or it is not available in the currentcontext.


558 16Attempt to open cursor % ` .*s' which is already open.


559 16Attempt to use a cursor % ` .*s' which is not open.Use the system stored procedure sp_cursorinfo formore information.


1119



560 16The UPDATE/DELETE WHERE CURRENT OF failed for thecursor % .*s' because it is not positioned on a row.


error message.

562 16The CURINFO datastream was not sent before thecursor command so no current cursor context isavailable.


563 16There is already another cursor with the name % ` .*s'at the nesting level % ` d'.


564 16The cursor identifiers are not available.


565 16The open processing for cursor % ` .*s' did not stopanywhere. The DECLARE CURSOR could have been aninvalid statement or there is some internal problem.


566 26The procedure buffer is not linked to the procedureheader for an execute cursor % ` .*s'. This isprobably an internal system problem.

Explanation: An internal locking/synchronization rule was broken.

Report the error to your System Administrator. Shut down and restartAdaptive Server.

1120



567 14You must have the following role(s) to execute thiscommand/procedure: % .*s' . Please contact a userwith the appropriate role for help.


568 14The caller does not have the required SystemSecurity Officer (SSO) role. Please contact a userwith System Security Officer (SSO) role for help.


569 16The specified object with object ID % ` d' is notfound.


570 14Only a person with System Security Officer (SSO)role can change another person's password.


571 16Invalid user specified, password left unchanged.


572 14Invalid caller's password specified, password leftunchanged.


1121



573 16New password specified is too short. Minimum lengthof acceptable passwords is 6 characters.


by message.

574 16New password supplied is the same as the previouspassword. Please supply a different new password.


575 16Error occured in internal encryptionroutines.


576 18Access was denied into the master database.Password left unchanged.


577 18The caller of the set_password builtin was notfound! Password left unchanged.


578 18Date acquisition function failed. Unable toretrieve the correct date in the set_passwordbuiltin function. Password left unchanged.



1122



579 18Unable to start a transaction in the set_passwordbuiltin. Password left unchanged.



580 18Unable to update Syslogins in the set_passwordbuiltin. Password left unchanged.


581 18Unable to open Syslogins table in the set_passwordbuiltin. Password left unchanged.


582 16Cursor %.*s' was closed implicitly because thecurrent cursor position was deleted due to an updateor a delete. The cursor scan position could not berecovered. This happens for cursors which referencemore than one table.


583 16The cursor % .*s' had it's current scan positiondeleted either because of a DELETE/UPDATE WHERECURRENT OF or a regular searched DELETE/UPDATE. Youmust do a new FETCH before doing an UPDATE or DELETEWHERE CURRENT OF.


1123



584 16Explicit 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 thedatabase because an integrity check or other semantic check on the

data failed.

585 16Explicit value must be specified for identity fieldin table % .*s' when IDENTITY_INSERT is set to ON.


586 16Illegal identity value specified for identity field

%` .*s' in table % ` .*s'.


587 16Identity value overflow for field % ` .*s' whileinserting into table % ` .*s'.


588 20Failure adding identity column to table % ` .*s' viaselect into.


589 16Invalid role string received.


1124



590 16Dynamic SQL error - Prepared statement % ` .*s' doesnot exist.



591 16Dynamic SQL error - Prepared statement % ` .*s' isalready being used by a cursor.


592 16The DELETE WHERE CURRENT OF to the cursor %` .*s'failed because the cursor is on a join.


593 16The UPDATE WHERE CURRENT OF to the cursor %` .*s'failed because column % ` .*s' being updated was notspecified in the FOR UPDATE OF list.

Explanation: Command failed. You tried to update a column notnamed in the cursor's FOR UPDATE list.

594 16The UPDATE WHERE CURRENT OF to the cursor %` .*s'failed because column % ` .*s' being updated was notspecified in the SELECT list.

Explanation: Command failed. You tried to update a column notnamed in the cursor's SELECT list.

595 16Trying to return NULL from stored procedure for bitvariable % .*s'


1125



596 17Your query overflowed the space allocated foraligning internal data structures. Please simplifyyour query by breaking it up into a series ofshorter queries.

Explanation: Command failed due to resource limitation. Modify thecommand to fit available resources, retry when the resource is available,

or contact your System Administrator to address the resource problem.

599 16The procedure, % .*s', that cursor % ` .*s' isdeclared on has been dropped and recreated since thefirst time the cursor was opened.


1126



601 21Descriptor for system table % ` ld' in database % ` d'not found in the descriptor hash table.


602 21Could not find row in sysindexes for dbid % ` d',object % ld',index % ` d'. Run DBCC CHECKTABLE onsysindexes.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnostics

run.

603 19There are not enough system session descriptorsavailable to run this query. The maximum numberavailable to a process is %d. Split query andrerun.


604 21Could not find row in sysobjects for object % ` ld' indatabase % .*s'. Run DBCC checktable on sysobjects.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun.

605 21An attempt was made to fetch logical page % ` ld' indatabase % .*s' from cache % ` .*s'. Page belongs toobject with id % ` ld', not to object % ` .*s'.


607 21Insufficient room was allocated in the sessiondescriptor for object % ` .*s' for search arguments.Only %d search arguments were anticipated.


1127



608 0Buffer holding logical page %ld of object '%.*s' indatabase '%.*s' was not kept in the first or secondslot o f the session descriptor for that objectduring a scan.


610 19Maximum number of databases that may be accessed bya transaction is 16. This number has been exceededby this query.

Explanation: Command failed when a non-configurable limit wasexceeded. Adaptive Server could not recover gracefully. Reconnect toAdaptive Server, and report the error to your System Administrator.

611 21Attempt made to end a transaction that is idle or inthe middle of an update.


612 21Attempt 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 21Request made to retrieve more rows from an alreadycompleted 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 SystemAdministrator. Adaptive Server must be restarted.

614 21A row on page %ld was accessed that has an illegallength of %d in database % ` .*s'.


615 21Unable to find database table.

Explanation: Run dbcc checks on the database. (This error is not raisedin Adaptive Server 11.0 and higher.)

1128



616 20Attempt to hash a previously hashed descriptor forobject % .*s' in database % ` .*s'.


your System Administrator so dbcc diagnostics can be run. (Not raisedin 11.0 and higher releases).

617 20Descriptor for object % ` ld' in database % ` d' notfound in the hash table during attempt to unhash it.


618 21A varno of %d was passed to opentable - the largestvalid value is %d.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your System

Administrator. Adaptive Server must be restarted and dbcc diagnosticsrun.

619 20A deferred update was requested but the query is notone of INSERT, DELETE or UPDATE.


620 21Log record encountered at deferred update time witheither a row length of less than 2 or an invalid logtype. The log type was %d and the row length was%d.


run.

1129



621 21A log record was encountered of type %d that is notone of the valid deallocation types.



622 20Opentable was passed a varno of %d. Object % ` .*s'already has that session descriptor in use.


623 21Attempt to retrieve row from page via RID failedbecause logical page %ld is not a data page.%S_RID. %S_PAGE.

Explanation: Refer to the writeup for this error.

624 21Attempt to retrieve row from page via RID failedbecause the requested RID has a higher number thanthe last RID on the page. %S_RID.%S_PAGE.


625 21Could not retrieve row from logical page %ld via RIDbecause the entry in the offset table for that RIDis less than or equal to 0.


627 20A transaction tried to call beginupdate while instate p repare'.

Explanation: There may be a problem due to an application issuinga PREPARE statement followed by an update. Check the application

SQL code.

628 13Attempt to issue S ` AVE TRANsaction' when there is noactive transaction.

Explanation: Rerun the command that raised this error.

1130



629 21Clustered index row entry for data page %ld ismissing in index page %ld of table '%S_OBJID' indatabase '%S_D BID'; index row contains data page%ld instead. You can recreate the clustered indexto fix this error. Xactid is (%ld, %d).


630 21The end of page limit has been exceeded whilebuilding an offset table for object %ld on page %ld,page addr 0x%lx, eop addr 0x%lx, sargptr addr 0x%lx.


all processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun.

631 21The length of %d passed to delete row routine forthe row at offset %d is incorrect on the followingpage: %S_PAGE.


632 20Memmove() was called with a length of %d - maximumallowed length is 2048.


633 21The PG_DEALLOC bit set by recovery is on at runtimeon the following page. %S_PAGE.

Explanation: Report the error to your System Administrator. (Notraised in Release 11.0 and higher.)

634 20Memmove() was called with an address of 0x%lx and alength of %d - which would cross a 2k boundary.

Explanation: There is a possible Adaptive Server problem. Run dbccchecks on the database that was being accessed when the error occurred.

635 20Process %d tried to remove DES resource lock that itdoesn't hold - %S_DES .


1131



637 20Index shrink program returned invalid status of 0.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator.Run dbcc indexalloc, checktable.

638 20Memmove() was called with an address of 0x%lx -which is not allocated memory.

Explanation: There is a possible Adaptive Server problem. Run dbccchecks on the database that was being accessed when the error occurred.

639 21Attempt to fetch logical page %ld dbid %d failed -page is not currently allocated.


640 21Attempt to insert/delete row on wrong type of page.%S_PAGE.


641 21Attempt to add BEGINUPDATE record in transaction%S_RID that already has an active CMD.


642 20Attempt to begin update in transaction %S_RID whichalready has an active transaction.


1132



643 20Attempt to read page %ld in database % ` .*s' which isnot allocated.



644 21Index row entry for data row id (%ld, %d) ismissing 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.


649 21Could not find the clustered index entry for Page%ld Objid %ld status 0x%x. Index page %ld wassearched for this entry in database % ` .*s'.



650 26Page %ld, dbid %d not locked.



651 26Startscan was called with an illegal combination ofindex and scan mode.


652 20The buffer 0x%lx should be kept in sdes 0x%lx onentry to this function and it is not.



1133



653 26Buffer not rlocked. %S_BUF. %S_PAGE.


654 26Page %ld, dbid %d not exclusive locked.


655 26Page should be marked as having overflow page:%S_PAGE.


656 26Locking not stipulated while attempting to modifypage. %S_PAGE.


657 26Passed buffer pointer for previous page is for page%ld, when the actual previous page is %ld. Thesepages are in database % ` *.s'.


658 22Last log page in database % ` .*s' incorrectlyidentified as page %ld. Run DBCC checktable onsyslogs.

Explanation: Report the error to your System Administrator. (Not

raised in Release 11.0 and higher.)

1134



659 16Table id %d contains suspect indexes. This table isonly available for read-only purposes until the DBCCREINDEX command has been run on the indicated tableto rebuild its suspect indexes.


by message.

660 10Index id %d cannot be used to access table id %das it is SUSPECT. Please have the SA run the DBCCREINDEX command on the specified table.


661 21As part of a transaction rollback, an attempt wasmade to modify object % ` S_OBJID' in database % ` .*s',even though the current session is not holding anexclusive lock on that object.


662 18The index with index id % ` d' on object with objectid = %d' was not found during cursor scan fixups.The fixup was being done for cursor % ` .*s'. This isan internal error.


663 18The lock on page % d' for object with object id= %` d' could not be obtained during cursor scanfixups. The fixup was being done for cursor % ` .*s'.This is an internal error.


1135



664 18The parameters passed to cursfix_main() were notcorrect. This is an internal error.



665 18The cursor fixup is being done for the predelete case with the data row for a scan using anon-clustered index and there was no fixup done forpre-delete of the non-clustered index row. This isan internal error.


666 18The current position deleted bit is set for an SDESbut there is no fixup information saved. This is aninternal error.


667 26Illegal locking strategy encountered at scaninitialization. Object %S_OBJID, database %S_DBID.This is an internal error.


668 18The cursor % .*s' which is scanning a list of ridsi.e a work table is having it's tables changed.This cursor should be read only and the tablesshould be private to it's query. This is aninternal error.


1136



669 18The length computation of the row is wrong. Thiserror was detected during cursor scan fixups forcursor % .*s'. This is an internal error. Theprocessing is being stopped for the current query.



670 16Out of bound insert attempted on table % ` .*s'.


671 14Writetext is not allowed in reclassify mode.

Explanation: Command failed due to invalid or illegal request.Adaptive Server cannot perform the requested action. Take anycorrective action indicated by the message.

672 16Out of bound update attempted on table % ` .*s'.


673 16Out of bound delete attempted on table % ` .*s'.


674 20Invalid Buffer Cache Access: Attempt to locatepage %` ld', database % ` ld' in cache failed becausethe cache id % ld' in scan_context is invalid.scan_context={objid % ` ld', indid % ` ld', cid % ` ld'}.Contact Technical Support for assistance.


1137



675 20Invalid Buffer Cache Access: Attempt to locate page

%` ld', database % ` ld' in cache failed because noobject id was specified. scan_context={objid % ` ld',indid % ld', cid % ` ld'}. Contact Technical Supportfor Assistance.


676 21NULL cache id specified in log record.


677 20Invalid Buffer Cache Access: Attempt to locatepage %` ld', dbid % ` ld', objid % ` ld', indid % ` ld' incache failed because the cache ID was not set in thescan_context structure. Contact Technical Supportfor assistance.


678 20Invalid Buffer Cache Access: Could not open object

%` ld' in database % ` d'


679 20Inconsistent update state found during expensivedirect update of object % ` ld'.


the current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics can be run.

1138



680 20Attempt to extend the log in database % ` .*s' faileddue to an internal error. The returned status was%d.


682 20The buffer 0x%lx , page number '%ld' for object'%.*s' in database '%.*s' should be latched on entryto this f unction and it is not.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics can be run. (Version11.9.2 and higher.)

683 20Failed to get lock on data page '%ld' row '%ld' forobject '%.*s' in database '%.*s'.


your System Administrator so dbcc diagnostics can be run. (Version11.9.2 and higher.)

684 26Page %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 restartAdaptive Server. (Version 11.9.2 and higher.)

685 21Expected page %ld to be in cache % ` .*s' for objectid %ld, index id %d, database id %d. Instead, theserver brought the page into wrong cache % ` .*s'.


686 20Expected page %ld to be in cache % ` .*s' for objectid %ld, index id %d, database id %d. Instead, theserver brought the page into wrong cache % ` .*s'.

Explanation: Page %ld is corrupted. (Introduced in Version 11.9.2).

1139



688 21Insufficient CFS while redo of expanding update onpage %ld belonging to object %ld. CFS - %ld, lengthof new row - %ld

Explanation: Command failed due to internal Adaptive Server problem.Report the error to your System Administrator. (Introduced in Version11.9.2).

689 10An unexpected log record (log op %d) was encounteredwhen scanning the log for a trigger.

Explanation: Informational message. Report the error to your SystemAdministrator. (Introduced in Version 11.9.2).

690 20Pageno in lk_pglocked (%ld) different from lockobj(%ld).


691 20Encountered invalid logical page '%ld' whileaccessing object '%ld' in database '%d'. This isan internal system error. Please contact SybaseTechnical Support.

Explanation: See the writeups for Error 691 and Error 605.

692 20Uninitialized logical page '%ld' was read whileaccessing object '%ld' in database '%d'. Pleasecontact Sybase Technical Support.


693 20Multiple copies of logical page '%ld' from database'%d' reside in more than one cache. This is aninternal system error. Please contact SybaseTechnical Support.


1140



694 24An attempt was made to read logical page '%ld',virtpage '%ld' from virtual device '%d' for object'%ld' in database '%d'. The page was not readsuccessfully. You may have a device problem or anoperating system problem.


695 21An attempt was made to read logical page '%ld' forobject '%ld' in database '%d' from disk. Wronglogical page '%ld' was brought into cache '%.*s'.


696 21An attempt was made to fetch logical page '%ld' intempdb from cache '%.*s'. Page belongs to object'%ld' and not to object '%ld'. Restart of SQLServer will clear the error. Please contact yourSystem Administrator for help.


697 21An attempt was made to fetch logical page '%ld' forobject '%ld' in database '%d' from cache '%.*s'.Wrong logical page '%ld' was found in cache.


1141



698 21%d consecutive attempts failed to read buffer forlogical page '%ld' of object '%.*s' (objid: '%ld'dbid: '%d'). Page found in cache with I/O errorand in write state. Check operating system logs forpossible device problems.

Explanation: Adaptive Server encountered an internal error affecting allprocesses using the current database. Report the error to your SystemAdministrator. (Discontinued in Version 11.9.2).

699 21I/O error on buffer for logical page '%d' of object'%.*s' (objid: '%d' dbid : '%d'). Page is incache and already hashed. Contact Sybase TechnicalSupport for assistance to run 'dbcc delbuff'.

Explanation: Adaptive Server encountered an internal error affecting allprocesses using the current database. Report the error to your SystemAdministrator. (Discontinued in Version 11.9.2).

1142



701 19There is not enough procedure cache to run thisprocedure, trigger, or SQL batch. Retry later, orask your SA to reconfigure SQL Server with moreprocedure cache.


702 20Memory request for %d bytes exceeds the size ofsingle page of %d bytes.


703 17You cannot run this procedure, trigger, or SQL batchbecause it requires more than %ld pages of memory.Break it up into shorter queries, if possible.


704 20Tried to free procedure header 0x%lx, but it'sstill in use by procedure % ` .*s' at procedure buffer0x%lx.

Explanation: The problem may be due to memory corruption. Shutdown and restart Adaptive Server to clear the memory structures.

705 19There is no room for process %d to store PROC_HDR0x%lx in Pss.

Explanation: Command failed when a configurable limit was exceeded.

Reconnect to Adaptive Server and report the error to your SystemAdministrator.

706 20Process %d tried to remove PROC_HDR 0x%lx that itdoes not hold in Pss.


707 20System error detected during attempt to free memoryat address 0x%lx. Please consult the SQL Servererror log for more details.


1143



708 17There is insufficient system memory to run kerneltask. spid %d, kpid %d.



709 17There is insufficient system memory to continuelogin process for spid %d.

Explanation: See the writeup for Error 709.

710 20Memory request for %d bytes is too small.



1144



801 20Process %d tried to remove resource lock it doesn'thold on buffer 0x%lx - %S_PAGE in cache %s.

Explanation: Check the Adaptive Server error log for 1105 or othererrors. Restart Adaptive Server.

803 20Unable to place buffer 0 ` x%lx' from cache % ` .*s'holding logical page % ` ld' in sdes for object % ` .*s'- either there is no room in sdes or buffer alreadyin requested slot.


804 20Unable to find buffer 0 ` x%lx' from cache % ` .*s'holding logical page % ` ld' in sdes 0 ` x%lx' keptbuffer pool for object % ` .*s'.


805 21Unable to find descriptor for object % ` .*s' indatabase % .*s' in hash table when marking bufferdirty or flushing syslogs.


806 21Could not find virtual page for logical page %ld indatabase %S_DBID'.


807 10Logical page %ld in buffer 0x%lx already kept inSDES for object % .*s' in database % ` .*s'.

Explanation: This is an informational message but may requirefollow-up action. Contact your System Administrator. (Not raised inRelease 11.0 and higher.)

1145



808 20Alloc page buffer pool in Pss is full - logicalpages %ld, %ld, and %ld in respective databases

%` .*s', % ` .*s' and %` .*s' are already held there.Cannot add logical page %ld in database % ` .*s'.



809 20Buffer 0x%lx, alloc pg %ld, in database % ` .*s' notin alloc buf pool in Pss.


810 20Attempt to pin log page buffer.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the errorto your System Administrator so DBCC diagnostics can be run. (Notraised in Release 11.0 and higher.)

811 21Attempt to grab buffer (from cache % ` .*s') which ison descriptor chain.

Explanation: Report the error to your System Administrator. AdaptiveServer must be restarted and DBCC diagnostics run. This error occursin diagserver.

812 21Attempt to grab a pinned buffer.

Explanation: Adaptive Server encountered an internal error affectingall processes using the current database. Report the error to yourSystem Administrator. Adaptive Server must be restarted and DBCCdiagnostics run. (Not raised in Release 11.0 and higher.

813 20Logical page % ld' in database % ` S_DBID', cache

%` .*s' is already hashed.


1146



814 20Keep count of buffer 0 ` x%lx' in cache % ` .*s' holdinglogical page %` ld' in database % ` .*s' has becomenegative.


815 21Unable to find buffer holding sysindexes page in thecache - pageno = %ld dbid = %d.


run.

816 20Process %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 affectingthe current process. Reconnect to Adaptive Server. Report the errorto your System Administrator so DBCC diagnostics can be run. (Notraised in Release 11.0 and higher.

817 20Process %d tried to remove a buffer resource lock%S_BUF that it does not hold in Pss 0x%lx.



818 19There 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 SystemAdministrator.

819 19There is no room for process %d to hold bufferresource lock %S_BUF in Pss.


1147



820 21Attempt to dirty non-log buffer %S_BUF which is inI/O.



821 20Attempt to unhash buffer in cache % ` .*s' at 0 ` x%lx'with a buffer pageno of % ` ld' and database id % ` ld'with HASHED status set failed - buffer was notfound. % S_PAGE'.


822 21Could not start I/O for request BLKIO flags = 0x%lx,size = %ld, errcode = 0x%lx, %S_BUF.


823 24I/O error detected during %S_MSG for %S_BUF.


824 21Attempt made to write page in buffer in databasethat has no entry in sysdatabases. %S_BUF.


825 21Attempt made to write page in buffer in databasewith no DBTABLE structure - sysdatabases row markedas in use by process %d. %S_BUF.


1148



826 20Attempt made to hold allocation page %ld that isalready in Pss pool. Database % ` .*s'.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error

to your System Administrator so DBCC diagnostics can be run. (Notraised in Release 11.0 and higher.

827 20Attempt to dirty unkept page % ` ld' in database

%` .*s', cache % ` .*s'.


829 21A problem with ordered writes was detected. Pleasecall SYBASE.

Explanation: Adaptive Server encountered an internal error affectingall processes using the current database. Report the error to your

System Administrator. Adaptive Server must be restarted and DBCCdiagnostics run. (Not raised in Release 11.0 and higher.

830 20Invalid magic number %ld for aux kept bufferstructure 0x%x, for sdes 0x%x, object id %ld.


831 20Unable to find buffer 0x%x holding logical page%ld in sdes 0x%x, aux keep struct 0x%x, for object

%` .*s'.


832 20Unable to place buffer 0x%x holding logical page %ldin sdes for object % ` .*s' - there is no room in sdesaux keep pool.

Explanation: Adaptive Server encountered an internal error or an errordue to lack of resources. Report the error to your System Administrator.

1149



833 20Attempt to read logical page %ld, database % ` S_DBID'into buffer 0x%x that is hashed.



834 20Illegal attempt to clean buffer: %S_BUF.


835 20Illegal attempt to change contents of buffer:%S_BUF.

Explanation: Shut down and restart Adaptive Server to clear the buffer

structure.

836 21Attempted to grab lru header.


run.

837 21Attempted to grab wash header.



838 21Grabbed buffer not marked in wash: %S_BUF.



839 21Grabbed buffer dirty but not writing: %S_BUF.



1150



840 17Device %.*s' (with physical name % ` .*s', andvirtual device number %d) has not been correctlyactivated at startup time. Please contact a userwith System Administrator (SA) role.


841 10Attempt to set bufreserves in RESOURCE structure tonegative value while unclaiming cache.

Explanation: This is an informational message but may require

follow-up action. Contact your System Administrator.

842 20Attempt to set bufclaims in PSS structure forprocess %d to negative value while unclaiming cache.


843 20Unable to find original instance of buffer 0x%xholding logical page %ld for object % ` .*s'.


843 20Unable to find original instance of buffer 0 ` x%x'holding logical page % ` ld' in cache % ` .*s' forobject % .*s'.


844 20Attempt to unpredirty buffer %S_BUF which is %s.


1151



845 20Attempt to do a large I/O for page %ld in database

%` .*s' with buffer 0x%x, which is not a largebuffer.

Explanation: Reconnect to Adaptive Server. Report the error to yourSystem Administrator so DBCC diagnostics can be run. (Not raised inRelease 11.0 and higher.)

846 10Hardware error detected writing logical page % ` ld',virtual page % ` ld' for dbid % ` ld', cache % ` .*s'.The user process will sleep until write completessuccessfully.


847 10Checkpoint process detected hardware error writinglogical page %` ld', virtual page % ` ld' for dbid

%` ld', cache % ` .*s'. It will sleep until writecompletes successfully.


848 21Could not start I/O for device % ` .*s' (withphysical name % .*s', and virtual device number %d).Operating system error %d.

Explanation: Reconnect to Adaptive Server. Report the error to yourSystem Administrator so DBCC diagnostics can be run. (Not raised inRelease 11.0 and higher.)

849 21I/O error detected for device % ` .*s' (with physicalname %` .*s', and virtual device number %d).


1152



850 20Wrong cache descriptor in buffer 0 ` x%x', page % d',dbid %d'. Cache descriptor points to cache % ` .*s'.

Explanation: Internal error with a buffer pointer. Reconnect toAdaptive Server. Report the error to your System Administrator so

DBCC diagnostics can be run. (Not raised in Release 11.0 and higher.)

851 20Wrong cluster mask for cache % ` .*s', maskencountered = %d, should = %d.

Explanation: Internal error with a cache descriptor. Reconnect toAdaptive Server. Report the error to your System Administrator soDBCC diagnostics can be run. (Not raised in Release 11.0 and higher.)

852 20Command Failed: Invalid request to move % ` ld'buffers from the % ` ld'K pool of the % ` .*s' cacheto the % ld'K pool. Source pool only contains

%` ld' buffers. Retry the command specifying fewerbuffers.


853 16Invalid Configuration: Unable to start SQL Serversince no information is available for configuringthe data cache. The server may be started witha default configuration using the -c startserveroption.


by message.

854 20Fatal buffer pool error. Please contact Sybasetechnical support.

Explanation: Internal error in finding a buffer pool descriptor. Reportthe error to your System Administrator. (Not raised in Release 11.0and higher.)

855 16Bad prefetch size of %d encountered.


1153



856 16Command Failed: Cannot move buffers from the % ` ld'Kpool to the % ldK' pool. % ` ld'K pool does notexist. Please specify a valid buffer pool.


857 16Command Failed: Cannot bind or unbind database

%` S_DBID' to or from a cache because it is currentlyin use. Retry the command once all users havestopped using the database.


858 16Cache %` .*s' does not exist.


859 20Invalid Buffer Cache Access: Attempt to locatepage %` ld', database % ` ld' in cache failed becausethe cache id % ld' in scan_context is invalid.Scan_context = {objid % ` ld', indid % ` ld', cid

%` ld'}. Contact Technical Support for assistance.


860 20Invalid Buffer Cache Access: Attempt to locatepage %` ld', dbid % ` ld' objid % ` ld', indid % ` ld' incache failed because the cache ID was not set in thescan_context structure. Contact Technical Supportfor assistance.


1154



861 16Command Failed: Cannot bind object % ` ld', dbid % ` d'to cache because you have an open cursor on thetarget object. Retry the command after closing thecursor.


862 16Command Failed: Database % d' must be in singleuser mode to bind target object.

Explanation: Command failed. The database must be in single user

mode to execute this command.

863 20Buffer resources in cache %s, id %d are unavailable.Please re-run this query or ask the systemadministrator to re-configure buffer cache memory.


864 16Command Failed: Cannot bind object % ` ld', dbid % ` d'to cache because you have active level0 scans on thetarget object. Retry the command after terminatingthe scans.


865 21Error deleting row from Sysattributes during cachebinding validation.

Explanation: Adaptive Server was unable to delete an existing rowfrom sysattributes. This is an internal error affecting all processes usingthe current database. Report the error to your System Administrator.

866 21Error inserting row into Sysattributes during cachebinding validation.



1155



867 16The system table Sysattributes or its indices maynot be bound to a named cache.


by message.

868 16The system table Sysallocpg may not be bound to anamed cache.


869 21Error updating row %S_RID in Sysattributes duringcache binding validation.


run.

870 10WARNING!!! You may have to change the log I/O sizefor the database % ` .*s'. Current setting is % ` dK'and the cache % .*s' does not have a % ` dK' memorypool.


871 20Process %d is trying to release a latch on buffer0x%x (dbid: %d, pageno: %d) without holding alatch on the buffer.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics can be run. (Introducedin Version 11.9.2).

1156



872 20Process %d is trying to get a %s latch on buffer0x%x (dbid: %d, pageno: %d) while already holdinga %s latch on the buffer.


873 20Process %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.


874 20Process %d is trying to unkeep buffer 0x%x (dbid:%d, pageno: %d) without releasing the %s latch itholds on t he buffer.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the errorto your System Administrator so dbcc diagnostics can be run. This isan informational message. Unless otherwise specified, no action isrequired. Contact your System Administrator about any warning issuedin the message. (Introduced in Version 11.9.2).

875 20Could not grab a buffer to allocate a new page forlog in database id %d. Tried %d buffers, all thebuffers in the wash section are pinned to PrivaleLog Cache. See errorlog for more information.


1157



876 20The process is holding log semaphore on database %dand is about to sleep on mass=0x%x with stat=0x%xfor page=%ld which is being written by some otherprocess that needs the log semaphore. This causes adeadlock, and can only be cleared by a reboot.

Explanation: Adaptive Server encountered an internal error affectingthe current process. The System Administrator can clear the problem byrestarting the server.

877 16The '%ldK' pool in the '%.*s' cache has been markedby a previous operation as being too small andtherefore not available for use. It cannot beincreased in size until it has first been deletedusing sp_poolconfig.

Explanation: To resize a buffer pool that has been marked unavailable,you must delete and recreate the pool. (Discontinued in Version 11.9.2).

878 21Task %d was expected to hold latch on buffer 0x%x ofpage %ld in database %d.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun. (Introduced in Version 11.9.2.)

879 21Task %d was expected to hold exclusive latch onbuffer 0x%x of page %ld in database %d.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun. (Introduced in Version 11.9.2.)

1158



902 24Hardware error detected reading logical page %ld,virtual page %ld in database % ` .*s'.

Explanation: Hardware error detected. Report the error to your SystemAdministrator. The database may have to be reloaded. It may benecessary to contact your hardware vendor.

903 23Unable to find row in sysindexes for clustered indexon system catalog %d in database %d. This indexshould exist in all databases. Run DBCC CHECKTABLEon sysindexes in the database.


904 22Unable to find master database row in sysdatabases.Cannot open master database.

Explanation: A table or index may be corrupt. Report the error to yourSystem Administrator. Adaptive Server must be restarted and dbccdiagnostics run.

905 17Unable to allocate a DBTABLE descriptor to opendatabase %S_DBID'. Another database must be closedor dropped before opening this one.


906 23Could not locate row in sysobjects for systemcatalog %d in database %d. This system catalogshould exist in all databases. Run DBCC CHECKTABLEon sysindexes in the database.


908 22Unable to find any entries in sysusages for dbid

%` d', database % ` S_DBID'. Run DBCC CHECKTABLE onsysusages in the master database.


1159



909 21More than %d entries required to build thelogical-virtual translation table for database

%` S_DBID'. The database is too fragmented.


910 17Could not allocate a new object descriptor forrequired system catalog in database % ` d'. Anotherdatabase must be closed or objects in anotherdatabase dropped in order to open this database.



911 16Attempt to locate entry in sysdatabases for database

%` .*s' by name failed - no entry found under thatname. Make sure that name is entered properly.


912 21DBTABLE descriptor cannot be found for database

%` .*s' which is supposed to be already open.



913 22Could not find row in sysdatabases with database id%d. Run DBCC CHECKTABLE on sysdatabases.


1160



915 21Descriptor for system catalog % ` .*s' not foundin DBTABLE chain for database % ` .*s' - all systemcatalogs should reside permanently in this chain.


916 14Server user id %d is not a valid user in database

%` .*s'


917 20Illegal attempt to close the master database for thelast time - this database must always be open.


918 14Database %.*s' has not yet been recovered - pleasewait before accessing this database.

Explanation: Command failed. The database is not available at thistime. Wait and try again.

919 21Database %.*s' was marked s ` uspect' by an earlierattempt at recovery. Check the SQL Server errorlogfor information as to the cause.


920 22Could not find syslogs row in sysindexes fordatabase % .*s'. Run DBCC CHECKTABLE on this systemcatalog.

Explanation: There may be a corrupt table or index. Adaptive Servermust be restarted and dbcc diagnostics run.

1161



921 14Database %.*s' has not been recovered yet - pleasewait and try again.


922 14Database %.*s' is being recovered - will wait untilrecovery is finished.

Explanation: Command failed. The database is not available at this

time. Wait and try again.

923 14User %d not allowed in database % ` .*s' - only theowner of this database can access it.


924 14Database %.*s' is already open and can only haveone user at a time.


925 19Maximum number of used databases for each query hasbeen exceeded. The maximum allowed is %d.


926 14Database %.*s' cannot be opened. An earlierattempt at recovery marked it s ` uspect'. Check theSQL Server errorlog for information as to the cause.


927 14Database %.*s' cannot be opened - it is in themiddle of a load.


928 14Database %.*s' cannot be opened - it is currentlybeing created. Wait and try query again.


1162



929 21Attempting to close a database which is not open.Please contact Technical support.



930 14Database %.*s' cannot be opened because eitheran earlier system termination left LOAD DATABASEincomplete or the database is created with f ` orload' option. Load the database or contact a userwith System Administrator (SA) role.


931 21Database %.*s' cannot be opened because of afailure to initialize the global timestamp. Thisindicates that a problem exists in the log for thecurrent database. Please contact Technical supportfor assistance.


932 22Database %.*s' cannot be opened because the log forthe current database is corrupt. Page %ld of thelog is linked to a page that belongs to a databaseobject with id %ld. Please contact Technicalsupport for assistance.


933 22Logical page %ld of the log encountered whileretrieving highest timestamp in database % ` .*s'is not the last page of the log and we are notcurrently recovering that database.


1163



934 21Fatal error encountered while freeing up DBTABLEstructure.


Administrator. Adaptive Server must be restarted and dbcc diagnosticsrun. (Not raised in Release 11.0 and higher.)

934 21Fatal error encountered while freeing up DBTABLEstructure.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun. (Not raised in Release 11.0 and higher.)

935 10WARNING - the timestamp in database % ` .*s' isapproaching the maximum allowed.

Explanation: This is an informational message. Unless otherwise

specified, no action is required. Contact your System Administratorabout any warning issued in the message.

936 14The Model database is unavailable. It is being usedto create a new database.


937 14Database %.*s' is unavailable. It is undergoingLOAD DATABASE.


938 14Database %.*s' is unavailable. It is undergoingLOAD TRANSACTION.

Explanation: Command failed. The database is not available at this

time. Wait and try again.

1164



939 20Illegal dbtable unlock: %S_DBT.


940 26Dbtable in wrong state for operation: %S_DBT.


941 20Illegal database context operation.


942 20Database cannot be opened because a systemdescriptor cannot be installed.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator.

943 14Database %.*s' cannot be opened since an attempt toupgrade it was unsuccessful.

Explanation: Command failed. The database is not available, this maybe due to an upgrade failure. Contact your System Administrator.

944 20Function %s requires that the user be in thedatabase being worked on. Process %d passed it adbtable for database %d, but is using database %d.


945 21Unable to locate page %ld for database id %d in thein-memory copy of Sysusages (spid=%ld). This is aninternal error. Please contact Sybase TechnicalSupport.


1165



946 10A %S_MSG has prevented Sysusages changes fordatabase %.*s from being copied into memory. Pleaserun sp_dbremap to complete database space changes.


947 14Database %.*s' has been marked as having corruptsecurity labels. Please contact a user with theSystem Administrator, System Security Officer, orOper role or the Database Owner.


948 14Database %.*s' is unavailable. It is undergoing asecurity label consistency fix.


949 14Database %.*s' is unavailable. It is being boundto a named cache.


950 14Database %.*s' is currently offline. Please waitand try your command again later.


951 14Database identity for server user id %d changedafter permission checking in database % ` .*s'.Please try again.


1166



952 20Database '%.*s' cannot be opened because a systemindex descriptor cannot be installed.


your System Administrator so dbcc diagnostics can be run. (Introducedin Version 11.9.2.)

953 11Page '%ld', passed to curunreservedpgs built-infunction, 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-enterwith the correct parameters.

1167


Server Error Messages 1100-1199Number Severity Text and Explanation

1101 17Unable to allocate new page for database % ` .*s'.There are no more pages available on validallocation pages. Space can be created by droppingobjects, extending the database, or dumping the logwith no_log.

Explanation: Command failed due to resource limitation. Modify thecommand 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 22Unable to locate allocation page %ld for database

%` .*s'. This allocation page contains the extentthat the target allocation page is in, but theallocation page is not in the translation table inthe DBTABLE. Run DBCC CHECKTABLE on sysusages.


1103 21Allocation page %ld in database % ` .*s' has differentsegment id than that of the object to which we areallocating. Run DBCC CHECKALLOC.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun. (Not raised in Release 11.0 and higher.)

1104 20Conflict between number of extents marked in logrecord in the allocation bitmap and the allocationcount. Allocation count is %d. Bitmap is 0x%lx0x%lx 0x%lx 0x%lx.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics (dbcc checkalloc) can berun on the database.

1168

Server Error Messages 1100-1199


1105 17Can't allocate space for object % ` .*s' in database

%` .*s' because % ` .*s' segment is full. If you ranout of space in syslogs, dump the transaction log.Otherwise, use ALTER DATABASE or sp_extendsegment toincrease size of the segment.


1106 20First pass through allocation page %ld found %d freeextents. After logging, only found %d free extents.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics can be run. (Not raisedin Release 11.0 and higher.)

1108 21Cannot deallocate extent %ld, database %d. Objectid %ld, index id %d, status %d in extent does notmatch object id %ld, index id %d, status %d inobject being deallocated. Run DBCC CHECKALLOC.


1109 21Attempt to read allocation page %ld failed eitherbecause object ID is not correct (%ld) or the pageID is not correct (%ld).


run. (Not raised in Release 11.0 and higher.)

1110 20Attempt to resource lock allocation page %ld indatabase % .*s' by process %d while allocating tonon-syslogs object % ` .*s'.



1169



1111 20Extent bitmap on allocation page %ld in database

%` .*s' does not have extents marked that are beingremoved.


1112 20Extent bitmap on allocation page %ld in database

%` .*s' already has extents marked that are beingadded.


1113 20Extent %ld already locked while allocating it indatabase % .*s'.


1114 20Attempt to resource lock page %ld in database % ` .*s'by process %d failed because lock is already held byprocess %d.


1115 20Attempt to transfer a resource lock to process ID 0on allocation page %ld in database % ` .*s'.


1116 20Attempt to backout the allocation of LOG page %ld,in database % .*s'.


1170



1117 21Extent chain for object %ld is not correctly linked.


1120 20Attempt to call pg__readalloc on page %ld which isnot an allocation page.


1122 20Attempt to read allocation page before openningSYSALLOCPGS.


1123 20Failed to get lock on OAM pg.


1124 20Failed to get lock on allocation page %ld.


1125 20Attempting to allocate page %ld in database %d toextent %ld which belongs to another object. Objectid and index id in page are %ld, %ld. Object id andindex id in extent are %ld, %ld.



1127 20Internal Error: The OAM has no room for newinserts. Check OAM for object %ld, index %d.


1171



1128 22The OAM entry for allocation page %ld is missingfrom the OAM which starts on page %ld.

Explanation: A table or index may be corrupt. Report the error to yourSystem Administrator. Adaptive Server must be restarted and dbcc

diagnostics run.

1129 22The requested update to the OAM for object %ld, dbid%ld, index %d, oam page %ld, would cause a negativepage count. allocation page: %ld, oamarrayused: %ld, oamarray unused: %ld, deltaused: %ld,deltaunused: %ld, spid: %ld. Contact your SystemAdmin.


1130 22A dealloc log record has been detected which doesnot have an OAM page supplied.


1131 22The OAM for object %ld, index %d, oam page %ld,database=%d, is currently allocated to anotherobject.


1132 22Attempted to log allocation to the log.

Explanation: Report the error to your System Administrator. AdaptiveServer must be restarted.

1133 22Page %ld was expected to be an OAM page for %ld andit is not.


1134 20Failed to get lock on OAM page %ld. This shouldnever happen.


1172



1135 10Page %ld was given as a target page for allocationto object %ld index id %d and there is no entry inthe OAM for this page. This may indicate corruptionof the OAM. Please run checkalloc on database %.*s.


1136 21P` lease run the upgrade38 utility before attempting

to upgrade your database to MP.'

Explanation: Adaptive Server encountered an internal error affecting allprocesses using the current database. Report the error to your SystemAdministrator.

1137 21T` here is insufficient space in database %.*s to run

this upgrade.'


1138 21F` ailed to complete allocation of SYSGAMS in

database %.*s.'



1139 20Impossible deadlock on page mgr lock.


1140 20P` age mgr lock should not already be held.'



1173



1141 20Unexpected value returned to page manager routine:%ld.


your System Administrator so dbcc diagnostics (tablealloc, checkalloc)can be run.

1142 22Invalid OAM Page %ld. Found pstat=0x%x, object=%ld,database=%d, indid=%d.


1143 22Invalid OAM Page %ld. Expected object=%ld. Foundobject=%ld, database=%d, pstat=0x%x, indid=%d.


1144 21Page number %ld is higher than the highest page indatabase % .*s': %ld.


run.

1145 20ss %d was expected to hold logical lock on page %ld.


your System Administrator so dbcc diagnostics (checkalloc, tablealloc)can be run.

1146 20Process %d was expected to hold logical lock onobject %ld.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator so dbcc diagnostics (checkalloc, tablealloc)can be run.

1174



1147 20Process %d trying to do a logged operation on anon-logged object %ld.



1148 16Error: %d, Severity: %d, State: %dn


1149 21A Log Run Deallocation routine was passed one ormore bad parameters. The bad parameter is either%ld or %ld.


run.

1150 20Failed to get intent lock on object %ld.


1151 11Object %ld passed to OAM builtin function no longerexists in database %d.

Explanation: An OAM-related system function such as ROWCNTwas called with incorrect arguments, or called for an object which hasbeen dropped.

1152 11Page %ld passed to OAM builtin function is not anOAM page for object %ld in database %d.

Explanation: An OAM-related system function such as ROWCNT wascalled with incorrect arguments.

1175



1153 11OAM page %ld passed to rowcnt function is anunallocated page in database %d.

Explanation: Check the arguments passed to the system functionROWCNT.

1154 16WARNING!!! Attempt to do a prefetch of size %dK isnot allowed. The prefetch request is reset to themaximum prefetch size of %dK.


1155 20Invalid page validation type, %d, requested for page%ld, object %S_OBJID, indid %d in database %S_DBID.


1156 20Unable to update the page linkage status for thedata only locked table %ld in database %d due to aninternal error.



1176



1201 20lock_logical was called with illegal locktype %d.


1203 20Caller of lock manager is incorrectly tryingto release or downgrade a lock which it doesn'thold. spid=%d loc ktype=%d dbid=%d page number (orobjid for table lock)=%ld, objid (if not a tablelock)=%ld, row number=%ld.


1204 19SQL Server has run out of LOCKS. Re-run your commandwhen there are fewer active users, or contact a userwith System Administrator (SA) role to reconfigureSQL Server with more LOCKS.


1205 13Your server command (process id #%d) was deadlockedwith another process and has been chosen as deadlockvictim. Re-run your command.


1221 26Lock free chain linkage has been corrupted.


1222 26A non lock is linked on the free chain.



1177



1223 26Lock hash table linkage has been corrupted.


1224 26A structure from outside the lock area has beenlinked onto a lock hash chain.


1225 26Lock record chain linkage has been corrupted.


1226 26A non lock record is linked onto a semaphore cursor.


1227 26Semaphore cursor chain linkage has been corrupted.


1228 26A non semaphore cursor is linked onto a semaphore.


1229 26The actual number of free locks does not match thefree lock count.

Explanation: An internal locking/synchronization rule was broken.Report the error to your System Administrator. Shut down and restart

Adaptive Server.

1178



1230 26A 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 SybaseTechnical Support.

1231 26An incorrect lock structure is linked on the freechain.


1232 26An incorrect lock structure is linked onto a hashchain.


1233 26An incorrect lock structure is linked a chain oflock structures.


1234 26An incorrect lock structure is linked to asemaphore.

Explanation: An internal locking/synchronization rule was broken.Shut down and restart Adaptive Server. Report the error to SybaseTechnical Support.

1235 26A semaphore cursor at the head of a semaphore queueis marked as waiting.


1179



1236 26A semaphore cursor not at the head of a semaphorequeue is marked as not waiting.


Adaptive Server.

1237 26A semaphore cursor has mutually incompatible lockrecords linked to it.


1238 26%d locks not accounted for.


1239 26%d extra locks found.


1241 26A semaphore cursor refers to a different semaphorethan the one it is linked to.


1242 26A lock record refers to a different semaphore cursorthan the one it is linked to.



1243 26Couldn't find object to be released.


1180



1244 20Could not find address lock at address 0x%lx whiletrying to release it.

Explanation: An internal locking/synchronization rule was broken.Report the error to Sybase Technical Support.

1245 26Lock record and process disagree.


1246 26Process attempting to wait on a lock that does notbelong to it.



1247 26Process attempting to wait on a lock that hasalready been waited for.


1249 20Process became runnable before lock it was waitingfor was released.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to Sybase Technical Support.

1250 26A non-preallocated semaphore cursor encounteredwhile trying to obtain a semaphore.


1251 26An in-use preallocated semaphore cursor wasencountered.


1181



1252 26Lock header linkage has been corrupted.


1253 26The wrong number of lock records was found on asemaphore cursor.


1254 26While following the lock record chain for a process,a lock record belonging to a different process wasencountered.


1255 26Unlinking a duplicate lock caused a task to beawakened.


1256 26Encountered a non-preallocated semaphore cursor on achain that should only have preallocated semaphorecursors.


1258 26A process is not waiting for a lock that it shouldbe waiting for.


1182



1259 26A process is waiting for a lock that has beengranted.


Adaptive Server.

1260 26A process is waiting for a lock that it did notrequest.


1261 20Attempt to promote from page to table locking onobjid %ld encountered an internal error.


1262 20No matching xdes found. Lock was requested forobjid %ld, dbid %d, type %d, by process %d.


1263 26A process was found to be waiting for the sameobject twice.


1265 20A lock manager routine expected a lock record as anargument but was passed something else. lr=0x%x,lrmagic=% c.


1183



1266 20Upgrade of lock on object id or page number %ld leftthe lock ungranted.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. If the problem

persists, report it to your System Administrator.

1267 26A lock record at the head of a semaphore queue isnot marked as granted.


1268 26A lock record is marked as granted, but isn't at thehead of the semaphore queue.


1269 10Temporary buffer overflow occurred while scanningthe lock table. Rows will be missing in syslocksfor one or more objects.

Explanation: This is an informational message. A non-configurablelimit was exceeded but processing continues. No action is required.

1270 26A task attempted to release a semaphore that it hadnot previously obtained.



1271 26A task attempted to acquire a semaphore with apreallocated semaphore cursor that did not belong toit.


Adaptive Server.

1184



1272 20Invalid parameter(s) passed to lock manager.


1273 16Syntax error at line %d of file %s starting at % ` s'.


1274 16Error with input file %s: %s.


1275 16The lock unit test can only be run with a singleengine on line.


1276 26Attempt to acquire a lock in dbid %d while in aninternal transaction. This is an internal error.


1277 20In a call to lock_multiple(), the lock requests wereout of order. They should be sorted by object id,dbid.



1185



1278 26This semawait (1st) should only have one lockrec.


1279 19SQL Server has run out of locks on engine %d.Re-run your command when there are fewer activeusers, or contact a user with System Administrator(SA) role to reconfigure maximum engine freelocks ornumber of locks.


1280 26Lock sleeptask (or waittask) chain has beencorrupted.


1281 26A structure of the wrong type is linked to the locksleeptask (or waittask) chain.


1282 26An incorrect lock sleeptask structure is linked tothe Lock Sleeptask chain.


1283 19Could not change deadlock checking period becauseSQL Server has run out of alarms. Please retry thecommand later.


1186



1284 26Used Lock Sleeptask Entry not in Chain.


1285 26Un-used Lock Sleeptask Entry in Lock SleeptaskChain.


1286 26Missing Preallocated Lock Sleeptask Entry.


1287 16Freelock transfer block size (%d) cannot be morethan half the number of freelocks allowed per engine(%d). To increase the number of freelocks allowedper engine please increase maximum engine freelocks.

Explanation: See the System Administration Guide for moreinformation about m` ax engine freelocks'.

1288 16Setting maximum engine freelocks to %d allows only%d freelocks per engine. This value cannot be lessthan twice the value of freelock transfer blocksize. Please reduce freelock transfer block size to%d and reattempt this command.

Explanation: See the System Administration Guide for more

information about f` reelock transfer block size'.

1289 20Internal Error in lock manager routine: Invalidlock mode %s, requested by task (family id %d, spid%d) conflicts with existing family request mode %sbelonging to task (family id %d, spid %d).

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the error toyour System Administrator.

1187



1290 20Internal Error in lock manager routine: Attemptedlock upgrade from %s to %s in parallel query thread(family id %d, spid %d) is Illegal.


1291 20Internal Error in lock manager routine: Attemptedlock anti-inheritance is an illegal operation for anon-parent thread (fid %d, spid %d).


1292 20Internal Error in lock manager routine: Thread (fid%d, spid %d) incorrectly attempted to acquire anon-queueing %s lock when thread (fid %d, spid %d)in its family already holds an insufficient %s lockon objid %d, dbid %d.


1293 20Internal Error in lock manager routine: Process(fid %d, spid %d) incorrectly attempted to transferlocks to itself, from a process (fid %d, spid %d)belonging to a different family.


1294 26Lock_logical was called with an illegal 'op'parameter: %d.


1188



1295 26Unconditional lock request for table or page %d,dbid %d was made while holding a latch.


Adaptive Server.

1298 26Unexpected position for NKL semawait. Thisindicates a programmer error.


1299 26NKL semawait is at an improper position in thequeue.






1189



1301 16The Propagation Context Data entry could not besaved. There is already an entry with the same keyvalues for the context provided.


1302 16A Propagation Context Data value could not bereturned in parameter %d because the datatype of thereturn parameter does not match the datatype of thestored field.

Explanation: Command failed. Check the syntax of the SQL statement

calling the system function.

1303 16The second argument for this Propagation ContextData built-in command specifies the number of keyssupplied with the call. This argument must be ofdatatype i ` nteger'.

Explanation: Command failed. Check the syntax of the SQL statementcalling the system function.

1304 16This Propagation Context Data built-in functionrequires at least %d arguments.

Explanation: Command failed. Check the arguments of the SQLstatement calling the system function.

1305 16This Propagation Context Data built-in functionrequires one argument.

Explanation: Command failed. Check the arguments of the SQL

statement calling the system function.

1190



1306 16The second argument for this Propagation ContextData built-in command specifies the number of keyssupplied with the call. The value % ` d' supplied ismore than the keys given. At most % ` d' argumentsmay be keys for this call.


1307 18Internal Error in Propagation Context routines:An invalid or garbaged command 0x%x was seen bypcxt__cmdinit().


1308 18Internal Error in Propagation Context routines:pcxt__nodenew(PCXT_NODE_ENTRY) copied %d arguments,expected %d arguments.


1309 18Internal Error in Propagation Context routines: Aninvalid or garbaged node type 0x%x tried to freememory at 0x%x in pcxt__nodefree(). The request wasignored.


1310 18Internal Error in Propagation Context routines: Thememory tracking fields in the PCD resource structureare inconsistent: inuse %d, free %d. Some PCDmemory may not be reclaimed until the login sessionends.


1191



1311 18Internal Error in Propagation Context routines:An invalid or garbaged node type 0x%x was seen bypcxt__nodedup().


1312 18Internal Error in Propagation Context routines:An invalid or garbaged node type 0x%x was seen bypcxt__nodenew().


1313 18Internal Error in Propagation Context routines: Aninvalid or garbaged event type 0x%x was seen bypcxt_event().


1314 16The built-in function requested %d data fieldsas return parameters. The Propagation ContextData entry that was selected contains only %d datafields. It is an error to request more data fieldsthan exist in the entry.


1315 16Argument %d of this Propagation Context Databuilt-in command must be of datatype i ` nteger'.


1192



1501 20Sort failure


1502 20Sort Internal Error: Bad Sort Descriptor!!


1503 20Sort Internal Error: The Root page of right/leftsub-index tree is missing.


1504 20Internal Sort Error. Empty Index Page found.


1505 14Create unique index aborted on duplicate key.Primary key is %` S_KEY'


1507 10Warning: deleted duplicate row. Primary key is

%` S_KEY'

Explanation: Report the error to your System Administrator. You mayneed to increase swap space.

1508 14Create index aborted on duplicate rows. Primary keyis %S_KEY'


1509 20Row compare failure


1193



1510 17Sort failed: Out of space in database % ` .*s'


1511 20Sort 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 20Reuse 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 21Sort failed because it attempted to allocate page%ld and found that the page was busy. Buffer %S_BUFcontains a cached and referenced page with objid %ldindid %ld and status 0x%x.


1515 20Bad session descriptor for sort


1519 20Internal Sort Error. A transaction that is involvedin Parallel Sort is being redone.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Restart Adaptive Server.

1520 18Sort failed for table % ` .*s' in database % ` .*s'because internal count of used pages is incorrect.Run DBCC TABLEALLOC to correct the value.


1194



1521 18Sort failed because a table in tempdb used for theprocessing of the query had a bad data page count.Tempdb should not have been damaged.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Restart Adaptive Server.

1522 20Sort failure. Prevented overwriting of allocationpage in database % S_DBID' by aborting sort.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Run d` bcc checkdb' and check available space.

1523 20Sort failure. Prevented incorrect extentdeallocation by aborting sort.


the current process. Run d` bcc checkdb' and check available space.

1525 21Sort Failure. Rollforward of sort encounteredsort descriptor timestamps out of sequence. Oldtimestamp in log: %04x %08lx. New timestamp inlog: %04x %08lx. Timestamp in sort descriptor:%04x %08lx.


run.

1526 17Sort failure. The configure size for data cache(%.*s) is not sufficient to handle the sort buffers(%d) requested. Please reconfigure the data cacheor sort buffers and try the command again.

Explanation: Command failed due to resource limitation on thespecified data cache. Contact your System Administrator to addressthe resource issue (see System Administration Guide for help withconfiguring memory).

1195



1527 20Sort failure. Unknown exception returned frombufclaimcache: %d.



1528 21Character data comparison failure. An unrecognizedSort-Map-Element type (%d) was found in theserver-wide default sort table at SMEL entry [%d].


run.

1529 21Character data comparison failure. A list ofSort-Map-Elements from the server-wide default sorttable does not end properly. This list begins atSMEL entry [%d].


1530 16Create index with sorted_data was aborted because ofrow out of order. Primary key of first out of orderrow is %S_KEY'


1531 16The sorted_data option cannot be used for anonclustered index if the keys are not unique withinthe table. Create index was aborted because ofduplicate keys. Primary key is % ` S_KEY'.


1532 20Invalid merge page. %s on page %ld.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator sodbcc checks (tablealloc, indexalloc) can be run .

1196



1533 20Internal Sort error. Extend read returns an invalidpage. Requested pageno=%ld Read pageno=%ld.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator so

dbcc checks (tablealloc, indexalloc) can be run .

1534 20Internal Sort error: Attempt to split presortedclustered data page failed. Attempted to splitpage, pageno = %ld.


1535 20Internal Sort error: Attempt to split presortedclustered data page failed. Split page, pageno =%ld.


1536 20Internal Sort error. Presorted clustered data pageinvalid. Page, pageno = %ld, parm1 = %d, parm2 =%d.


1537 17Cannot create clustered index on partition table dueto not enough sort buffers. Configure atleast %ldsortbuf fers to create clustered index on partitiontable.


1197



1538 17Parallel degree %ld is less than required paralleldegree %ld to create clustered index on partitiontable. Ch ange the parallel degree to requiredparallel degree and retry.

Explanation: Command failed due to resource limitation. Contact yourSystem Administrator to address the resource problem.

1539 17Only %d worker processes are available when %dworker processes are required. Process aborted.


1540 10Warning: Only %d worker processes are availablewhen %d worker processes are required.

Explanation: This is an informational message.

1541 10Internal sort error: cannot allocate memory in datasampling.


1542 10Internal sort error: Too small a sample set!


1543 20Cannot create a pipe group for sorting in parallel.


1544 20Parallel Sort: Cannot initiate producers andconsumers.


1198



1545 20Parallel sort parent driver cannot send message tochild thread.



1546 20Parallel sort parent driver cannot receive messagefrom child threads.


1547 20Parallel sort parent driver error in waiting forchild threads


1548 10The Create Index is done using %s


1549 10Partition Element: %ld


1550 10Sort buffer size: %ld


1551 10Parallel degree: %ld


1552 10Number of producer threads: %ld


1553 10Number of consumer threads: %ld


1199



1554 10Number of output devices: %ld


1555 10Number of sampled records: %ld


1556 16No such message!

Explanation: Check command syntax and semantics.

1557 10Inconsistent distribution map (%d elements withoutelement information)!


1558 10Empty distribution map


1559 10The distribution map contains %d element(s) for %dpartitions.


1560 10Warning: Number of filled elements differs from thedata structure.


1561 20Producer cannot insert rows into pipe buffers.


1562 10The sort for Worktable%d is done in %s


1563 10The sort for %.*s is done in %s


1200



1564 10Psort option is not enabled in this database.Create Index will be done using Serial Sort

Explanation: This is an informational message. No action is requiredunless you wish to use parallel sort for the operation.

1565 20The database option pllsort option is not enabled inthis database. Create Clustered Index on partitiontable cannot be done using Serial Sort. Set thepllsort database option and rerun.


1566 10Warning: Attempt to create a clustered index on thepartitioned table '%.*s' with distinct key valuesless than the number of partitions. Some partitionswill be empty if the index is successfully created.


1567 20Create Index Internal Error %ld detected


1568 16Unable to find sort order. Please check sort orderID or name.


1569 17Unable to get a conversion handler for the built-insort function.

Explanation: Command failed due to resource limitation. Contact yourSystem Administrator to address the resource problem.

1570 10The generated sortkey has been truncated.


1571 10Unknown sort order ID %ld. Using binary sort orderinstead.


1201



1572 16Unknown sort order file name '%.*s' or Unicode cacheis full.


1573 16Can't open the directory $SYBASE/collate/unicode.

Explanation: Command failed due to invalid or illegal request. Checksyntax and permissions.

1574 20Begin transaction failed when attempting to updatesyscharsets sort order information.


1575 20Unable to open syscharsets table to update sortorder information.


1576 20Unable to lock syscharsets table to update sortorder information.


1577 20Update of sort order informarion in syscharsetsfailed.


1578 20Unable to insert sort order information intosyscharsets.


1579 16Error converting characters into Unicode to generatesort keys. There maybe illegal byte(s) in sourcestring, or failure to allocate memory.


1202



1580 16Unable to generate sortkey.


1581 16Create index was aborted because pages in the dataonly locked table are not linked.

Explanation: Notify your System Administrator so that dbcc diagnosticscan be run.

1582 17Failed to allocate memory for %ld auxiliary keepbuffers. Try this operation when there is enoughmemory in the procedure cache, or increase theprocedure cache memory and retry the sort operation.



1583 20Found a rowlen of %ld, from the merge, whilebuilding index on %.*s. Please contact SybaseTechnical Support.


1584 20Unable to build the parent page at level %d whilebuilding index on %.*s. Please contact SybaseTechnical Support.


1585 20Validation of datapage %ld in table %.*s failed.Please contact Sybase Technical Support.


1586 20Internal Sort Error. Attempt to hash a buffer fromcache %.*s into cache %.*s. Please contact SybaseTechnical Support.


1203



1587 20Empty buffer 0x%lx or mismatch in page or rownumber. SDES page=%ld, rownum=%ld, RID page=%ld,rownum=%ld. Ple ase contact Sybase TechnicalSupport.


1588 20Attempt to create an index with sorted data optionfailed. Please contact Sybase Technical Support.


1589 20Found bad merge type %d while merging sub-indexes.Please contact Sybase Technical Support.


1204



1601 21There are not enough u ` ser connections' availableto start a new process. Retry when there are feweractive users, or ask your System Administrator toreconfigure SQL Server with more user connections.


1602 21Unable to initialize network %d


1603 21Process priority %d invalid or no process slotsavailable



1604 21Process 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 SystemAdministrator.

1605 21Failed to open virtual socket for new connections


1606 21Failed to initialize network receive buffer


1607 21Failed to initialize network send buffer

Explanation: A problem was encountered by a client process connectingto Adaptive Server. If the problem recurs, contact your NetworkAdministrator.

1205



1608 18A client process exited abnormally, or a networkerror was encountered. Unless other errorsoccurred, continue processing normally.


1609 21Kpid %d out of range

Explanation: A problem was encountered by a client process connecting

to Adaptive Server. If the problem recurs, contact your NetworkAdministrator.

1610 21Could not kill process %d

Explanation: A problem was encountered by a client process connecting

to Adaptive Server. If the problem recurs, contact your NetworkAdministrator.

1611 21Could not install quit function

Explanation: A problem was encountered by a client process connectingto Adaptive Server. If the problem recurs, contact your Network

Administrator.

1612 21Could not install attention function

Explanation: A problem was encountered by a client process connectingto Adaptive Server. If the problem recurs, contact your Network

Administrator.

1613 21Could not close network %d connection for serverprocess %d.


1614 21Could not yield process



1206



1615 21Process unable to sleep


1616 21Failed to flush receive stream buffer

Explanation: A problem was encountered by a client process connectingto Adaptive Server. If the problem recurs, contact your NetworkAdministrator.

1617 21Could not infect process %d


1618 21Could not spawn the checkpoint process, unable tocontinue.



1619 21Could not open TEMPDB, unable to continue.



1620 21Failure to open master db for the first time



1207



1621 18Type %` c' not allowed before login.


1622 18Type %` c' not implemented.


1623 21Warning: dataserver -p option fails. Please checkfor state %` d' to see where it fails.


1624 18Warning: Errors occured while initializingthresholds on tempdb. Trying to continue thestartup. Thresholds might not be active on tempdb.


1208



1701 16Creating table % ` .*s' failed because row size wouldbe %d. This exceeds the maximum allowable size of arow in a table, %d.


1702 16Create table failed because column % ` .*s' in table

%` .*s' exceeds the maximum of 250 columns.


1703 17Failed to allocate disk space for a work table indatabase % .*s'. You may be able to free up spaceby using the DUMP TRANsaction command, or you maywant to extend the size of the database by using theALTER DATABASE command.


1704 16Only the SA can create the system table % ` .*s'.


1705 16Must create system table % ` .*s' in the MasterDatabase.

Explanation: Command failed due to invalid or illegal request, checkcurrent database. System table shown in the message should be createdin master database.

1706 16System table % .*s' was not created, because ad-hocupdates to system catalogs are not enabled.


1209



1707 18Could not create system table % ` .*s'.


1708 16Warning: Row size 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 Adaptive Server requirementas indicated in the error message.

1709 16Referenced table name missing in a referentialconstraint declaration on table % ` .*s'.


1710 16Referenced table % ` .*s' specified in a referentialconstraint declared on % ` .*s' does not exist in thedatabase % .*s'.


1711 16There is no unique constraint on the referencedcolumns in the referenced table % ` .*s' specifiedin referential constraint declaration on the table

%` .*s'.


1712 18Internal inconsistency - constraint exists insysconstraints table, but not sysobjects table, id= %d.


1210



1714 16Exceeded maximum allowed referenced columns in asingle referential constraint declaration, table =

%` .*s', database = % ` .*s'.


1715 16The number of columns in a foreign key column listand primary key/referenced column list not thesame in referential constraint declaration on table

%` .*s', in database % ` .*s'.


1716 18Invalid system table given for status update, thisis an internal error.


1717 16System catalog column/table specified for statuschange not found.


1718 16The number of columns in a forign key column listis less than a primary/referential column list in areferential constraint declaration, table = % ` .*s',data base = % .*s'.


1211



1719 16Primary key does not exist for the table referencedin a referential constraint declaration, table =

%` .*s', data base = % ` .*s'.


1720 16A column referenced in a referential constraintdeclaration does not exist, referencing table =

%` .*s', data base = % ` .*s'.


1721 16Column types of referencing and referencedcolumns don't match. referencing column = % ` .*s',referenced column = %` .*s'.


1722 16Column lengths of string type referencing andreferenced columns don't match. referencing column= %` .*s', referenced column = % ` .*s'.


1723 16Column precision and scale of numeric referencingand referenced columns don't match. referencingcolumn = %` .*s', referenced column = % ` .*s'.


1212



1724 16The number of columns in a forign key column list isgreater than a primary/referential column list in areferential constraint declaration, table = % ` .*s',data base = % .*s'.


by message.

1725 16SELECT INTO failed because column %d in table % ` .*s'has a null column name. Null column names are notallowed.


1726 18Internal inconsistency: database id %d sent tocrt_main() does not match Pss->pcurdb value of %d.


1727 20The crt_main() function is trying to put too manylock requests in the lock_requests[] array.


1729 10An object with the same name, but owned by adifferent user, is already being replicated. Thetable % .*s' is not marked as replicated.


1213



1730 10Due to an internal error the table % ` .*s' is notmarked as replicated. Please contact your SystemAdministrator (SA) for help.


1732 20Failed to reserve/initialize allocation hints spacein table % .*s'.


1734 16You cannot specify both a default value of NULL anda NOT NULL constraint for column % ` .*s' in table

%` .*s'. Retry your command with only one of thesecolumn options.

Explanation: The SQL statement is semantically incorrect. Chooseeither NULL or NOT NULL.

1736 16Cannot create auditing-related tables in anydatabase other than sybsecurity database.

Explanation: This message is generated when an SSO tries to createaudit tables in a database other than sybsecurity.

1737 16Cannot create tables starting with s ` ysaudits_'.

Explanation: This message is generated when a user tries to create a

table starting with sysaudits_. This is not allowed.

1738 16Creating this referential constraint would result inthe total number of referential constraints of table%.*s exceeding %d. Please run: 'sp_helpconstraint%.*s' to find out the number of referentialconstraints that this table has.

Explanation: Adaptive Server could not perform the requested action.(Introduced in 11.9.2).

1739 10Warning: Parameter e ` xp_row_size' is not applicableto table % .*s' in allpages locking scheme


1214



1740 10Warning: Parameter m` ax_rows_per_page' is notapplicable to table % ` .*s' in d ` atapages' or

d` atarows' locking scheme


1741 10Warning: Parameters e ` xp_row_size' and

m` ax_rows_per_page' both specified for table%` .*s'. Only parameter appropriate to lock scheme

specified will be used internally, but both arestored. 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 16Expected row size specified on table '%.*s' isinvalid. Expected row size should be either 0, 1 orbetween minrow length %d and maxrow length %d


error message.

1743 10Multiple 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 theerror message. (Introduced in 11.9.2).

1744 10Internal error: Dataonly Lock scheme is notsupported on this system table '%.*s'. Contactsybase technical support for help.

Explanation: There may be a potential problem with a database ordatabase object. Contact your System Administrator. (Introduced in11.9.2).

1750 20Failed to reserve attribute space for table '%.*s'.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator.(Introduced in 11.9.2).

1215



1751 20Failed to initialize attribute space for table'%.*s'.


(Introduced in 11.9.2).

1752 16Table '%.*s' has fixed length schema. Parameter'exp_row_size' is not applicable to tables withfixed length schema.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. (Introduced in 11.9.2).

1753 16DELETE STATISTICS failed on table '%.*s' see errorlog for more information.


1754 16DELETE STATISTICS duplicate column '%.*s' specified,column can only be referenced once.


1755 16DELETE STATISTICS column name '%.*s' not found.


1756 18syscolumns cannot be read.


Perform any diagnostic action indicated by the message. Report theerror to your System Administrator. (Introduced in 11.9.2).

1757 10UPDATE STATISTICS - could not obtain required lockson table '%.*s

Explanation: Report this error to your System Administrator.(Introduced in 11.9.2).

1216



1758 10UPDATE STATISTICS failed to complete on table '%.*s

Explanation: Report this error to your System Administrator.(Introduced in 11.9.2).

1759 16UPDATE STATISTICS number of step values requested'%d' must be greater than or equal to '%d' values


1760 16UPDATE STATISTICS - index and column list cannot bespecified at the same time


1761 13Deadlock detected on '%.*s' while processingstatistics

Explanation: Rerun the command that raised this error. (Introduced in11.9.2).

1762 18Cannot insert rows into sysstatistics

Explanation: Command failed due to internal Adaptive Server problem.Perform any diagnostic action indicated by the message. Report theerror to your System Administrator. (Introduced in 11.9.2).

1763 18Cannot insert rows into sysstatistics, due tomultiple equal frequency values, please contactSybase Techn ical Support


1217



1764 18Failed to insert row into worktable, when projectingbase table on to work table for collectingstatistics .


1765 10Unable to start a level zero scan on table '%.*s'for UPDATE STATISTICS. This can happen if some DDLcommand like ALTER/CREATE INDEX/REORG/DROP is activeon the table. (Introduced in 11.9.2).

Explanation: Retry the scan after completing the DDL command.

1218



1801 16Database %.*s' already exists


1802 11CREATE DATABASE failed. Some disk names listed incommand were not found. Check that names exist andare spelled correctly before re-running


1803 17CREATE DATABASE failed. Could not allocate enoughdisk space for a new database on the disks named inthe command. Total space allocated must be at least%d Mbytes (%ld 2048-byte pages) to accommodate copyof Model Database.


1804 10There is no disk named %` .*s'. Checking other disknames.


1805 10CREATE DATABASE: allocating %ld pages on disk % ` .*s'


1806 21Crdb_dbrow: Getnext SCAN_NOINDEX onsysdatabases.dbid failed to find row for MODELDBID.


1219



1807 17MODEL database in use, cannot create new database.Contact a user with System Administrator (SA) rolebefore re-running CREATE DATABASE.


1808 21Crdb_disk: Getnext SCAN_NOINDEX onsysdevices.status=DEFAULT failed to find defaultrows


1809 14CREATE DATABASE must be preceded by a U` SE master'command. Check with your DBO <or a user withSystem Administrator (SA) role> if you do not havepermission to USE master.


1810 16CREATE DATABASE failed because of incorrectlyspecified or unavailable space. Total number ofmegabytes specified and available must be at least%d megabytes so Model Database can be copied to thenew database.


1811 16%` .*s' is the wrong type of device for CREATE or

ALTER database. Please check sysdevices. TheCREATE or ALTER is aborted.


1813 16Cannot open new database % .*s'. CREATE DATABASE isaborted.


1814 10Problem creating Temporary Database - if out ofspace, please extend and reboot. If some otherproblem, please contact Technical Support.


1220



1816 16CREATE or ALTER DATABASE failed because the device'%.*s' has no space available either for log or fordata.


1817 16Problem allocating extents for SYSGAMS. Create/alterdatabase is aborted.


1818 17CREATE DATABASE failed because the device % ` .*s' isnot online.



1820 20This command adds %S_MSG space to disk % .*s', whichpreviously contained only %S_MSG. You must specifyWITH OVERRIDE to force this allocation.

Explanation: Adaptive Server encountered an internal error affectingthe current process. In order to mix data and log space take corrective

action as indicated in the error message.

1822 16Invalid database maxhold provided.


1823 16Invalid label provided. Dbmaxhold must be dominatedby your maxwrite.


1221



1824 16Invalid label provided. Dbmaxhold must dominateyour minwrite.


by message.

1825 14Invalid curwrite label for creating sybsecuritydatabase, label must be DATA_HIGH.


1827 14You need SA authorization to create databasesybsystemdb.

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.(Discontinued in 11.9.2).

1828 16Cannot create sybsecurity with the log segment andthe default segment on the same device.

Explanation: An SSO tried to create the sybsecurity database withdefault segment and log segment on the same device.

1829 16CREATE DATABASE failed because there is no spaceleft on any of the data disk(s) specified.

Explanation: CREATE DATABASE failed because there is no space lefton any of the specified data disk(s).

1222



1901 16Column %` .*s' -- Can't create index on a column ofBIT data type.


1902 16Cannot create more than one clustered index on table

%` .*s'. Drop the existing clustered index % ` .*s'before creating another


1903 16%d is the maximum allowable size of an index.Composite index specified is %d bytes.


1904 16Cannot specify more than %d column names for indexkey list. %d specified.


1905 21Could not find z ` ero' row for index % ` .*s' the tablein sysindexes.


1906 11Cannot create an index on table % ` .*s', because thistable does not exist in database % ` S_DBID'.


1907 10Create index on non-empty table not supported yet



1223



1908 16Too many parameters -- symbol table overflow.


1909 16Can't use duplicate column names in index key list.Column name %` .*s' listed more than once.


1910 16Cannot create more than %d indexes on one table.


1913 16There is already an index on table % ` .*s' named

%` .*s'


1914 16Cannot create index on object % ` .*s' because it isnot a user table.


1915 14Only the owner of table % ` .*s' or a user with SystemAdministrator (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 16CREATE INDEX options %s and %s are mutuallyexclusive.


1224



1918 10Non-clustered index (index id = %d) is beingrebuilt.

Explanation: This is an informational message. Unless otherwisespecified, no action is required. Contact your System Administrator

about any warning issued in the message.

1919 16Column %` .*s' -- Can't create index on a column ofTEXT or IMAGE data type.


1920 16A column in a primary key constraint's column listis not constrained to be not null, column name:

%` .*s'.


1921 16An index with the same columns in the same orderalready exists on the table % ` .*s'.


1922 16An unknown index creation error occurred: %d.


1923 16A table cannot have more than one primary key,attempt to define a second primary key failed ontable % .*s'.


1225



1924 16You cannot create an index on the sysaudits table.


1927 25Create Index failed because user curwrite level isnot equal to the level of table % ` .*s'.


1928 16Cannot create clustered index '%.*s' on '%.*s' whichhas %d partitions because the maximum number ofpartitions allowed on a table with clustered indexis %d.


1929 20Failed to reserve/initialize allocation hints spacein index % .*s' on table % ` .*s'.


1930 16Cannot specify more than %d column names for indexkey list. %d specified. Check sp_dboption fornonunique index option, it has added an extra keyfor indentity coulumn.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby message. (Discontinued in 11.9.2).

1931 16You cannot re-create the same non-clustered index(ID %d) for object ID %ld in database % ` .*s' becauseyou dropped it twice in a single transaction.Transaction rolled back.

Explanation: For a database which has been marked for d` dl in tran', anon-clustered index cannot be re-created if it has already been droppedtwice within a transaction.

1226



1932 16You cannot re-create the same clustered index forobject ID %ld in database % ` .*s' more than once in asingle transaction. Transaction rolled back.

Explanation: For a database which has been marked for d` dl in tran',a clustered index cannot be re-created more than once within atransaction.

1933 12The object % .*s' is not a partitioned table.UPDATE PARTITION STATISTICS can only be run onpartitioned tables.

Explanation: (Introduced in 11.9.2).

1934 16Invalid partition number %d. Valid partition numberis a positive integer.

Explanation: Re-try the query using a valid number. (Introduced in11.9.2).

1936 10Warning: Clustered index '%.*s' has been created onthe empty partitioned table '%.*s'. All insertionswill go to the first partition. To distribute thedata to all the partitions, re-create the clusteredindex after loading the data.

Explanation: This is an informational message. Take the indicatedaction if you wish to distribute data across partitions. (Introduced in11.9.2).

1937 10Warning: Clustered index '%.*s' has been createdon the partitioned table '%.*s' with %d partitionsusing the segment %d with %d devices. For completeI/O parallelism, each partition should be on aseparate device.

Explanation: This is an informational message but may requirefollow-up action. Contact your System Administrator. (Introduced in11.9.2).

1227



1938 16Cannot create index or unique constraint becausecursor '%.*s' is still open. Close the cursor(s)before creating index or constraint.

Explanation: Re–try the query after taking the indicated action.(Introduced in 11.9.2).

1939 16Cannot create a clustered index with sorted_dataoption on the 11.0 partitioned table '%.*s'. Thisoption isn't allowed. To create the index do notuse this option.

Explanation: Re–try the query using the recommended action.(Introduced in 11.9.2).

1940 16Cannot create clustered index on table '%.*s'because there are one or more isolation level 0scans, or RE ORG command, active on the table.

Explanation: Retry the command after the scans are complete.(Introduced in 11.9.2).

1941 10Warning: Clustered index '%.*s' has been createdwith ignore_dup_row on table '%.*s', which usesdata-only locking. ignore_dup_row cannot beenforced for subsequent insertions and updates.

Explanation: This is an informational message but may requirefollow-up action. Contact your System Administrator. (Introduced in11.9.2).

1942 16You cannot drop and re-create the same clusteredindex with sorted data for object ID %ld in database'%.* s' in a single transaction. Transaction rolledback.

Explanation: Adaptive Server could not perform the requested action.Modify your command to meet the Adaptive Server requirement for theobjects or variables shown in the error message. (Introduced in 11.9.2).

1228

Server Error Messages 2000–2099

Server Error Messages 2000–2099Number Severity Text and Explanation

2001 10Cannot use duplicate parameter names. Parametername %` .*s' listed more than once.


2002 10Cannot use variable % ` .*s' without first declaringit.


2004 16Procedure % .*s' has already been created with groupnumber %d - create procedure with an unused groupnumber



2005 18Maximum procedure %s count exceeded. Limit is %d.Modify the procedure to use fewer %ss.


2007 11Cannot add rows to sysdepends for the current storedprocedure 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 16The object % .*s' is not a procedure so you cannotcreate another procedure under that group name.


2009 16Group number not allowed in ESP creation.

Explanation: You cannot use group numbers when creating extendedstored procedures. (Introduced in 11.9.2)

1229



2010 16A procedure by that name already exists.

Explanation: Use a different name for the new procedure. (Introducedin 11.9.2)

2011 16System stored procedures (that is, stored proceduresbeginning with 'xp _' or 'sp_' and which are ownedby the dbo) can only be created in either 'master'or 'sybsystemprocs'.

Explanation: You tried to create a system stored procedure in a databasethat does not allow it. You must use master or use sybsystemprocs, and re-tryprocedure creation.

1230



2103 16Cannot create a trigger on a view, name: %.*s


2106 11Cannot create a trigger on table % ` .*s', becausethis 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 16Cannot CREATE TRIGGER on table %.*s',because youcan only create a trigger on a table in the currentdatabase.


2109 16Cannot CREATE TRIGGER on table %.*s', that accesses

i` nserted' or d ` eleted' because the table wascreated with the no_log option


2110 20The proccreate() function is trying to put too manylock requests in the lock_requests[] array.


1231



2111 16Create trigger aborted. User's cuwrite is not equalto the hurdle of table % ` .*s'.


by message.

2112 16Cannot CREATE TRIGGER on table %.*s', because it isa system table. Triggers are not allowed on systemtables.

Explanation: Triggers are not allowed on system tables. Check yourquery and working database context.

1232



2201 16Could not open file/device %s unix errno=%d. Checkmode of db file.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby the message. (Introduced in 11.9.2)

2202 21Could not translate virtual read address to deviceand seek vaddr=0x%x. (Introduced in 11.9.2)


2203 24Could not seek to vaddr 0x%x for read. Fd=%d errno=%d.

Explanation: Hardware error detected. Report the error to your SystemAdministrator. The database may have to be reloaded. It may be

necessary to contact your hardware vendor. (Introduced in 11.9.2)

2204 24Could not read complete record. Count=%d fd=%derrno =%d.,

Explanation: Hardware error detected. Report the error to your SystemAdministrator. The database may have to be reloaded. It may benecessary to contact your hardware vendor. (Introduced in 11.9.2)

2205 21Could not translate virtual write address to deviceand seek vaddr=0x%x.

Explanation: Adaptive Server encountered an internal error affecting allprocesses using the current database. Report the error to your SystemAdministrator. (Introduced in 11.9.2)

2206 24Could not seek to vaddr 0x%x for write. Fd=%d errno=%d.

Explanation: Hardware error detected. Report the error to your SystemAdministrator. The database may have to be reloaded. It may benecessary to contact your hardware vendor. (Introduced in 11.9.2)

1233



2207 24Could not write complete record. Count=%d fd=%derrno =%d.


necessary to contact your hardware vendor. (Introduced in 11.9.2)

2208 21Tried to read unopened device vaddr=0x%x.


2209 21Tried to write unopened device vaddr=0x%x.


2210 16Tried to write database without using -w or -W flag.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby the message. (Introduced in 11.9.2)

1234



2301 19Operating System allocation call failed.

Explanation: Command failed when a non-configurable limit wasexceeded. Reconnect to Adaptive Server and report the error to yourSystem Administrator. (Introduced in 11.9.2)

1235



2401 11Character set conversion is not available betweenclient character set % ` .*s' and server character set

%` .*s'.


2402 16Error converting client characters into server'scharacter set. Some character(s) could not beconverted.


2403 10WARNING! Some character(s) could not be convertedinto client's character set. Unconverted bytes werechanged to question marks ( ? ` ').



2404 18Buffer overflow converting characters from clientinto server's character set.


2405 18Internal error occurred while converting characters.


2406 16Cannot use SET CHAR_CONVERT ON, since this sessionhas never had codeset conversions turned on.


1236



2407 17Cannot use the requested character set since thecharacter set cache is full.



2408 11Cannot find the requested character set inSyscharsets: id = %d.


2409 11Cannot find the requested character set inSyscharsets: name = %` .*s'.


2410 18Unexpected error returned from the Character SetManager: return value = %d.


2411 10No conversions will be done.


2412 10Existing character conversions (if any) will remainin effect.



2414 10Since only 7-bit ASCII characters are allowed withthe special character set a ` scii_7', the languagefor this session is being forced to u ` s_english'.



1237



2415 10Due to previous errors, the language for thissession is being forced to u ` s_english'.



2416 10Due to codeset conversion errors in the remoteservername/password list of the LOGINREC, remoteprocedure calls to other servers may not work.


2417 11Unable to use Unicode-based character set conversion- client character set '%.*s' and server characterset '%.*s' are incompatible.

Explanation: Command failed. Check syntax and your Adaptive Serverenvironment. (Introduced in 11.9.2)

2418 11Unable to load Unicode-based character setconversion table '%.*s' - table not found.


2419 11Unable to load Unicode-based character setconversion table '%.*s' - the conversion table iscorrupted. Please notify your system administrator.


2420 17Unable to load Unicode-based character setconversion table '%.*s' - Unicode conversion cacheis full. Please notify your system administrator toadd mode unicode buffers.


command to fit available resources, retry when the resource is available,or contact your System Administrator to address the resource problem.(Introduced in 11.9.2)

1238



2421 11Unable to use Unicode-based character set conversion- The requested character set is not supported: id= %d.


2422 11Unable to use Unicode-based character set conversion- The requested character set is not supported:name = '%.*s'.


2423 18Unexpected 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 theerror to your System Administrator. (Introduced in 11.9.2)

2424 16TEXT data not supported when data size is changingbetween the '%.*s' and '%.*s' character sets due tocharacter set conversion. The conversion ratio is%d:%d. Please connect again with conversions off,or use client-side conversions.

Explanation: (Introduced in 11.9.2)

2425 18Unable to use Unicode-based character set conversion- Can not get conversion handle for server's defaultcharacter set. Please check server's error logfile.

Explanation: Command failed due to internal Adaptive Server problem.Perform any diagnostic action indicated by the message. Report theerror to your System Administrator. (Introduced in 11.9.2)

2426 10LONGCHAR datatype not allowed on output becauseclient does not support it.


specified, no action is required. (Introduced in 11.9.2)

1239



2427 10LONGCHAR datatype not allowed on output becauseunicode conversions have not been enabled. Pleasesee the System Administrator for asistance.

Explanation: This is an informational message. Unless otherwisespecified, no action is required. (Introduced in 11.9.2)

2428 10Unrecongnized server or client unilib character setID. Expansion factor is set to 1.


2429 10No matched unilib character set ID for the server orclient character set ID. Expansion factor is set to1 .


1240



2501 16Table named %.*s not found; check sysobjects


2502 16Table Corrupt: A page is linked in more than onechain; check this page:page number=%ld allocationstatus=%d


2503 16Table 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)


2504 16Table Corrupt: The index id in alloc page does notmatch the index id in sysindexes (alloc page#=%ld;extent id=%ld; index id in alloc=%d; index id insysindexes=%d)

Explanation: There may be possible corruption in a database or adatabase object. Take any corrective action indicated by the message.Consult the Adaptive Server System Administration Guide and theTroubleshooting Guide.

2505 16Table Corrupt: Free offset in page header is notreasonable; free offset should be >= %d and <= %d;check this page and offset (page#=%ld freeoffset onthe page header=%ld)


2506 16Table Corrupt: The values in adjust table shouldbe in ascending order starting from the end of thetable (page#=%ld row#=%d); check adjust table inthis row


1241



2507 16Table Corrupt: Offset table is incorrect (page#=%ldrow#=%d offset in offset table is=%d correct offsetis=%d)


2508 16Table Corrupt: Row length is incorrect (page#=%ldrow#=%d minimum row length=%d row length=%d)


2509 16Table Corrupt: The row number and offset of eachrow in the page should have a matching entry in rownumber table; check this page (page#=%ld row#=%doffset in row number table=%d)


2510 16Key mismatch between index page %ld (row %d)and data page %ld in database % ` .*s'. Drop andre-create index id %d of table % ` .*s'.


2511 16Keys of index id %d for table % ` .*s' in %S_MSG %ldshould be in ascending order. Drop and re-createthe index in database % ` .*s'.


2512 16Table Corrupt: The specified row number %d in indexpage %ld cannot be found on data page %ld


2513 16Table Corrupt: Object id %ld (object name =%S_OBJID) does not match between %.*s and %.*s


1242



2514 16Table Corrupt: Type id %ld (type name = %.*s) doesnot match between %.*s and %.*s


2516 16Table Corrupt: Segment number %d does not matchbetween %.*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 theTroubleshooting Guide.

2517 16Table Corrupt: Procedure id %ld (procedure name =%S_OBJID) does not match between %.*s and %.*s


2518 16Database Corrupt: Incorrect last checkpoint insyslogs

Explanation: This message is generated when dbcc checkcatalog detectscorruption in the syslogs table of a database. Collect dbcc output andreport the error to Sybase Technical Support.

2519 16Database Corrupt: The last checkpoint insysdatabases is incorrect. Syslogs recorded adifferent checkpoint


2520 16Database named %.*s not found; check sysdatabases


2521 16Table Corrupt: Page is linked but not allocated.Run DBCC TABLEALLOC to correct the problem. (allocpage#=%ld, extent id=%ld, logical page#=%ld, objectid in extent=%ld, index id in extent=%ld, objectname=%S_OBJID)


1243



2522 16Table Corrupt: The object id %ld (object name =%.*s) in page# %ld is different from the object id%ld (object name = %.*s) in sysindexes


2523 16Table Corrupt: Page number %ld is out of range forthis database %S_DBID. The maximum page number inthis database is %ld

Explanation: There may be possible corruption in a database or adatabase object. Collect dbcc output and report the error to SybaseTechnical Support.

2524 16Table Corrupt: Row length is inconsistent betweenthe computed row length and the recorded rowlength on page; check the following page and row:pageno=%ld row#=%d computed row length=%d row lengthon page=%ld


2525 16Table 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)


2526 16Incorrect DBCC command: Please see the SQL ServerReference Manual for DBCC commands and options.


2527 10DBCC detected internal database inconsistancy;contact a user with System Administrator (SA) role.


1244



2528 10DBCC execution completed. If DBCC printed errormessages, contact a user with System Administrator(SA) role.


2529 16Table Corrupt: Attempted to get page %ld, object%ld; got page %ld, object %ld.


2531 16Table Corrupt: Index id on extent should be 0;check the following page and ids: alloc page=%ldextent=%ld index id on extent=%d

Explanation: There may be possible corruption in a database or adatabase object. Takeany corrective action indicated by the message.Consult the Adaptive Server System Administration Guide and theTroubleshooting Guide.

2532 16Table Corrupt: No syslogs entry in sysindexes.


2533 16Table Corrupt: Incorrect index key length %d ininternal (sarg) structure.


2534 16Table Corrupt: No keys found on index page %ld.Offset for the free space: (freeoff=%ld)


1245



2535 16Table Corrupt: Page# %ld belongs to object id %ld(object name = %.*s) not object id %ld (object name= %.*s)


2536 10Checking %.*s


2537 10Checking %ld.


2538 10Alloc page %ld (# of extent=%ld used pages=%ld refpages=%ld)


2539 10Total (# of extent=%ld used pages=%ld ref pages=%ld)in this database



2540 16Table Corrupt: Page is allocated but not linked;check the following pages and ids: allocationpg#=%ld extent id=%ld logical pg#=%ld object idon extent=%ld (object name = %S_OBJID) indid onextent=%ld


1246



2541 16Table Corrupt: object id does not match betweenextent in allocation page and sysindexes; check thefollowing extent: alloc pg#=%ld extent#=%ld objectid on extent=%ld (object name = %.*s) object id insysindexes=%ld (object name = %.*s)


2542 16Table Corrupt: Extent is linked in more than onechain. Check the following allocation page andextent: alloc pg#=%ld extent#=%ld status=%d



2543 16Table Corrupt: Extent structures are linkedincorrectly; check the following extent: allocpg#=%ld extent#=%ld previous extent# on thisextent=%ld previous extent should be=%ld


2544 16Table Corrupt: Extent id %ld on allocation pg# %ldhad object id %ld (object name = %.*s) on but usedbit off


2545 16Table Corrupt: Extent#=%ld on allocation pg#=%ldwas used but object id was 0,


2546 16Table Corrupt: Extent id %ld on allocation pg# %ldhas objid %ld and used bit on, but reference bitoff.


1247



2547 16Table Corrupt: Segment number %d specified for usein the segment map in sysusages has no entry insyssegments. The entry in sysusages is for dbid %d(db name = %S_DBID), with a virtual starting addressof %ld.

Explanation: Run dbcc checkcatalog, collect dbcc output and report theerror to Sybase Technical Support.

2548 16There is no default segment specified insyssegments.

Explanation: Information in syssgements may be corrupt. Run dbcccheckcatalog, collect dbcc output and report the error to SybaseTechnical Support.

2549 16There is more than one default segment specified insyssegments.

Explanation: Information in syssgements may be corrupt. Run dbcccheckcatalog, collect dbcc output and report the error to SybaseTechnical Support.

2550 16Missing segment in sysusages segmap.


2551 10The following segments have been defined fordatabase %d (database name %S_DBID).


2552 10virtual start addr size segments

Explanation: This is a message header. (Introduced in 11.9.2)

2553 10-------------------- --------------------------------


2554 10%ld %ld


1248



2555 10%d


2556 20Page #%ld of sysindexes in database %d not found incache after read.


2557 14Only the owner of object % ` .*s' or a user withSystem Administrator (SA) role can run DBCC %s onit.


2558 16Extent not within segment: Object %ld, indid %dincludes extents on allocation page %ld which is notin segment %d.


2559 16Data page number %ld is empty but is not the firstpage. Status = 0x%x.


2560 16Incorrect parameter passed to DBCC command.


2561 16Unable to open log for database %d.


2562 16%s cannot access object % ` .*s' because it is not atable.


1249



2563 14Only the DBO of database %S_DBID or a user withSystem Administrator (SA) role can run the DBCCCHECKCATALOG command.


2564 14Only the DBO of database %S_DBID or a user withSystem Administrator (SA) role can run the DBCCCHECKDB command.


2565 14Only the DBO of database %S_DBID or a user withSystem Administrator (SA) role can run the DBCCCHECKALLOC/CHECKGAM command.


Have the database owner or a user with SA role run this command.

2567 14Only the DBO of database %S_DBID or a user withSystem Administrator (SA) role can run the DBCCDBREPAIR command.


2568 16Page %ld is out of range for this database


2570 10Warning - Page %ld has DEALLOC bit on - indid %d,status 0x%x


1250



2571 14Permission denied. Only a user with SystemAdministrator (SA) role can use the DBCC command

%` .*s'.


2572 10Database %S_DBID' is not in single user mode- may find spurious allocation problems due totransactions in progress.


2573 16Database %.*s' is not marked suspect. You cannotdrop it with DBCC.


2574 16Index page number %ld is empty. Status = 0x%x.

Explanation: There may be possible corruption in a database or adatabase object. Take any corrective action indicated by the message.

Consult the Adaptive Server System Administration Guide and theTroubleshooting Guide.

2575 16The last page %ld in sysindexes for table % ` .*s' hasnext page # %ld in its page header. The next page #should be NULL. Please check sysindexes.


database object. Takeany corrective action indicated by the message.Consult the Adaptive Server System Administration Guide and theTroubleshooting Guide.

2576 16The %S_MSG page %ld specified in sysindexes fortable % .*s' can not be found. Please checksysindexes.


database object. Takeany corrective action indicated by the message.Consult the Adaptive Server System Administration Guide and theTroubleshooting Guide.

1251



2577 16The root page %ld in sysindexes for table % ` .*s' hasnext page # %ld and previous page # %ld in its pageheader. Both the next page # and the previous page# should be NULL. Please check sysindexes.

Explanation: There may be possible corruption in a database or adatabase object. Takeany corrective action indicated by the message.


2578 16The first page %ld in sysindexes for table % ` .*s'has previous page # %ld in its page header. Theprevious page # should be NULL. Please checksysindexes.


2579 10The total number of data pages in this table is %ld.


2580 16The clustered index page (%S_PAGE) has an unexpectedkey pointer to an overflow data page (%S_PAGE).Please check page status.


1252



2581 16Data page (%S_PAGE) indicates that an overflow pageis linked to it; however, the next page (%S_PAGE)has not been marked as an overflow page. Pleasecheck page status.



2582 16Data page (%S_PAGE) has been marked as an overflowpage; however, the previous page (%S_PAGE) does notindicate that there is an overflow page linked toit.


2583 10Number of data pages counted by DBCC differs fromcount in the data OAM.


2584 16The last key in the previous page (%S_PAGE) is equalto the first key in the current page (%S_PAGE);however, the status of current page does notindicate that it is an overflow page.



2585 16The 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 pageindicates that there is a disconnected overflowpage.


1253



2586 16The last key in the previous page (%S_PAGE) is equalto the first key in the current page (%S_PAGE);however, the status of previous page indicates thatthere is no overflow page.



2587 16The last key in the previouse page (%S_PAGE) isnot 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 thatthere is no disconnected overflow page.



2589 16Object % .*s' must have its status updated insysobjects, to reflect the intent of repairing theindex on it.


Contact your System Administrator.

2590 16DBCC option available for system tables only.


2591 16Could not find index row which has id %d for table

%` .*s'.


1254



2592 10%s index successfully restored for object % ` .*s' in

%` .*s' database.



2593 10There are %d rows in %ld pages for object % ` .*s'.


2594 16Invalid index id specified (index id = %d).


2595 16Database %.*s' must be set to single user modebefore executing this command.


2596 16%S_PAGE has an incorrect pgfreeoff value of %d. Theoffset should be %d.


2597 16The database is not open. Please issue a u ` se %.*s'and re-run the DBCC command.


1255



2598 16Indexes on sysobjects and sysindexes cannot berecreated.

Explanation: You cannot recreate the indexes on these system tables.

2599 16Invalid monitor group specified: % ` .*s'. Pleasere-enter.



1256



2601 14Attempt to insert duplicate key row in object % ` .*s'with unique index % ` .*s'%S_EED


2603 21No space left on logical page %ld of index % ` .*s'for object %` .*s' when inserting row on index page -this situation should have been taken care of whiletraversing the index.


2610 22Could not find leaf row in nonclustered index % ` .*s'page %ld that corresponds to data row from logicaldata page %ld, row offset %d during update indexattempt after data page split in dbid %d.


2613 20Attempt to remove resource lock on buffer holdinglogical page %ld failed - the buffer was notresource locked.


2615 14Attempt to insert duplicate row in table % ` .*s' withindex %.*s' in database % ` .*s'. Could drop andrecreate index with ignore duprow or allow duprow.


2616 20Buffer holding logical page %ld cannot move to slot1 since buffer holding logical page %ld is alreadythere.


1257



2617 20Buffer holding logical page %ld not found in keeppool in SDES for object % ` .*s'



2618 20Couldn't find dupkey group starting at offset %d onpage %ld.


2619 20Keys did not match overflow page when inserting rowat 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 wheninserting a data row into a clustered index overflow page. Report theerror to your System Administrator so dbcc diagnostics can be run.

2620 21The offset of the row number at offset %d does notmatch the entry in the offset table of the followingpage: %S_PAGE.


2621 20Process %d already has the buffer we are using foran allocation resource locked: %S_PAGE.


2622 21Insufficient room on this page to insert a row oflength %d. %S_PAGE.


run.

1258



2623 21The PG_DEALLOC bit is on in this page at runtime -should have been turned off by deallocating page inrecovery. %S_PAGE.


2624 21Insert into table %S_DES fails because rowlength %dis less than minlen %d.



2625 20Deadlock encountered in log allocation for database

%` .*s'. This state should not be reached.


2626 21Illegal attempt to insert duplicate key row inthe clustered index for object % ` .*s' in database

%` .*s'.


2627 22Non-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 yourSystem Administrator. Adaptive Server must be restarted and dbcc

diagnostics run. (Discontinued in 11.9.2)

1259



2628 21In database % .*s', page %ld is linked forward topage %ld, but that page is linked backward to page%ld. Please report this internal error to SybaseTechnical Support.



2629 21Invalid length for index row: database % ` S_DBID',table % S_OBJID', indid: %d, indmaxlen: %d,indminlen: %d, row length: %d, data rid: %S_RID,xactid: %S_RID.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator. Adaptive Server must be restarted and dbcc diagnosticsrun. (Discontinued in 11.9.2)

1260



2701 10Database name %.*s' ignored, creating table inTempdb.


2702 16Database %.*s' does not exist.



2703 16Segment %` .*s' does not exist.


by message.

2705 16Column names in each table must be unique. Columnname %` .*s' in table % ` .*s' is specified more thanonce.


by message.

2706 11Table %.*s' does not exist.


2710 16You are not the owner specified for the object named

%` .*s' in this command (CREATE, ALTER, TRUNCATE,UPDATE STATISTICS, or BULK INSERT). The databaseowner can use the SETUSER command to assume theidentity of another user.


1261



2714 16There is already an object named % ` .*s' in thedatabase.


2715 16Can't find type '%.*s'.


2716 16Can't specify a length or scale on type '%.*s'.


2717 16Specified length is too large for type '%.*s'.


2718 16Column or parameter #%d: -- can't specify Nullvalues on a column of type BIT.



2719 14You must be the owner of table '%.*s' or a SystemAdministrator to update the table's statistics.


2721 11Could not find a default segment to create the tableon. Contact a user with System administrator (SA)role to specify a default segment in syssegments.

Explanation: Command failed. Check syntax and your Adaptive Serverenvironment.

1262



2724 10Parameter % .*s' has an invalid data type.

Explanation: An invalid datatype was specified for a table columnor stored procedure parameter when creating the object. Check SQLsyntax.

2727 11Cannot find index % ` .*s'.


2728 21Could not find sysobjects row for table % ` .*s'.


2729 16Procedure % .*s' group number 1 already exists inthe database. Choose another procedure name orprocedure number.


2730 11Cannot create procedure % ` .*s' with a group numberof %d because a procedure with the same name and agroup number of 1 does not currently exist in thedatabase. Must CREATE PROCEDURE %` .*s';1 first.


2731 16Column or parameter #%d: -- can't specify columnwidth of zero for % ` .*s'.



1263



2732 16User error number %ld is invalid. Number must bebetween %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 16User name %.*s does not exist in sysusers.


2735 16Object text is too long - can only support 255 rowsin syscomments. Shorten the object text or splitinto multiple objects. Text which caused overflowstarts at: % ` .*s'.

Explanation: QL Server could not perform the requested action.Rewrite the command to conform to the requirement specified in theerror message.

2736 16Owner name that was specified is a group name.Objects cannot be owned by groups.


2737 16Message passed to %s must be of type CHAR orVARCHAR.


2738 16A table can only have one timestamp column. Sincetable % .*s' already has one, you can't add thecolumn %` .*s'.



1264



2739 16TEXT and IMAGE datatypes are invalid for parametersor local variables.


by message.

2740 16SET LANGUAGE failed because % .*s' is not anofficial language name or a language alias on thisSQL Server.

Explanation: Command failed. Use sp_helplanguage and see theAdaptive Server Reference Manual for help with language maintenance.

2741 16SET DATEFORMAT date order %` .*s' is invalid.

Explanation: Command failed. See the Adaptive Server ReferenceManual for help with dateformat.

2742 16SET DATEFIRST %d is out of range.

Explanation: Command failed. See the Adaptive Server ReferenceManual for help with datefirst.

2743 16%s command requires %S_MSG parameter.


2744 16Index distribution page was %ld, now %ld. Perhapsanother UPDATE STATISTICS command is currentlyrunning. Retry your command.


2745 16%s command is missing an argument positionspecifier.


1265



2746 16Duplicate position specifier in format string of %scommand.


by message.

2747 16Incorrect position specifier in format string of %scommand.


2748 16Message number %d, passed to RAISERROR, does notexist in Sysmessages.


2749 16Number of argument position specifiers in %s commandis greater than the number of arguments passed.


2750 16Can not have more than %d arguments in a call to %s.


2751 16%s command failed because the resulting stringexceeded the maximum length of %d bytes.


1266



2752 20The PRINT/RAISERROR function received an illegaldatatype of % s'.



2753 20Received an error code of % ` d' from

i` ntl_strblist()'.


2754 16There is an argument position specifier that is outof range in a call to %s. Valid argument positionspecifiers must be in the range from 1 to %d.



2756 16Specified type precision %d more than the maximumprecision %d.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions.

2757 16Specified scale %d more than the specified precision%d.


2758 16Resdom says that column or parameter has noarguments but the length is non-zero. Given length%d.


2759 10Internal error: illegal tree encountered.


1267



2760 10Column name %` .*s' does not exist in target table.


2761 10Failed to create declarative constraints on table

%` .*s' in database % ` .*s'.


2762 16The %` s' command is not allowed within amulti-statement transaction in the % ` .*s' database.


2763 16An attempt to grant CREATE TABLE permission toPUBLIC in tempdb failed.


2764 16Identity field % ` .*s' must be a numeric with a scaleof 0 and not null allowed.

Explanation: QL Server could not perform the requested action.


2765 16A table can only have one identity column. Sincetable % .*s' already has one, you can't add thecolumn %` .*s'.


by message.

1268



2766 16Cannot use logsegment to create a user table or anindex.


by message.

2767 16The table with id=<%ld> in dbid=<%d> does notexist. It may have been created in a concurrentlyrunning transaction that rolled back and is nowinaccessible.


2768 16SET label (CURREAD, CURWRITE) failed because newvalue is an invalid label, or new value doesn'tsatisfy the dominance relationships among sessionlabels.

Explanation: An invalid label was encountered in s` et curread' or s` etcurwrite' command.

2769 16Invalid maxhold label specified for the table.


2770 16Invalid minhold label specified for the table.


2771 16Invalid hold label specified. A table's maxholdlabel should always dominate it's minhold label.


by message.

1269



2772 16Invalid hold label specified. Only labels belowyour @@maxwrite are acceptable.


by message.

2773 16Invalid hold label specified. Only labels aboveyour @@minwrite are acceptable.


2774 16Hold label provided is above database maxhold.Please provide a label below the database maxhold.


2775 20Object is not a table, or table has NULL maxholdand/or minhold value.


2776 16The s` et update_mode' command only takes in a CHARor VARCHAR argument.


2777 16Invalid update_mode provided. The only allowableupdate modes are: reclassify, over_range, andstandard.


1270



2778 12The object % .*s' is not a table. Update statisticscan be used only on user tables or system tables

Explanation: UPDATE STATISTICS can only be run on a table. Theoperation is illegal for other objects.

2779 20Lock request count has overrun the lock requestarray boundary. This is an internal error.


2780 20maxlen (%d) is less than length (%d)


2781 18Internal Error. Master to DB SLID conversionfailed.


2782 16An untyped variable in the PREPARE statement % ` .*s'is being resolved to a TEXT or IMAGE type. This isillegal in a dynamic PREPARE statement.


2783 14The user's curwrite needs to be at the table'shurdle when updating a table's statistics.


2784 18Internal row labeling error occured.


1271



2786 16MAX_ROWS_PER_PAGE value of %d is invalid. It mustbe between 0 and %d.


by message.

2787 16Cache, %s, cannot be found in sysconfigures.


2790 16Setting maximum online engines to %d causes numberof engine freelocks (%d) to fall below half thevalue of freelock transfer block size (%d). Pleaseincrease maximum engine freelocks to %d andreattempt this command.


2792 16Cannot change curread label with open cursors.Please contact a user with System Security Officer(SSO) role for help.


2793 16User error number %ld is of invalid type. Numbermust be an integer.


2794 16SET PROCESS_LIMIT_ACTION { ABORT | QUIET | WARNING }failed because '%. *s' is not a valid parameter.


1272



2795 10The value of 'parallel_degree' ( % ` d') cannot belarger than the value of configuration parameter'max parallel degree' ( % ` d'). The value '%d' isused for 'parallel_degree'.

Explanation: This is an informational message. No action is required.(Introduced in 11.9.2).

2796 16The values of 'parallel_degree' and'scan_parallel_degree' cannot be less than zero.

Explanation: Command failed due to invalid or illegal request.(Introduced in 11.9.2).

2797 10The value of 'parallel_degree' ( % ` d') cannot belarger than the value of 'parallel_degree' set by acalling procedure. The value '%d' is used.

Explanation: This is an informational message. No action required.


2798 10The value of 'scan_parallel_degree' ( % ` d') cannotbe larger than the lesser of the configurationparameter 'max scan parallel degree' ( % ` d') andcurrent 'parallel_degree' ( % ` d'). The value % ` d' isused for 'scan_parallel_degree'.

Explanation: This is an informational message. No action required.(Introduced in 11.9.2).

1273



2801 20Bad procedure status: 0x%x.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator.(Not raised in Release 11.0 and higher.

2802 20Both the tree and plan pointer are set; Ambiguousprocedure.


the current process. Report the error to your System Administrator.(Not raised in Release 11.0 and higher.

2803 20Bad pointer encountered during remapping: 0x%x.



2804 20Stored procedure %` .*s' is out of sync with its ownprocedure header.


2805 20Bad pointer 0x%lx encountered while remapping storedprocedure % .*s'. Must re-create procedure.


2806 20Stored procedure %` .*s' is corrupted. Mustre-create procedure.


1274



2807 18Process %d could not unlock stored procedure % ` .*s'because the procedure is not currently locked bythat process.


2808 18Incorrect object structure returned from getobject.


2809 18The request for %S_MSG % .*s' failed because % ` .*s'is a %S_MSG object.


2810 18Cache reports negative usage count for procedure

%` .*s'.


2811 18Cannot create procedure dbid %d, objid %ld, with agroup number of %d.


2812 16Stored procedure %` .*s' not found. Specifyowner.objectname or use sp_help to check whether theobject exists (sp_help may produce lots of output).


1275



2813 20Procedure %.*s in procedure buffer 0x%lx notproperly linked with procedure header 0x%lx.


(Not raised in Release 11.0 and higher.

2814 20Procedure %.*s in procedure buffer 0x%lx does notcontain the same object id as procedure header0x%lx.


2815 20Procedure %.*s in procedure buffer 0x%lx containspage address 0x%lx which is not aligned on a 2Kboundary.


2816 20Procedure %.*s in procedure buffer 0x%lx containspage address 0x%lx which is not within any memorymap.


2817 20Procedure %.*s in procedure buffer 0x%lx containspage address 0x%lx which should be allocated.


2818 20You must provide both name and object id in order toinstall a procedure.


1276



2819 20You must provide both name and object id in order toremove a procedure.



2820 20You must provide procedure buffer to remove theprocedure %.*x.


2821 16You must drop and recreate procedure %.*s.

Explanation: Command failed. Take indicated corrective action. Youmay need to drop/recreate triggers, rules and defaults for the table.

2822 20Bad version number encountered for procedure %.*s.



2823 20Process %d tried to remove a PROC_BUF 0x%lx named

%` .*s' that it does not hold in the hold procedurelinked list.


2824 19Process %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, ordefault at a time.


1277



2825 20Process %d tried to remove a PROC_BUF 0x%lx named

%` .*s' that it does not hold.



2826 20Process %d has held the PROC_BUF 0x%lx named % .*s'in the hold procedure linked list already; Checkyour procedure cache.


2827 20Procedure % .*s' in procedure buffer 0x%lx is notproperly hashed.


2832 17There are no more available procedure buffers.Configure your system for more.


2833 26While cleaning up descriptor for object %d, aprocedure buffer was found in use (use count = %d)


2834 26Expected to find procedure buffer with usage countof %d and not %d.


1278



2835 16The procedure tree is old. Use the sp_remapprocedure to remap all the procedures in thisdatabase.


2836 26The cursor % .*s' is already tracking anotherprocedure. This is an internal error.


2837 16The object % .*s' must be recompiled. Use

s` p_recompile %.*s', then rerun your command.



2838 16Invalid procedure name

Explanation: Attempted to execute a stored procedure withoutspecifying a procedure name. (Not raised in Release 11.0 and higher.)

2841 16The text for the object '%.*s' is missing insyscomments. This object can not be accessed.

Explanation: Check syntax and object name. (Introduced in 11.9.2).

1279



2901 19Exception stack limit (%d) exceeded.


2902 10Simulating error %d, state %d, at line %d in file%.*s.



2903 20While processing an exception, another exceptionoccurred, which could result in some internalresources not being released.



1280

Server Error Messages 3000 — 3099

Server Error Messages 3000 — 3099Number Severity Text and Explanation

3001 21DUMP DATABASE for database %` .*s' failed:insufficient memory to allocate backout structure.


3003 20DUMP DATABASE failed to establish a connection tothe Backup Server. Attempt to dump database % ` .*s'has failed.

Explanation: Check the Backup Server error log. Check that BackupServer is running.

3004 14You must be the DBO of database %.*s or haveOperator (OPER) role to run DUMP DATABASE.


3005 10DUMP DATABASE failed to end flushlistsynchronisation. In database % ` .*s', sometransactions may be suspended and further DUMPDATABASEs blocked, requiring reboot of theSQLServer.


3008 17There is not enough server memory available tocomplete this dump database.

Explanation: Command failed due to resource limitation. Modify thecommand to fit available resources, retry when the resource is available,or contact your System Administrator to address the resource problem.(Introduced in 11.9.2).

1281



3013 24An I/O error was detected while doing I/O on diskbuffer 0x%x, for page %ld, dbid %d.


necessary to contact your hardware vendor. (Not raised in 11.9.2).

3015 10WARNING: In order to LOAD the master database, theSQL Server must run in single-user mode. If themaster database dump uses multiple volumes, you mustexecute sp_volchanged on another SQL Server at LOADtime in order to signal volume changes.


3016 17DUMP DATABASE for %` S_DBID' cannot continue becauseof insufficient log space. Free some log space withDUMP TRANSACTION or turn off replication.


1282



3101 16Database in use. A user with System Administrator(SA) role must have exclusive use of database to runload.


3102 16Specified file % ` .*s' is not in valid dump databaseformat.


3103 17LOAD DATABASE for database %.*s' failed:insufficient memory to allocate backout structure.


3105 16Data on dump will not fit into current database.Need %d Mbyte database.


3108 16LOAD DATABASE must be used in single user mode iftrying to restore the Master database.


3109 16This dump was created from the Master database. Adump from Master can only be loaded as part of theRestore Master procedure.

Explanation: Load failed. To check that you are using the correct dump,run load with listonly=full.

3110 14You must be the DBO of database %.*s or haveOperator (OPER) role to run LOAD DATABASE.



1283



3111 16This dump was not created from the Master database.Master can only be loaded from a dump of the Masterdatabase.

Explanation: Load failed. To check that you are using the correct dump,run load with listonly=full.

3112 16Cannot load any database other than Master whenserver in single-user mode.


3113 21Database %.*s does not have an entry in SYSUSERS forthe DBO.


3114 21Database %.*s does not have an entry inSysdatabases.


3115 10User %.*s in database %.*s has suid %d, which isthe same as the suid of the DBO (as defined inSysdatabases). User %.*s will be given suid %d.


3116 10When all load transactions have been completed fordatabase %.*s, user %.*s should be given a uniquesuid.

Explanation: This is an informational message but may requiredfollowup action.

1284



3117 10Database %.*s already has a user with suid %d.Please call Technical Support.


3118 16LOAD DATABASE has been interrupted by a USERATTENTION signal. A LOAD DATABASE must be completedin this database before it will be accessible.

Explanation: A database maintenance operation failed. Take anycorrective action indicated by the message. Check the Adaptive Servererror log.

3120 16The database you are attempting to LOAD was DUMPedunder a different sort order ID (%d) or characterset ID (%d) than the ones running on this server(SortOrd = %d, CharSet = %d). If the sort ordersdiffer, at least one of them is non-binary.


3121 16Index %s.%s (objid = %ld, indid = %d) may beinvalid. It uses CHAR or VARCHAR columns in itskey 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 betweenthe time that the database was dumped and loaded back in again; itmay also be caused by using dump and load between different servers.Drop and re-create the index.

3122 21Failed to patch the transaction log for database

%` .*s'.



1285



3123 16The dump header contains an invalid dump type code:%ld. This is not a valid transaction log dump ordatabase dump.


3124 10This is a %S_MSG dump of database ID %d, name

%` .*s', from %S_DATE_LONG. SQL Server version:%.*s. Backup Server version: %.*s.


3125 10Database contains %ld pages; checkpointRID=(%S_RID); next object ID=%ld; sort orderID=%d, status=%d; charset ID=%d.


3126 10Log 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; %ldpages deallocated; requires database with %ld pages.


3127 10All dumped pages have been loaded. SQL Server isnow clearing pages above page %ld, which were notpresent in the database just loaded.


1286



3128 10SQL Server has finished clearing database pages.


3129 10Failed to clear in-load status bit for database

%` .*s'.


3130 16Database maxhold label found in dump is an invalidsecurity label. Discontinuing load.


3131 16Database hurdle label found in dump is an invalidsecurity label. Discontinuing load.


3132 16Server Data Low label found in dump is an invalidsensitivity label. Discontinuing load.

Explanation: A database maintenance operation failed. Take any

corrective action indicated by the message. Check the Adaptive Servererror log.

3133 16Server Data High label found in dump is an invalidsensitivity label. Discontinuing load.


1287



3134 10Security label consistency check failed. Pleaserun DBCC SECURITY (LABEL_CHECK, %` S_DBID', {FULL |NOREPORT}, FIX) after all loads have been performedin order to make this database usable.


3135 10Please run DBCC SECURITY (LABEL_CHECK, , [FULL |NOREPORT], FIX) after all loads have been performed.


3136 10Database log version=%d; database upgradeversion=%ld.


3137 10Use the ONLINE DATABASE command to bring thisdatabase online; SQL Server will not bring it onlineautomatically.

Explanation: After a load sequence completes, you must use 'onlinedatabase' to bring the database back online. This command alsoupgrades databases.

3138 10User defined role '%.*s' used in database '%.*s'does not exist in this server. Use CREATE ROLE tocreate this role after the database online.

Explanation: After onlining the database upon completion of a loadsequence, a role is found to be missing from the server. Create the rolenow for consistency.

1288



3139 10The user name, '%.*s', in SYSUSERS is the sameas a role name in this Server. See the SecurityAdministration Guide for information on how toresolve this naming conflict.


3140 10The group name, '%.*s', in SYSUSERS is the sameas a role name in this server. See the SecurityAdministration Guide for information on how toresolve this naming conflict.


1289



3201 16No dump device has been specified.


3202 16Received MULTARG is not for device name as expected.


3203 16Backup Server has detected a SQL Server error.


3204 16User aborted DUMP or LOAD for database % ` S_DBID'.


3205 26DUMP failed in database % ` S_DBID': attempt to addrun to full run list.



3206 20Backup Server has returned an unexpected status toSQL Server: %d.


3207 16More parameters have been specified to DUMP or LOADthan can be passed to the Backup Server.


1290



3208 16Unexpected end of file while reading beginning ofdump. Please confirm that dump media contains avalid SQL Server dump. The SQL Server error log maycontain more information on the problem.

Explanation: A database maintenance operation failed. Take anycorrective action indicated by the message. Check the Adaptive Server

error log.

3209 16%` .*s' is not a DUMP or LOAD device. Please check

sysdevices.


3210 20DUMP or LOAD of database %.*s' encountered lockdenial on SYSDEVICES to prevent deadlock. Deadlockshould not have been possible.


3211 20DUMP failed in database %.*s: error occurredexecuting RPC.


3212 17DUMP failed in database %.*s: unexpected statusexecuting RPC: %d.


3214 21%s: virtual page %ld does not belong to any validdisk device.


1291



3216 10Backup Server session id is: %ld. Use this valuewhen executing the s ` p_volchanged' system storedprocedure after fulfilling any volume change requestfrom the Backup Server.

Explanation: This is an informational message. See the writeup forError 3216.

3217 20%s for database % .*s' failed to write the dumpheader.


3218 21%s for database % .*s' failed to write the dumptrailer.


3219 21The Backup Server encountered an invalid dumptrailer page, so SQL Server is not able to correctlyrecover database %` .*s'. Because of this error, thedatabase is now suspect.


3220 17Could not establish communication with Backup Server

%` .*s'. Please make sure that there is an entry inSysservers for this server, and that the correctserver is running.


1292



3221 20Could not install a function required to create a%s; returned error code is %ld.



3222 20Attempt to write a %S_MSG failed; returned errorcode is %ld.


3223 20Attempt to read a %S_MSG failed; returned error codeis %ld.


3224 20INTERNAL ERROR: function % s' was passed an invaliddump type code: %d.


3225 21I/O failed while attempting to clear pages startingat page %ld of disk number %ld.


3226 21Attempt to allocate a %s failed -- there are noneavailable. SQL Server is unable to clear unusedpages in the database being loaded. Because of thiserror, the database is unusable.


1293



3227 10No extent-sized buffers were available, so pagesare being cleared by writing each page separately.Please be patient; %ld pages are being written,which may take a substantial amount of time. (Roughestimate: %ld minutes.)


3228 17Insufficient contiguous SQL Server memory toallocate DB disk status array; %d bytes wererequired.


3229 10For logical disk device % ` .*s', primary device

%` .*s' is not active. Secondary device % ` .*s' willbe used.


3230 24For logical disk device % ` .*s', neither primarydevice % .*s' nor secondary device % ` .*s' is active.%s cannot continue.

Explanation: Hardware error detected. See the writeup for Error 3230.

3231 20Invalid disk side token: %d.


3232 17For logical disk device % ` .*s', %S_MSG physical diskdevice % .*s' has become unmirrored since the startof %s. Resulting work is invalid.


1294



3233 17%s for database % S_DBID' failed: an alarm functioncould not be installed.



3234 20%s for database % S_DBID' failed to remove alarmwith ID = %d.


3235 20For logical disk % ` .*s', %S_MSG physical deviceis internally designated DB device for %s, butSysdevices.status value 0 ` x%x' conflicts.


3236 10Remirroring the affected portions of the usage mapthat are on mirrored devices.


3237 20%s failed to find disk status entry for virtual page

%` ld'.


3238 20Internal I/O error on %S_MSG pysical device onvirtual page number % ` ld' while %s was remirroringloaded database.


1295



3239 17%s could not allocate a large IO buffer. Try againlater.



3240 20Unable to obtain the SQL Server's current workingdirectory. The SQL Server must have searchpermission on its current working directory and thename must be shorter than %d bytes.


3241 20Unable to get IO access type for device % ` .*s'.


3242 20Internal sensitivity label inconsistency encounteredduring dump. Conversion of Data High, DataLow, database maxhold, or database hurdle tohuman-readable string failed.


3243 10Loading a dump from a non-B1 SQL Server into a B1SQL Server is not allowed.

Explanation: The dump you are trying to load may not be compatiblewith your Server version.

3244 20%s failed for database % ` S_DBID' with an internaltransaction logging system failure; returned errorcode is %ld.


1296



3246 18Unable to update the sysdatabases.dumptrdate columnfor dbid %d. The next DUMP TRANSACTION on thedatabase will automatically correct this.

Explanation: The database DUMP TRANSACTION date could notbe updated.

3247 16%s for database '%.*s' failed: connection to %S_MSGfailed. %S_MSG may have been shut down with nowait, or killed with an operating system command.

Explanation: Check that the remote server is running. (Introduced in11.9.2).

1297



3301 21Invalid log record found in syslogs (logop %d).


3303 21Failed to find SAVEPT in log for xact %S_RID,current number is %d, looking for %d.


3305 21Page %ld in database % .*s' read in during runtimeor load xact was uninitialized.


3306 21Process %d was expected to hold logical lock on page%ld instead of process %d.


3307 21Process %d was expected to hold logical lock on page%ld in database %S_DBID for object %S_OBJID, indexnumber %d.


1298



3308 21Page %ld was expected to have %s lock on it.


3309 21While in backout, process %d was chosen as deadlockvictim while waiting for a resource lock on page%ld.


3310 21Cannot find log record with RID: (%ld, %d).


3311 22No space left on page %ld to move data of %d length.


3312 22Free offset %d is invalid on page %ld.


3313 10Error while redoing log row in database % ` S_DBID'.%S_RID.


1299



3314 10Error while undoing log row in database % ` .*s'.%S_RID.


3315 21While redoing a transaction, the end of the log wasencountered before the endxact record.


3316 21While redoing a transaction, an attempt to reget anXCMD row failed.


run.

3317 16ROLLBACK TRIGGER can only be executed when atrigger is executing. It may be called directly bythe trigger, or from a stored procedure executeddirectly or indirectly from a trigger.


3318 21Failed to start a scan on syslogs, Error number %ld

Explanation: Adaptive Server encountered an internal error affecting allprocesses using the current database. Report the error to your SystemAdministrator. (Introduced in 11.9.2).

1300



3401 21Rec_init: getnext SCAN_RID of last checkpointfailed on Rid from sysdatabases. %S_RID.


3403 22During recovery initialization, page %ld wasencountered. This page belongs to object %ld, notthe log.


3404 21Rec_complete: Could not open controlling database(id %d) of controlling database in multi-dbtransaction.


3405 10Recovering database %` .*s'.


3406 10%d transactions rolled forward.


3407 10%d transactions rolled back.


3408 10Recovery complete.


1301



3409 10Roll forward transaction % ` .*s'.


3410 10Roll back transaction % ` .*s' -- was aborted.

Explanation: This is an informational message. See the writeup forError 3410.

3411 10Roll back transaction % ` .*s' -- no e ` ndtransaction'.


3412 21Database %d, table %ld. Attempt to mark table assuspect. Getnext SCAN_CLUST on sysobjects.objidfailed.


3413 21Database %d. Attempt to mark database as suspectfailed. Getnext NC scan on sysdatabases.dbidfailed.


3414 10Database %.*s' (dbid %d): Recovery failed. Checkthe SQL Server errorlog for further information asto the cause.


1302



3417 21Cannot recover the master database, exiting.


3418 21Not enough deses to open %` .*s'.


3419 16Unable to proceed with the recovery of dbid <%d>because of previous errors. Continuing with thenext database.


3421 21Unable to recover database % ` .*s' because of afailure to initialize the global timestamp. Thisindicates that a problem exists in the log for thecurrent database. Please contact Technical supportfor assistance.



3423 21Error recovering database % ` .*s' - could not findexpected BEGIN TRANSACTION record at location:%S_RID.


1303



3424 21No more room in transaction table for transaction(%ld, %d).



3425 21Transaction (%ld, %d) not found in transactiontable.


3426 10Could not make log consistent during specialrecovery of database %d. Please contact Technicalsupport for assistance.


3429 21Error recovering database % ` .*s' - could not connectto commit service to check completion status ofxact: %S_RID.


3430 16Could not add a checkpoint record during specialrecovery of database %d. If you intend to doupdates in this database, first free up space byrunning DUMP TRANasction WITH NO_LOG, and thencheckpoint the database.


3431 10Could not build an allocation map for the database%.*s. It does not have a DBINFO structure


1304



3433 16Name is truncated to % ` .*s'. The maximum namelength is %d.


error log.

3434 20Cannot change sortorder. Server shutting down.Restart to continue with sortorder unchanged.

Explanation: A database maintenance operation failed. RestartAdaptive Server and take any corrective action indicated by themessage. Check the Adaptive Server error log.

3435 20Sortorder cannot be changed because user objects oruser databases exist.


3436 20Cannot rebuild index %d for the % ` .*s' table in the

%` .*s' database.


3437 10Please run sp_dbupgrade in database %.*s to updatesystem catalogs.


3438 21Function %s was called by process %d, which is notthe recovery process.



1305



3439 10Database %S_DBID' has inconsistent security labels.Disabling use of database.


3440 10System stored procedures are not currentlyaccessible due to a recovery error. Pleaseconsult the errorlog. You may need to drop andre-create the sybsystemprocs database and re-runthe installmaster SQL script if the error isunrecoverable.


3443 16Invalid log version found for database % ` S_DBID':

%` d'. A log version greater than % ` d' is from anlater, incompatible version of SQL Server. Databasecannot be opened.


3444 10Database %.*s' is now online.


3445 10SQL Server could not bring database % ` .*s' online.


3446 16You do not have privilege to bring database % ` .*s'online.


3447 10Database %.*s' appears to be in the process ofbeing loaded; SQL Server will not bring it onlineautomatically. Use the ONLINE DATABASE command tobring this database online.


1306



3448 10Database %.*s' appears to be at an older revisionthan the present installation; SQL Server willassess it, and upgrade it as required.


3449 10Database %.*s': beginning upgrade step: %S_MSG %s[ID %d]


3450 20Database %.*s': upgrade item %d contains a badaction identifier, %d. Please report this internalerror to Sybase technical support.


3451 20Database %.*s': upgrade has failed for thisdatabase. Please refer to previous messages for thecause of the failure, correct the problem and tryagain.


3452 20Database %.*s': upgrade item %d depends on item%d, which could not be installed. Please refer toprevious messages for the cause of the failure,correct the problem and try again.


3453 20Database %.*s': upgrade failed to open table %d.This table should exist in every database.


3454 10Database %.*s': SQL Server could not completelyupgrade this database; upgrade item %d could not beinstalled.


1307



3455 20Database %.*s': SQL Server could not find itsinternal description of system table % ` .*s'. Pleasereport this internal error to Sybase technicalsupport.



3456 20Database %.*s': during an upgrade, SQL Servercould not create table % ` .*s'.


3457 20Database %.*s': the dependency list for upgradeitem %d contains an invalid identifier, %d. Pleasereport this internal error to Sybase technicalsupport.


3458 20Database %.*s': upgrade was asked to locatecolumn %` .*s' for table % ` s'; this column does notexist. Please report this internal error to Sybasetechnical support.


3459 20Database %.*s': upgrade could not determine thename of table ID % d'. Please refer to previouserror messages to determine the problem. Fix theproblem, then try again.


1308



3460 20Database %.*s': upgrade could not record theinstallation of upgrade item % ` d'. Please refer toprevious error messages to determine the problem.Fix the problem, then try again.

Explanation: A database maintenance operation failed. RestartAdaptive Server and take any corrective action indicated by the

message. Check the Adaptive Server error log.

3461 20Database %.*s': upgrade could not install requiredupgrade item % d'. Please refer to previous errormessages to determine the problem. Fix the problem,then try again.


3462 10Database %.*s': upgrade could not install optionalupgrade item % d'. Please refer to previous errormessages to determine the problem. Upgrade willcontinue.


3463 20Database %.*s': upgrade was asked to create anindex on table %` s'; this table does not exist.Please report this internal error to Sybasetechnical support.

Explanation: A database maintenance operation failed. Restart

Adaptive Server and take any corrective action indicated by themessage. Check the Adaptive Server error log.

3464 20Database %.*s': upgrade item %d has a bad format:info=%d, data='%s'. Please report this internalerror to Sybase technical support.

Explanation: A database maintenance operation failed. Restart

Adaptive Server and take any corrective action indicated by themessage. Check the Adaptive Server error log.

1309



3465 20Database %.*s': upgrade could not locate a rowin systypes with usertype=%d and type=%d. Pleasereport this internal error to Sybase technicalsupport.

Explanation: A database maintenance operation failed. RestartAdaptive Server and take any corrective action indicated by the

message. Check the Adaptive Server error log.

3466 20Database %.*s': upgrade could not locatesystypes.name where usertype=%d and type=%d. Pleasereport this internal error to Sybase technicalsupport.


3467 20Database %.*s': Index % ` s.%s' has id %d inSysindexes, but %d in our internal description.Please report this internal error to Sybasetechnical support.


3468 20Database %.*s': upgrade was asked to createindex %d on table % s', but there is no suchindex. Please report this internal error to Sybasetechnical support.


3469 20Database %.*s': upgrade failed to create index%d on table %s'. Please refer to previous errormessages to determine the problem. Fix the problem,then try again.


1310



3470 10SQL Server could not completely upgrade database

%` .*s', but the database was online when upgradebegan, so it will be left online.


3471 10Database %.*s' can not be brought online because ithas replicated tables that have not been completelytransferred. It will come online automaticallyafter replication is complete.


3472 21Unable to access database '%.*s' (dbid %d):recovery failed, please contact Sybase TechnicalSupport.


3473 21There is no space available in SYSLOGS for process%d to log a record for which space has beenreserved. It may be necessary to add space to thelog segment. The internal error number is %d.

Explanation: Adaptive Server encountered an internal error affecting allprocesses using the current database. Report the error to your System

Administrator.

3474 21During redo the page timestamp value is lessthan old timestamp from log. Page #= %ld, objectid = %ld, page timestamp=%04x %08lx. Log oldtimestamp=%04x %08lx.


1311



3475 21There is no space available in SYSLOGS for process%d to log a record for which space has beenreserved. This process will retry at intervals ofone minute. The internal error number is %d.


Administrator.

3476 16Redo pass: %d records done (%d%%); %d records left.


3477 16Undo pass: %d records done (%d%%); %d records left.


3478 21During undo the page timestamp value is lessthan new timestamp from log. Page #= %ld, objectid = %ld, page timestamp=%04x %08lx. Log newtimestamp=%04x %08lx.


3479 10Redo pass of recovery has processed %d committed and%d aborted transactions.


3480 10Undo pass of recovery has processed %d incompletetransactions.


3481 10Undo pass of recovery has processed %d incompletenested top actions.


1312



3501 21Could not get sysdatabases row for database % ` d' atcheckpoint time.

Explanation: This message indicates a problem with the ReplicationAgent Thread due to shutdown or abnormal termination. Contact yourSystem Administrator.

3502 21No checkpoint records found in syslogs for database

%` .*s'.

Explanation: This message indicates a problem with the ReplicationAgent Thread due to shutdown or abnormal termination. Contact yourSystem Administrator.

3505 14Only the DBO of database %S_DBID or a userwith System Administrator (SA) role may run thecheckpoint command.


3508 10Attempt to set %` .*s' database to single usermode failed because the usage count is %ld. Makesure that no other users are currently using thisdatabase and rerun CHECKPOINT.


1313



3604 10Duplicate key was ignored.


3605 10Duplicate row was ignored.


3606 10Arithmetic overflow occurred.


3607 10Divide by zero occurred.



3608 10Null value used in an expression.


3612 10Execution Time %ld.


3613 10Parse and Compile Time %ld.


3614 10Total writes for this command: %ld


1314



3615 10Table: %.*s scan count %ld, logical reads:(regular=%ld apf=%ld total =%ld), physical reads:(regular=%ld apf=%ld total=%ld), apf IOs used=%ld


3616 22Non-leaf page %D in table %D, index %d is empty -please rebuild the index.


3618 10Transaction has been aborted.


3619 10Unable to write CHECKPOINT record in database %dbecause the log is out of space.

Explanation: There may be a potential problem with a database or

database object. Contact your System Administrator.

3620 10Automatic checkpointing is disabled in database

%` .*s' because the log is out of space. It willcontinue when the DBO successfully checkpoints thedatabase. Please free up some space or extend thedatabase and then run CHECKPOINT.



3621 10Command has been aborted.


3622 10Domain error occurred.


1315



3623 10A transaction on a no_log table was undone. Checkthe errorlog file in the SQL Server directory fordetails.


3624 10Truncation error occurred.


3625 10Table: %.*s scan count %.0lf, logical reads: %ld,physical reads: %ld


3626 17The transaction was aborted because it used too muchstack space. Either use sp_configure to increasethe stack size, or break the query into smallerpieces. spid: %d, suid: %d, hostname: %.*s,application name: %.*s


3627 10Conversion of char/varchar datatype to securitylabel datatype failed.


3628 10Conversion of security label datatype tochar/varchar datatype failed.



1316



3629 10Statement: %d Subquery: %d cache size: %d hits:%d misses: %d



3630 10Total estimated I/O cost for statement %u (at line%u): %ld.


3631 10Total actual I/O cost for this command: %ld.

Explanation: This is an informational message. No action is needed.

3632 10Command batch has been aborted.


3634 20Task %d is trying to release a latch 0x%x which isalready free.

Explanation: This is an internal error affecting the current process.Contact your SA.

1317



3701 11Cannot drop the %S_MSG %` .*s', because it doesn'texist in the system catalogs.


3702 16Cannot drop the %S_MSG %` .*s' because it iscurrently in use.


3703 11Cannot drop the %S_MSG with object-id %ld indatabase %d, because it doesn't exist in the systemcatalogs.


3704 16Cannot drop the %S_MSG %` .*s' because you are notthe owner or a user with System Administrator (SA)role.


3705 16Cannot use DROP %s with %.*s' because % ` .*s' is a%S_MSG. Use DROP %s.


3708 16Cannot drop the %S_MSG %` .*s' because it is a system%S_MSG.


1318



3709 16Cannot drop % .*s' because you are not currently inthe 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 16Cannot use DROP with % .*s' because % ` .*s' is a%S_MSG. Use ALTER TABLE.


3711 16Cannot use ALTER TABLE with % .*s' because % ` .*s' isa %S_MSG. Use DROP %s.


3712 16Cannot drop %S_MSG %` .*s' because it still hasreferential integrity constraints.

Explanation: A table cannot be dropped if it has dependent foreignkeys or other referential integrity constraints. Check the constraintsassociated with the table.

3716 16The %S_MSG %` .*s' cannot be dropped because it isbound to one or more %S_MSG.


3718 11Could not drop index % ` .*s' because thetable/clustered index entry cannot be found inthe sysindexes system catalog.


1319



3723 16The table % .*s' does not have the %S_MSG % ` .*s'.Cannot drop.


by message.

3724 16Level of table or object % ` .*s' does not matchuser's curwrite level. Cannot drop.


3725 16Level of index %` .*s' does not match user's curwritelevel. Cannot drop.


3726 16Level of database % ` .*s' does not match user'scurwrite level. Cannot drop.


3727 16Can not drop the database % ` .*s' because cursor

%` .*s' is still open. Close the cursor(s) beforedropping the database.


1320



3728 16Cannot drop this database % ` S_DBID' as it has somedependencies (referential constraints) from database

%` S_DBID'. Drop the referencing database first,before dropping the referenced database (dependentdatabase).


3729 20The dropo() function is trying to put too many lockrequests in the lock_requests[] array.

Explanation: An internal Adaptive Server error occurred. Report theerror to Sybase Technical Support.

3730 16Can not drop index %` .*s' because cursor % ` .*s'is open. Close the cursor(s) before dropping theindex.


3731 16Cannot drop table %` .*s' because it is partitioned.


3732 16Cannot drop index %` .*s' because there are one ormore isolation level 0 scans active on table.


3733 10Warning: There is an invalid cross-databasereference in the system catalogs. The referenceddatabase '%.*s' does not exist.

Explanation: This is an informational message. Notify your SystemAdministrator about the message.

1321



3734 10Warning: There is an invalid cross-databasereference in the system catalogs. The referencingdatabase '%.*s' does not exist.


3735 10Warning: There is an invalid cross-databasereference in the system catalogs. A referencedtable, id %d, in database '%.*s' does not exist.


3736 10Warning: There is a missing referential constraintcatalog entry in database '%.*s'.


3738 16Drop index error: %S_MSG % .*s' does not have anyindexes. Only tables have indexes.

Explanation: DROP INDEX was attempted on an object with noindexes. Only tables with associated indexes may be targeted for thiscommand.

3739 14You need SA authorization to drop databasesybsystemdb.

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.(Not raised in 11.9.2).

3740 10The d` rop' command is bypassing updation ofreferential status bits and flags in database

%` .*s', because a referenced table, id %d, isnon-existent. The command will execute successfully(assuming no further errors in processing).

Explanation: This is an informational message. Unless otherwisespecified, no action is required. Contact your System Administratorabout any warning issued in the message. (Not raised in 11.9.2).

1322



3741 16Cannot drop object % ` .*s' because it is tagged aspartitioned (# of slices=%ld) although it shouldn't.


by message.

3742 11Cannot drop the lightweight procedure '%.*s' becauseit doesn't exist.

Explanation:

1323



3801 16There is no host variable corresponding to the onespecified by the PARAM datastream. This means thatthis variable % ` .*s' was not used in the precedingDECLARE CURSOR or SQL command.


3802 18There is no cursor information given with thecurrent datstream. A cursor id of zero wasspecified and no name was specified. The currentbatch of commands is being aborted. This is aninternal error.



3803 16The statement used to define the cursor % ` .*s' isneither a SELECT nor an EXECUTE.


3804 16More than one SELECT statement is used to define thecursor % .*s'.


by message.

3805 18The token datastream length was not correct. Thisis an internal protocol error.


1324



3806 16Both the READ ONLY and the FOR UPDATE options havebeen specified for cursor % ` .*s'.


by message.

3807 18The datastream specifies a wrong option or command.The datastream is %` s'. This is an internal error.


3808 18The column is not part of the RESDOM column list.This means the plan for the cursor is corrupted.This is an internal error.


3809 18Unknown datatype token %` d' has been sent to theserver. This is an internal error.


3811 18A wrong datastream has been sent to the server. Theserver was expecting token %d but got the token %d.This is an internal error.


3812 18The datastream for token %d should only be sentafter other datastreams. It can not be a commanddatastream on it's own. This is an internal error.


1325



3813 18A wrong datastream has been sent to the server. Theserver was expecting a dynamic sql command token butgot the token %d. This is an internal error.


3814 16The parameter of type %d did not have a valid value.


3816 18Internal Syslabels manager Error.


3819 16The dynamic PREPARE statement % .*s' failed becauseof an internal problem while sending the inputparameters formats to the client.


1326

Server Error Messages 3900 – 3999

Server Error Messages 3900 – 3999Number Severity Text and Explanation

3901 17This transaction uses too many databases and/oraggregates. The maximum allowed is %d. Thetransaction must be split into smaller sections.


3902 13The commit transaction request has no correspondingBEGIN TRANSACTION.

Explanation: Adaptive Server detected an invalid transaction context

for the commands. Check your commands.

3903 13The rollback transaction request has nocorresponding BEGIN TRANSACTION.

Explanation: Adaptive Server detected an invalid transaction contextfor the commands. Check your commands.

3904 21Can't unsplit logical page %ld in object % ` S_OBJID'in database % S_DBID' - both pages together containmore data than will fit on one page.


3905 21Can't unsplit logical page %ld in object % ` S_OBJID'in database % S_DBID' - row number %d is used onboth pages.



3906 16Attempt to BEGIN TRANsaction in database % ` .*s'failed because database is READ ONLY.


1327



3907 21Failed to receive results from PROBE. Thedistributed transaction named %.*s has not beencommitted and data may be inconsistent acrossdatabases.

Explanation: Adaptive Server encountered an internal error witha distributed transaction affecting all processes using the current

database. Report the error to your System Administrator.

3908 16Attempt to BEGIN TRANsaction in database % ` .*s'failed because database is in BYPASS RECOVERY mode.


3909 18While closing transaction descriptor, server foundit not marked as having a kept database.


3913 26Attempt to use an inactive internal transaction.This is an internal system error.


3914 26Illegal internal transaction status. This is aninternal system error.


3915 26Attempt to make a transaction in dbid %d internal.This is an internal system error.



1328



3916 26Internal transaction lock context chains mixed up.This is an internal system error.


Adaptive Server.

3917 16An attempt was made to startup a multi-databaseupdate in database % ` S_DBID' after starting up themaster transaction in tempdb. This could render thedatabase %S_DBID' unrecoverable and this update istherefore not allowed.

Explanation: Command failed due to invalid or illegal request. Checkthe database context for the transaction. Take any corrective actionindicated by message.

3918 26There are extra used elements in thePss->ptrig_stmt[] array in slot(s) after the XDESbeing removed.

Explanation: An internal locking/synchronization rule was broken.Report the error to your System Administrator. Shut down and restartAdaptive Server. (Not raised in Release 11.0 and higher).

3919 26The internalxact XDES cannot be found in thePss->ptrig_stmt[] array.

Explanation: An internal locking/synchronization rule was broken.Report the error to your System Administrator. Shut down and restartAdaptive Server. (Not raised in Version 11.9.2)

3921 14You cannot start a two-phase commit transaction inmaster, model, or sybsystemdb.


3922 26Attempt to start a sub transaction without a parenttransaction. This is an internal system error.


Adaptive Server.

1329



3923 26Attempt to set parallel status on transaction bynon-parent thread. This is an internal error.


Adaptive Server.

3924 26Illegal attempt to start sub-transaction by a parentthread. This is an internal error.


3925 26Attempt to set parallel status on transaction thatis not in CMD mode. This is an internal error.


3926 26Empty Parent Session Id passed to start a subtransaction. This is an internal system error.


3927 19The server has run out of free xdeses. Pleaseincrease the number of connections and boot yourserver again. Currently, %d XDESes are allocated.

Explanation: Command failed when a configurable limit was exceeded.Reconnect to Adaptive Server and report the error to your SystemAdministrator.

3928 16An attempt was made by this thread (spid=%d)to attach to a transaction. This is illegalbecause this thread is already associated with atransaction. Use systransactions to find out moreinformation.

Explanation: Query failed. Take any corrective action indicated by the

message.

1330



3929 16An attempt was made by this task (spid=%d) todetach from a transaction. This is illegal becausethis task is currently not associated with thetransaction. Use systransactions table to obtainmore information.

Explanation: Query failed. Take any corrective action indicated by themessage.

3930 20Systransactions system table does not exist inthis database. You need to upgrade to the correctversion. The command is aborted.


3931 16Transaction Manager API '%.*s' failed. It wasinvoked with a wrong transaction type '%ld'.

Explanation: Command failed due to invalid or illegal request. Checksyntax and semantics.

3932 16Attempt to begin a multi database transactionfailed. It is illegal to begin a subordinatetransaction in the master database.

Explanation: Command failed due to invalid or illegal request. Checksemantics and working context.

3933 16Attempt to start an external transaction failed. Itis illegal to begin an external transaction fromwith in the scope of a local transaction.


3934 16Transaction manager has detected a nesting failure.Number of BEGIN TRAN commands (issued after anattach operation) do not match the number of COMMITTRAN commands (issued before a detach operation).


1331



3935 16Fatal protocol error. xact_beginupdate() API wasinvoked in the wrong c ontext. The transaction iscurrently in '%d' state.


3939 10Illegal attempt to rollback transaction (xactname'%.*s') that has already committed in database'%.*s', spid %d.

Explanation: Check command semantics and processing logic of yourquery.

1332



4001 11Cannot open default database % ` .*s'.

Explanation: Command failed. Check syntax and your Adaptive Serverenvironment.

4002 14Login failed.


4013 14Login failed - not a secure SQL Server.


4016 16Language name in login record % ` .*s' is not anofficial name on this SQL Server. Using default

%` .*s' from syslogins instead.


by message.

4017 16Neither language name in login record % ` .*s' norlanguage name in syslogins % ` .*s' is an officiallanguage name on this SQL Server. Using server-widedefault % .*s' instead.


4018 16Your default language name from syslogins % ` .*s' isnot an official language name on this SQL Server.Using server-wide default % ` .*s' instead.


1333



4019 16Default date order % ` .*s' for language % ` .*s' isinvalid. Using m ` dy' instead.


by message.

4020 20While reading characters from the client, thereceiving buffer has been detected to be too small.


4022 10Password has expired -- However, you are stillallowed to login. You must change your passwordbefore you can continue.


4023 10Your password will expire in %s days.



4024 10The packet size (%d) specified at login time isillegal. Legal values are between 512 and %d.


4025 10A serious error was encountered while attempting toincrease the packet size specified for spid %d. TheNetwork memory map maybe corrupt. Call TechnicalSupport for further assistance.



1334



4047 18Failed to drop all orphans.

Explanation: Command failed due to internal Adaptive Server problem.Perform any diagnostic action indicated by message. Report the error toyour System Administrator. (Not raised in 11.9.2)

4048 18Failed to identify why temp. object %l could not bedropped.

Explanation: Command failed due to internal Adaptive Server problem.Perform any diagnostic action indicated by message. Report the error toyour System Administrator. (Not raised in 11.9.2)

4049 17Failed to queue the temp. object %l, which can notbe dropped.

Explanation: Command failed due to resource limitation. Modify thecommand to fit available resources, retry when the resource is available,or contact your System Administrator to address the resource problem.(Not raised in 11.9.2)

4050 11Component Integration Services not enabled or notinstalled.

Explanation: Command failed. Check your Adaptive Serverenvironment.

4051 14Security Control Layer has not been initialized.Security session cannot be established.

Explanation:

4052 14Failed to allocate data structure for use by theSecurity Control Layer. Cannot establish a securitysession.

Explanation:

4053 14Security session setup failed during securitysession establishment.



1335



4054 14Protocol negotiation failed during security sessionestablishment.

Explanation:

4055 14Unified Login through the underlying securitymechanism is required to connect to the SQL Server.

Explanation:

4056 16Login name %.*s not found. Check and make sure anentry exists in Syslogins.

Explanation: You used an invalid login name. Check that the nameexists in syslogins.

4057 16Login name %.*s not a user in the current database.

Explanation: Check login and working database context.

4058 16Login currently under set session authorization.It is required to go back to the original identitybefore performing another set session authorization.

Explanation: You can only assume another identity from the originalidentity.

4059 16Set session authorization requires a targetidentity. Please specify a valid login name.

Explanation: Check for missing information in query.

4060 16Login name not found for suid %d. Check and makesure an entry exists in Syslogins.

Explanation: Check the syslogins system table.

4061 10The SQL Server is using the default authenticationinformation file for it's authenticationinformation.


1336



4062 10Some of the requested security services are notsupported by the underlying security mechanism.Please contact a user with SSO_ROLE.

Explanation: This is an informational message but may require actionas indicated.

4063 10Security services being used for this connectionare inadequate as per the SQL Server's securityconfiguration requirements. Please contact a userwith SSO_ROLE.

Explanation: You may be logging in to Adaptive Server via an insecureconnection.

4064 16Invalid security service requested.

Explanation: Invalid or incorrect connection context. Contact a userwith System Security Officer (SSO) role.

4066 16Login account %.*s is locked. Please contact aperson with SA or SSO role.

Explanation: Contact the System Administrator to resolve the loginsecurity issue.

1337



4201 17DUMP TRANSACTION for database %` .*s' failed:insufficient memory to allocate backout structure.


4204 17Unable to continue logged version of DUMP TRAN. Nospace left in database; use NO_LOG option or runALTER DATABASE. Else, an old transaction may beactive; see Syslogshold table.


4205 16Syslogs does not exist in its own segment indatabase %S_DBID' with segmap % ld' with logicalstart page number of % ` ld'. You cannot use DUMPTRANSACTION in this case, use DUMP DATABASE instead.


4206 16You cannot run DUMP TRANsaction WITH NO_LOG insidea user transaction.


4207 16Dump transaction is not allowed because a non-loggedoperation was performed on the database. Dump yourdatabase or use dump transaction with truncate_onlyuntil you can dump your database.


1338



4208 16DUMP TRANsaction to a dump device is not allowedwhile the trunc. log on chkpt. option is enabled.Disable the option with sp_dboption, then use DUMPDATABASE, before trying again.


error log.

4210 16While attempting DUMP TRANsaction WITH NO_TRUNCATE,couldn't find database %.*s.


4211 23Couldn't complete DUMP TRANsaction WITH NO_TRUNCATEon database % .*s', because the log pointer insysdatabases (page number %ld) is not accurate.


4212 16Page %ld in database % .*s' cannot be used as atruncation page because the page belongs to objectID %ld and not to the log. Choose another page.


4213 16Page %ld in database % .*s' cannot be used as atruncation page because the page is not allocated.Choose another page.


1339



4214 16Cannot use page %ld in database % ` .*s' as the truncpage because the LTM trunc state is not set toTRUNC_VALID. Set LTM trunc state to TRUNC_VALID withDBCC SETTRUNC.

Explanation: Contact your System Administrator to address theReplication Server LTM setting.

4215 21%s failed in database %.*s: %ld not first log pagein serially allocated log extent or allocation page.Should be: %ld. Previous log record in scan: %ld.


4216 21%s failed in database %.*s: unexpected end of logencountered on page %ld while scanning for page %ld.


4217 26Failure during DUMP TRANSACTION in database

%` S_DBID': caller does not possess dump lock.


4218 21Failure during DUMP of database '%.*s': serial logpage allocation rules broken . Current page: %ld;next page: %ld; piece end: %ld; end-of-scan: %ld.


1340



4219 21DUMP TRANsaction encountered an unexpected end tothe log page chain. Last page in log as scanned:%ld.


4220 14You must be the DBO of database %.*s or haveOperator (OPER) role to run DUMP TRANSACTION.


4221 16DUMP TRANsaction to a dump device is not allowedwhere a truncate-only transaction dump has beenperformed after the last DUMP DATABASE. Use DUMPDATABASE instead.


4222 16DUMP TRANSACTION for database %` S_DBID' failed:log page (%ld) is on a data-only segment. This isprobably due to an incomplete move of the log to adevice separate from the data. Complete the logmigration or contact the System Administrator.


4223 18Deadlock occurred in SQL Process %d.


4224 16An interruption occurred in process %d due to USERATTENTION or connection failure.



1341



4225 16This database has not been dumped since it wascreated or upgraded. You must perform a dumpdatabase before you can dump its transaction log.


4226 16Logged DUMP TRANSACTION cannot run in database %.*s,because that databases's log version (%d) disagreeswith the SQL Server's log version (%d); use DUMPTRANSACTION WITH NO_LOG. Versions will agree onceONLINE DATABASE has run.



4227 17No space left in database master; creating userobjects in master database not recommended. Else,an old transaction may be active; see Syslogsholdtable.


4228 17No space left in database % ` S_DBID'; Use ALTERDATABASE to increase size of database. Else, an oldtransaction may be active; see Syslogshold table.


4231 16DUMP TRANSACTION is not allowed as the previousattempt to dump the database was terminated beforethe dump completed. Dump the database with DUMPDATABASE. Then retry DUMP TRANSACTION.

Explanation: A database maintenance operation failed. Take anycorrective action indicated by the message. (Not raised in 11.9.2).

1342



4232 16Dump the database with DUMP DATABASE. Then retryDUMP TRANSACTION.

Explanation: You must dump the database first before you can re-tryDUMP TRANSACTION. (Not raised in 11.9.2).

4233 19%s failed in database %.*s: Unable to findquiescent point in the log. Log backward scan startmarker (%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 thesecondary truncation page %ld.


Administrator.

4235 20%s failed in database %.*s: Bad quiescent point wasfound.


4236 10%s for database '%.*s' could not truncate thelog. Either extend the log using ALTER DATABASE... LOG ON command or eliminate the oldestactive transaction in database '%. *s' shown insyslogshold table.

Explanation: Database maintenance operation failed. Take specifiedaction.

1343



4301 16Database in use. A user with System Administrator(SA) role must have exclusive use of DB to loadtransaction.


4302 16Specified file % ` .*s' is not in valid dumptransaction format.



4305 16Specified file % ` .*s' is out of sequence. Currenttime stamp is %S_DATE while dump was from %S_DATE.


4306 16There was activity on database since last load,unable to load. Must restart load sequence with theload database to continue.


4312 14You must be the DBO of database %.*s or haveOperator (OPER) role to run LOAD TRANSACTION.


4313 16Recreate index failed for table %ld, index %d. Thetable has been left in an inconsistent state, andthe index is missing, so LOAD TRANSACTION errors mayresult. Run DBCC CHECKTABLE on the table if LOADTRANSACTION succeeds.


1344



4314 20Cannot find table %ld to recreate index %d.


4315 20Log scan for recreate index failed.


4316 16Can only LOAD TRANsaction in master if SQL Server isin single-user mode.


4317 21Could not read log page %ld for database % ` *s'; theDBINFO structure for this database is invalid, orthe page chain is corrupt. Cannot proceed with LOADTRANSACTION.


4318 21Last log page n` ext free byte' value is out ofrange: %ld; should be no greater than %ld.


1345



4319 21Failed to patch the transaction log for database

%` .*s'.



4320 16Dump or load commands require a logical dumpdevice name from the sysdevices system table. Usesp_addumpdevice to add %` .*s' to sysdevices.


error log.

4321 16SQL Server can not load this transaction log dumpbecause version information in the dump does notmatch information in the database. Database:log version=%d, upgrade version=%ld. Dump: logversion=%d, upgrade version=%ld.


error log.

4322 16SQL Server cannot load a dump of the master databasethat 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.


4323 16The specified RID (%d,%d) was not found in thetransaction log.

Explanation: Check command parameters.

4324 20The transaction log could not be opened for point intime recovery.

Explanation: Database log is not available for this maintenanceoperation.

1346



4325 16The specified recovery date (%S_DATE_LONG) isnot between the start (%S_DATE_LONG ) and end(%S_DATE_LONG) date.

Explanation: Check parameters for the point in time recoverycommand.

4327 10A load transaction to a point in time will resetthe transaction log sequence. A database dump isrequired to restart the log sequence.


1347



4401 16View %` .*s' no longer exists.


4402 16Infinite loop in view definition. Cannot resolvethe view definitions in the query to the underlyingtables.


4403 16View %` .*s' is not updatable because it containsexternal aggregates , or group by clauses , orinternal aggregates . Internal aggregates may begenerated by certain subqueries .


by message.

4404 16View %` .*s' is not updatable because either the viewdefinition contains DISTINCT or the view is builtupon a view created with DISTINCT option.


by message.

4405 16View %` .*s' is not updatable because the FROM clausenames multiple tables.


1348



4406 16View %` .*s' is not updatable because a field of theview is derived or constant.


by message.

4408 19The query and the views in it exceed the limit of %dtables.


4409 20The columns in the query definition and the viewdefinition do not match.


4411 16View %` .*s' does not allow this UPDATE becauseeither it was created WITH CHECK OPTION or it spansanother view created WITH CHECK OPTION, and oneof the update columns appears in a multi-tableexpression in the WHERE clause of a CHECK OPTIONview.


4412 16View %` .*s's definition contains % ` .*s', which isa temporary object. Views can only be based onpermanent objects.


1349



4413 16View resolution could not succeed because thepreviously mentioned objects, upon which the viewdirectly or indirectly relies, do not currentlyexist. These objects need to be recreated for theview to be usable.


4414 16View %` .*s' does not allow INSERT because it isderived from more than one object and it was eithercreated WITH CHECK OPTION or it spans another viewcreated WITH CHECK OPTION.


4415 18Internal system error: corrupt sequence treeencountered while processing the DISTINCT view

%` .*s'. Notify a user with System Administrator(SA) role.


4416 19Could not allocate a work table while processingviews. The total number of work tables generatedby the query exceeds the limit (%d) of work tables.Simplify the query or the views referenced in thequery.


1350



4417 16The view %.*s' has one or more tables with any ofthe keywords HOLDLOCK/NOHOLDLOCK that conflicts withthe query to be run AT ISOLATION 0.


4418 16Query has too many subqueries when all views aretaken into account. Error found on view % ` .*s'.The limit is %d subqueries.


4420 16View %` .*s' is not updatable, possibly due to anouter join being in the view, or due to a subquerybeing in the select list of the view.


4422 16View %` .*s' cannot be updated since no underlyingtables are referenced.


4423 16View %` .*s' cannot be updated since view is theinner table of an outer join.


1351



4424 16View %` .*s' contains a table being updated, and thistable is referenced elsewhere in the query whichis not allowed if create view WITH CHECK OPTION isused.


by message.

4425 16View %` .*s' cannot have WITH CHECK OPTION appliedsince it contains subqueries.


4426 16This query cannot be processed because it containsTEXT/IMAGE columns and references a view definedwith a subquery, an outer join, or a distinctclause.


1352



4501 16View %` .*s' has more columns defined than columnnames given.


4502 16View %` .*s' has more column names specified thancolumns defined.


4503 20The create view tree has a resdom with no right handside. View % .*s', resdom % ` .*s'.



4504 16CREATE TABLE failed because there was not enoughspace to allocate memory for the table.


4505 16CREATE VIEW failed because column %` .*s' in view

%` .*s' exceeds the maximum of 250 columns.


4506 16Column names in each view must be unique. Columnname %` .*s' in view % ` .*s' is specified more thanonce.


1353



4507 16Column %` .*s' specifies storage type %d, which doesnot currently exist.


by message.

4508 16Views are not allowed on temporary tables. Tablenames that begin with # ` ' denote temporary tables.


4509 10Column names in each view must be unique. Anunnamed column is specified more than once in view

%` .*s'.


1354



4601 14This permission can only be GRANTed or REVOKEd byowner %` .*s' of object % ` S_OBJID', or by a user withGRANTable privileges in database % ` S_DBID'


4602 14Permission denied. Only users with SystemAdministrator (SA) role can GRANT/REVOKE CREATEDATABASE permission.


4603 14Only owner of current database may GRANT/REVOKE thispermission.


4604 16There is no such user %.*s.


4605 25Can't initiate update to sysprotects.

Explanation: Contact your System Administrator.

4606 16GRANTed/REVOKEd privilege %s not compatible withobject.


4607 16Privilege %s may not be GRANTed or REVOKEd.


1355



4608 16Only users with System Administrator (SA) role canGRANT/REVOKE ALTER DATABASE permission, and onlyto/from users with CREATE DATABASE permission.


4609 16You cannot specify a column list with INSERT orDELETE.


4610 16You may only GRANT or REVOKE permission on objectsin the current database.


4611 16The user %.*s' has granted this privilege to otherusers. You must use REVOKE WITH CASCADE to revokeprivileges for % ` .*s' as well as the other users.


4612 16Too many users to revoke privileges from,due tocascading GRANT WITH GRANT. To continue, use REVOKEWITH CASCADE on user %` .*s'.


4613 16WITH GRANT OPTION does not apply to groups androles.


1356



4614 16Column list may be specified either with theprivileges or with the table. It cannot bespecified in both places.


4615 16Permissions may not be revoked from either the DBOor the object owner.


4616 25Public has been granted permission on the objectwith the grant option. Please revoke the GRANT WITHGRANT option from public before revoking from anyuser/group.


4617 25Public has GRANT WITH GRANT permission on atleastone of the columns you are trying to revoke. Pleaserevoke the GRANT WITH GRANT option from publicbefore revoking from the users/groups.


4618 16The user's curwrite must be at the security labelof an object in order for that user to grant/revokeaccess to that object.


1357



4619 16The user's curwrite must be at Data Low in order togrant/revoke create database permission.



4620 16The user must be in the master database in order togrant/revoke create database access.


4621 16Warning. All permissions except CREATE DATABASEare granted/revoked. Only System Administrator cangrant/revoke CREATE DATABASE permission.


4622 10Some or all of the specified privileges were notrevoked because, they were not granted, or they weregranted by some other user.


4623 18Error encountered while retrieving columninformation. Aborting grant/revoke command.


1358



4624 16The user must be in the master database in order togrant/revoke connect access.

Explanation: Command failed. Check database context.

4625 16The user must be in the master database in order togrant/revoke set session authorization access.

Explanation: Command failed. Check database context.

1359



4701 11Cannot truncate table % ` .*s', because this tabledoes not exist in database % ` S_DBID'.


4706 17Could not truncate table % ` .*s' because there is notenough room in the log to record the deallocation ofall of the index and data pages.



4708 16Could not truncate object % ` .*s' because it is nota table.


4709 16You are not allowed to truncate the system table

%` .*s'.


4710 16Cannot truncate table % ` .*s' because you are not theowner or a user with System Administrator (SA) role.


4711 14Permission denied. @@curread does not dominate themaxhold of table %` .*s'.


1360



4712 14Permission denied. @@maxwrite does not dominate themaxhold of table %` .*s'.


4713 14Permission denied. The minhold of table % ` .*s' doesnot dominate @@minwrite.


4714 14Permission denied. Only users possessing the SSOrole can truncate the audit log.


4715 14Permission denied. The hurdle of table % ` .*s' doesnot equal @@curwrite.


4716 16Cannot truncate table % ` .*s' because it ispartitioned.


4717 16Could not truncate table % ` .*s' because there arereferential constraints defined on it and there aredata rows in some of the referencing tables.


4718 17Failed to write the TRUNCTAB log record for theexecution of truncation of table '%.*s' in database'%S_DBID'. The 'truncate table' command is aborted.

Explanation:

1361



4719 20TRUNCATE TABLE aborted due to an internal error.Failed to obtain the owner name informationassociated with object ID %d in database '%S_DBID'.Please contact Sybase Technical Support.


your System Administrator so DBCC diagnostics can be run.

4720 16Cannot truncate table '%.*s' because there are oneor more isolation level 0 scans, or REORG command,active on the table.

Explanation: Retry your command later.

1362



4801 20Bulk_main: opentable on BULK INSERT table failed.Dbid=%d name='%.*s'.

Explanation: The bulk copy command failed. Adaptive Server couldnot open the specified table. Check command and target table.

4802 21Bulk_main: getindex of primary index row failed onBULK INSERT table.

Explanation: There is a potential problem affecting the consistencyof the system catalog or the indexes on the table specified in the bcpcommand. Investigate with dbcc checktable, checkcatalog and checkdb.

4804 21Premature end-of-message while reading current rowfrom host. Host program may have died.

Explanation: The bcp activity could be incomplete. Althoughcorruption is unlikely, some rows in the target table for bcp may need tobe cleaned up using delete/truncate table command.

4805 17The front end tool you are using does not supportthe feature of bulk insert from host, please use theproper tools for this command.


4806 16You cannot run the non-logged version of bulk copyin this database. Please check with the DBO.


4808 10The bulk copy of this table has been aborted becausethe CHECKPOINT record could not be written in thelog. Please free up space in the database.

Explanation: The bcp activity could be incomplete. Althoughcorruption is unlikely, some rows in the target table for bcp may need

to be cleaned up using delete/truncate table command. Restart thebcp job after cleanup.

1363



4809 20Unable to open SYSCOLUMNS in dbid %d to retrievetable schema information.



4810 16Expected TEXT token in data stream for bulk copy oftext data.

Explanation: This error is seen when bulk copying in a table that hastext/image columns. Does not cause corruption but the bcp batch maybe terminated.

4811 16Expected column offset in data stream for bulk copyof text data.


4812 16Expected row offset in data stream for bulk copy oftext data.


4813 16Expected text length in data stream for bulk copy oftext data.


4814 20Bulk_getschema: Unable to open the system catalogSYSCOLUMNS in database %` .*s' while attemptingto retrieve table schema information. Run DBCCCHECKTABLE on sysobjects in % .*s'.



1364



4818 11Error encountered while retrieving table schemainformation for object % ` .*s' in database % ` .*s'.Re-check the schema for the table.


4819 16You cannot BCP into the sysaudits table.


4820 16Illegal identity value specified for identity columnin table % .*s' through BCP.


4821 16Identity 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 identityvalue range to load the data.

4822 14You do not have the role required to run bcp in withthe labelled option.


4823 16Sensitivity label out of range for some row(s).


4824 16Invalid sensitivity label for some row(s).


1365



4825 16Some row(s) not copied.


4826 16Expected sensitivity label length in data stream forbulk copy of sensitivity label data.


4827 16Expected row offset in data stream for bulk copy ofsensitivity label data.


4828 16Expected sensitivity label data in data stream forbulk copy of sensitivity label data.


4829 16Attempt to copy in row sensitivity labels withoutusing bulk copy labelled option. Labels will beoverwritten.


4830 16The labelled option was specified, but rowsensitivity labels were not passed in.


Check your command for missing or incorrect database objects, variablenames, and/or input data.

1366



4831 16Expected TEXT or SENSITIVITY token in data streamfor bulk copy of text or sensitivity label data.



4832 16You cannot use a pre-10.0 client to bulk copy intoa Secure SQL Server.


4833 16Expected text data in data stream for bulk copy.


4834 17Bulk copy failed due to insufficient SQL Servermemory. Please retry later when there is lessload/users on the SQL server, or ask your SystemAdministrator to reconfigure SQL Server with morememory.


4835 18Failed to update the identity pre-burn factorfor table %` .*s' through BCP. Please re-try theoperation or contact your SA for details.


1367



4836 18Error occurred while creating the identity valuefor table %` .*s' through BCP. Please re-try theoperation or contact your SA for details.


4837 16Bad row data received from the client while bulkcopying into object %d in database %d. Received arow of length %d while maximum possible row lengthis %d.


4838 16You cannot BCP into a view.


4839 18Server has encountered badly formatted rows frombulk copy. Could not locate the row positionreserved for the insertion of the identity value.


4840 16Bulk copy failed. You cannot specify a partition IDwhen doing BCP into table '%. *s' because it has aclustered index.

Explanation: Check command parameters and retry.

4841 16Bulk copy failed. Partition number %d does notexist in table '%.*s'.

Explanation: Check command parameters and retry.

1368



4842 16Bulk copy failed. Partition number %d was specifiedfor table '%.*s', but that table is not partitioned.

Explanation: Check command parameters and table, and retry.

4843 10Slow 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 16Bulk copy failed. Identity start value %S_NUME wasspecified for table '%.*s', but that table does nothave an identity column.

Explanation: Check command parameters and table,and retry.

4845 16Bulk copy failed. Client does not have thecapability to bulk copy into the dataonly lockedtable '%.*s'.

Explanation: Check Adaptive Server and client environment, setup.

4846 20Bulk copy failed. Error occurred while updating thelast page of the table.

Explanation: Error in bulk copy affected current process. ContactSystem Administrator.

4847 16BCP insert operation is disabled when LONGCHARcapability is turned on and data size is changingbetween client and server character sets since BCPdoes not support LONGCHAR yet.

Explanation: Illegal command.

1369



4901 16ALTER TABLE only allows columns to be added whichcan contain nulls. Column % ` .*s' cannot be added totable % .*s' because it does not allow nulls.


4902 11Cannot alter table % ` .*s', because this table doesnot 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 21ALTER TABLE failed because page %ld of the systemcatalog sysindexes in database % ` .*s' is not in thecache.


run.

4909 16Can't alter %.*s because it is not a table.


by message.

4910 16Cannot alter table % ` .*s' because you are not theowner or a user with System Administrator (SA) role.


4912 16Cannot replace default to % ` .*s.%.*s' because italready has a default bound using sp_bindefault.


1370



4913 16Alter table command has unrecognized action. Cannotprocess.


by message.

4914 16Cannot alter table % ` .*s' because the alter tablestatement contains multiple identity fields.


4915 16Cannot add new identity field to % ` .*s' via altertable because the table already contains an identityfield.


4916 16Cannot add new identity field to % ` .*s' viaalter table because the number of existing rows(%ld) exceeds the maximum value for the specifiedprecision (%d).


4917 20Failure adding identity column % ` .*s' to table

%` .*s'.


4918 16Maximum row width exceeded when adding identitycolumn %` .*s' to table % ` .*s'.


1371



4919 16Identity value overflow when adding column % ` .*s' totable % .*s'.


by message.

4920 16Permission denied. A table can only be altered ifthe table's hurdle equals the user's curwrite.


4921 14Permission denied. A table's labels cannot bealtered while it is in use.


4922 14Invalid hold label specified.


4923 14Permission denied. A table's maxhold should alwaysdominate its minhold.


4924 14Permission denied. A table's maxhold should alwaysbe dominated by the maxhold of the database thatcontains it.


4925 14Permission denied. User maxwrite does not dominatespecified maxhold.



1372



4926 14Permission denied. User minhold does not dominatespecified minwrite.


4927 14Permission denied. Maxhold label specified is belowprevious table maxhold.


4928 14Permission denied. Minhold label specified is aboveprevious table minhold.


4929 14Permission denied. User minwrite is not dominatedby specified maxhold.


4930 14Permission denied. User maxwrite does not dominatespecified minhold.


4931 16Cannot alter system table % ` .*s' because ad-hocupdates to system catalogs are not enabled. Auser with System Security Officer (SSO) role mustreconfigure system to allow this.


4932 16Dropping a column from a system table is notallowed.


by message.

1373



4933 16Dropping a column from a replicated table is notallowed.


by message.

4934 16A column by this name doesn't exist in the table

%` .*s'.


4935 16Dropping the only column in a table is not allowed.


4936 17Dropping the column failed while reformatting dataon page %d, row %d. This command is being rolledback.



4937 17Deleting text pages failed. This command is beingrolled back.


4938 20Cannot undo a drop column command because the numberof rows on the log record does not match the numberof rows on the data page.


1374



4939 16Dropping a column used by an index is not allowed.Drop the %s' index before dropping this column.


by message.

4940 16Dropping an identity column is not allowed.


4941 16Dropping a column which has a constraint associatedwith it is not allowed. Drop the constraint (objectid %ld') before dropping this column.


4942 16Dropping a column which has a default bound to it isnot allowed. Unbind the default (object id % ` ld')before dropping this column.


4943 16Dropping a column which is a primary key is notallowed. Drop the constraint (object id % ` ld')before dropping this column.


4944 16Dropping a column which is a foreign key is notallowed. Drop the constraint (object id % ` s')before dropping this column.


1375



4945 16Cannot drop the column because cursor % ` .*s' isstill open. Close the cursor(s) before dropping thecolumn.


4946 16Dropping a column from a table which has aconstraint associated with it is not allowed. Dropthe constraint (object id % ` ld') before droppingthis column.


4947 16Dropping an identity column from a table whileidentity_insert is o ` n' is not allowed. Setidentity_insert to o ` ff' before dropping thiscolumn.


4948 25Dropping the column failed while logging data frompage %d. This command is being rolled back.


4949 20The alttab_begin() function is trying to put toomany lock requests in the lock_requests[] array.


4950 16Cannot partition table % ` .*s' because it is a systemtable.


1376



4951 16Cannot create %d partitions on the table '%.*s'with clustered index because the maximum number ofpartitions allowed on a table with clustered indexis %d.


4953 16Cannot partition table % ` .*s' because it is alreadypartitioned.


4954 16Cannot unpartition table % ` .*s' because it is notpartitioned.


4955 16Number of partitions must be greater than one


by message.

4956 16Cannot alter table if REORG command or level 0 scansare active.


4958 16Cannot partition table % ` .*s' because it is in apre-System 11 database.


4959 16Dropping a TEXT/IMAGE column is not allowed.


1377



4960 16Lock scheme currently on the table % ` .*s' iscorrupted. For this version of SQL server it shouldhave been set properly.


4961 16Cannot partition table '%.*s' because it has beenpartitioned and unpartitioned too many times.


4962 16To partition: bcp the data out of the table,drop and recreate the table, and then bcp into apartitioned/unpartitioned table.

Explanation: Follow the steps in the message to partitioned a table.

4963 16Table '%.*s' is already locked in the desiredlocking scheme.

Explanation: This is an informational message. The command did notexecute.

4964 17Lock scheme conversion failed due to insufficientSQL Server memory. Please retry later when thereis less load/users on the SQL server, or ask yourSystem Administrator to reconfigure SQL Server withmore memory.


4965 16Lock scheme conversion on system tables notsupported.

Explanation: You can only change lock schemes on a user table.

1378



4966 10Warning: Table '%.*s' with a clustered index hasbeen partitioned. All data rows are in the firstpartition and all data insertions will go to thefirst partition. To distribute the data to all thepartitions, re-create the clustered index.

Explanation: The table is partitioned but will not stay balanced unlessyou take the specified action.

4967 16Cannot execute '%.*s' command on table '%.*s',because this table does not exist in database'%S_DBID'.

Explanation: Check syntax and working database.

4968 16The table '%.*s' you've specified is a system table.Executing the '%.*s' command is not permitted onsystem tables.

Explanation: Invalid command.

4969 16The table '%.*s' you've specified is a temporarytable. Executing the '%.*s' command is notpermitted on temporary tables.


4970 16Cannot unlock this table because the table is notlocked in that mode.


4971 16This table cannot be locked in '%.*s' mode becauseit was already locked in '%.*s ' mode.


4972 10Warning: Empty Table '%.*s' with a clustered indexhas been partitioned. All data insertions will goto the first partition. To distribute the data toall the partitions, re-create the clustered indexafter loading the data.

Explanation: Table is partitioned but will become unbalanced withfuture inserts. Take the recommended action to maintain partitionbalance.

1379



4973 20Row size exceeded the maximum row size limit of dataonly locked format while changing the lock schemefrom ALLPAGES to DATAONLY for object '%.*s' (ID %d)in database '%.* s' (ID %d). The lock scheme forthe object was not changed.

Explanation: Consult the System Administration Guide for moreinformation.

4974 21Process %d was expected to hold logical lock onobject %ld.


4975 16Cannot alter table for lockscheme change becausecursor '%.*s' is still open. Close the cursor(s)before lockscheme change.

Explanation: Wait for the process holding the cursor to complete.

4977 16You cannot run ALTER TABLE LOCK in this databasebecause the 'select into/bulkcopy' option is off.Please check with the DBO.

Explanation: Invalid or illegal command.

4978 16User aborted ALTER TABLE LOCK change command fortable %.*s

Explanation: DDL command aborted.

4979 20ALTER TABLE LOCK change for table '%.*s' failed:insufficient memory to allocate backout structure.

Explanation: Retry the DDL command when there is more memoryavailable for the task.

4980 17No space left in database '%S_DBID'; Use ALTERDATABASE to increase size of database. Else, an oldtransaction may be active; see Syslogshold table.

Explanation: Check the syslogshold table for long-running transactions.

1380



4981 16You cannot drop a column from table '%.*s', as thistable does not use the allpages lock scheme.


4982 10Due to an internal error the table '%.*s' cannot beconverted to new lock scheme. Please contact yourSystem Administrator (SA) for help

Explanation: An Adaptive Server error occurred. Notify the SystemAdministrator.

4983 10Primary index (indid = %d) is suspect for table'%.*s'. Please check and reissue the lock changecommand.

Explanation: Check the index and table using dbcc. You may needto recreate the index.

4984 10Computed effective expected row size value(%d)for the table '%.*s' with the expected row sizevalue(%d) is invalid. Forcing the default value.


1381



5001 16User must be in Master Database.


5002 16Database %.*s does not exist; check sysdatabases.


5004 16ALTER DATABASE failed. The size request must bepositive.

Explanation: Command failed due to invalid or illegal request. Specifya positive (and minimum allowed) value for the size parameter of the

alter database command.

5005 10Extending database by %ld pages on disk %.*s



5006 16Could not find enough space on disks to extenddatabase %.*s.


5008 16System does not support Deextend Database currently.



5009 16ALTER DATABASE failed. Some disk names listed incommand were not found. Check that names exist andare spelled correctly before re-running command.


by message.

1382



5011 14Only the owner of database %.*s or a user withSystem Administrator (SA) role can ALTER it.


5013 16Cannot extend the MASTER database onto any deviceother than m aster'. The ALTER DATABASE wasaborted.


5015 16ALTER DATABASE failed. The total size specifiedmust be 1 megabyte or greater.


by message.

5016 10ALTER DATABASE failed. The Model database may notbe larger than the Temporary database. Alter tempdbfirst.


5017 16ALTER DATABASE failed. Database %.*s not createdwith f or load' option.


5018 10Caution: You have set up this database to includespace on disk %d for both data and the transactionlog. This can make recovery impossible if that diskfails.

Explanation: This is an informational message. Keeping data and logseparate is recommended.

1383



5020 14Permission denied. @@curwrite has to be set equalto the database's hurdle in order for the alter toproceed.


5021 14Too many dbmaxhold specifications made.


5022 16Invalid dbmaxhold provided.



5023 14Permission denied. The database maxhold youspecified does not dominate your minwrite.


5024 14Permission denied. The database maxhold youspecified is not dominated by your maxwrite.


5025 14Permission denied. The database maxhold youspecified does not dominate the current databasemaxhold.


5026 10Updating database maxhold.


1384



5028 16ALTER DATABASE failed. This command will not makechanges to a database that would cause the numberof device fragments to exceed the maximum of 128.Recreate the database and try again.


by message.

5029 16ALTER DATABASE failed. Log space in master databasehas reached the last chance threshold. Pleasefree-up log space in master database and try again.

Explanation: This is a serious condition. Refer to “Managing Free SpaceWith Thresholds” in the System Administration Guide for immediatecorrective action.

5030 16The database %S_DBID is in the middle of a loadsequence. Altering it will not let you load othertransaction dumps in the dump-set. If you stillprefer to do it please use OVERRIDE option.

Explanation: Retry the command after completing the load sequence.

5031 10Database %S_DBID which is currently offline has beenaltered from size %d pages to %d pages.


5032 10Alter database on '%S_DBID' broke the load sequencefor that database.

Explanation: The alter command was executed in the middle of atransaction load sequence.

5033 16Attempt to alter database '%S_DBID' failed becauseit is in read-only mode.

Explanation: You must first change the database read-only mode usingsp_dboption.

1385



5101 15Must give parameters for D ` ISK %s' command. Usage:%s.


5102 15No such command: D` ISK %.*s'.


5103 16Illegal disk address range. The sum of VSTART andSIZE must be less than 16777216 (0x1000000).


5104 16Device number %d already used.


5105 16Device activation error. PHYSNAME % ` .*s' may beincorrect.

Explanation: Check the physical device name.

5106 15Parameter % s' requires value of type % ` s'.


5107 15Value is wrong type for parameter % ` s' (requirestype %s').


5108 15Parameter % s' does not take a value.


1386



5109 16No such parameter: %` .*s'.


5114 20Could not yield.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Report the error to your System Administrator.(Not raised in Release 11.0 and higher.)

5115 16I/O error during disk initialization. PHYSNAME

%` .*s' may be incorrect or %ld (VSTART + SIZE) mayexceed the size of the device. Please consult theSQL Server error log for more details.


5116 14Permission denied. Only users with SystemAdministrator (SA) role can run DISK commands.


5117 16Unable to run DISK command. Must be in masterdatabase to run this command.


5118 16Unable to run DISK REFIT. SQL Server must bebooted with the -m option. Please see your SystemAdministration guide about the Restore Masterprocedure.


1387



5119 18Unable to reserve a buffer, aborting DISK REFITcommand. Please retry Restore Master procedure.



5120 10Bad 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 valuewith correct information after Disk Refit completes.


5121 10Warning: Disk Refit may not have the correctsegment map information in sysusages. Please reviewthese after the command completes to verify theiraccuracy.


5122 10The disk size must be >= 512.


5123 16DISK INIT encountered an error while attemptingto open/create the physical file. Please consultthe SQL Server error log (in the SQL Server bootdirectory) for more details.


5124 10Activating disk % ` .*s'.


1388



5125 10Failed to complete unmirror of logical device % ` .*s'after recovery of the master database.


5126 16The logical device % ` .*s' does not exist inSYSDEVICES.


5127 16The device % .*s' is already mirrored and mirroringis enabled.


5128 16The device % .*s' is already mirrored but mirroringis disabled. Use the DISK REMIRROR command toenable mirroring or unmirror the device.


5129 16Syntax error detected in the value for parameter

m` irror'. You must provide a valid physicaldevice/file name for this parameter.


5130 16The value for parameter m ` irror' translates tothe same name as that for the primary device. Useanother physical device for the mirror.


1389



5131 16The device % .*s' is not currently mirrored.


5132 10DISK MIRROR encountered an error while attempting tocreate the physical file % ` .*s'. Please consult theSQL Server error log for more details.


5133 10Unable to start i/o to % ` .*s'. Please consult theSQL Server error log for details.


5134 10Dynamic mirroring failed for logical device % ` .*s'.Check the SQL Server error log for more information.


5135 10Starting Dynamic Mirroring of %ld pages for logicaldevice % .*s'.


5136 10%*.d pages mirrored...


5137 10Failed to mirror device % ` .*s'.


1390



5138 10Failed to unmirror device % ` .*s'.


5139 10Failed to remirror device % ` .*s'.


5140 10Creating the physical file for the mirror...



5141 17Unable to start Dynamic Mirroring because an i/obuffer is not currently available. Try the commandagain later.



5142 16Mirroring for device % ` .*s' is not currentlyenabled.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby the message.

5143 10The remaining %ld pages are currently unallocatedand will be mirrored as they are allocated.


1391



5144 16You can't remove the secondary physical device forvirtual device % ` .*s' since it is currently the onlyoperational device. Use the SIDE=PRIMARY qualifierfor the DISK UNMIRROR COMMAND.


error message.

5145 16Error re-initializing device % ` .*s'. Check SQLServer errorlog for more information.


5146 16The VDEVNO of %ld is out of range. The maximumVDEVNO allowed is %ld.


5147 10Device size set to %ld blocks.


5148 16Device %.*s' already exists.


5149 16You cannot remove the primary physical device forvirtual device % ` .*s' since it is currently theonly operational device. Use the SIDE=SECONDARYqualifier for the DISK UNMIRROR COMMAND.


error log.

1392



5150 16DISK UNMIRROR cannot be performed, because database

%` S_DBID' is currently undergoing DUMP or LOAD.Either wait for that command to complete, or abortit.


error log.

5151 16PHYSNAME %` .*s' is already in use.


5152 16DISK REFIT failed. Either the database is corruptedor the value of the VSTART parameter supplied toDISK INIT and DISK REINIT were different.

Explanation: Check that the VDISK parameter supplied to DISKREINIT is consistent with that supplied to DISK INIT.

5153 16Device '%.*s' cannot be released since it is in useby database id '%S_DBID'. Drop that database andretry.

Explanation: Illegal command. Check device before retrying.

5154 16Device '%.*s' is not a valid database device.

Explanation: Check command syntax.

5155 16The command 'DISK %s' cannot be executed since diskmirroring has been disabled. In order to enabledisk mirroring, use: sp_configure 'disable diskmirroring',0 and restart the server.

Explanation: A database maintenance operation failed. Take anycorrective action indicated by the message.

1393



5201 26Failure concurrent with dump in database %d: DFLManager caller must be DUMP DATABASE; instead,command token was %d.


5202 26DUMP DATABASE for database %d failed: DFLsynchronisation is prematurely set.



5203 17DUMP DATABASE for database %d failed: insufficientmemory to allocate DFL.


5204 26DUMP DATABASE for database %d failed: initial DFLallocation will not fit in initial memory block.


Adaptive Server.

5205 26DUMP DATABASE for database %d failed: duplicatedflheader found.


5206 26DUMP DATABASE for database %d failed: dumpflushlist structures have not been allocated.


1394



5207 26DUMP DATABASE for database %d failed: DFLsynchronisation is not set.


Adaptive Server.

5208 10User aborted DUMP DATABASE for database %d.


5209 26Failure during concurrent dump in database %d: DFLManager caller must not be DUMP DATABASE, but is.


5210 26Failure during dump in database %d: caller does notpossess dump lock.


5211 26Failure concurrent with dump in database %d: callerdoes not possess flushlist lock.


5212 26Failure concurrent with dump in database %d: no DFLpieces on not-full list.


1395



5213 26Failure concurrent with dump in database %d: callerimproperly holds flushlist lock.


Adaptive Server.

5214 20During DUMP DATABASE for database %d, flushlistclosure not complete at end of synchronisation.


5215 26DUMP DATABASE for database %d failed: could notfind dflinfohead to deallocate.


5216 26DUMP DATABASE for database %d failed: trailingpiece in not-full list proved not-empty.


5217 20DFL Manager failed to sleep.


1396



5701 10Changed database context to % ` .*s'.


5702 10The SQL Server is terminating this process.


5703 10Changed language setting to % ` .*s'.


5704 10Changed client character set setting to % ` .*s'.


1397



5803 10Unknown config number in sysconfigures, config = %d.


5804 16The value for % s' must not exceed % ` s' or % s'.

Explanation: Command failed. Check syntax and semantics. Checkyour configuration file and any configuration parameters supplied.

5805 16Warning: The next configuration change willoverwrite % s'. To avoid this rename, move,or delete old configuration files. See SystemAdministration Guide for details.


5806 16Warning: The file % ` s' has been overwritten.To prevent this rename, move, or delete oldconfiguration files. See System AdministrationGuide for details.

Explanation: Command failed. Check syntax and semantics. Check

your configuration file and any configuration parameters supplied.

5807 10Invalid memory move request encountered for the

%` dK' pool in cache % ` s'. Move should be atleastequal to 1 buffer of size % ` dK'.


by message.

5808 10WARNING: Dynamic loading of caches and pools throughloading a new file are not supported. However, theloadfile % ` s' will be inspected for consistency.Refer to s p_cacheconfig' and s ` p_poolconfig' tocreate or alter pools and caches.


1398



5809 16Less memory moved than requested in cache %s cache.Requested size = %d kb from pool %d, actual memorymoved = %d kb.


5810 16new (%d) buffer pool of size %d for cache %s isbeing created


5811 16The new load file does not have the cache %sdefinition. Cache type, size and number of cachesshould match the running values. Use sp_cacheconfigto determine the running value


5812 16The new load file has %d caches defined againstrunning %d cache definitions.Cache type, size andnumber of caches should match the running values.Use sp_cacheconfig to determine the running value.


5813 16The new load file has duplicate %s cachedefinitions, caches should be uniqueue.


5814 16Must configure with at least %d engine on-line.

Explanation: Check the System Administration Guide for informationabout online engines.

5816 16Legal values for the number of remote logins are 0or positive numbers.


1399



5817 16Legal values for the number of remote sites are 0 orpositive numbers.


5818 16Legal values for the number of remote connectionsare 0 or positive numbers.


5819 16Legal values for the number of pre-read packets perremote connection are 0 or positive numbers.


5820 16Number of remote logins should be greater than thenumber of remote sites.


5821 16Number of remote connections should be greater thanthe number of remote sites.


5822 16Version number should be between 0 and 10000.


5824 16Cannot reconfigure server to use sort order ID %d,because the row for its underlying character set (ID%d) does not exist in syscharsets.


1400



5825 16Cannot reconfigure the server's sort order since thesyscharsets table does not exist. You must upgradeyour server prior to attempting this.


5826 10You have just reconfigured SQL Server's default sortorder. System table indexes will be rebuilt whenyou reboot the SQL server.


5827 10In changing the default sort order, you have alsoreconfigured SQL Server's default character set.


5828 16Legal values for number of user connections are 1through %d.



5829 16Do not recommend more than %d engines on-line. Useoverride option to force this option.


5830 16Must configure with at least %d engine(s) on-line.


5831 16Cannot reconfigure the server's character set without of bounds character set ID %d.


1401



5832 10The stack size must be a multiple of the page size.It has been rounded from %d to %d.



5833 16Cannot reconfigure the server with an out-of-bound,illegal value for Systemwide Password ExpirationInterval.


5835 16Cannot reconfigure the server with an out-of-rangeaudit queue size. The valid range is %d to %dinclusive.


5836 10The additional network memory size must be amultiple of SYBPAGESIZE(2048). It has been roundeddown from %d to %d.


5837 10The default network packet size must be a multipleof 512. It has been rounded down from %d to %d.



5838 10The maximum network packet size must be a multipleof 512. It has been rounded down from %d to %d.


1402



5839 16The value of m ax network packet size', % ` ld',must be greater than or equal to the value of the

d` efault network packet size', % ` ld'.


5840 16Illegal value (%ld) specified for the number oflarge extents.


5841 16Cannot reconfigure the server's sort order with anout of bounds sort order set ID %d.



5842 16Number of cleanup blocks should be at least asgreat as the number of users. The number of userscurrently configured is %d.


5843 16Invalid Configuration: Cache alignment % ` ld' isinvalid. Alignment must be a power of 2 greaterthan or equal to 2048. Retry the command with alegal value.


5844 16Cannot reconfigure the auto identity column size tobe %d because the minimum precision of a numeric is1.


by message.

1403



5845 16Invalid value configured for lock promotionthreshold = %d. Configured value must be greaterthan or equal to %d.


5846 16Illegal value % ` ld' specified for configurationoption % s'. The legal values are between % ` ld' and

%` ld'.


5847 16Configuration Error: Configuration file % ` s' doesnot exist or you do not have the required read/writepermission for the file.


by message.

5848 16Warning: Unknown parameter % ` s' found on line

%` ld' of configuration file % ` s'. This parameter isignored. Edit the configuration file to remove orcorrect this parameter.


5849 16Verification failed for parameter % ` s'.



5850 16Notification failed for parameter % ` s'.


5851 16Configuration Error: Configuration file % ` s' has anunknown format on line %d.


1404



5852 16Changing the value of % ` s' is not allowed since itis a static option.


5853 19%` s' has been modified from % ` ld' to %` ld' by the

verification routine.


5854 18Configuration Error: Cannot write out file % ` s' dueto system error % ` s'.


5855 16Cannot change any of the configuration parameterssince the s` ysconfigures' table was not updatedduring startup.


5856 16The configuration parameter % ` s' can only be changedvia the stored procedure s ` p_configure'.


5857 16Changing the value of % ` s' is not allowed since itsvalue is calculated.


5858 10The configuration option % ` s' has been changed by

%` s' from % ld' to %` ld'.


5859 16The configuration number % ` d' is invalid.


5860 18Invalid datatype encountered for parameter % ` s'.


1405



5861 16The t` otal memory', % ` ld', is not enough to changethe parameter % s' to % ld'.


5862 18Invalid portion encountered.


5863 18Invalid group encountered.


5864 18Invalide option encountered in % ` s'.


5865 18error in os_get_cpu_count: %d


5866 10Configuration file % ` s' has been written and theprevious version has been renamed to % ` s'.


5867 16The wash size for the %dk buffer pool in cache%s has been incorrectly configured. It must be aminimum of %d buffers and a maximum of %d percent ofthe number of buffers in the pool.


5868 16Invalid type configured for cache %s. Cache typemay be one of mixed OR log only but NOT both.


5869 16Invalid buffer size of %dk for cache %s. Validbuffer sizes are powers of 2 between %dk and %dkinclusive.


1406



5870 16An invalid buffer size of %dk was encounterd incache %s. Valid buffer sizes for caches are powersof 2 between %dk and %dk inclusive.


5871 16Invalid pool size of %dk (%d buffers) encounteredfor the %dk pool in cache %s. Buffer pools musthave a minimum total size of %dk or %d buffers,whichever is greater.


5872 16The total size of the configured pools (%dk) incache %s is greater than the total size (%dk) of thecache.


5873 16Invalid configuration for the default %dk pool incache %s. The default %dk pool must be a minimum of%dk.


5874 16The total size of all configured caches (%dk) isgreater than the memory available for caches (%dk).


5875 16The cache type for the default data cache cannot bemodified.


1407



5876 16Multiple pools containing buffer sizes of %dkencountered in cache %s. Buffer sizes in a cachemust be unique.


5877 16Bad alignment value of %d encountered. Valid cachealignment values are powers of 2 in between %dKand %dK inclusive. The units of this value are inbytes.


5878 14Permission denied. Only users with role % ` .*s' canchange this configuration option.



5879 16The r` econfigure' command is no longer needed andsupported since its functionality has been migratedinto the s` p_configure' command'. Please refer tothe Reference Manual for details.


5880 16Warning: The operating system setting for filedescriptors, %d, is not large enough to configure

u` ser connections' to %d, d ` evices' to %d, andr` emote sites' to %d.


5881 16The value of d efault network packet size', % ` ld',must be less than or equal to the value of the m ` axnetwork packet size', % ` ld'.


1408



5882 16A cache alignment factor of %dk was specified butno buffer pool containing %dk buffers has beenconfigured. An attempt will be made to create thispool with extra memory (%dk bytes) from cache %s.


5883 16The value of n umber of locks', % ` ld', is not enoughto configure u ` ser connections' to % ` ld'. n ` umberof locks' should be at least twice the value of

u` ser connections'.


5884 10%s


5885 16The '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 actionindicated by message.

5886 16The 'lock promotion LWM'= '%d', cannot be greaterthan the 'lock promot

Explanation: ion HWM'= '%d'. Command failed due to invalid or

illegal request. Check syntax, semantics, and permissions. Take anycorrective action indicated by message.

5887 16Configuration Error: Duplicate Named Cache % ` s'found around line % ` ld' in the configuration file.


1409



5888 16Configuration Error: Two Named Caches with the

c` ache status' defined as d ` efault data cache' isnot allowed.


5889 16Configuration Error: Unknown cache status % ` s'defined for cache % ` s'.


5890 16Configuration Error: A Named Cache with c ` achestatus=default data cache' does not exist in theconfiguration file.


5891 16Named cache %` s' has been configured too small. Theminimum size of a named cache is %d Kilobytes.


5892 16You cannot use a llow sendmsg' option becausesyb_sendmsg() builtin is not supported on thisplatform.


5893 16The sum, (%s) + (%s %s) + (%s) + (%s), must be nogreater than %` ld'.


5894 16Configuration Error: Duplicate pool size definitionof %` s' for Named Cache % s'.


1410



5895 16Configuration Error: Duplicate wash size definitionof %` s' for Named Cache % s'.


by message.

5898 10WARNING!!! %dK buffer pool has been deleted. Thelog I/O size for the following databases have beenset to %dk. You must change the log I/O size to anexisting pool size.


5899 16The value of the t ` otal memory' parameter (%ld)defined in the configuration file is not high enoughto set the other parameter values specified in theconfiguration file.


1411



5901 20Was unable to get an alarm, the backgroundcheckpoint process is unable to run.


5902 20Serious kernel error reported on upsleep call,unwilling to continue. Aborting the backgroundcheckpoint process.


5903 16Unable to open database with id = %d, suspectinconsistency in sysdatabases table.

Explanation: Report this error to the System Administrator so dbccdiagnostics can be run.

1412



6001 10SHUTDOWN is waiting for %d process(es) to complete.


6002 10A SHUTDOWN command is in progress. Please log off.


6003 10This process terminated by SHUTDOWN command.


6004 14Permission denied. Only users with SystemAdministrator (SA) role can run the SHUTDOWNcommand.


6005 10A SHUTDOWN is in progress.


6006 10Server SHUTDOWN by request.


1413



6008 10Unable to write statistics for object %ld indatabase %ld. Please run update statistics on thistable after boot-up or prior to accessing the tablenext time.

Explanation: This is an informational message but requires the specifiedfollowup action.

6009 10Unable to write statistics for all objects indatabase %ld. Please run update statistics on allobjects in this database after boot-up or afterloading this database.


6010 10Unable to write statistics for index %ld of object%ld in database %ld. Please run update statisticson this index after boot-up or prior to using thisindex.


6011 10Unable to write statistics for all indexes of object%ld in database %ld. Please run update statisticson all indexes after boot-up or prior to using theindexes next.


1414



6101 16Process %d' is not a valid process number. Choosea number between 1 and % d'.


6102 14Permission denied. Only users with SystemAdministrator (SA) role can run the KILL command.


6103 17Unable to do cleanup for the killed process;received Msg %d.


6104 16You cannot use KILL to kill your own process.


6106 16Process %d' is not an active process number.


6107 14Only User processes can be KILLed or SYB_TERMINATEd.


6108 16Process %d' is not sleeping under a valid KILLcondition, and therefore cannot be KILLed.


1415



6201 10STEP %d


6202 10The type of query is SELECT (into Worktable%d).


6203 10The type of query is %s.


6204 10The update mode is direct.


6205 10The update mode is deferred.


6206 10GROUP BY


6207 10Vector Aggregate


1416



6208 10Scalar Aggregate


6209 10This step involves sorting.


6210 10Worktable%d created for ORDER BY.


6211 10Worktable%d created for DISTINCT.


6212 10Worktable%d created for REFORMATTING.



6213 10Worktable%d created for SELECT_INTO.



6214 10TO TABLE



1417



6215 10FROM TABLE


6216 10Worktable%d.


6217 10%.*s


6218 10DISJOINT TABLE : nested iteration.


6221 10Using GETSORTED



6222 10Using Dynamic Index.



6223 10Table Scan.



1418



6224 10Using Clustered Index.


6225 10Index : %.*s


6226 10Index name not found.


6227 10Log Scan.


6228 10Cursor name %.*s' is declared on procedure % ` .*s'.



6229 10Cursor name %.*s' is declared at nesting level

%` d'.


6230 10The cursor is positioned after the last row.


1419



6231 10The current cursor position has been deleted.


6232 10The cursor is positioned before the next row.


6233 10The cursor is positioned on a row.


6234 10There have been %d rows read, %d rows updated and %drows deleted through this cursor.


6235 10The cursor is not open.


6236 10The cursor will be closed if the current position isdeleted.



6237 10The cursor will be closed when a transaction iscommitted or rolled back.


1420



6238 10The cursor will remain open when a transaction iscommitted or rolled back.



6239 10The number of rows returned for each FETCH is %d.


6240 10The cursor is read only.


6241 10The cursor is updatable.


6242 10There are %d columns returned by this cursor.


6245 10Name = %` .*s', E ` xpression Result', Type = %s,Length = %d (%S_MSG)



6246 10Name = %` .*s', Table = % ` .*s', Type = %s, Length =%d (%S_MSG)


1421



6249 10There are no active cursors.


6250 10There are no active cursors that match the searchcriteria.


6251 10This cursor is declared within a stored procedure.The cursor's memory usage cannot be distinguishedfrom that of the procedure as a whole.


6252 10This cursor is declared on a stored procedure.It is presently using % ` d' bytes. However, thememory usage will increase when the cursor is openedbecause the query plan will be associated with thecursor at that time.


6253 10This cursor is declared on a stored procedure. Itis using %ld bytes of memory. The procedure's plan(%ld bytes) will be returned to the procedure cachewhen the cursor is closed.


1422



6254 10This cursor is using %ld bytes of memory.


6255 10The cursor id is %ld.


6256 10The cursor has been successfully opened %d times.


6257 10The cursor was closed by a CLOSE CURSOR statement.


6259 10The cursor was closed because its current scanposition could not be maintained following a delete,update or insert.


6260 10The cursor was closed because it was declared on ajoin and its current position was deleted.


1423



6261 10The cursor was closed due to an error on the OPENCURSOR statement.



6262 10The cursor was closed because CLOSE ON ENDTRAN wasSET ON and the transaction containing the cursorended.


6263 10The cursor is read only because it is declared on aunion.


6264 10The cursor is read only because it is declared on agroup by or its plan includes a group by operation.


6265 10The cursor is read only because it contains aDISTINCT.


6266 10The cursor is read only because it contains anaggregate.


1424



6267 10The cursor is read only because it contains an ORDERBY clause.



6268 10Showplan output for the cursor:


6269 10The cursor is currently scanning at isolation level0.


6270 10The cursor is currently scanning at a nonzeroisolation level.


6271 10The cursor was compiled at isolation level %d.


6272 10Using I/O Size %d Kbytes for index leaf pages.


6273 10With %S_MSG Buffer Replacement Strategy for indexleaf pages.


1425



6274 10Evaluate Grouped %s.


6275 10Evaluate Ungrouped %s.


6276 10Forward scan.

Explanation: This is an informational message or a message header.


6277 10Backward scan.


6278 10Positioning at start of table.


6279 10Positioning at end of table.


6280 10Positioning by Row IDentifier (RID).


6281 10Positioning by key.



6282 10Positioning at index start.


1426



6283 10Positioning at index end.


6284 10Scanning only the last page of the table.


6285 10Scanning only up to the first qualifying row.



6286 10Index contains all needed columns. Base table willnot be read.


6287 10Keys are:


6288 10%.*s %S_MSG


6289 10QUERY PLAN FOR STATEMENT %u (at line %u).


6290 10MRU


1427



6291 10LRU


6292 10Using %d Matching Index Scans


1428



6401 16Cannot rollback %.*s - no transaction or savepointof that name found.


6402 20Inconsistency in rollback logic. ROLLBACK findsno matching SAVE TRANsaction or BEGIN TRANsaction.ROLLBACK aborted.


the current process. Report the error to your System Administrator.

6403 20No matching savexact record found when rolling backthe subordinate transaction %.*s.


6404 18Process %d in database %` .*s' was aborted. Thetransaction was rolled back, but an ENDXACT recordwas not written, probably because the log is full.


1429



6701 16Could not open dbid %d, object %ld.


6702 20Protection hash chain corrupt: element of typeUNUSED found in hash chain (dbid %d, object %ld,protection type %d, protection status %d, column map%ld)



1430



6901 21Overflow on High component of timestamp occurred indatabase %d. Database table possibly corrupt.


6902 21Page timestamp value falls between the old and newtimestamps from log. Page #=%ld, object id = %ld,page timestamp=%04x %08lx. Log: old timestamp=%04x%08lx, new timestamp=%04x %08lx.


6903 21High order of timestamp indicates that timestampstructure may be incorrect.

Explanation: Adaptive Server encountered an internal error affectingall processes in the current database. Report the error to your SystemAdministrator so dbcc diagnostics can be run. (Printed with trace

output in Release 11.0 and higher.)

6904 21Mismatch between database table passed and the onefound in the system structure when requesting newdatabase timestamp. Database id passed in : %d.System database id : %d.

Explanation: Report the error to your System Administrator. Checksystem tables first. (not raised in Release 11.0 and higher.)

1431



7001 16A transaction attempted on external table.


7002 16Attempt to open VOS file failed


7003 16Attempt to close VOS file failed


7004 16Attempt to sequential_read VOS file failed


7005 16Segment name must be non-null; holds fully qualifiedVOS file path name


7006 16External table file name error


7007 16Illegal datatype for external table


1432



7008 16NULL not allowed for external table


7009 16Create unique index and create clustered index arenot allowed for external tables.


7010 16No index named %.*s' exists on the OS file forexternal table % ` .*s'.


7011 16Attempt to get file status for external tablefailed.


7012 16External table - skipped.


7013 10Create database feature is disabled.


7014 10Drop database feature is disabled.


1433



7015 10Alter database feature is disabled.


7016 10Only money(19, 4) is allowed for non-externaltables.


7017 10The %s (%d) for column '%.*s' in external table'%.*s' must be within the range %d to %d.


7018 20Bad offset (%d) should be (%d) for external tablecolumn.


7019 20No conversion buffer available for conversion, fatalerror.


7020 16Attempt to bulk copy into an external table.


by message.

1434



7021 16The embedded_key index type must be used whencreating a VOS index for external tables.


by message.

7022 16Descending order not allowed in the VOS index usedfor external tables, use ascending order.


7023 16The argument duplicates_allowed must be true in theVOS index for external tables.


7024 16The collation_code argument must be ascii or numericwhen creating a VOS index for extgernal tables.


7025 20Process not running on engine with attached portsfor external table during external table scan.


7026 16External tables index file name % ` .*s' is too long.Maximum length is %d.


by message.

1435



7101 17Unable to allocate new text value, dbid %d.


7105 22TEXT/IMAGE page %d does not have a next page,although it should.


7109 22Unexpected log record of type %d found whileprocessing TEXT/IMAGE data.


7112 17Deadlock occurred while trying to lock page %ld,which is held by SQL Server process %d.

Explanation: Retry the command.

7114 22Page %ld is not a valid text page.

Explanation: Refer to the detailed writeup for Error 7114 in the chapter“Error Message Writeups”.

7120 22Log record %ld:%d was not found in the LOG.


7121 22Free 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 dbccdiagnostics run.

1436



7123 16Invalid text pointer value %s.


7124 16The offset and length specified in the READTEXTcommand is greater than the actual data length of%ld.


7125 16Text pointer value conflicts with the column namespecified.


7126 16Text pointer value references a data page with aninvalid text status.


7127 16Text pointer value references a data page with aninvalid time stamp.


7128 16Text pointer value references a data page which isno longer allocated.


7129 16Synchronization time stamp does not agree with textdata page value.


1437



7130 16WRITETEXT with no log is not valid at this time.Database %s must first be configured for this.


7131 16Invalid table and column name specified in textvalidfunction.



7132 16Selection of TEXT and IMAGE datatypes require DBLIB4.0 or greater.


7133 16NULL textptr passed to %s function.


7134 16The text table and the table referenced by the textpointer disagree.


7136 16SQL Server is now using a multi-byte characterset, and the TEXT character counts have not beenre-calculated using this character set for table'%.*s'. Use DBCC FIX_TEXT on this table beforerunning the query again.

Explanation: Take the corrective action before running queries.

1438



7137 20Textptr Write Failed: An error occured whileattempting to write text/image replicationinformation for database %.*s, table %.*s, column%.*s. Please contact Sybase Technical Support forassistance. ( page %ld, datapage %ld, datarow %d )


7138 20Text/Image Replication Failure: A memory allocationerror occured during replication of table %.*s, indatabase %.*s. Try restarting the Sql Server with alarger procedure cache, or contact Sybase TechnicalSupport.


7139 16Insert to a TEXT/IMAGE column from a non TEXT/IMAGEfield which involves internal worktable (eg.orderby, groupby) processing is not supported.Rewrite your query to avoid conversion from nonTEXT/IMAGE datatype to TEXT/IMAGE datatype.



7140 16A deadlock was detected while attempting to lock thefirst text page for text pointer %s.

Explanation: A locking or deadlock error occurred during an attempt toupdate a TEXT/IMAGE page. Retry the command.

7141 16A lock request was interrupted while attempting tolock the first text page for text pointer %s.

Explanation: A SQL command involving a TEXT page was interruptedby the user with a control-c or equivalent.

1439



7142 16The text pointer %s refers to a TEXT/IMAGE pagethat has been allocated to a different row. Thisoccurred because the original row was updatedor deleted during an internal deadlock avoidancemanuever.

Explanation: A locking or deadlock error occurred during an attempt toupdate a TEXT/IMAGE page. Retry the command.

7143 18The maxlen field of non-TEXT/IMAGE constant node isnon-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 toyour System Administrator. (Not raised in Version 11.9.2)

7144 16Mime pointer %s does not point to a multi-partmessage.

Explanation: Check input and syntax.

7145 16Message pointed to by mime pointer %s has less than%d parts.

Explanation: Check command input.

7146 16Non-zero starting offset can not be used with MIMEtype.


7147 16Retrieval of partial MIME messages is not supported.


7148 16Feature %s is not implemented.

Explanation: Invalid or illegal command.

7149 16Invalid input value (%s) for parameter %s


7150 16MIME message malformed - can't find concludingboundary '--%.*s--'. Insert/Update is aborted.

Explanation: Check command and input data.

1440



7151 22Selected message has %d bytes less than expected.Message is probably corrupt. Please contact yoursystem administrator.

Explanation: Report the error to your System Administrator. AdaptiveServer must be restarted.

7152 16Boundary string specified in 'content-type' headeris too long. Maximum allowable length is 70characters.

Explanation: Check query and input data.

1441



7201 17Can't open a connection to site % ` S_SRVID' becausethere are no remote sites available. Rerun whenthere are fewer active remote sites, or contact auser with System Administrator (SA) role.


7202 17Can't open a connection to site % ` S_SRVID' becausethere are no available PSS structures.


7203 17Can't open a connection to site % ` .*s' becauseSQL Server is not configured for enough userconnections. See the error log file in the SQLServer boot directory.



7204 18Can't open a connection to site % ` .*s' because thesite is already active.


7205 18Can't open a connection to site % ` S_SRVID'. See theerror log file in the SQL Server boot directory.


7206 17Can't open a connection to site % ` S_SRVID' becauseall channel numbers are in use.



1442



7207 17Can't open a connection to site % ` S_SRVID' becausethere are no remote connections available. Rerunwhen there are fewer remote users and/or fewer localusers making remote accesses, or contact a user withSystem Administrator (SA) role.

Explanation: Refer to the detailed writeup for Error 7207 in the chaptertitled “Error Message Writeups”.

7208 17Can't open a connection to site % ` S_SRVID' becausethere are no remote logins available. Rerun whenthere are fewer local users making remote accesses,or contact a user with System Administrator (SA)role.


7209 17Cannot open a connection to site % ` S_SRVID' because%S_MSG buffer could not be initialized.


7210 18Can't open a connection to site % ` S_SRVID' because

s` et up channel' message could not be sent.



7211 18Can't open a connection to site % ` S_SRVID' because

s` et up channel' message was not acknowledged.

Explanation: Refer to the detailed writeup for this message in thechapter titled “Error Message Writeups”.

7212 11Can't close connection %d on site % ` S_SRVID' becauseit is not active.


1443



7213 18Can't remove site % ` .*s' from list of active sitesbecause it is missing.



7214 11No site name received in server login packet.Server login rejected.


7215 18Can't send to site % ` S_SRVID'.


7216 18Can't read from site % ` .*s'.


7217 18Echo failed from site % ` .*s'.


7218 11Site % .*s' not found in sysservers.


7219 11Site %d not found in sysservers.


7220 11Site %s' not found in interfaces file.


7221 14Login to site % ` S_SRVID' failed.


1444



7222 18Received bad token 0x%x from site % ` S_SRVID'.


7223 16Cannot %S_MSG site %S_SRVID'.


7224 16Unexpected end-of-message encountered in RPCresponse from site % ` S_SRVID'.

Explanation: Failure in Remote Procedure Call (RPC). Check syntax.Check sending and receiving Adaptive Server environments for remoteaccess.

7225 16Unknown datatype token %d % s' encountered.

Explanation: Failure in Remote Procedure Call (RPC). Check syntax.Check sending and receiving Adaptive Server environments for remoteaccess.

7226 16Alternate row received for id %d with nocorresponding format information.

Explanation: Failure in Remote Procedure Call (RPC). Check syntax.Check sending and receiving Adaptive Server environments for remote

access.

7227 17Can't open a connection to site % ` S_SRVID' becauseSQL Server is not configured for remote access.Ask a user with System Administrator (SA) role toreconfigure SQL Server to allow remote access.


7228 18Received a final DONE packet with DONE_ACK on site

%` .*s'.


1445



7229 18Unable to obtain the remote Server's OS SessionLabel.



7230 18The OS Session Label of the remote Server processdoes not equal the connection level assigned to it.


7231 18The OS Session Label, curread and curwrite labels ofthe Client do not equal the connection level for theremote Server.


7232 18Internal MAC Subsystem error. OS Binary to MasterSLID Conversion failed.


7233 18Internal MAC Subsystem error. Master SLID to OSBinary Conversion failed.


7234 10Failed to connect to remote server %s %s %s %s %sfor site %s. Trying the next query entry of thisserver, if any.

Explanation: Refer to the detailed writeup for Error 7234 in the chapter

titled “Error Message Writeups”.

1446



7235 17No other query entry found for the remote server %s- site %s. Aborting this site handler, as no remoteserver responded. Please make sure the remoteserver is accepting connections.


7236 20Remote site % S_SRVID' became unavailable duringexecution of an RPC.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the errorto your System Administrator so dbcc diagnostics can be run. (Notraised in 11.9.2).

7237 17Unable to connect to site % ` S_SRVID' since thecorresponding site handler is about to exit.

Explanation: Failure to connect to a remote site - the corresponding sitehandler was exiting. (Not raised in 11.9.2).

7239 17Failed to allocate a security session structure forsite %s.



7240 18Mechanism %s is not enabled for use for RPC ModelB because the Security Control Layer has not beeninitialized.


Report the error to your System Administrator.

7241 18Security Session establishment failed during SecuredRPC Model B login.


1447



7242 18Security Negotiation failed during Secured RPC ModelB login.


7243 16Internal Limit reached. All local LOGCONN arraysegments are full. The following display isaccurate, but it does not contain all activeLOGCONNs. Displaying %d active LOGCONNs in %d localarrays.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby message. (Not raised in 11.9.2).

1448



7301 15FOR UPDATE has been incorrectly specified for a READONLY cursor.


7302 15The row number specification for a SET CURSOR ROWSstatement must be an integer value greater than0.The given value is % ` d'.


7303 15FOR BROWSE can not be used in the declaration of acursor.


7304 15FOR READ ONLY can not be used in a SELECT which isnot part of the declaration of a cursor or which isnot inside a stored procedure.



7305 15FOR UPDATE can not be used in a SELECT which is notpart of the declaration of a cursor or which is notinside a stored procedure.


7307 15COMPUTE clause can not be used in the declaration ofa cursor.


7308 15SELECT-INTO can not be used in the declaration of acursor.


1449



7309 10SQL statement on line number %d contains %S_MSG. Theerror is caused due to the use of %s.


7310 10SQL statement on line number %d contains %S_MSG. Theerror is caused due to the use of non-ANSI option:%S_MSG.


7311 10Line number %d contains %S_MSG. The error is causeddue to the use of Sybase declared global/localvariables.


7312 10Line number %d contains %S_MSG. The error is causeddue to the use of Sybase built-in function: %.*s.


7313 10Line number %d contains %S_MSG. The error is causeddue to the use of non-standard control flow: %s.


7314 10Line number %d contains %S_MSG. The error is causeddue to the use of non-standard transaction keyword(s): %S_MSG.


7315 10Line number %d contains %S_MSG. The error is causeddue to the use of Non-ANSI conversion function(s).


7316 10Line number %d contains %S_MSG. The error is causeddue to the use of database prefix.


7317 10Line number %d contains %S_MSG. The error is causeddue to the use of %S_MSG %S_MSG.


1450



7318 10Line number %d contains %S_MSG. The error iscaused due to the use of Non-ANSI drop objectfunctionality: %S_MSG.


7319 10Line number %d contains %S_MSG. The error is causeddue to the use of Non-ANSI operator: %S_MSG.


7320 10Line number %d contains %S_MSG. The error iscaused due to the use of Non-ANSI pattern matchingcharacter(s).


7321 10Line number %d contains %S_MSG. The error is causeddue to the use of column name(s) in a select listwith aggregates but column name(s) not in group bylist.


7322 10Line number %d contains %S_MSG. The error is causeddue to the use of set operations in an insertselect: %S_MSG.


7323 10Line number %d contains %S_MSG. The error is causeddue to the use of column headings.


7324 10Line number %d contains %S_MSG. The error is causeddue to the use of compute statement.


7325 16Nulls not allowed in a primary key column.


1451



7326 10Line number %d contains %S_MSG. The error is causeddue to the use of Non-ANSI escaping of [ ` o` r ] ' ina LIKE ESCAPE.


7327 10Length specification %d is zero or negative.


7328 10Specified scale %d is negative.


7329 15There are too many parameters given with function

%` .*s'. The maximum number of parameters allowed is%d.


7330 15Within %s, you are not allowed to specify thedatabase name prefix for the new object name in%s. All new objects must be created in the currentdatabase.


7331 15Within %s, you can't create an object owned byanother user. The specified object owner is % ` .*s',but the schema authorization id is % ` .*s'.


7332 15%S_MSG is allowed only in %S_MSG


7333 15%s does not allow specifying the user name as aprefix to the object name.


1452



7334 16Subqueries are not allowed in a RAISERROR.


7335 15A SELECT statement that assigns a value to avariable must not be combined with a COMPUTE clause.


7336 10Line number %d contains non-ANSI identifier. Lengthof identifier % ` .*s' is greater than 18.


7337 10FIPS WARNING: Truncation when inserting longchar/varchar into shorter char/varchar.


7338 10FIPS WARNING: Union of exact numeric with differentprecision or scale.


7339 10FIPS WARNING: Union of chars or of literals withdifferent lengths.


7340 10FIPS WARNING: Union of chars with literal.


7341 10FIPS WARNING: Inserted approximate numeric intoexact numeric.


7342 15Keyword SHARED can not be used in a SELECT statementwhich is not part of the declaration of a cursor.


1453



7343 15The value (%d) given to the %S_MSG is not within theallowed range. The allowed range is between %d and%d.


7344 16DECLARE CURSOR must be the only statement in a querybatch.


7345 16SELECT is not allowed in a dynamic EXECUTE IMMEDIATEstatement.


7346 16Invalid arguments for RAISERROR extended error data.



7347 16The IDENTITY function should be used only when theSELECT statement has an INTO clause.


7348 16Select expression results in more than one columnhaving same name. Column name % .*s' is specifiedmore than once


1454



7349 16FIPS WARNING: Due to usage of the name of anexpression in the ORDER BY clause which has acorrelation name in the select list


7350 16FIPS_WARNING: Use of implicit or explicit ALL inCOUNT aggregate function. Only COUNT(*) or COUNT(DISTINCT <expression> ) is allowed.


7351 16Local or global variables not allowed in viewdefinition


7352 16The SET option with ARITH_OVERFLOW is allowed onlyin SET ARITHABORT or SET ARITHIGNORE.

Explanation: See s` et arithabort/arithignore' command restrictions.

7353 16The SET option with NUMERIC_TRUNCATION is allowedonly in SET ARITHABORT.


7354 16The SET can have option restrictions only when thereis one option in the command.


1455



7355 16Table (or view) % ` .*s' created by SELECT INTOor CREATE VIEW results in a column with no name.Please specify a column name for computed columns.


7356 16Aggregates or subqueries are not allowed in checkconstraints.


7357 15Label options (CURREAD, CURWRITE) cannot be usedwith non-label SET options in a single SET commmand.


7358 16Invalid type argument specified for the %s builtinfunction. Argument must either be SENSITIVITY orSENSITIVITY_BOUNDARY.



7359 16SYB_IDENTITY is not allowed in READ or WRITE TEXTScommands.


7360 16Explicit updates/inserts cannot be done onsensitivity or information columns.


by message.

1456



7361 16FIPS WARNING: GROUP BY clause specified when all theitems in select list are aggregate functions or noneof the items in select list are aggregate functions.


7362 16FIPS WARNING: Select list contains aggregatefunction(s) but GROUP BY clause not specified.


7363 16You can not have variable assignments in a SELECTstatement with the UNION operation.


7364 16Tables %.*s' and %` .*s' have same exposed names.Use correlation names to distinguish them.


7365 16A column in the FOR UPDATE OF list can only bequalified by a table or correlation name. Column

%` .*s' is qualified by an table owner and/ordatabase name.


by message.

7366 16A column in the FOR UPDATE OF list can only bequalified by an exposed table or correlationname. %` .*s' is not an exposed name in the selectstatement.


1457



7367 16Expected row size '%d' is not a valid value;expected row size must be greater th an 9 or can beeither 0 or 1.


7368 16Can not create column by name S ` YB_IDENTITY_COL'.This name has special meaning when a ` uto_identity'option is ON.



7369 15Procedure Grouping is not allowed.



7370 16Specified precision %d is more than the maximumprecision %d.


7371 16Specified scale %d is more than the specifiedprecision %d.


7372 15Cursor FOR UPDATE cannot be specified at isolationlevel 0.


7373 15Browse mode cannot be specified at isolation level0.


1458



7374 15Invalid isolation level specified.


7375 15SELECT INTO cannot be specified with isolation levelclause.


7376 15Select in a CREATE VIEW cannot be specified withisolation level clause.



7377 15SELECT INSERT cannot be specified with isolationlevel clause.


7378 15HOLDLOCK/NOHOLDLOCK/SHARED/READPAST conflicts withAT ISOLATION LEVEL 0.


7379 14Permission denied. You must have the R ` eplication'role to set %.*s ON or OFF. Please contact a userwith System Security Officer (SSO) role for help.

Explanation: Command failed. Certain SET commands requirereplication role.

7380 10WARNING: Line %d. Invalid value for % ` S_MSG'specified. This value will be ignored, defaultvalue will be used instead.


1459



7381 10prefetch size


7382 16Subqueries are not allowed in an ORDER BY clause.


7383 16Subqueries are not allowed in a GROUP BY clause.


7384 16Subqueries are not allowed in a COMPUTE clause.


7385 16The number of subqueries in the query exceeds themaximum allowed (%d).


7386 10Set dup_in_subquery is no longer supported. Toget similar performance and semantics, rewrite thesubquery as a join.


7387 15The maximum number of parameters in a dynamic SQLstatement is %d.


1460



7388 16An aggregate of an aggregate produces a scalarvalue. Any further nesting of aggregates has noeffect. Remove the aggregates beyond level two.


7389 16A HAVING clause with aggregates of different levelsis not allowed.


7390 14Permission denied. Only a user with R ` eplication'authorization can set %.*s ON or OFF. Please contactyour System Administrator (SA) for help.


7391 15The table count specification for a SET TABLE COUNTstatement must be an integer value greater than 0.The given value is % ` d'.


7392 15Procedure Grouping is not allowed. Please contacta user with System Security Officer (SSO) role forhelp.


7393 16The value of forced parallel degree cannot benegative.


7394 15Duplicate specification of '%S_MSG' clauses for onetable is not allowed.

Explanation: Check command syntax.

1461



7395 10forced index

Explanation: This is informational text.

7396 10forced parallel


7397 10forced lru/mru


7398 10forced prefetch


7399 15Reserved page gap '%d' is not a valid value;reserved page gap must be between 0 and 255

Explanation: Command error. Check parameters.

1462



7401 10Could not allocate memory for the threshold task'sargument list; threshold task cannot be spawned fordatabase %d, segment %d, free space %ld.


7402 10Could not spawn the threshold handler procedure fordatabase %d, segment %d, when only %ld free pageswere left in the segment.


7403 10Threshold task could not use database %d, and socannot execute the threshold procedure for segment%d, free space %ld.


7404 10Could not find row in systhresholds for database%.*s describing segment %d, free space %ld.


7405 10Threshold procedure name is missing from thesysthresholds row in database %.*s for segment %d,free space %ld.


7406 16%s: unknown option: %.*s


7407 10Failed to execute the threshold procedure fordatabase %d, segment %d, free space %ld.


7408 16Could not find a dbtable for database %d.


1463



7409 20This task tried to sleep waiting for space to becomeavailable in the log, but could not. The currentcommand is being aborted because no further databasechanges can be logged.


7410 26%s: function called with invalid argument.


7411 21Table s ysthresholds' in database % ` .*s' is not inits correct sort order. Either the clustered indexis missing or there is data corruption in the table.


7412 10Space available in the log segment has fallencritically low in database % ` .*s'. All futuremodifications to this database will be %S_MSG untilthe log is successfully dumped and space becomesavailable.


7413 10%d task(s) are sleeping waiting for space to becomeavailable in the log segment for database %.*s.


7414 10Threshold procedure % ` .*s' returned an errorindication (@status=%d) when called for database

%` .*s', segment % ` .*s', free_space %ld.


7415 16The transaction log in database %.*s is almost full.Your transaction is being %S_MSG until space is madeavailable in the log.


1464



7416 20Could not open Systhresholds table for database%.*s.


your System Administrator so DBCC diagnostics can be run.

7417 21The last chance threshold entry for logsegmentis not present in threshold cache for database'%S_DBID'. Please use 'dbcc thresholds' to see thethreshold cache contents and contact your systemadministrator.

Explanation: Adaptive Server encountered an internal error affectingall processes using the current database. Report the error to yourSystem Administrator. Adaptive Server must be restarted and DBCC

diagnostics run.

7418 22The last chance threshold entry for logsegment isnot 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 yourSystem Administrator. Adaptive Server must be restarted and DBCC

diagnostics run.

7419 16lct_admin(abort): Process %d that you are trying toabort is not a valid process. Choose a process withid between %d and %d.

Explanation: Check command inputs and retry.

7420 16lct_admin(abort): Cannot abort yourself. Yourprocess id %d and the given process id %d.


7421 16lct_admin(abort): Process %d is not an activeprocess. Cannot abort it.


1465



7422 16lct_admin(abort): Process %d is not an userprocess. Only an user process waiting onlog-suspend mode can be aborted.


7423 10lct_admin(abort): Process %d waiting on log-suspendstate on database '%S_DBID is being aborted.


7424 16lct_admin(abort): Cannot abort process %d, as itis not sleeping on log-suspend state in database'%S_DBID'.


7425 16lct_admin(unsuspend): This command is not supportedanymore. If you want to abort the tasks sleepingon log-suspend state, please consider usinglct_admin(abort).


7426 16lct_admin(abort): Database '%S_DBID' did not reachthe last chance threshold. This command will haveno effect on the database.


7427 10Failed to complete LCT_ADMIN() function. Pleaselook for any previous messages that may helpidentify the cause.


about any warning issued in the message. (Not raised in 11.9.2)

7428 17Could not add the last chance threshold for database'%S_DBID'.

Explanation: Command did not execute due to potential resourceproblem.

1466



7429 16Database '%.*s' contains too many thresholds. Itmay contain at most %d thresholds. Drop thresholdsas required to bring the database below the limit.

Explanation: Take the corrective action indicated.

7430 16The unsuspend option is disabled. To free logspace, terminate the longest running transaction inthis database.

Explanation: A long-running transaction is holding log space. Check

the transaction id (xactid) in the syslogs table. (Not raised in Version11.9.2)

7431 16To resolve the problem, locate the spid of thelongest running transaction in master..syslogshold.Terminate that session so that you can dump thetransaction log and free up log space.

Explanation: A long-running transaction is holding log space. Checkthe transaction id (xactid) in the syslogs table. (Not raised in Version11.9.2)

7432 14Unable to complete lct_admin() as it failed duringprotection check.

Explanation: You do not have permission to execute this command.Have the object owner or a user with the needed role run this command.

(Not raised in Version 11.9.2)

7434 16lct_admin('unsuspend') is no longer supported. Werecommend that you use the KILL command to stopsuspended processes. You may wake individualprocesses using lct_admin('w akeup', <spid>).

lct_admin('unsuspend') is no longer supported. Werecommend that you use the KILL command to stopsuspended processes. You may wake individualprocesses using lct_admin('w akeup', <spid>).


1467



7435 16lct_admin(abort): Process %d is a child-process.Cannot abort it.


7436 18lct_admin(abort): Unable to obtain DBTABLE forprocess %d. Cannot abort it.


Report the error to your System Administrator.

1468



7601 14Permission denied. System Security Officer (SSO)role is required to open an auditing system table.


7602 16There is no such audit option. If you received thismessage while executing a Sybase-supplied auditingstored procedure, this is a system error, and youshould contact a user with System Administrator (SA)role.


by message.

7603 14The ad_hoc_audit builtin function cannot be calleddirectly. You must use sp_addauditrecord to send anad-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 20An unknown audit event type was received. This is asystem error. Contact a user with System SecurityOfficer (SSO) role.


7605 20An attempt to send a message to the audit processhas failed. This is a system error. Contact a userwith System Security Officer (SSO) role.


1469



7606 20An attempt to allocate memory for the audit queuehas failed. This is a system error. Contact a userwith System Security Officer (SSO) role.


7607 20An attempt to establish a system mailbox for theaudit process has failed. This is a system error.Contact a user with System Security Officer (SSO)role.


7608 20An attempt to open the sybsecurity database hasfailed. This is a system error. Contact a userwith System Security Officer (SSO) role.


7609 20An attempt to load the global audit options intosysauditoptions has failed. This is a system error.Contact a user with System Security Officer (SSO)role.


7610 20An attempt to open the sysaudits table has failed.This is a system error. Contact a user with SystemSecurity Officer (SSO) role.


7611 20An attempt to awaken the server initializationprocess has failed. This is a system error.Contact a user with System Security Officer (SSO)role.


1470



7612 20An attempt to get an audit record from the auditqueue has failed. This is a system error. Contacta user with System Security Officer (SSO) role.


7613 14Permission denied. System Security Officer (SSO)role is required to create or drop the sybsecuritydatabase.


7614 14Permission denied. System Security Officer (SSO)role is required to create an auditing system table.


7615 16The auditing system tables can only be created inthe sybsecurity database.


7616 16You can only use SELECT or SELECT INTO with thesysaudits table.


7617 20An attempt to get a free audit record buffer fromthe audit queue has failed. This is a system error.Contact a user with System Security Officer (SSO)role.


1471



7618 20The audit process is not currently active. Contacta user with System Administrator (SA) or SystemSecurity Officer (SSO) role.


7619 20An insert to the sysaudits table has failed. Thisis a serious error, and you should contact a userwith System Administrator (SA) or System SecurityOfficer (SSO) role.


7620 14You must use one of the Sybase-supplied auditingstored procedures to change audit options.



7621 20The sybsecurity database has run out of space oris not readable. Please check with your SA. Youcan use the threshold manager to avoid 1105 (outof space) errors. The audit process has beenterminated.

Explanation: Adaptive Server encountered an internal error affectingthe current process. A transaction was started but there is no spaceor the database is not readable. Report the error to your System

Administrator. (Not raised in 11.9.2)

7623 20Auditing: Fatal error - unable to get objectowner name to fill in the audit record. This is aninternal error.

Explanation: Adaptive Server encountered an internal error affectingthe current process. A username could not be obtained for the audit

record. Report the error to your System Administrator.

1472



7624 20Auditing: Fatal error - unable to get auditcreation flags in the database with dbid % ` d'. Thisis an internal error.

Explanation: Adaptive Server encountered an internal error affectingthe current process when trying to update audit records. Report theerror to your System Administrator.

7625 20Audit table number % ` d' is invalid.


7626 20Auditing: Internal erorr - could not get the nextaudit table number.


7627 20Auditing: Fatal error - current audit table is fulland server is configured to suspend auditing whendevice is full, but it failed to suspend the auditprocess. This is an internal error.


7628 16Invalid value for audit related configurationparameter because the audit subsystem is notrunning. Contact a user with System SecurityOfficer (SSO) Role.

Explanation: You attempted to change audit configuration withoutinstalling sybsecurity database.

1473



7629 18Auditing: Internal error - current audit tableconfig parameter value may not be updated in theconfiguration file and in sysconfigures systemtable. Accurate value of this parameter is insyscurconfigs system table. This is not a criticalerror.

Explanation: Adaptive Server encountered an error while attemptingto change audit table information. Report the error to your System

Administrator.

7631 16Current audit table can not be changed to % ` d'because it is not empty.

Explanation: Adaptive Server encountered an error while attemptingto change audit table information. Report the error to your SystemAdministrator.

1474



7701 16Overflow when converting from char to type %s, value= %` .*s'.


7702 16Overflow when converting from numeric(%d,%d) to type%s'%.*s', value = % ` .*s'.


7703 16Overflow when converting from decimal(%d,%d) to type%s'%.*s', value = % ` .*s'.


by message.

7704 16Truncation error when converting to exactnumeric(%d,%d) from type %s'%.*s', value = % ` .*s'.


7705 10Invalid pattern string. The character following theescape character must be percent sign, underscore,left square bracket, right square bracket, or theescape character.


7706 10Pattern string is too long. The given patternstring % .*s' is converted using the escapecharacter % .*s'. The converted string is longerthan 255 bytes.


1475



7707 10Illegal escape character found. There are fewerbytes than necessary to form a valid character.


7708 10Pattern string is too complex. There are too manyblocks requiring special attention for right bracket(]), circumflex (^), or dash (-).


7709 20Server-initiated remote procedure call state error.


7710 20Attempt to retrieve a returned parameter lengthfrom a server-initiated stored procedure withoutspecifying the parameter name.



7711 20Parameter not found while trying to retrieve thereturned parameter length from a server-initiatedstored procedure.


7712 16Stored procedure %` .*s' may be run only in chainedtransaction mode. The S ` ET CHAINED ON' command willcause the current session to use chained transactionmode.


1476



7713 16Stored procedure %` .*s' may be run only in unchainedtransaction mode. The S ` ET CHAINED OFF' commandwill cause the current session to use unchainedtransaction mode.


by message.

7714 16In a CREATE SCHEMA statement, the authorization idmust match the current user name. The suppliedauthorization id, % ` .*s', does not match the currentuser name, % .*s'.


7715 18Object % d' specified as a rule for tabid % ` d',colid % d' does not have a variable node in thetree.


7716 16Cannot convert CHAR value to REAL. The CHAR valuehas incorrect syntax.


7717 20Attempted to drop temporary table with object id%ld, which is not in the temporary object lists forthis task.


1477



7718 16The %` s' command is not allowed within amulti-statement transaction in the % ` .*s' database.


by message.

7719 17There is no memory available to save the currentsequencer state -- cannot continue processing thisquery.


7720 16Update/Delete from a table which is the inner tableof an outerjoin is not allowed. Command aborted.


7725 16Cursor %.*s' was declared with a FOR UPDATE clause.This cursor was found to be read only.


7726 16Execute cursor %` .*s' is declared on a procedurewhich has more than one SQL statment. For thedeclaration of this cursor to be legal the procedureshould have a single SELECT statement clause.


1478



7727 26An internal error occurred for the cursor variable

%` .*s'. It could not be found on any variable listof the procedure.


7728 14Permission denied. You must have the followingrole(s) to execute %.*s : % ` .*s' . Please contacta user with the appropriate role for help.


7729 16Invalid role string % ` .*s' entered.


7730 14SET ROLE fails. The caller is not granted with thespecified %` .*s' role. Please contact a user withSystem Security Officer (SSO) role for help.



7731 16SET ROLE fails. The caller cannot assume the newuser identity (uid) in the current database. Pleasecontact a user with System Security Officer (SSO)role for help.


7732 16The UPDATE/DELETE WHERE CURRENT OF failed for cursor

%` .*s' because the cursor is read only.


1479



7733 18Unable to locate the base procedure header(Pss->phdr) which had been switched earlier.



7734 18The search for table name when adding a resdom ins_addident() failed. The resdom for the column

%` .*s' did not contain the table name. This is aninternal error.


7735 16The specfied row count % ` d' for the cursor % ` .*s' isinvalid. The rowcount should always be greater thanzero.


7736 20Unable to find lock request for tabid %ld dbid %d.This is an internal error.


7739 18Internal error - SELECT INTO not found, perhaps treecorrupted.


1480



7740 18The declaration for cursor % ` .*s' has the column

%` .*s' in it's FOR UPDATE list which is not part ofthe SELECT list for the cursor. Either select thatcolumn or remove it from the FOR UPDATE list.



7741 18Internal error - Both SHARED AND UPDLOCK have beenset on table %` .s'.


7742 16You must change your password using the sp_passwordsystem stored procedure before you can continue.


7743 16An explicit value for the identity field in table

%` .*s' can only be specified in an insert statementwhen a field list is used.


7744 16Illegal attempt to update identity field % ` .*s'.


7745 16Attempting to add a new identity field to a table

%` .*s', via select into, which would have a field%` .*s' that inherits the identity property.


1481



7746 16Attempting to add more than 1 new identity field toa table % .*s', via select into.


by message.

7747 16Unable to SET IDENTITY_INSERT to ON for table % ` .*s'because it is already on for tabid %ld dbid %d.


7748 16Pseudo-column S YB_IDENTITY' used incorrectly. Notable in the query has the identity property.


7749 16Pseudo-column S YB_IDENTITY' used ambiguously.Multiple tables in the query have the identityproperty.


7750 16Argument type % s' is invalid for argument %d of

%` s' function.


7751 16Unable to SET IDENTITY_INSERT to ON/OFF for table

%` .*s' because the object either does not exist orcannot be opened.



1482




%` .*s' because you are neither the DBO nor theobject owner.


7753 16Unable to SET IDENTITY_INSERT to ON/OFF for object

%` .*s' because the object is not a user table.


7754 16Operand data type % s' is invalid for % ` s' operator.


7755 18Attempt to switch base procedure header (Pss->phdr)more than once.This is an internal error.



%` .*s' because the table does not have the identityproperty.


7757 16The order-by position number % ` ld' is out of rangeof the number of items in the select-list.


1483




%` .*s' in it's FOR UPDATE OF list which is notupdatable after view resolution.



%` .*s' in it's FOR UPDATE OF list which is notupdatable because it has the identity property.


7760 16Conversion of security label datatype tochar/varchar datatype failed.


7761 16The data type % s' is invalid for the %sfunction. Allowed types are: CHAR/VARCHAR andSENSITIVITY/SENSITIVITY_BOUNDARY.


7762 16Trigger label configuration incompatible with user'sprofile.


7763 16Procedure label configuration incompatible withuser's profile.


1484



7764 23Sysobjects entry NOT found for procedure bufferentry.

Explanation: The database may be corrupt. Report the error to yourSystem Administrator. Adaptive Server must be restarted and dbcc

diagnostics run.

7765 23Invalid owner curread for view, procedure, ortrigger in sysobjects entry.


7766 16A conversion from %` s' label to character stringresulted in an overflow.


7767 16THe user's curread label does not dominate theconverted label.


7768 16Invalid label syntax.


7769 18Internal conversion error detected while convertingto/from % s' label datatypes.


1485



7770 10Warning: There are other roles currently active.


7771 16Insert into the sensitivity column of table % ` .*s'attempted. Explicit inserts into the sensitivitycolumn are not allowed.


7772 18Internal error encountered while processing@@update_mode global variable.


7773 16Execute cursor %` .*s' is declared on a procedurewhich contains a non-SELECT or a SELECT with aCOMPUTE clause. For the declaration of this cursorto be legal it should have a single SELECT statementwithout a COMPUTE clause.


7774 16The procedure % .*s' contains a select statementwith FOR UPDATE clause. This should be the onlystatement in the procedure.


1486



7775 16The column %.*s' in FOR UPDATE list is not partof the SELECT list. Either select that column orremove it from the FOR UPDATE list.


7776 16Transaction to update certification state of object%S_OBJID, database %S_DBID failed.


7777 16Changing certification state of object %S_OBJID,database %S_DBID to SUSPECT because of change instate of dependent object %.*s (previous object id%ld), database %S_DBID.


7778 16Suspect procedure %S_OBJID, database %S_DBID found.Cannot execute query.

Explanation: There may be possible corruption in a database or adatabase object. Take any corrective action indicated by the message.Consult the Adaptive Server System Administration Guide and the

Troubleshooting Guide.

7779 16UNCERTIFIED object %S_OBJID, database %S_DBIDaccessed by CERTIFIED object %S_OBJID, database%S_DBID. Cannot execute query.



1487



7780 16Procedure %S_OBJID, database %S_DBID with labelsfound UNCERTIFIED. Cannot execute query.



7781 16Suspect view %S_OBJID, database %S_DBID found.Cannot execute query.


7782 16Remote procedure call from within CERTIFIED storedprocedure %S_OBJID, database %S_DBID not allowed.Cannot execute query.


7783 10Internal error -- server failed to do garbagecollection on this procedure, id = %ld. Please savethe query tree and procedure text and inform thetechnical support. This is not a critical error, soserver continues processing.

Explanation: There was an error during procedure query treecompression. This is not a critical problem as Adaptive Server cancontinue processing the procedure.

7784 16Illegal escape character found. There are fewerbytes than necessary to form a valid character.


by message.

1488



7785 16Attempting to create a table % ` .*s', via selectinto, with column % ` .*s' whose numeric precision,%d, exceeds the maximum allowed precision (%d).


7786 16Unable to turn role off since user is not a validuser in the current database.


7787 16Sensitivity column of view % ` .*s' accessed. Aview's sensitivity column is not user accessible.


7788 10WARNING: An explicit or implicit HOLDLOCK/NOHOLDLOCKwas specified for table % ` .*s'; however,since this is an isolation level 0 scan, theHOLDLOCK/NOHOLDLOCK is ignored.


7789 16Unable to allocate work table for processing groupby or distinct clause during query optimization.Maximum limit (%d) of work tables is exceeded.Simplify the query and retry.


by message.

7790 18Internal error - Unable to remap cursors duringrecompilation. This is a non-fatal internal error.

Explanation: During recompilation, Adaptive Server remaps declaredcursors from the old procedure header to the new header. This messagemeans that an error is found during remapping.

1489



7791 16Unable 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 serverneeds 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 somereason.

7792 16An isolation level %d scan is being attemptedon cursor % .*s', but the cursor was declared atisolation level %d. You must re-declare the cursorat isolation level %d.


by message.

7793 16An isolation level '%d' scan is being attempted byan ad hoc query, but the query was compiled in thebatch at isolation level '%d'.


by message.

7794 16You cannot scan table '%.*s' at isolation level 0because another process is running a utility commandthat is incompatible with level 0 scans. Pleaseretry later.

Explanation: Another process is running a DROP INDEX, ALTERTABLE, TRUNCATE TABLE, REORG REBUILD, or CREATECLUSTERED INDEX command on the table.

7795 18Internal error - Unable to process subqueries duringtransformations. Maximum limit (%d) of subqueriesis exceeded. Please save the DBCC TRACE(100) outputand inform technical support.


1490



7796 18Internal error - Unable to process subqueries duringtransformations due to a corrupt query tree. Pleasesave the output from DBCC TRACE(100) and informtechnical support.


by message.

7798 16SELECT INTO queries can include no more than %dtables, including the table being selected into.

Explanation: Adaptive Server could not perform the requested action.Rewrite the command to conform to the requirement specified in theerror message. (Not raised in 11.9.2).

7799 16The %s operation cannot take a %s datatype as anargument.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby message. (Not raised in 11.9.2).

1491



7901 16Page %ld was expected to be the first page of aTEXT/IMAGE value.


7902 16Data size mismatch occurred while checkingTEXT/IMAGE values. The first page for this valueis: %ld. There were %ld bytes found, which isdifferent from the expected data length of %ldbytes.


7903 16Page %ld was expected to be a TEXT/IMAGE page. Thisoccurred when link number %ld was examined.


7904 10The total number of TEXT/IMAGE pages in this tableis %ld.



7905 10The number of rows in sysindexes for this table was%ld. It has been corrected to %ld.


1492



7906 10The number of data pages in sysindexes for thistable was %ld. It has been corrected to %ld.



7907 16The status in the first page (%ld) of the no_logtable %.*s and the status in the sysobjects row, donot match.



7908 10The table %.*s was created with the no_log option.



7909 10A transaction involving the no_log table %.*swas undone. This may have left the table in aninconsistent state. Rebuild the table.


7910 16Page %ld allocated (Alloc page: %ld Extent ID: %ldAlloc mask: 0x%x)


7911 16Page %ld deallocated (Alloc page: %ld Extent ID:%ld Alloc mask: 0x%x)


1493



7912 16EXTID:%ld (Alloc page: %ld) is initialized. Extentfollows:


by message.

7913 16PTNID=%d SPARE=%d OBJID=%ld RESERVE=0x%xFORWARD=0x%x ALLOC=0x%x DEALLOC=0x%x IND ID=%dSTATUS=0x%x


7914 10Allocation page %ld extid %ld is not referenced,but there are referenced pages within this extent.Contact Technical Support for assistance on object%ld.



7915 10Allocation page %ld extid %ld is referenced, butthere are no referenced pages within this extent.Contact Technical Support for assistnace on object%ld.


7916 10Total (# alloc pages = %ld, # of alloc pagesmodified = %ld).



7917 16Total (# pages allocated=%ld pages deallocated=%ldextents deleted=%ld).


1494



7918 16Alloc page %ld (pgs allocated=%ld pgsdeallocated=%ld extents deleted=%ld).


by message.

7919 16Fix_al not processed. Database needs to be inSINGLE USER mode.


7920 16Processed %ld entries in the sysindexes for dbid %d.


7921 16Found %ld bad entries in the sysindexes.


7923 16TABLE: %.*s OBJID = %ld


7924 16INDID=%ld FIRST=%ld ROOT=%ld SORT=%d



7925 16Indid : %d. %ld Index pages allocated and %ldExtents allocated.


1495



7926 16Data level: %d. %ld Data pages allocated and %ldExtents allocated.



7927 16TOTAL # of extents = %ld


7928 16Index %.*s is not consistent; found %ld leaf rowsbut %ld data rows. Drop and recreate the index.


7929 16Table has %ld data rows.



7930 16Table Corrupt: keys in left child do not precedethe parent key; check left child page %ld.

Table Corrupt: keys in left child do not precedethe parent key; check left child page %ld.


7931 16Table Corrupt: keys in right child precede theparent key; check right child page %ld.

Explanation: There may be possible corruption in a database or adatabase object. Consult the Error Messages and Troubleshooting Guideto see how to locate the table, and run dbcc diagnostics.

1496



7932 16The indexes for %` .*s' are already correct. Theywill not be rebuilt.


by message.

7933 16One or more indexes are corrupt. They will berebuilt.


7934 16The table % .*s' has no indexes.


7935 16REINDEX received an exception - command aborted.


7936 10Checktable on sysgams is not allowed.


7937 16The data in table % ` .*s' is possibly corrupt - DBCCREINDEX aborted. Run DBCC CHECKTABLE and reporterrors to a user with System Administrator (SA)role.


1497



7938 16Table Corrupt: The oam entry for object %ld, indid%ld, alloc pg %ld, has a used count of %d and anunused count of %d. The used count should be %d andthe unused count should be %d.



7939 16Table Corrupt: The entry is missing from the OAMfor object id %ld indid %d for allocation page %ld.


7940 22The counts in the OAM are incorrect. This impliesthat there are entries missing. Run tableallocutility with the FIX option on the table with theinaccurate OAM counts.


7941 16Couldn't find table %.*s.


7942 10The missing OAM entry has been inserted.


7943 10Attempt to insert missing OAM entry failed.


7944 10*** NOTICE: Space used on the log segment is %sMbytes, %s%%.


1498



7945 10*** NOTICE: Space free on the log segment is %sMbytes, %s%%.



7946 10*** NOTICE: Notification of log space used/freecannot be reported because the log segment is not onits own device.


7947 16The sortorder and character set ID's for index %d onthis table were %d:%d in sysindexes. They have beencorrected to %d:%d.


7948 16Page %ld, object %ld, index %d, level %d, was foundwith fixed-row status improperly set. That statushas been cleared by DBCC.


7949 16The number of pages used and unused for object %ldindex %d on allocation page %ld do not match thecounts in the OAM entry.


7950 16Unable to %.*s engine. Check sysengines count andmax online engines config value.


1499



7951 16Data size mismatch occurred while checking a TEXTvalue. The first page for this value is: %ld.There were %ld characters found, which is differentfrom the expected length of %ld characters.



7952 10A TEXT value with an invalid MAGIC NUMBER has beenfound on page %ld. TEXT values will no longerbe checked for this table. Note because of this,the TEXT page count will be inaccurate. Use DBCCFIX_TEXT to fix the TEXT values.



7953 10Unable to acquire an exclusive lock on text page%ld. This text value has not been recalculated.In order to recalculate those TEXT pages you mustrelease the lock and reissue the DBCC FIX_TEXTcommand.



7954 10There are no TEXT pages in table %.*s to be updated.


7955 10Not all of the TEXT pages in table %.*s have beensuccessfully updated, however, DBCC FIX_TEXT isrestartable. Please issue the command again onceany other errors have been addressed.


1500



7956 16Remapping utility - Column descriptor should havebeen remapped earlier. This is an internal systemerror.


7957 25Remapping utility - procedure is corrupted inSysprocedures. Recreate this procedure.



7958 16Remapping utility - a pointer exists in a tree whenit should not.


7959 16Remapping utility - unable to locate the givenprocedure %.*s in Sysprocedures.



7960 16Remapping utility - Procedure needs to be recreatedfor this port.


1501



7961 16Remapping utility - Wrong kind of node passed totree remapping. This is an internal system error.



7962 16Upgrade requires the SQL Server to be booted insingle user mode. Reboot the SQL Server with the -mflag.



7963 16Upgrade encountered a fatal error. Please check theSQL Server errorlog.


7964 14Permission denied. You do not have the necessaryrole to run this command. Please contact SybaseTechnical Support for assistance in running thiscommand.



7965 10The f` ix' option has been ignored for this command.To use the f ix' option with system tables, runthe command from the database where the table islocated. The database must be in single user mode.


1502



7966 20The global space allocation report requires anexclusive lock on object 99. This process doesnot hold this lock in database %d. This report iscancelled.



7967 20Allocation page %ld in database %d does not holdthe address lock required for initializing thediagnostic bitmaps or correcting its allocationerrors.


7968 20The object allocation map for tabid %ld indid %dis corrupt, therefore the optimized report cannotbe generated. Contact Technical Support forassistance.


7969 10Allocation reports cannot be generated for object%ld in database %d.


7970 10The default report option of %.*s is used for thisrun.


1503



7971 10The default fix option of %.*s is used for this run.


7972 10The oam counts for objid %ld indid %d are corrected.


7973 10The optimized report may generate erroneous messagesdue to the missing OAM entry. Run the optimizedreport with the fix option, to correct this error.


7974 16ILLEGAL use of module %.*s. See the errorlog fordetail information.


7975 20System catalog entrie(s) for Object %ld, Database%ld are corrupted.


7976 16Object %ld in database %ld does not have anyTEXT/IMAGE data.


1504



7977 16First page %ld and Root page %ld are not same.


7978 20One or more text chain(s) for object %ld in database%ld is corrupt.



7979 16Text chain linkage corrupted for Page %ld of Object%ld.


7980 16Unreferenced text chain found for page %ld, nextpage%ld, prevpage %ld.



7981 16The new transaction mode must be unchained, chainedor anymode.


7982 16The specified object % ` .*s' is not a storedprocedure in database % ` .*s'.


by message.

1505



7983 16You must be either the system administrator (SA),the database administrator (dbo), or the owner ofthis stored procedure to change its transactionmode.



7985 16Server name %*.s' not found in system catalog.


7986 16You can not change the mode of a remote storedprocedure.


7987 16User named %` .*s' not found; check sysusers.


7988 16The specified object % ` .*s' is not found in database

%` .*s'. Check sysobjects to make sure you own theobject.


7989 16The serial allocation flag was found to beimproperly set in allocation unit %ld, at extent ID%ld, with alloc map = %d and objid = %ld. This flaghas been cleared by DBCC.


1506



7990 16Permission denied. User's operating system sessionlabel must dominate database maxhold to use the DBCCcommand %` .*s'.


7991 18Label consistency check for database % ` S_DBID'failed.


7992 14The user needs to be in the master database toexecute this command.


7993 18Either the execution of the D ` BCC SECURITY(LABEL_CHECK)' command failed or one or moredatabases have been detected to have inconsistentsecurity labels.


7994 16Database %.*s' has references to other databases.Drop those references and try again


1507



7995 14Permission denied. Only the Database Owner (DBO) ora user with the System Administrator (SA), SystemSecurity Officer (SSO), or Oper role can executethis command for database % ` S_DBID'.


7996 14Permission denied. Object % ` S_OBJID' not found.


7997 14Permission denied. User's curwrite does not matchthe sensitivity label of object % ` S_OBJID'.



7998 14Permission denied. Database % ` S_DBID' not found.


7999 14Permission denied. User's curwrite does not matchthe sensitivity label of database % ` S_DBID'.


1508



8002 15Parameter number %d and subsequent parameters mustbe passed as @name = value'. Once the form @ ` name= value' has been used, all subsequent parametersmust be passed in the form @ ` name = value'.


8003 15There are too many parameters in this CREATEPROCEDURE statement. The maximum number is %d.


8004 16Received an unrecognized datatype %d from TDSdatastream.


8005 15Received a procedure name length of %d. The TDSdatastream is incorrect.


8006 20SQL Server error detected by %S_MSG. Refer to thepreceding %S_MSG message.


8007 20Unknown token returned by %S_MSG: %d.


1509



8008 16Parameter no. %d, of type %d, did not have a validvalue.


by message.

8009 16Error encountered by %S_MSG. Please refer to %S_MSGmessages for details.

Explanation: Refer to the detailed writeup for this message in thechapter titled “Error Message Writeups”.

8010 16datalen (%d) must be less than maxlen (%d) for rpcparameter %d

Explanation: Check your RPC parameters. There may be aninconsistency between length and max length values.

8011 16Parameter %d has datatype %s. This datatype is notvalid for use in parameters for an RPC.


by message.

1510



8201 26Keep count of descriptor (objid=%ld, dbid=%d) wasexpected to be %d. Instead %d was found.


8203 26Expected to find the descriptor for object %d indatabase %d in %s state.


8204 20Expected to receive system catalog id. Instead %dwas received.


8205 20Invalid field token passed to descriptor (id = %d,field = %d).


8206 21Object %d was not found in %s.


8207 17Couldn't find an available descriptor for anobject.Configure your system for more descriptors.


8208 21Descriptor for object %d in database %d was notfoundin the expected dbtable.


1511



8209 26Descriptor found was not expected to have %s state.


8210 21Duplicate of work table descriptor found in the idhash table for temporary object %d.


run.

8211 26Mismatch found between the name and id descriptorhash table. Descriptor hashed by name = 0x%0x andhashed by id = 0x%0x.


8213 20Failed to acquire address lock on object %.*s


8215 14An attempt was made to drop the DES of object %ld,which is not a user-defined object.


Adaptive Server cannot perform the requested action. Take anycorrective action indicated by the message.

8216 20Failed to acquire table lock on object %.*s



8219 18Couldn't compute lock promotion level in DES forobject %d in database %d. Using default level = %d.


1512



8221 20Couldn't find the identity column for object %.*s.


8222 20Maximum rows per page value not found in thedescriptor for table=%d, index=%d on database %d.

Explanation: Adaptive Server encountered an internal error affectingthe current process. Reconnect to Adaptive Server. Report the errorto your System Administrator so dbcc diagnostics can be run. (Not

raised in 11.9.2)

8223 21As part of a transaction rollback, an attemptwas made to modify object '%S_OBJID ' in database'%.*s', even though the current session is notholding an exclusive lock on that object.

Explanation: The server encountered an internal error affecting allprocesses using this database. Report the error to your SA.

8224 21Internal error: could not save description oflightweight procedure '%.*s'.

Explanation: The server encountered an internal error affecting allprocesses using this database. Report the error to your SA.

8225 16Invalid object '%.*s' in dbid %d

Explanation: Check query and retry.

8226 16Operation not allowed. System table '%.*s' cannotbe bound/unbound.

Explanation: Invalid operation for this system table.

8227 16Trying to bind/unbind an already bound/unboundobject '%.*s' in database %d

Explanation:

1513



8228 16Cannot do an unbind at this time. The database %dis in use. Try doing unbind when there are no usersusing the database.

Explanation: Illegal operation for a database in use.

8229 16Trying to bind/unbind objects to dbid=%d.Bind/Unbind objects not allowed in master andtempdb.

Explanation: Illegal operation for this database.

1514



8401 21Object with id of %ld was not found in databasenumber %d.


8402 21Index row for object %ld (index id %d) was not foundin database %d.


8403 21Index tag structure doesn't contain the search modeexecuted.


8404 21Index tag structure indicates fast and slow searchmodes.


8405 21No modify lock was acquired for an index row %s.


8406 21Insert of sysindexes row failed.


1515



8407 21Delete of sysindexes row failed.


8408 21Didn't expect to find active modify lock forsysindexes.



8409 21Invalid status found in sysindexes tag structure.Expected status: %s.


8410 21Expected to find search lock during sysindexes scan.


8411 21Invalid setup status found in sysindexes Managerduring a call to: %s.



8412 21No object id specified in sysindexes Manager callto: %s.


1516



8414 21Copy of sysindexes row failed.


8415 21Unexpected value % d' returned from lock managerafter waiting for lock on page %ld, dbid %d.



8416 20Invalid scan type %d specified



8417 20Internal error occurred while running the sysindexesexerciser.

Explanation: Internal error affecting the current process. Contact yourSA.

8418 20Invalid index descriptor field (%d) specified withinsysindexes manager.


8419 21Could not find index descriptor for objid %d, indid%d in dbid %d.


8420 20Could not install index descriptor for objid %d,indid %d in dbid %d.


1517



8421 20Invalid input to sysindexes manager. Expected validsession descriptor for sysindexes system table.


8422 21Indid mismatch between index descriptor 0x%x (indid%d) and page 0x%x (indid %d) for objid %d in dbid%d.


8423 21Expected table descriptor to be set for objid %d indbid %d.

Explanation: Internal error affecting the current process. Contact your

SA.

8424 17Cannot find an available index descriptor foran index. Increase the value of 'number of openindexes'. If sp_configure fails due to lack ofindex descriptors, edit the configuration file andrestart the server.

Explanation: Check the installation and configuration guides forassistance with the recommended task.

8425 21Couldn't find an available index descriptor forsystem objects.


8426 26Index descriptor 0x%x is already installed on thehash table for objid %d, indid %d in dbid %d.

Explanation: Internal locking/synchronization rule was broken. Reportthe error to your SA, and restart the server.

8427 20Invalid input to sysindexes manager. Expected tohave dbid or dbtable pointer set


1518



8428 26Unexpected keep count %d of index descriptor.Expected %d.

Explanation: Internal locking/synchronization rule was broken. Reportthe error to your SA, and restart the server.

8429 20Object with objid %d in dbid %d is not a table.


8430 10Did not find table descriptor linked to process slotstructure 0x%x when SQL Server tried to release it.


SA.

8431 20Invalid transaction descriptor passed to thesysindexes manager internal function


8432 20Invalid object descriptor passed to the sysindexesmanager internal function.


8433 20Table descriptor (0x%x) for objid %d in dbid %d isalready linked to another transaction.


8434 20Invalid initialization flag %d specified withinsysindexes manager.


1519



8435 26Expected to find the index descriptor for objid %dindid %d in dbid %d, in a %s state (found state %dinstead).

Explanation: Internal locking/synchronization error. Contact your SAand restart the server.

8436 26Index descriptor found was not expected to be in a%s state.

Explanation: Internal locking/synchronization error. Contact your SAand restart the server.

8437 20Update failed. SQL Server could not find field '%d'within index descriptor/buffer.


SA.

8438 21Updating wrong indexrow in dbid %d. Objid foractual row updated is %ld, objid for intended rowwas %ld. Index id for intended row was %d. Indexpage is %ld, field updated is %d. Index row addressis %0x, row number is %d.


run.

1520



8501 26Object id's are not the same during an abort: %dand %d.


8502 21Invalid record type passed to abort: %d.



1521



8601 20Process %d tried to keep the PSS for process %d whenit already had the PSS for process %d kept.


1522



8701 26Sitebuf has invalid state or keepcount.sitebuf=0x%lx, state=%d, keepcount=%ld.


8702 26Sitebuf has invalid state. sitebuf=0x%lx, state=%d.



8703 26Invalid keep count in sitebuf. sitebuf=0x%lx,keepcount=%ld.


8704 26Could not get the address lock. address=0x%lx,status=%d.


8705 26Remotely started site handler.


8706 26Invalid keep count in sitebuf. sitebuf=0x%lx,keepcount=%ld, lcfreed=%d.



1523



8801 26Logconn has invalid state or keepcount.logconn=0x%lx, state=%d, keepcount=%d.


8802 26Logconn has invalid state. logconn=0x%lx, state=%d.



8803 26Missing sitebuf for siteid %d.


Adaptive Server.

8804 26Packet acknowledgment is neither read nor write.rdwr=%d.


8805 26Invalid set parameter to lc_wconnstat. set=%d.


8806 26Corrupted pre-read data list in lc__flush.logconn=0x%lx, dtbeg=0x%lx, dtend=0x%lx.


1524



8901 26Databuf has invalid state. databuf=0x%lx,state=%ld.


8902 26Logconn has invalid state or keepcount.logconn=0x%lx, state=%d, keepcount=%d.


8903 26Invalid state in logconn. logconn=0x%lx, state=%d.


8904 26Invalid state in databuf or corrupted databuf chain.databuf=0x%lx, state=%ld, dnext=0x%lx.


Adaptive Server.

1525



9001 20Process %d has requested a memory size %d that isgreater than the memory size %d in the disk buffer0x%X, dbid %d.


9002 20Process %d is accessing disk buffer 0x%X, in dbid%d that has been freed. The current status of theDSKBUF is 0x%X.


9003 20Could not start I/O for request %S_BLKIOPTR.


9004 20I/O error detected on disk buffer 0x%X for pagerequest %ld, dbid %d.



1526



9005 20Process %d is requesting an illegal I/O type of0x%x.



9006 20Process %d is attempting to free a disk buffer thatis already freed. Disk buffer address 0x%X, dbid%d.


1527



9101 16The total size of all parameter values for storedprocedure % .*s' exceeds maximum size (%d bytes)allowed for replication. Stored procedure % ` .*s' isnot replicated.


9102 16Failed to convert the %s log record into row formatfor database % .*s', XACT ID %S_RID, RID %S_RID.Information associated with the %s log record is notreplicated.


9103 16Failed to send the %s log record for database

%` .*s', XACT ID %S_RID, RID %S_RID. Informationassociated with the %s log record is not replicated.


9104 16Cannot identify the object on the %s log recordfor database % .*s', XACT ID %S_RID, RID %S_RID.Information associated with the %s log record is notreplicated.


9105 16A missing log record indicates a prematurelytruncated log or a corrupt log. The %s logrecord in database % ` .*s', XACT ID %S_RID, is notreplicated.


1528



9106 10The deferred insert (INOOP) log record referencedby the insert indirect (INSIND) log record was notfound as expected at RID %S_RID.


9107 16Unexpected function return value %d while processingthe %s log record of database % ` .*s', XACT ID%S_RID, RID %S_RID. The %s log record may not havebeen replicated.


9108 10Number of qualifiers supplied to the DBCCLOGTRANSFER command exceeds limit of %d. The DBCCLOGTRANSFER command is not executed.


9109 10Cannot find user name for user ID %d while sendingthe %s log record for database % ` .*s', XACT ID%S_RID, RID %S_RID. The user ID will be used insteadof the user name.


9110 10Found an ENDXACT log record before finding anexpected INSERT log record in database % ` .*s', XACTID %S_RID, RID %S_RID.


9111 10Failed to send the LTM truncation point informationfor database % .*s'. The DBCC GETTRUNC commandfails during execution.


1529



9112 16The DBCC LOGTRANSFER command must be invoked with atleast %d parameters. The DBCC LOGTRANSFER commandis not executed.


9113 16%` .*s' is not a valid QUALIFIER for the DBCC

LOGTRANSFER command. The DBCC LOGTRANSFER commandis not executed.


9114 16%` .*s' is not a valid VERB for the DBCC LOGTRANSFER

command. The DBCC LOGTRANSFER command is notexecuted.


9115 16%` .*s' is not a valid COMMAND for the DBCC

LOGTRANSFER command. The DBCC LOGTRANSFER commandis not executed.


9116 16%` d' is not a valid numeric value for the specified

QUALIFIER. The DBCC LOGTRANSFER command is notexecuted.


1530



9117 16The DBCC LOGTRANSFER command was invoked withan invalid combination of QUALIFIERs. The DBCCLOGTRANSFER command is not executed.


9118 16The specified COMMAND requires additionalQUALIFIERS. The DBCC LOGTRANSFER command is notexecuted.


9119 17Execution of the the %s command fails due toinsufficient memory.


9120 16The log transfer context for database % ` .*s' has notbeen reserved with the DBCC LOGTRANSFER ( r ` eserve',

c` ontext') command. The specified DBCC command isnot executed.


9121 16The log transfer context for the current databaseis already reserved by SQL Server process %d. Thelog transfer context for the current database is notreserved.


1531



9122 21The log transfer process lost its connectionto the LTM for database % ` .*s'. Once the LTMre-establishes the connection, replication willcontinue with no data loss.

Explanation: This is an informational message. The log transfer processencountered a broken connection. The LTM will re-establish the

connection and replication will continue with no data loss.

9123 17Unable to set a wakeup alarm for the log transferprocess. The log transfer scan of database

%` S_DBID' will not honor the specified timeout of %dseconds.


9124 16INTERNAL CODING ERROR. Log record ID %d is notvalid. Please contact Sybase Technical Support.


9125 16Usage: DBCC SETTRUNC( l` tm', { v ` alid' | i ` gnore' |

p` ageid', page number })


9126 16Usage: DBCC GETTRUNC()


1532



9127 16INTERNAL CODING ERROR. The building of aninternal data structure required more memory thananticipated. Please contact Sybase TechnicalSupport.


by message.

9128 16Ran out of memory trying to send an UPDATE command'sDELETE/INSERT log record pair for database % ` .*s',XACT ID %S_RID, RID %S_RID. The %s log record is notreplicated.


9129 16Unable to determine the end of the log for database

%` .*s'. The log transfer scan of database % ` .*s' isaborted.


9130 16The BEGINXACT log record referenced by theCHECKPOINT log record for database % ` .*s', XACT ID%S_RID, RID %S_RID, was not found at RID %S_RID asexpected.


9131 21The log transfer context for the current database isalready reserved by your SQL Server process. TheDBCC LOGTRANSFER ( r` eserve', c ` ontext') command isignored.



1533



9132 16Failed to write the log record for the execution ofstored procedure % ` .*s' in database % ` .*s'. Storedprocedure % .*s' is not replicated.


9133 16The SQL Server was not started with the propercommand line option to enable Replication Serversupport. The DBCC command is not executed.


9134 16The DBCC LOGTRANSFER ( s` etqual', ...) command wasinvoked with parameters of incorrect type. TheDBCC LOGTRANSFER ( s` etqual', ...) command is notexecuted.


9135 16Usage: DBCC LOGTRANSFER( s` can', { n ` ormal' |

r` epeat' | c ` ontinue' })


9136 16Unable to find the RID of the last ENDXACT orCHECKPOINT log record. The log transfer context forthe current database is not reserved.


1534



9137 16LTM trunc. point not yet established with DBCCSETTRUNC(). Until the LTM trunc. point isestablished, changes to the object % ` .*s' may not bereplicated.


9138 16Even though Replication Server support is disabled,database %S_DBID' contains a valid LTM trunc.point which prevents the complete truncation of allexpendable log pages.


9139 17Failed to free allocated but unused memory inorder to satisfy memory allocation request. Memoryallocation request fails.



9140 17Memory allocator used for Replication Server supportfailed to fulfill memory allocation request.


9141 16The stored proc. % ` .*s' associated with the %slog record in database % ` .*s', XACT ID %S_RID,RID %S_RID, was dropped after the log record waswritten. The %s log record is not replicated.


1535



9142 16Usage: DBCC REPLICATE_TXTCOL (objid, colid,{ always_replicate | replicate_if_changed |do_not_replicate } )


9143 16%` .*s' is not a valid replication status. The DBCC

REPLICATE_TXTCOL command is not executed.


9144 16The requested column cannot be located. Checkthe objid and colid specified. The DBCCREPLICATE_TXTCOL command is not executed.

Explanation: Check the column ID and object ID specified in thecommand.

9145 16The datatype of the specified column must be TEXTor IMAGE. The DBCC REPLICATE_TXTCOL command is notexecuted.

Explanation: The column that was specified for this operation is not aTEXT or IMAGE column. Recheck the column specified.

9146 20The excution of DBCC REPLICATE_TXTCOL failed dueto an internal error. Please contact your SystemAdministrator (SA) for help.


1536



9147 16Replication Not Enabled: Replication on table %.*sin database %.*s, has not been enabled yet. Runsp_setreplicate or sp_setrepcol before calling DBCCREPLICATE_TXTCOL, the DBCC REPLICATE_TXTCOL commandis not executed. (objid %ld)


9148 20Replication server could not send log records forlog version change processing in database % ` .*s'because the log processing functions returnedinternal error %d.


9149 10LTM Truncation point has not been establishedwith DBCC SETTRUNC. Changes to the objects in thedatabase may not be replicated until the truncationpoint is set.

Explanation: This informational message requires corrective actionas indicated.

9150 16The log transfer context for the current databasecannot be reserved because the current database hasbeen enabled for a Rep Agent Thread.

Explanation:

9151 16Permission denied. User cannot execute the built-infunction '%.*s' in database ' %d'.

Explanation: Check login/role permissions.

1537



9201 20%S_REPAGNT: Could not map OAM Page (%d) to objectid, current marker (%d, %d).

Explanation: Internal error, affects current process. Contact your SA.

9202 20%S_REPAGNT: Nested replicated stored proceduredetected. Transaction log may be corrupt. Pleasecontact SYBASE Technical Support. (current marker= %d, %d)


9203 20%S_REPAGNT: Encountered an End Transaction that wasnot in abort state while locating after image forDelete at (%d, %d), transaction = (%d, %d).


9204 20%S_REPAGNT: Could not locate schema for object withid = (%d), current marker (%d , %d).


9205 20%S_REPAGNT: A replicated End Stored ProcedureExecution log record was found with out a Begin.Transaction log may be corrupt. Please contactSYBASE Technical Support. objid = (%d), currentmarker = (%d, %d)


9206 20%S_REPAGNT: Error initializing the Rep Agent. Couldnot set affinity to engine (% d).

Explanation:

9207 20%S_REPAGNT: Could not re-read XCMDTEXT log record at(%d, %d), current marker (%d , %d).


1538



9208 20%S_REPAGNT: Update detected within a subscribablefunction. Transaction log may be corrupt. Pleasecontact SYBASE Technical Support. (current marker= (%d, %d)).


9209 20%S_REPAGNT: Missing datarow in TEXT/IMAGE insert logrecord. Transaction log may be corrupt. Pleasecontact SYBASE Technical Support. (current marker= (%d, %d)).


9210 20%S_REPAGNT: Fatal error from CT-Lib. (CT-Libcommand = %s, return status = %d).


9211 20%S_REPAGNT: Received the following error messagefrom the Replication Server: Msg %ld. %.*s.


9212 20%S_REPAGNT: Received the following communicationserror message: Msg %s: %.*s.


9213 16%S_REPAGNT: The version of this Rep Agent Thread,does not support Replication Server version. Afterfixing this problem, please restart the Rep AgentThread for this database. (RepAgntVers = %d,RepSvrVers = %d, RepSvr = %.*s).


9214 16%S_REPAGNT: Failed to connect to Replication Server.Please check the Replication Server, username, andpassword specified to sp_config_rep_agent. RepSvr =%.*s, user = %. *s).

Explanation: Check your replication environment as recommended.

1539



9215 16%S_REPAGNT: The Secondary Truncation Point isnot valid. Please make sure that the SecondaryTruncation Point is valid, and then restart the RepAgent Thread for this data base.

Explanation: Take recommended action.

9216 10%S_REPAGNT: The Rep Agent Thread will retry theconnection to the Replication Server every %dsecond(s). (RepSvr = %.*s).

Explanation: Informational message.

9217 10%S_REPAGNT: Trace log file set to % ` s'.


9218 16Database %S_DBID has not been enabled yetfor an integrated Rep Agent Thread. Runsp_enable_rep_agent() to enable the database.

Explanation:

9219 20%S_REPAGNT: Internal coding error.


9220 16%S_REPAGNT: The Rep Agent Thread context fordatabase %S_DBID has already been reserved byanother session.

Explanation:

9221 16Parameter count/type mismatch. Please check thenumber and types of the parameters passed to thebuiltin function, '%.*s'.

Explanation:

9222 16You must be SA, DBO, or have REPLICATION role toexecute the builtin function, '% .*s'. Please checkyour current roles.

Explanation:

1540



9223 16Unknown operation, '%.*s', specified to builtinfunction rep_agent_admin(). Please check parameterspelling and placement.

Explanation:

9224 16Unknown category, '%.*s', specified to builtinfunction rep_agent_config(). Please check parameterspelling and placement.

Explanation:

9225 16Unknown property, '%.*s', specified to builtinfunction rep_agent_config(). Please check parameterspelling and placement.

Explanation:

9226 16Database %S_DBID has already been enabled to use aRep Agent thread.

Explanation:

9227 17%S_REPAGNT. Could not allocate memory to spawn RepAgent thread. (size=%d)

Explanation:

9228 17%S_REPAGNT. Could not spawn Rep Agent Thread.

Explanation: There may be a memory-related or other resourceproblem.

9229 16%S_REPAGNT. Could not change to database, %S_DBID.

Explanation: Check syntax and input data.

9230 16The Rep Agent Thread for database, %S_DBID, is notrunning. Please retry this command after startingthe Rep Agent Thread for this database.

Explanation:

1541



9231 16%S_REPAGNT. The Connect Dataserver name was notspecified via 'sp_start_rep_agent ', nor was itfound in sysattributes, or sysservers. Make surethat you have done a 'sp_ad dserver <svr>, local'.

Explanation: When generating the 'connect source' command forReplication Server, the connect dataserver attribute could not be

determined. You can set connect dataserver attribute directly withsp_start_rep_agent, or configure it via sp_config_rep_agent. This is onlynecessary if the requested dataserver is other than the currentdataservername. You must also do an 'sp_addserver , local' in all cases.

9232 16%S_REPAGNT. The Connect Database name was not foundin sysattributes, or sysdatabases.

Explanation: When generating the 'connect source' command forReplication Server, the connect dataserver attribute could not bedetermined. You can set connect dataserver attribute directly withsp_start_rep_agent, or configure it via sp_config_rep_agent. This is only

necessary if the requested dataserver is other than the currentdataservername.

9233 17%S_REPAGNT. Could not allocate %d bytes from theprocedure cache. Please retry the last operationwhen more memory is available, or re-configure theserver with a larger procedure cache.


9234 17%S_REPAGNT. Could not start Rep Agent Thread.

Explanation:

9235 17Could not allocate memory for gettrunc. Pleaseretry gettrunc() later when more memory isavailable, or re-configure the server with a largerprocedure cache.

Explanation:

1542



9236 11Unknown dbid '%d' specified. Please check the dbidspecified.

Explanation: Check the value of the database ID specified in the query.

9237 16%S_REPAGNT. The row for %.*s could not befound in sysattributes. Please check theconfiguration 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 16Settrunc() is not permitted when a Rep Agent Threadis currently running on the database.

Explanation:

9239 17%S_REPAGNT: Could not allocate a Procedure Cache forthe Rep Agent Thread. Try restarting the Rep AgentThread after freeing up, or allocating a largerProcedure Cache.

Explanation:

9240 17%S_REPAGNT: Could not allocate an alarm. Tryrestarting this Rep Agent Thread after freeing upsome alarms, or restart the server with more alarmsallocated.

Explanation:

9241 20%S_REPAGNT: Failure initializing the Rep AgentContext.


9242 20%S_REPAGNT: Underflow or overflow of state stackoccurred.


9243 20%S_REPAGNT: Interface error with the ReplicationServer. The Rep Agent may not be compatible withthe Replication Server.


1543



9245 20Failure during update/insert/delete fromsysattributes.

Explanation: Report this error to the System Administrator so dbccdiagnostics can be run.

9249 17Failed to reserve context in shared mode.

Explanation: Replication error. Contact your SA.

9250 10%S_REPAGNT Failed to open trace file, '%.*s'. Tracemessages will go to stdout of the server.


9251 20%S_REPAGNT Write to trace file, '%.*s', failed


9252 20Internal coding error in builtin function, '%.*s'.

Explanation: Contact Sybase Technical Support.

9253 20Failed to get secondary truncation point.


9254 20%S_REPAGNT: Could not locate schema version forobject id '%d' in the transaction log.


9255 20%S_REPAGNT: Rewrite of PREPARE log record failed at(%d, %d).


9256 20%S_REPAGNT: Could not read INOOP log record at (%d,%d), current marker (%d, %d).


9257 20%S_REPAGNT: Could not read ROWIMAGE log record at(%d, %d), current marker (%d, % d).


1544



9258 20%S_REPAGNT: Could not re-read EXECBEGIN log recordat (%d, %d), current marker (% d, %d).


9259 20%S_REPAGNT: Could not read TEXTINSERT/INOOPTEXT logrecord at (%d, %d), current marker (%d, %d).


9261 20%S_REPAGNT: This Rep Agent Thread is aborting dueto an unrecoverable communications or ReplicationServer error.


9262 16Failed to start a Rep Agent Thread for the databasespecified because a Rep Agent Thread is alreadyrunning for that database.

Explanation: Check replication environment.

9263 10%S_REPAGNT: Turning Batch mode on.

Explanation:

9264 10%S_REPAGNT: Turning Batch mode off.


9265 10%S_REPAGNT: Ignoring LTL errors.


9266 10%S_REPAGNT: Error in passthru packet: '%.*s'.

Explanation:

9267 20%S_REPAGNT: A security mechanism was specified, butno security service(s) were specified. Please use'sp_config_rep_agent' to specify which securityservice(s) to use when connecting to the ReplicationServer.


by the message.

1545



9268 20%S_REPAGNT: The security service '%.*s' wasspecified, but it is not supported by thesecurity mechanism. Please check the securityservice(s) and/or security mechanism specified tosp_config_rep_agent. (CT-lib error %d).

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby the message.

9269 20%S_REPAGNT: Failure initializing the securitymechanism '%.*s'. Please check the 'securitymechanism' specified to sp_config_rep_agent.(CT-lib error % d).

Explanation: Check the security mechanism that was specified forconnections to the Replication Server.

9270 10%S_REPAGNT: Using default security mechanism.


9271 20%S_REPAGNT: Failure initializing the defaultsecurity mechanism. Please check that a securitymechanism has been properly configered. (CT-liberror %d)

Explanation: Check the default security mechanism set up forReplication Server.

9272 20%S_REPAGNT: Failure specifying the keytab filename.Please check that the keytab file '%.*s', exists andis accessable. (CT-lib error %d).

Explanation: Check the Replication Server setup indicated in themessage.

9273 10%S_REPAGNT: Using default keytab file becausesecurity mechanism requir es a keytab file, but theno keytab file was specified at server startup.


1546



9274 16Cannot disable the RepAgent thread for database%S_DBID, because the RepAgent is still running.Please stop the RepAgent on that databasewith 'sp_stop _rep_agent' before re-issuing'sp_config_rep_agent disable'.

Explanation: Command failed due to invalid or illegal request. Takecorrective action indicated by the message.

9275 20%S_REPAGNT: Could not locate the after image for theDELETE log record at (%d, %d).


9276 20Error executing the command 'set proxy %.*s'.

Explanation: Failure to execute the command 'set proxy %.*s' on theReplication Server. Report the error to your System Administrator.

9277 20%S_REPAGNT: The security mechanism configuredrequires a keytab file. Check that the a keytabfile was specified at server startup, and that 'usesecurity services' has been configured.

Explanation: The RepAgent is initializing security services, and themechanism needs a keytab file. However it cannot locate the keytabfile, either because a keytab file was not specified at server startup, or

because 'use security services' has not been configured yet.

1547



9301 23Inconsistent SLID representation in object metadata.


9302 18Unexpected EX_CONTROL exception has been raisedinside the Syslabels Manager: error = %d, severity= %d, state = %d


9303 18Syslabels Manager: Insert into

%` S_DBID.dbo.syslabels' failed during callto %s().


9304 20Internal MAC sub-system error. Corrupted masterSLID value found. DO NOT USE THIS SERVER AND ITSASSOCIATED DEVICES UNTIL THE CAUSE OF THIS ERROR HASBEEN ELIMINATED.



9305 20Internal MAC sub-system error. Corrupted databaseSLID value found in database % ` d'. DO NOT USE THISDATABASE UNTIL THE CAUSE OF THIS ERROR HAS BEENELIMINATED.


1548



9306 20Bad database id ( %` d') found. Run DBCC checktableon sysdatabases and DBCC checkdb on all databasesused by this query.


9307 20Internal MAC sub-system error. MSLID to DBSLIDconversion failed in database % ` d'. DO NOT USE THISDATABASE UNTIL THE CAUSE OF THIS ERROR HAS BEENELIMINATED.


9308 20Internal MAC sub-system error. DBSLID to MSLIDconversion failed in database % ` d'. DO NOT USE THISDATABASE UNTIL THE CAUSE OF THIS ERROR HAS BEENELIMINATED.


9309 20Internal MAC sub-system error. DO NOT USE THISSERVER AND ITS ASSOCIATED DEVICES UNTIL THE CAUSE OFTHIS ERROR HAS BEEN ELIMINATED.


9310 20Internal MAC sub-system error. Label comparisonfailed. DO NOT USE THIS SERVER AND ITS ASSOCIATEDDEVICES UNTIL THE CAUSE OF THIS ERROR HAS BEENELIMINATED.


1549



9311 21Syslabels Manager: Trying to boot the serverwithout initializing values of Data_High andData_low.


9312 21Syslabels Manager: Current process label, or labelof the MASTER DEVICE do not match with value ofData_High stored in the server.


9313 21Syslabels Manager: Attempt to change values ofData_High and/or Data_Low is not allowed.



9314 14Only a user with the System Administrator (SA),System Security Officer (SSO), or Oper role or theDatabase Owner (DBO) can execute this command.



9315 18Security label specified in the syslabels row withdb_slid % d' is not a valid label in the underlyingtrusted OS.


1550



9316 18Security label specified in the syslabels row withdb_slid % d' is not dominated by Data High.



9317 18Security label specified in the syslabels row withdb_slid % d' does not dominate Data Low.


9318 10Database %S_DBID' passed Syslabels Check.


9319 10Database %S_DBID' passed Database MaxholdConsistency Check.


9321 18Corrupt security label encountered in database

%` S_DBID'. Marking database as having inconsistentlabels and checking the master database for possiblerelated corruption.


9322 18Maxhold inconsistency detected in database

%` S_DBID'.


1551



9324 21Corrupt security labels found in the masterdatabase. Shutting down the server.



9325 18Internal error. Failed to clear database % ` S_DBID'of its security label inconsistency status.


9326 18Internal error. Failed to mark database % ` S_DBID'as having inconsistent security labels. Marking itas suspect instead.


9328 16Inconsistency found in Syslabel Manager Cache.Contact a user with System Administrator (SA) role.


9329 16There are other current users of database % ` S_DBID'.Discontinuing execution.


9330 16Unsupported report or fix option requested.Available report options are: FULL, NOREPORT.Available fix options are: FIX, NOFIX.


1552



9331 18Master SLID mismatch identified in syslabels rowwith db_slid % ` d'.



9332 10Beginning security label consistency of database

%` S_DBID'.


9333 10Security label consistency check of database

%` S_DBID' done.


9334 10Skipping checking of security label consistency fordatabase %S_DBID' as it hasn't been initializedwith the proper Data High and Data Low values.


9335 16A security label consistency fix can only beperformed on the master database if the server wasbooted up in single-user mode.


9336 18Row corruption detected in syslabels row withdb_slid % d'.



1553



9501 10Warning - null value eliminated in set function


9502 16Data exception - string data right truncated


9503 14You must have one of the following role(s) toexecute this command/procedure: % ` .*s'. Pleasecontact a user with the appropriate role(s) forhelp.


9504 16An isolation level 0 cursor scan has failed on anattempted restart for cursor % ` .*s', table % ` .*s',index id % d'. The cursor is being closed.


9505 16An isolation level 0 scan has failed on an attemptedrestart on table % ` .*s', index id % ` d'.


9506 10Warning: Using only the first %d characters forpassword


1554



9507 18The builtin function s ` yb_sendmsg' is not supported.


9508 16The builtin function s ` yb_sendmsg' failed to sendthe message %.*s' to the destination address

%` .*s' at port number %d, because the length of theInternet address is greater than 255 bytes. Pleaseprovide a valid destination address and retry.


9509 16The builtin s ` yb_sendmsg' failed to send the message

%` .*s' to the destination address % ` .*s' at portnumber %d, because the port number is not valid.Please enter a valid (positive integer value between0 and 65535) port number and retry.


9510 16The builtin function s ` yb_sendmsg' failed tosend the message % .*s' to destination % ` .*s' atport number %d because the Internet address isincorrectly formed or is non-existent. Please enterthe Internet address in its correct form and retry.


1555



9511 18The builtin function s ` yb_sendmsg' failed to sendthe message %.*s' to the destination address % ` .*s'at port number %d due to an internal error whichrequired the message to be sent atomically. Pleasereport this error to your Systems Administrator.


9512 18The builtin s ` yb_sendmsg' failed to send the message

%` .*s' to destination % ` .*s' at port number %ddue to failure in opening or setting the socket tonon-blocking mode. Please report this internalerror to your Systems Administrator.


9513 18The builtin function 'syb_sendmsg' failed to sendthe message '%.*s' to the destination address '%.*s'due to a failure to bind the socket to a localport number %d provided by using dbcc tune. Pleasereport this error to your Systems Administrator.


9514 18The builtin function s ` yb_sendmsg' failed to sendthe message %.*s' to the destination address % ` .*s'at port number %d due to an internal error whiledoing the actual send. Please report this error toyour Systems Administrator.


1556




%` .*s' failed because the isolation level is at 0.


by message.

9516 16%d is an invalid spid. You could use sp_who toidentify the correct spid.


9517 16Table %.*s' does not exist in the database.


9518 17Insert 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. Checkstatus of tempdb.

9519 18Failed to update the identity pre-burn factor forfield % .*s' in table % ` .*s'. Please re-try theoperation or contact your SA for details.



9520 18Error occurred while creating the identity value forfield % .*s' in table % ` .*s'. Please re-try theoperation or contact your SA for details.



1557



9521 16The parameter that specifies the number of rows in aSET CURSOR ROWS statement must be an integer with avalue greater than 0.


9522 16The parameter that specifies the number of rows ina SET ROWCOUNT statement must be an integer with avalue greater than 0.


9523 18The builtin s ` yb_sendmsg' is not currently enabled.Please contact your Systems Administrator for moreinformation.


9524 16SELECT is not allowed in a dynamic EXECUTE IMMEDIATEstatement. This SELECT may have been part of astored procedure or a trigger.


9525 16A positioned update/delete on a row in table % ` .*s'failed. This is because cursor % ` .*s' does notpoint to a valid row in an inner(outer) table of anouter(inner) join used in the query.

Explanation: Attempted to delete or update a non-existent row in atable. Check join statement in the named cursor targeting this table.Cursor fetch may have returned NULL values due to no matching rows.

1558



9526 16The dynamic sql operation is not allowed with cursor

%` .*s'.

Explanation: You cannot use a client cursor within a dynamicallyprepared statement.

9528 16The optimizer could not find a unique index which itcould use to scan table % ` .*s' for cursor % ` .*s'.

Explanation: Command failed due to invalid or illegal request. Checksyntax, semantics, and permissions. Take any corrective action indicatedby message. Not raised in 11.9.2.

9529 20Deadlock during parallel merge. This is an internalerror. Use SET PARALLEL_DEGREE 1 to run this query,and contact Sybase Technical Support to report theproblem.

Explanation:

9532 20Internal error: unable to locate an extra SDES forcursor '%.*s'. The cursor was probably compiledwith the incorrect locking scheme for the targettable.

Explanation:

9533 20Internal error: unable to locate a temporary objectduring preprocessing.

Explanation:

9534 20Interal error: could not determine theconfiguration value for parameter '%s'.

Explanation:

9536 18Unable 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.

1559



9537 17Insufficient number of worker processes to executethis parallel query. Increase the value ofthe configuration parameter 'number of workerprocesses'.

Explanation:

9538 17Insufficient number of mailboxes to executethis parallel query. Increase the value of theconfiguration parameter 'number of mailboxes'.

Explanation:

9539 17Insufficient amount of memory per worker process toexecute this parallel query. Increase the valueof the configuration parameter 'memory per workerprocess'.

Explanation:

9540 17Insufficient number of messages to executethis parallel query. Increase the value of theconfiguration parameter 'number of messages'.

Explanation:

9541 18Worker Process API internal error %d. Considerrunning this query serially by setting the sessionparameter 'parallel_degree' to 1. Please contactSybase Technical SUpport

Explanation:

9543 16Parameter passed to %s has an invalid type. It mustbe of type %s.

Explanation:

9544 16Invalid time syntax in parameter for %s: '%.*s'.

Explanation:

9545 16Invalid time value in parameter for %s: '%.*s'.

Explanation:

1560



9546 10AN ADJUSTED QUERY PLAN IS BEING USED FOR STATEMENT%d BECAUSE

Explanation: The remainder of this explanatory message appears in9547.

9547 10NOT ENOUGH WORKER PROCESSES ARE CURRENTLY AVAILABLE.

Explanation: The first portion of this explanatory message appearsin 9546.

9548 10ADJUSTED QUERY PLAN:

Explanation: This is a message header.

9549 17Worker process (fid=%d, spid=%d) encountered error:%d, severity: %d, state: %d during parallelquery 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 parallelquery. fid is the family id of the worker process. You can use set

parallel_degree 1 to limit the session to serial operation.

9550 16The lightweight procedure '%*.s' cannot be executedbecause it does not exist.

Explanation:

1561



9601 10A %.*s error occurred during %.*s cleanup. Cleanupwill proceed for %.*s.


9602 20SQL Server has run out of CLEANUP ITEM BLOCKS.Re-run your command when there are fewer activeusers, or contact a user with System Administrator(SA) role to reconfigure SQL Server with moreCLEANUP ITEM BLOCKS.



1562



9701 16Parameter % .*s' has an invalid type.


9702 16Parameter % .*s' is invalid.


9703 16%` .*s' is not a valid account name.


9704 16Unable to get SQL Server security information.


9705 16Unable to set SQL Server security information.


9706 16SQL Server's user account cannot be modified.


9707 16No privilege to revoke.


1563



9708 16The account name provided is a domain. Unable togrant privileges to a domain.



9709 16The account name provided is a deleted account.Unable to grant privileges to a deleted account.


9710 16There must be at least one account with % ` .*s'privilege.


9711 16There must be at least one account with % ` .*s'privilege other than the % ` .*s'.


9712 16Access granted.

Explanation:

9713 16Access revoked.

Explanation:

9714 16login mode

Explanation:

9715 16default account

Explanation:

1564



9716 16default domain

Explanation:

9717 16set host

Explanation:

9718 16key _

Explanation:

9719 16key $

Explanation:

9720 16key @

Explanation:

9721 16key #

Explanation: Informational header.

9722 16name

Explanation: Header text.

9723 16config_item


9724 16standard


9725 16integrated

Explanation:

9726 16mixed

Explanation:

9727 16unknown mode

Explanation:

1565



9728 16true

Explanation:

9729 16false

Explanation:

9730 16space

Explanation:

9731 16domain separator

Explanation:

9732 16null

Explanation:

1566



9802 20Deletion of row in SYSPARTITIONS failed. Databaseid %d, Object id %d, Partition number %d.


9803 21Missing row in SYSPARTITIONS. Database id %d, Objectid %d, Partition number %d.


9805 10Partition number %d for object id %d in database %ddoes not exist.



9807 20Process %d encountered deadlock while trying to lockcontrol page %d of partition %d for object id %d.


9809 21Control page %d specified for partition number %d ofobject id %d in database %d does not exist.



1567



9810 21Control page %d specified for partition number %dfor object id %d in database %d is corrupt.



9814 21SYSPARTITIONS table is missing in database %d.



9816 17Unable to allocate an in-memory partition structurefor object id %d in database %d. To increase thenumber of available partitions update the p ` artitiongroups' configuration parameter.


9817 16Invalid object ID %ld. Valid user object ID is apositive integer.


by message.



9819 11Object ID %ld does not exist in database % ` .*s'.


1568



9820 11Partition number %d for object ID %ld in database%

`.*s' does not exist.


9821 12The object % .*s' is not a partitioned table.


9822 21An error occured during an update to a control page.The old last page ID %d does not match the last pageID of any partition for object % ` .*s' (ID %d) indatabase %` .*s' (ID %d) . The transaction is beingrolled back.


9823 20Insert new partition row in SYSPARTITIONS failed.Database id %d, Object id %d



9824 20Update row in SYSPARTITIONS failed. Database id %d,Object id %d, Partition number %d


1569



9901 14Permission denied. Only a user with curread set to@@data_high can perform the DBCC command % .*s'.


9902 14Only users with SA and SSO roles can run this dbccdbrepair command for the database %S_DBID.


9903 14Only users with SA and SSO roles having theircurread dominating the maxhold of the database canrun this dbcc dbrepair command for the database

%` S_DBID'.


9904 10Total (# of text chains = %ld text pages = %ld) inthis table.



9905 10Processed %ld tables. Found %ld good text entries,%ld bad text entries in this database


9906 16Unrecognized option. Available options: dbccengine(net, show, engine#), dbcc engine(net,showall), dbcc engine(net, netengine)


1570



9908 16Syspartitions system table does not exist indatabase id %S_DBID.



9909 10The total number of pages in partition %ld is %ld.


9911 10Object %ld has one row in Syspartitions


9912 10Object %ld has partition %ld instead of %ld inSyspartitions


9913 16MAX_ROWS_PER_PAGE value of %d is invalid. It mustbe between 0 and %d.


9914 16Amount of memory transferred (%dk) is less than theamount of memory requested (%dk).



1571



9915 16I/O size must be a power of 2.


9916 16I/O size must be a power of 2.


9917 16Can't find database id for %.*s. Check that thisdatabase exists and re-run the command.


9918 16Encountered error using dbid %d.


9919 16Can't find object id for %.*s. Check the objectname and re-run this command.


9920 16Index id %d not found for object id %d, dbid %d.


9921 16Index %.*s not found for object id %d dbid %d.



1572



9922 16The first page %ld in sysindexes for table % ` .*s'does not match with first page %ld for the table'sfirst partition in Syspartitions.


9923 16The first page %ld in syspartitions for partition%ld of table % .*s' has previous page # %ld in itspage header. The previous page # should be NULL.


9924 16The last page %ld in syspartitions for partition%ld of table % .*s' has next page # %ld in its pageheader. The next page # should be NULL.


9926 16This option has been converted to the configurationparameter % s'. Use s` p_configure' to set it.



9927 16This option requries a table name as the thirdparameter. Use s` p_configure % ` s'' to set theoption serverwide.



1573



9928 16This option has been disabled. Use s ` p_poolconfig'instead.


by message.

9929 14Only the DBO of database %S_DBID or a user withSystem Administrator (SA) role can run DBCCTEXTALLOC command.


9931 22The %S_MSG page (%ld) found in the page chain doesnot match with the %S_MSG page (%ld) found in theslice control page (%ld), for table % ` .*s', on slice%ld. The table may be corrupt.


9932 22The %S_MSG page (%ld) found in the page chaindoesn't match with the %S_MSG page (%ld) stored inthe Sysindexes for table % ` .*s'. The table may becorrupt.


9933 16The option max_rows_per_page cannot be set for atext/image index (%d) on table % ` .*s'.


syntax, semantics, and permissions. Take any corrective action indicatedby message. Not raised in 11.9.2.

9934 16Invalid index ID %d. Values for index ID must bebetween 0 and 255.

Explanation:

1574



9935 10SQL Server will not refresh index descriptor as theobject descriptor for objid % ld in dbid %d is notinstalled in cache.

Explanation:

9936 20Error while trying to refresh sysindexes row withinindex descriptor with indid % d objid %ld and dbid%d.

Explanation:

9938 16Table with ID %ld not found; check sysobjects.


9939 16DBCC %s command is not supported anymore.

Explanation: Refer to the System Administration Guide for details onsupported dbcc commands and usage.

9940 16The source text of object named '%s' with object id'%d' has already been hidden.



9941 16The source text of object named '%s' with object id'%d' is missing and it is not hidden.


9942 16Failed to hide the source text.


1575



9943 16The hidden text of object named '%s' with object id'%d' does not exist.


by message.

9944 10Too many errors have been detected on device'%.*s' (physical device: %.*s). Page and objectchecking on that device has been discontinued. (TheCHECKSTORAGE operation stops when more than 25%% ofthe checks are abandoned.)

Explanation:

9945 10Too many errors have been detected on table '%.*s'index '%.*s'. Checking for that object will bediscontinued. (The CHECKSTORAGE operation stopswhen more than 25 %% of the checks are abandoned.)

Explanation: Run dbcc checktable to determine the state of this object.

9946 17An attempt to reserve a 16K buffer failed. Increasethe size of the 16K buffer pool in the buffer cache'%.*s'.

Explanation:

9947 17An attempt to allocate memory failed due toinsufficient SQL Server memory.

Explanation:

9948 17The CHECKSTORAGE operation failed to cache a scanworkspace row because of a cache overflow. This isan internal error. Please contact Sybase TechnicalSupport.

Explanation:

9949 24An I/O in a workspace failed, page %d in database%d. Check your hardware for problems that couldcause I/O failures.

Explanation:

1576



9950 17Workspace '%.*s' is incorrectly allocated. Usesp_dbcc_createws to create a new workspace.

Explanation:

9951 17Workspace '%.*s' is too fragmented to be used. Usesp_dbcc_createws and sp_dbcc_updateconfig to correctthe problem.

Explanation:

9952 17Workspace '%.*s' is too small to permit theCHECKSTORAGE operation to proceed. Usesp_dbcc_alterws and sp_dbcc_updateconfig tocorrect the problem.

Explanation:

9953 20SQL Server failed to synchronize the activity ofa worker process with the coordinating process.This is an internal error. Please contact SybaseTechnical Support.

Explanation:

9954 10Storage checks for '%.*s' are complete. DBCC is nowrecording the results in the dbccdb database.

Explanation:

9955 20A worker process could not access database '%.*s'.This is an internal error. Please contact SybaseTechnical support.

Explanation:

9956 10A worker process failed to complete its assignedwork during the scan phase. The results of theCHECKSTORAGE operation will be incomplete.

Explanation: Informational message but may impact outcome of dbcccheckstorage.

1577



9957 10A worker process failed to complete its assignedwork during the page chain check phase. The resultsof the CHECKSTORAGE operation will be incomplete.


9958 10A worker process failed to complete its assignedwork during the OAM check phase. The results of theCHECKSTORAGE operation will be incomplete.


9959 10The CHECKSTORAGE operation has aborted.

Explanation: Problem impacts outcome of dbcc checkstorage.

9960 10A non-recoverable error has occurred in theCHECKSTORAGE operation. The operation has beenaborted.


9961 17DBCC failed to connect to the requested number ofworker processes. The number of workers configuredis insufficient, or the number of workers exceeds128. Use sp_dbcc_updateconfig to reduce 'max workerprocesses' for this database.


9962 17Access to table '%.*s' index '%.*s' in the targetdatabase failed.


9963 16An error occurred while attempting to insert a rowinto the dbcc_faults table or the dbcc_fault_paramstable.


9964 16Database '%.*s' was not found. Use sp_helpdb tolist the available databases.


1578



9965 16The entries in dbcc_config for database '%.*s' areeither missing or invalid. Use sp_dbcc_evaluatedbto determine appropriate values for the entries andsp_dbcc_updateconfig to set them.


9966 16DBCC could not access the scan workspace '%.*s'.Verify that the workspace exists .


9967 16DBCC could not access the text workspace '%.*s'.Verify that the workspace exists .

Explanation: Problem impacts outcome of dbcc checkstorage. Checkthe SA Guide for assistance.

9968 16DBCC could not evaluate SQL Server's deviceconfiguration. Check the contents of thedbcc_dev_info table.

Explanation: Problem impacts outcome of dbcc checkstorage. Check

the SA Guide for assistance.

9969 16The operation sequence number update for database'%.*s' in the dbcc_config table failed.


9970 16DBCC failed to either insert or update the rowin the dbcc_operation_log table for this check ofdatabase '%.*s'.


9971 20DBCC failed to schedule work for the workerprocesses. This is an internal error. Pleasecontact Sybase Technical Support.


SA.

1579



9972 16An error occurred while inserting the results intothe dbcc_counters table.


9973 16An error occurred while inserting the results intothe dbcc_operation_results table.


9974 10DBCC CHECKSTORAGE for database '%.*s' sequence%d completed at %s. %d faults and %d suspectconditions were located. %d checks were aborted.You should investigate the recorded faults, and plana course of action that will correct them.

Explanation:

9975 10DBCC CHECKSTORAGE for database '%.*s' encountered anerror. Some results may not be available. Correctthe problems reported and reexecute the CHECKSTORAGEcommand.

Explanation:

9976 10There is an inconsistency between the dbcc_dev_infotable and the sysdevices table. Use DBCCCHECKDEVINFO to regenerate the dbcc_dev_info table.

Explanation:

9977 16The cache '%.*s' specified in the dbcc_config tabledoes not exist.


9978 16The 16K buffer pool in the configured cache is toosmall. %dK is the minimum size .

Explanation: Check the SA Guide for assistance.

1580



9979 10Too many worker processes (%d) are configured forthe available 16K buffer pool. This buffer pool canonly support %d workers.

Explanation: Check the SA Guide for assistance.

9980 10%d text column values were not checked because thetext workspace was too small. Use sp_dbcc_alterwsto increase its size by %dK.



9981 16Correct syntax is:dbcc createws({dbccdb|dbccalt},segment name, workspace name, {scan|text}, size)dbcc alterws({dbccdb|dbccalt}, workspace name,{scan|text}, size)

Explanation:

9982 16The minimum size for a DBCC workspace is %d pages.


9983 16DBCC failed to create the workspace '%.*s'.


9984 16DBCC could not expand the size of workspace '%.*s'in database '%.*s' to %d pages .


9985 16DBCC could not truncate the size of workspace '%.*s'in database '%.*s' by %d pages.



1581



9986 10Suspect conditions are to be treated as faults ifthe same suspect condition persists in subsequentCHECKSTORAGE operations, or if they are alsodetected by other DBCC functions.

Explanation:

9987 16DOL datapage %ld of object %ld does not haveextended page header bits set correctly.

Explanation:

9988 16NCFS value %ld in DOL datapage %ld is larger thanavailable space %ld in the page

Explanation:

9989 16Number of deleted rows %ld in page header of DOLdatapage %ld is incorrect. This value cannot benegative.

Explanation:

9990 10Insert free space value %ld in page header of DOLdatapage %ld is greater than sum of cfs and ncfs(%ld) in the page

Explanation:

9991 16Orphan row at offset %ld in page %ld of object %ldmust be marked committed delete and is not

Explanation:

9992 16Actual #rows %ld in DOL datapage %ld and count of#rows - nextrno - %ld in page header do not match

Explanation:

9993 16There is a mismatch between value of ncfs counter%ld in page header of DOL datapage %ld and theactual amount of garbage %ld in the page

Explanation:

1582



9994 16There is a mismatch between count of #deleted rows%ld in page header of DOL data page %ld and theactual # deleted rows %ld in the page

Explanation:

9995 16There is a mismatch between value of insert freespace %ld in page header of DOL datapage %ld andactual value of insert free space %ld computed fromthe page with expected row size as %ld

Explanation:

9996 16Keys of index id %d for table '%.*s' in %S_MSGnot in proper order. Drop and recreate the index.(index page %ld)

Explanation:

9997 16Root page %ld in index id %ld of object id %ld doesnot have BT_ROOT bit set

Explanation:

9998 16Index page %ld has object id %ld which is differentfrom object id %ld

Explanation:

9999 16Rids not in ascending order in index page %ld forrow %ld at offset %ld (indid %l d, object %ld).Drop and recreate the index.

Explanation:

1583



10101 16The object_type column cannot be NULL.


10102 16The attrib_notify() function can only be used froma system stored procedure or with ad hoc updatesenabled.


10104 16Class %d is not a valid attribute class.


10105 16Attribute %d is not a valid attribute within class%d.


by message.

10106 16Class cannot be NULL.


10107 16Attribute cannot be NULL.


1584



10108 16The a` ction' parameter cannot be NULL.


10109 16The value of the parameter % ` s' is % d'. The valueshould be between %d and %d.


10110 10The entry being added will have no effect due toprecedence or scope rules.

Explanation:

10111 10The entry being dropped is preceded by anotherspecification; dropping the entry will have noeffect.

Explanation:

1585



10201 10NESTING LEVEL %u SUBQUERIES FOR STATEMENT %u.


10202 10QUERY PLAN FOR SUBQUERY %u (at nesting level %u andat line %u).



10203 10Subquery under an IN predicate.



10204 10Subquery under an ANY predicate.



10205 10Subquery under an ALL predicate.


10206 10Subquery under an EXISTS predicate.


10207 10Subquery under an EXPRESSION predicate.


1586



10208 10Correlated Subquery.


10209 10Non-correlated Subquery.


10210 10END OF QUERY PLAN FOR SUBQUERY %u.


10211 10Run subquery %u (at nesting level %u).


10212 10The cursor is read only because it contains asubquery.


10213 10The update mode is deferred_varcol.


10214 10The update mode is deferred_index.


1587



10215 10There have been %d scan fixups and %d matchingsearch argument fixups for this cursor.



10216 10The cursor is read only because it is referencing adynamic table.


10217 10Executed by coordinating process.

Explanation:

10218 10Executed in parallel by coordinating process and %ldworker processes.

Explanation:

10219 10Executed in parallel by %ld worker processes.

Explanation:

10220 10Executed in parallel with a %ld-way partition scan.

Explanation:

10221 10Executed in parallel by coordinating process and %ldworker processes.

Explanation:

10222 10Parallel work table merge.

Explanation:

10223 10Parallel network buffer merge.

Explanation:

10224 10Parallel result buffer merge.

Explanation:

1588



10225 10Auxiliary scan descriptors required: %d

Explanation:

10226 10The specified spid value '%d' is out of range. Itmust be positive and not exceed the maximum numberof user connections.

Explanation:

10227 10There is no active server process for the specifiedspid value '%d'. Possibly the user connection hasterminated.

Explanation:

10228 10The specified spid value '%d' applies to a serverinternal process, which does not execute a queryplan.

Explanation:

10229 10The process with the specified spid value '%d' hasnot been assigned an sqltext structure. Query planretrieval cannot continue.

Explanation:

10230 10The query plan for spid '%d' is unavailable.Possibly the query has not started or has finishedexecuting.

Explanation:

10231 10The current batch id '%d' does not match thespecified batch id '%d'. Specify just the spidvalue to obtain the current batch id.

Explanation: This message is sent when the target process has receiveda new SQL batch since the user executed sp_showplan.

1589



10232 10The current context id '%d' does not match thespecified context id '%d'. Specify just the spidvalue to obtain the current context id.

Explanation: This message is sent when the target process has invokedor returned from a procedure since you executed sp_showplan. So thequery plan may not correspond to other information retrieved.

10233 10The specified statement number '%d' is greater thanthe number of statements in the batch or procedure.Specify just the spid value to obtain the currentstatement number.

Explanation:

10234 10The SQL batch contains '%d' bytes. Text is '%.*s'.

Explanation:

10235 10The cursor was closed because the object associatedwith it has been dropped.


10236 10Executed by %ld worker processes.

Explanation:

10237 10Executed in parallel with a %ld-way hash scan.

Explanation:

10239 10With %S_MSG Buffer Replacement Strategy for datapages.

Explanation: Displays the buffer replacement strategy selected by theoptimizer for the data pages a given table.

10240 10Using I/O Size %d Kbytes for data pages.

Explanation: Displays the I/O size of the data pages selected by theoptimizer for a given table.

1590



10241 10ASC

Explanation: This is informational text or header.

10242 10DESC

Explanation: This is informational text or header.

10243 10Index key order not found.

Explanation:

10244 10Optimized using simulated statistics.


1591



10301 14Can't find database id for % ` .*s'. Check that thisdatabase exists and re-run the command.


10302 14Only the DBO of database %` S_DBID' or a user withSystem Administrator (SA) role can run this command.


10303 14Object named %.*s' not found; check sysobjects.


10304 14Only the owner of object % ` S_OBJID' or a user withSystem Administrator (SA) role can run this command.


10305 14Datatype 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 withthe correct name.

10306 14You do not have the permission to use datatype named%.*s in database %.*s.


10307 14Curread should dominate the label being used.


1592



10308 14Supplied label is invalid.


10309 14Curwrite is not equal to the label at which write isattempted.


10310 14Session labels dominance relationship has beenviolated by the label being used.



10311 14You must use one of the Sybase-supplied auditingstored procedures to change audit options.


10312 14The ad_hoc_audit builtin can only be called from thefollowing stored procedures: sp_addauditrecord,sp_bindmsg, sp_unbindmsg, sp_bindefault,sp_unbindefault, sp_bindrule, sp_unbindrule,sp_addmessage, sp_dropmessage.


10313 14The caller of the set_password builtin was notfound! Password left unchanged.


10314 14Only a person with System Security Officer (SSO)role can change another person's password.


1593



10315 14Invalid caller's password specified, password leftunchanged.


10316 14New password supplied is the same as the previouspassword. Please supply a different new password.


10317 14New password specified is too short. Minimum lengthof acceptable passwords is 6 characters.


10318 14Invalid user specified, password left unchanged.


10319 14SET ROLE fails. The caller is not granted with thespecified role. Please contact a user with SystemSecurity Officer (SSO) role for help.


10320 14SET ROLE fails. The caller cannot assume the newuser identity (uid) in the current database. Pleasecontact a user with System Security Officer (SSO)role for help.


10321 14Ad-hoc updates to system catalogs not enabled. Auser with System Security Officer (SSO) role mustreconfigure system to allow this.


1594



10322 14In a CREATE SCHEMA statement, the authorization idmust match the current user name. The suppliedauthorization id, % ` .*s', does not match the currentuser name, % .*s'.


10323 14You do not have the permission to use datatype id %din database id %d.


10324 14User %` .*s' not found in database % ` S_DBID'.; checksysusers.


10325 14Database named %.*s not found; check sysdatabases.


10326 14Suspect object %S_OBJID, database %S_DBID found.Cannot execute query.



10327 14Procedure %S_OBJID, database %S_DBID with labelsfound UNCERTIFIED. Cannot execute query.


1595



10328 14UNCERTIFIED object %S_OBJID, database %S_DBIDaccessed by CERTIFIED object %S_OBJID, database%S_DBID. Cannot execute query.


10329 14Sysobjects entry NOT found for procedure bufferentry.


10330 14%s permission denied on object %S_OBJID, database%S_DBID, owner %.*s


10331 14%s permission denied, database %S_DBID, owner %.*s



10332 14%s permission denied on column %.*s of object%S_OBJID, database %S_DBID, owner %.*s


10333 14Incorrect DBCC command: Please see the CommandsReference Manual for DBCC commands and options.


10334 14Permission related internal error was encountered.Unable to continue execution.


1596



10335 14SET label (CURREAD, CURWRITE) failed because newvalue is an invalid label, or new value doesn'tsatisfy the dominance relationships among sessionlabels.



10336 14Permission denied. Only the Database Owner (DBO) ora user with the System Administrator (SA), SystemSecurity Officer (SSO), or Oper role can executethis command for database % ` S_DBID'.


10337 16Object % S_OBJID' not found.


10338 14Permission denied. User's curwrite does not matchthe sensitivity label of object % ` S_OBJID'.


10340 14Permission denied. User's curwrite does not matchthe sensitivity label of database % ` S_DBID'.







1597



10343 14Permission denied. Only a user with curwrite set to@@data_low can perform the command % .*s'.


10344 14Permission denied. Only a user with curwrite set to@@data_high can perform the command % .*s'.


10345 14Permission denied. The user cannot insert into theobject % S_OBJID'.


10346 14Permission denied. The user cannot insert into theobject % S_DBID'.


10347 14Permission denied. The subject cannot see all thecontents of the container object % ` S_OBJID'.


10348 14Permission denied. The subject cannot see all thecontents of the container object database % ` S_DBID'.


10349 14Permission denied. Only a user with curread set to@@data_high can perform the command % .*s'.


1598



10350 14Permission related internal error was encountered.Unable to continue execution.


10351 14Server user id %d is not a valid user in database

%` .*s'


10352 14You can only use SELECT or SELECT INTO with thespecial table.


10353 14You must have the following role(s) to execute thiscommand/procedure: % .*s' . Please contact a userwith the appropriate role for help.


10354 14Permission denied. You must be either the systemadministrator (SA), the database administrator(dbo), or the owner of this object to perform thisoperation.


10355 16Changing certification state of object %S_OBJID,database %S_DBID to SUSPECT because of change instate of dependent object %.*s (previous object id%ld), database %S_DBID.


1599



10356 14Illegal datatype encountered; check systypes.


10357 14Permission denied. User's curwrite does not matchthe sensitivity label of datatype named % ` .*s' indatabase % .*s'.


10358 14Curread cannot be set below the current database'shurdle.


10359 18The curread and curwrite labels of the Client do notequal the connection level for the remote Server.



10360 18Site % .*s' not found in sysservers.



10361 14The attrib_notify() function can only be used froma system stored procedure or with ad hoc updatesenabled.

Explanation:

10362 14The logschema() built-in function can only be calledfrom the following stored procedures: sp_rename,sp_setreplicate, sp_setreptable, sp_setrepproc.

Explanation:

1600



10363 14The built-in function '%.*s' can only be called fromsystem stored procedures.

Explanation:

10364 14Permission denied. You must either be thedatabase/object owner or possess the following rolesin order to perform this operation: '%.*s'.


10365 14Permission denied. You must have '%s' access on thetable to lock it in '%s' mode.

Explanation: Failure to execute command LOCK TABLE in eithershared or exclusive mode. Check permissions.

1601



10401 10additional network memory allocates additionalmemory for clients which request packet sizes thatare larger than the default packet size for theserver.


10402 10address lock spinlock ratio specifies the number ofrows in the address locks hash table protected byone spinlock (rows per spinlock).



10403 10allow nested triggers is a toggle that controls theuse of nested triggers. When the value is set to 1,data modifications made by triggers can fire othertriggers.


10404 10allow remote access determines whether users fromremote servers can access this SQL Server. Thedefault is 1, to allow SQL Server to communicatewith Backup Server.



10405 10allow sql server async i/o is a toggle that enablesSQL Server to run with asynchronous disk I/O.


1602



10406 10allow updates to system tables allows system tablesto be updated directly. The default is 0 (off).



10407 10audit queue size determines the number of auditrecords that the audit queue can hold. The defaultis 100.


10408 10configuration file specifies the location of theconfiguration file you want to use.


10409 10cpu accounting flush interval specifies how manymachine clock ticks to accumulate before addingcpu usage data to syslogins for use in chargebackaccounting statistics.


10410 10cpu grace time specifies the maximum amount of time(in milliseconds) a user process can run withoutyielding the CPU before SQL Server infects it.


1603



10411 10deadlock checking period specifies the minimumamount of time (in milliseconds) a process must waitfor a lock before SQL Server initiates a deadlockcheck.



10412 10deadlock retries specifies the number of times atransaction will retry to acquire a lock after ithas become a deadlock victim.


10413 10default character set id is the number of thedefault character set used by the server.


10414 10default database size sets the default number ofmegabytes allocated to each new user database. Thedefault run value is 2 (megabytes)


10415 10default fill factor percent sets how full SQLServer makes each page when creating a new indexon existing data (unless user gives other value increate index statement).


1604



10416 10default language id is the number of the languagethat is used to display system messages unlessa user has chosen another language from thoseavailable on the server.



10417 10default network packet size sets the default size ofnetwork packets for all users on SQL Server.


10418 10default sortorder id is the number of the currentdefault sortorder on SQL Server. Do not change thisparameter. See the System Administration Guide formore information.


10419 10disk i/o structures specifies the initial numberof disk I/O control blocks SQL Server allocates onstartup.


10420 10event buffers per engine specifies the numberof events per SQL Server engine that can besimultaneously monitored. Events are used forobserving SQL Server performance.


1605



10421 10executable code size reports the size of the SQLServer executable.



10422 10freelock transfer block size specifies the number oflocks moved between the engine freelock cache andthe global freelock list.


10423 10housekeeper free write percent sets the maximumpercentage that database writes can increase becauseof free writes started by the housekeeper process.


10424 10i/o accounting flush interval specifies how manydisk I/Os to accumulate before flushing the data tosyslogins for use in chargeback accounting.


10425 10i/o polling process count specifies the number oftasks the scheduler will run before checking fordisk and/or network I/O completions.


1606



10426 10identity burning set factor sets the percentage ofpotential IDENTITY column values made available ineach block.


10427 10identity grab size allows each SQL Server processto reserve a block of IDENTITY column values forinserts into tables that have an IDENTITY column.


10428 10lock promotion HWM sets the maximum number of pagelocks allowed before SQL Server escalates to a tablelock. The default value is 200.


10429 10lock promotion LWM sets the minimum number of pagelocks allowed before SQL Server escalates to a tablelock. The default value is 200.


10430 10lock promotion PCT sets the percentage of page locksallowed before SQL Server escalates to a table lock.The default value is 100.


1607



10431 10lock shared memory disallows swapping of SQL Serverpages to disk, and allowing the operating systemkernel to avoid the server's internal page lockingcode.



10432 10max async i/o's per engine specifies the maximumnumber of asynchronous disk I/O requests that can beoutstanding for a single engine at one time.


10433 10max async i/o's per server specifies the maximumnumber of asynchronous disk I/O requests that can beoutstanding for SQL Server at one time.


10434 10max engine freelocks specifies the maximum number oflocks available in an engine freelock cache.


10435 10max network packet size sets the maximum networkpacket size that a client program can request.


1608



10436 10max number of network listeners specifies themaximum number of network listeners that can be openat one time.


10437 10max online engines controls the number of engines ina symmetric multiprocessor environment.


10438 10memory alignment boundary determines on whichboundary buffer caches are aligned.


10439 10min online engines is not currently used.


10440 10number of alarms specifies the number of alarmsallocated by SQL Server. Alarms are used with theTransact-SQL waitfor command.


10441 10number of devices controls the number of databasedevices SQL Server can use. It does not includedevices used for database dumps.



1609



10442 10number of extent i/o buffers allocates the specifiednumber of extents (8 data pages) for use by createindex. Do not set this value to more than 100.


10443 10number of index trips specifies the number of timesan aged index page recycles itself onto the MRUchain.


10444 10number of languages in cache is the maximum numberof languages that can simultaneously be held in thelanguage cache. The default is 3.


10445 10number of locks sets the number of available locks.The default run value is 5000.


10446 10number of mailboxes sets the number of mailboxstructures SQL Server allocates on start-up.Mailboxes are use for process-to-processcommunication and synchronization.


1610



10447 10number of messages specifies the number of messagestructures allocated by SQL Server at start-uptime. Messages are used in conjunction withmailboxes for process-to-process communication andsynchronization.


10448 10number of oam trips specifies the number of times anaged OAM page recycles itself onto the MRU chain.


10449 10number of open databases sets the maximum numberof databases that can be open at one time on SQLServer. The default run value is 12.


10450 10number of open objects sets the maximum number ofdatabase objects that can be open at one time on SQLServer. The default run value is 500.


10451 10number of preallocated extents specifies the numberof extent structures allocated in a single trip tothe page manager.


1611



10452 10number of remote connections controls the limit onactive connections initiated to and from this SQLServer. The default is 20.


10453 10number of remote logins controls the number ofactive user connections from this SQL Server toremote servers. The default is 20.


10454 10number of remote sites controls the number ofsimultaneous remote sites that can access this SQLServer. The default is 10.


10455 10number of sort buffers specifies the number ofbuffers used to hold pages read from input tables.


10456 10number of user connections sets the maximum numberof user connections that can be connected to SQLServer at one time.


1612



10457 10page lock spinlock ratio specifies the ratio ofspinlocks protecting the internal page locks hashtable.


10458 10page utilization percent controls when SQL Serverperforms an OAM (Object Allocation Map) scan to findunused pages. The default run value is 95.


10459 10partition groups sets how many partition groupsto allocate for the server. Partition groups areused by SQL Server to control access to individualpartitions of tables.


10460 10partition spinlock ratio sets the number ofpartition caches each spinlock protects. Thesespinlocks keep processes from using partition cachesused by other processes.


10461 10permission cache entries determines the number ofcache protectors per task.


1613



10462 10print deadlock information enables printing ofdeadlock information to the error log.



10463 10print recovery information determines whatinformation SQL Server displays on the consoleduring recovery.


10464 10procedure cache percent specifies the amount ofmemory allocated to the procedure cache after SQLServer's memory needs are met. The default runvalue is 20.


10465 10recovery interval in minutes sets the maximum timeper database that SQL Server uses to complete itsrecovery procedures in case of a system failure.


10466 10remote server pre-read packets controls the numberof packets that a site handler will pre-read inconnections with remote servers. The default is 3.


1614



10467 10runnable process search count specifies the numberof times an engine will loop looking for a runnabletask before relinquishing the CPU.


10468 10sort page count specifies the maximum amount ofmemory a sort operation can use.


10469 10sql server clock tick length specifies the durationof the server's clock tick, in microseconds.


10470 10stack guard size specifies the size of the stackguard area.


10471 10stack size sets the size of SQL Server's executionstack.


10472 10systemwide password expiration is the number ofdays that passwords remain in effect after theyare changed. The default is 0 (passwords do notexpire).


1615



10473 10table lock spinlock ratio specifies the number ofspinlocks protecting the table locks hash table.



10474 10tape retention in days sets the number of days youwant to retain each tape after it has been used fora database or transaction log dump.


10475 10tcp no delay disables TCP packet batching.


10476 10time slice sets the number of milliseconds that SQLServer's scheduler allows a user process to run.The default run value is 100 milliseconds.


10477 10total data cache size represents the amount ofmemory currently available for use as a data cache.It is a calculated value that is not directlyuser-configurable.


10478 10total memory sets the size of memory, in 2K units,that SQL Server allocates from the operating system.


1616



10479 10upgrade version is changed by the upgrade programprovided with new releases.



10480 10user log cache size specifies the size (in bytes)for each user's log cache.


10481 10user log cache spinlock ratio specifies the numberof user log caches per user log cache spinlock.


10482 10shared memory starting address determines thevirtual address at which SQL Server starts itsshared memory region. Most users do not need tomodify this.


10483 10size of auto identity column sets the precision ofIDENTITY columns automatically created with thesp_dboption a` uto identity' option.


1617



10485 10os file descriptors is a read-only parameterthat indicates how many file descriptors havebeen allocated to SQL Server. It is notuser-configurable.



10486 10Allow-limits allows the Resource Governor feature tobe used by SAs. Default is 0 (off); static.

Explanation:

10487 10number of auxiliary scan descriptors sets themaximum number of auxiliary scan descriptors thatcan be shared among all connections at one time.The default run value is 2 00.

Explanation:

10488 10number of open indexes sets the maximum number ofindexes that can be open at one time on SQL Server.The default value is 500.

Explanation:

10489 10object descriptor spinlock ratio specifies thenumber of open objects protected by one spinlock.The default value is 100.

Explanation:

10490 10index descriptor chain spinlock ratio specifies thenumber of internal hash tables for open indexesprotected by one spinlock. The default value is100.

Explanation:

10491 10index descriptor spinlock ratio specifies the numberof open indexes protected by one spinlock. Thedefault value is 100.

Explanation:

1618



10492 10enable cis specifies whether Component IntegrationServices is loaded when the server is started. Thedefault is 0 (do not load).


10493 10cis connect timeout specifies the number of secondsto wait for a connect request to a remote server tocomplete.


10494 10cis bulk insert batch size specifies the number ofrows in a bulk copy batch when performing a SELECTINTO operation.


10495 10max cis remote connections specifies the maximumnumber of connections to remote servers that can beactive at one time.


10496 10max cis remote servers specifies the maximum numberof remote servers that can be accessed at one time.


1619



10497 10cis packet size specifies the maximum size of anetwork packet.



10498 10cis cursor rows specifies the maximum number of rowsthat will be returned in response to a single fetchoperation.


10499 10CIS idle timeout specifies the number of seconds towait before terminating an idle connection with aremote server.


1620



10501 16Database '%.*s' not found; check sysdatabases.

Explanation:

10502 16Internal error occurred. Unexpected value supplied.Please call Sybase Technical Support.

Explanation:

1621



10601 10lock hashtable size specifies the number of bucketsin the lock hash table.


10602 10the lock spinlock ratio specifies the number ofbuckets in the lock hash table which are protectedby each spinlock (buckets pe r spinlock).



10603 10row lock promotion HWM sets the maximum number ofrow locks allowed before SQL server escalates to atable lock. The default value is 200.



10604 10row lock promotion LWM sets the minimum number ofrow locks allowed before SQL server escalates to atable lock. The default value is 200.



10605 10row lock promotion PCT sets the percentage of rowlocks allowed before SQL Server escalates to a tablelock. The default value is 100.


1622



10606 10dump on conditions indicates whether the SQLServer will create a shared memory dump file ifany conditions configured using the sp_dumpconfigstored procedure occurs. Possible values are 0 (notenabled) or 1 (enabled).


10607 10enable SQL Server performance monitoring withWindows NT Perfmon.


10608 10enable unloading of a DLL after each execution ofextended stored procedure.


10609 10specify the extended stored procedure executionpriority on the XP Server. The values range from 0to 15. The default value is 8.


10610 10specify the extended stored procedure stack size onthe XP Server. The values range and the defaultvalue is platform dependent.


1623



10611 10restrict the client execution privileges of theOS command specified with xp_cmdshell. Consultdocumentation for further details.


10612 10enable start of Sybmail session with Windows NT mailsubsystem with SQL Server startup.


10613 10enable SQL Server Error logging with Windows NTEvent Viewer.


10614 10enable SQL Server audit (logon success) logging withWindows NT Event Viewer.


10615 10enable SQL Server audit (logon failure) logging withWindows NT Event Viewer.


10616 10specify the computer name for centralized errorlogging with Windows NT Event Viewer.


1624



10617 16cis rpc handling specifies whether ComponentIntegration Services or a site handler is used tosend RPCs. The default is 0 (a site handler isused).


by message.

10618 16This parameter is used to change the value of themaximum number of roles that can be enabled by anyuser in a session.


10619 10number of large i/o buffers controls the number ofextent size i/o disk buffers which are allocated atserver startup. These buffers are used by 'diskmirroring', 'load database' and some dbcc commands.


10620 10number of worker processes is the maximum number ofworker processes that can be in use Server-wide atany one time.


10621 10memory per worker process is the additional amountof memory that will be allocated to each workerprocess.


1625



10622 10max parallel degree is the maximum number of workerprocesses that can be used by a given query at anyone time.


10623 10max scan parallel degree is the maximum number ofworker processes that can be used for a parallelscan against a non-partitioned object.


10624 10When set to 1, the Server will allow ONLY those userconnections which have already been authenticated bythe underlying security mechanism. Default is 0.


10625 10When set to 0, the Server will not initializethe Security Control Layer (support for securityservices is disabled). Default is 0.


10626 10When this parameter is set to 1, the SQL Server willnot allow any user connections which are not usingmessage confidentiality. Default value is 0.


1626



10627 10When this parameter is set to 1, the SQL Server willnot allow any user connections which are not usingmessage integrity. Default value is 0.


10628 10When set to 1, the Server will not allow any userconnections which are not using message replaydetection checks. Default value is 0. When setto 0, the Server will allow connections which usemessage replay as well as those which don't.


10629 10When set to 1, the Server will not allow any userconnections which are not using message originchecks. Default value is 0. When set to 0, theServer will allow connections which use messageorigin checks as well as those connections whichdon't.


10630 10When set to 1, the Server will not allow any userconnections which are not using message out ofsequence detection checks. Default value is 0.


1627



10631 10Each character from this string that appears in theprincipal name is mapped into the DOLLAR sign. Thisis required to take care of those characters thatmay be valid in an underlying security mechanism butnot valid in the SQL Server name space.


10632 10This login will be used by the SQL Server to let auser enter the SQL Server as a secure default loginif the user has already been authenticated by theunderlying security mechanism but does not have anentry in the syslogins table.


10633 10Each character from this string that appears in theprincipal name is mapped into the POUND sign. Thisis required to take care of those characters thatmay be valid in an underlying security mechanism butnot valid in the SQL Server name space.


10634 10Each character from this string that appears inthe principal name is mapped into the UNDERSCOREsign. This is required to take care of thosecharacters that may be valid in an underlyingsecurity mechanism but not valid in the SQL Servername space.


1628



10635 10determines whether users can modify their curreadwhen a cursor is open. The default is 1 (allowusers to modify their curread when a cursor isopen).



10636 10enables/disables the grouping of stored procedures.The default is 1 (procedure grouping allowed).


10637 10enables/disables granting select to public to thetext column of the syscomments table. The defaultis 1 (grant select on syscomments.text to public).


10638 10enables/disables the ability to send messages tointernet addresses. The default is 0 (sendmsg notallowed).


10639 10enables/disables auditing for the whole server. Thedefault is 0 (auditing disabled).


1629



10640 10establishes where SQL Server writes audit records.Values can be 1 to 8, representing sysaudits_01through sysaudits _08; 0 means to set the currentaudit table to the next in sequence. The default is1.


10641 10controls what happens when the audit table becomesfull. Values are (1) suspend the audit process andall auditable user processes (default), and (0)truncate the next audit table and start using it asthe current table.


10642 10indicates the default port number for sendinginternet messages.


10643 10enables/disables character conversion before sendingto or receiving from the client. The default is 0(SQL Server will convert characters before sendingto or received from the client).


10645 16Maximum dump conditions indicates the maximumnumber of shared memory dump conditions that can beconfigured on this server. The value of this fieldmay be from 10 to 100. The default value is 10.


1630



10646 16This configuration option enables/disables thebidirectional index scans


by message.

10647 10enables/disables asynchronous prefetch server-wide.Sets the percentage of each buffer pool in whichprefetched but unused pages can be stored. Ifneeded, this value can be overridden for a pool withlocal async prefetch limit

Explanation:

10648 10enable disk mirroring is a toggle that allows theuser to utilize SQL Server disk mirroring.


10649 10A transaction descriptor is used for eachtransaction started in a database by a userconnection. The number of transaction descriptorsper process times the number of user connectionsis the total number of transaction descriptorsavailable.


10650 10enables unicode-based character set conversions.When set to 1, enables conversions for charactersets not already in syscharsets. When set to2, enables Unicode-based conversions for allconnections. The default is 0 (off).

Explanation: This message is generated from sp_configure when youask for a description of the 'enable unicode conversions' option.

10651 10size of unilib cache sets the size of memory (inbytes) to be set aside for additional Unicode-basedconversions and collations.

Explanation: This is an informational message returned by sp_configureto describe what the 'number of unilib buffers' option does.

1631



10652 10size of unilib cache sets the size of memory (inbytes) to be set aside for additional Unicode-basedconversions and collations.

Explanation:

10659 10The 'license information' configuration parametersets the number of user logins for which AdaptiveServer is licensed. When this count is exceeded, aninformational message is printed to the error log.Contact Sybase to purchase additional licenses.

Explanation:

1632



10801 16Invalid type configured for cache %s. Cache typecan be one of default OR mixed OR log along with HKignore but NOT just HK ignore alone.


10802 16Configuration Error: Configuration Parameter % ` s'cannot be changed to 1 when parameter e ` valuatedconfiguration' is set to 1.


10803 16Configuration Error: Cannot set configurationparameter e valuated configuration' to 1. OtherSecurity related configuration parameters need to beset properly before this parameter can be changed to1. Please contact a user with SSO role for help.


10807 16The value of m ax parallel degree' ( ` %d') cannot beless than the value of m ` ax scan parallel degree'( %d').


10808 10Use sp_configure to lower the value of m ` ax scanparallel degree' or raise the value of m ` ax paralleldegree'.


1633



10809 16The value of n umber of worker processes' ( ` %d')cannot be less than the value of m ` ax paralleldegree' ( ` %d').


10810 16Use sp_configure to lower the value of m ` ax paralleldegree' or raise the value of n ` umber of workerprocesses'.



10812 20Auditing: Fatal erorr - could not truncate theaudit table % ` s'. This is an internal error.


10813 16Audit table cannot be changed because the log devicein the sybsecurity database is full.

Explanation: SSO is trying to change the current audit table numberbut the log for sybsecurity is full.

10814 20Auditing: Fatal error - could not get the name ofthe audit table with the object id % ` d' to truncateit. This is an internal error.


10815 16The lock hashtable size must be a power of 2. Youhave specified a size of %d, which is not a power of2. The next highest power of 2, %d, will be usedinstead.



1634



10816 16The value of the d ` ump on conditions' configurationparameter must be either 0 or 1.


by message.

10817 16Configuration Error: Unknown cache replacementpolicy % s' defined for cache % ` s'.


10818 10Warning: the value provided for p ` arallel_degree'( %` d') was less than the value of

s` can_parallel_degree' ( % ` d'). The valueof s can_parallel_degree' has been adjusted to % ` d'.


10819 10The value of s` can_parallel_degree' ( % ` d') cannot belarger than the value of s ` can_parallel_degree' setby a calling procedure. The value % ` d' is used.


10820 10The configuration option % ` s' has been changed by

%` s' from % s' to % s'.


10821 16The configuration option % ` s' requires a characterstring.


1635



10822 16The string size of the configuration option % ` s'must be less than %` d'.


by message.

10823 16The specified memory, % ` ldK', is not big enough toconfigure the configuration parameter, % ` s', to avalid value.


10824 16Illegal value % ` s' specified for configurationoption % s'. The legal values are between % ` ld' and

%` ld'.

Explanation: You tried to read in a configuration file which contains analphanumeric value for an integer configuration parameter. Correctthe file entries.

10825 16Configuration parameter, % ` s', will consume morethan %ld bytes of memory if configured at %ld.


10827 10Warning: the value of the configuration parameter'max scan parallel degree' has been set to %d. Foroptimal performance, a value no larger than 4 isrecommended.


1636



10828 10Consider increasing the value of configurationparameter 'total memory' or decreasing the value ofconfiguration parameters causing significant memoryconsumption, such as 'number of user connections'.

Explanation: Refer to “Configuring Memory” in the SystemAdministration Guide for information on how Adaptive Server uses

memory.

10829 16Adaptive Server cannot estimate the memoryrequirement. See the System Administration Guidefor information about Adaptive Server memoryrequirement.


10830 16Configuration parameter '%s' can be only 0 or 1.


10831 16Configured 'number of cache partitions' ('%d') isillegal in cache '%s'. The value must be a power of'2' and between '%d' and '%d'.

Explanation:

10832 16The size of each partitioned pool must have atleast512K. With the '%d' partitions we cannot configurethis value for buffer pool (%dk) in cache (%s).Please configure a bigger pool or reduce the numberof cache partitions.

Explanation:

1637



10901 20This query requires %d auxiliary scan descriptors,but currently there are only %d auxiliary scandescriptors available. Either raise the valueof the n umber of auxiliary scan descriptors'configuration parameter or try your query later.


10902 20This query requires %d auxiliary scan descriptors,but the Server is configured with only %d auxiliaryscan descriptors. Raise the value of the n ` umber ofauxiliary scan descriptors' configuration parameterbefore trying this query.


1638



11001 10Row count exceeded limit of %d.

Explanation: Indicates that resource limits defined with ResourceGovernor were exceeded.

11002 10Estimated IO cost exceeded limit of %d.

Explanation: Indicates that resource limits defined with ResourceGovernor were reached.

11003 10Actual IO cost exceeded limit of %d.


11004 10Query batch running time exceeded limit of %d.

Explanation: Indicates that resource limits defined with Resource

Governor were reached.

11005 10Transaction's running time exceeded limit of %d.


11006 17Unable to set a kernel alarm; timerange manager isunable to run.

Explanation: Resource Governor could not set an alarm. Check alarmresources.

11007 17Unable to set a kernel alarm; time limit alarmcannot be set.

Explanation: Resource Governor could not set an alarm. Check alarmresources.

11008 20An attempt to get a free cache member from theResource Governor's pool has failed. This isa system error -- contact a user with SystemAdministrator (SA) role.

Explanation:

1639



11009 16Syntax error converting to DATETIME fromBINARY/VARBINARY string.

Explanation:

11010 10Unknown limit type %d encountered -- limit will beignored.

Explanation: Illegal limit type was defined with Resource Governor.

11011 10Unknown limit scope 0x%x encountered -- limit willbe ignored.

Explanation: Illegal limit range was defined with Resource Governor.

11012 10Unknown limit enforcement time %d encountered --limit will be ignored.

Explanation:

11013 16Correlated columns are not allowed in the outer joinclause of the subquery.


11014 16Insufficient worker processes available. Queryexecuted using current available worker processes.Inform the system administrator (SA) that the valueof worker processes m ay be too low.

Explanation:

11015 16Insufficient worker processes available. Toexecute, wait until the system is less busy orset process_limit_action to quiet or warning, orincrease the value of worker processes.

Explanation:

11016 16Cannot disable the role '%.*s' since you don't haveit enabled.

Explanation:

1640



11017 20DLL for the extended stored procedure '%1!' is notfound. This is an internal error. Please contactSybase Technical Support.

Explanation:

11018 10XP Server must be up for ESP to execute.

Explanation:

11019 16Parameters to extended stored procedure must bepassed all by name or all by position.

Explanation:

11020 16Pseudo-column SYB_IDENTITY is referenced from astored procedure after the identity column haschanged. Please drop/recreate the stored procedure.


by message.

11026 10Warning: The statement on line %d uses the '%.*s'option with the view '%.*s'. Performance hintoptions are valid only for tables. This hint willbe ignored.

Explanation:

11029 16An index was found on table '%.*s' created viaSELECT INTO. Parallel inserts into indexed tables isunsupported. Drop the table and retry the command.

Explanation:

1641



11101 16Cannot grant the role '%.*s' because it containsrole '%.*s' which is mutually exclusive with role'%.*s' which is possessed by grantee '%.*s'. Removethe exclusivity and try again.

Explanation:

11102 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at activation ormembership level with role '%.*s' (contained by role'%.*s' which is the grantee role or the ancestorrole of grantee). Remove the exclusivity and tryagain.

Explanation:

11103 16Cannot grant the roles '%.*s' and '%.*s' becausethey are mutually exclusive at activation ormembership level. Remove the exclusivity and tryagain.

Explanation:

11104 16Cannot grant the role '%.*s' to role '%.*s' becauseit will result in cycle.

Explanation:

11105 16No such user/role '%.*s' exists.

Explanation:

11106 16Failed to grant role '%.*s' to grantee '%.*s'because failed to expand the role to be granted.

Explanation:

11107 10All the roles specified to be granted in the grantrole statement have already been granted to grantee'%.*s'.

Explanation:

1642



11108 10The result of the REVOKE ROLE command will takeeffect once the user logs out and then logs inagain.

Explanation:

11109 14You must have SSO authorization to grant/revoke userdefined roles.

Explanation:

11110 14You must be in the master database to GRANT/REVOKEROLE. Contact the System Administrator (SA) if youdo not have permission to run USE master.

Explanation:

11111 16No such role '%.*s' exists.

Explanation:

11112 16You must have SSO authorization to create UserDefined Roles.

Explanation:

11113 16You must be in the master database to run CREATEROLE command. Contact the System Administrator (SA)if you do not have permission to run USE master.

Explanation:

11114 16A role with name '%.*s' already exists in thisserver.

Explanation:

11115 16The role '%.*s' was not dropped because it still hasprivilege granted to it. Use the 'WITH OVERRIDE'option to drop it.

Explanation:

11116 16Cannot drop role '%.*s' because it does not exist inthis server.

Explanation:

1643



11117 16You must have SSO authorization to drop User DefinedRoles.

Explanation:

11118 16You must be in the master database to run DROP ROLEcommand. Contact the System Administrator (SA) ifyou do not have permission to run USE master.

Explanation:

11119 16The role '%.*s' was not dropped because it is one ofthe system roles.

Explanation:

11120 16You must have SSO authorization to use ALTER ROLE todefine roles exclusivity.

Explanation:

11121 16You must be in the master database to run ALTERROLE. Contact the System Administrator (SA) if youdo not have permission to run USE master.

Explanation:

11122 16Cannot drop the '%.*s' exclusivity between role'%.*s' and '%.*s' since it does not exist in thisserver.

Explanation:

11123 16Operation failed because the user '%.*s' has beengranted both role '%.*s' and role '%.*s'. Revokeone of the roles from the user and rerun thiscommand.

Explanation:

11124 16Operation failed because role '%.*s' has beengranted both role '%.*s' and role ' %.*s'. Revokeone of the granted roles from role '%.*s' and rerunthis command.

Explanation:

1644



11125 10Warning: User '%.*s' (process ID '%d') has bothroles '%.*s' and '%.*s' enabled. This violates the'%.*s' exclusivity just added. Terminate the user'sprocess to remove the violation.


about any warning issued in the message. (Not raised in 11.9.2)

11126 16Cannot add the '%.*s' exclusivity between role'%.*s' and role '%.*s' because it already exists forthis server.

Explanation:

11127 16The role named as '%.*s' does not exist for thisserver. Check the name and resubmit the ALTER ROLEcommand

Explanation:

11131 16Failed to expand the role with srid '%d' becausethis exceeds the maximum role limit of '%d'. Pleaserevoke/disable roles you don't require and thenrerun your command.

Explanation:

11132 16SQL Server failed to execute the built-in function%s because it failed to expand the role '%.*s'.

Explanation:

11133 16%s: unknown option: '%.*s'. Use either '%s' or'%s' as an option value.

Explanation:

11134 16You already have the role '%.*s' active.

Explanation:

1645



11136 16You have reached the limit on the number of rolesyou can enable per session. Increase the value ofthe configuration parameter 'max roles enabled peruser' and rerun your command.

Explanation:

11137 18Failed to add the role '%.*s' into the currentdatabase catalogs.

Explanation:

11138 16Failed to create role '%.*s', because this exceedsthe maximum number roles limit of '%d'. Pleasedelete roles you don't need and rerun your command.

Explanation:

11141 16Password required to set role '%.*s' on.

Explanation:

11142 16You specified the wrong password for enabling role'%.*s'. Try again with the correct password.

Explanation:

11143 16The password specified in CREATE/ALTER ROLE commandis too short. The minimum length of passwords is %dcharacters. Try again with a password that is %d ormore characters in length.

Explanation:

11145 16Command failed because no password exists for role'%.*s'.

Explanation:

11146 16Password already exists for role '%.*s'. Drop theexisting password and then add the new password.

Explanation:

1646



11148 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at activation ormembership level with role '%.*s' (which is theancestor of role '%.*s' in the hierarchy). Removethe exclusivity and try again.

Explanation:

11149 16Operation failed. Role '%.*s' is containedby/contains role '%.*s'. Revoke the granted rolefrom role '%.*s' or '%.*s' and rerun the command.

Explanation:

11150 16Operation failed. Role '%.*s' is mutually exclusiveat membership or activation level with role '%.*s'.Remove the exclusivity and try again.

Explanation:

11151 16Cannot grant the role '%.*s' because it is mutuallyexclusive with role '%.*s' which is possessed bygrantee '%.*s'. Remove the exclusivity and tryagain.

Explanation:

11152 16Operation failed. Role '%.*s' is mutually exclusiveat activation or membership level with role '%.*s'(contained by role '%.*s' which is the granteerole or the ancestor role of grantee). Remove theexclusivity and try again.

Explanation:

11153 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at membership oractivation level with role '%.*s'. Remove theexclusivity and try again.

Explanation:

11154 16Operation failed. Role '%.*s' has not been grantedto role '%.*s'.

Explanation:

1647



11155 16Operation failed. Role '%.*s' has not been grantedto user '%.*s'.

Explanation:

11156 16Operation failed. Role '%.*s' is mutually exclusiveat activation or membership level with role '%.*s'(which is the ancestor of role '%.*s' in thehierarchy). Remove the exclusivity and try again.

Explanation:

11157 16Operation failed. Role '%.*s' is mutually exclusiveat membership level with role '%.*s' (which alongwith role '%.*s' has been granted to user '%.*s').Remove the exclusivity and try again.

Explanation:

11158 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at membership levelwith role '%.*s' (which along with role '%.*s'has been granted to user '%.*s'). Remove theexclusivity and try again.

Explanation:

11159 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at activation ormembership level with role '%.*s' (contained by role'%.*s'). Remove the exclusivity and try again.

Explanation:

11160 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at activation ormembership level with role '%.*s'. Remove theexclusivity and try again.

Explanation:

1648



11161 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at activation levelwith role '%.*s' (contained by role '%.*s', whichhas already been enabled).

Explanation:

11162 16Operation failed. Role '%.*s' (contained by role'%.*s') is mutually exclusive at activation levelwith role '%.*s' (which has already been enabled).

Explanation:

11165 16A user or group with the name '%.*s' already existsin this Server.

Explanation: Informational: A role name has to be unique across theentire database.

11166 16User '%.*s' is currently logged in. The revocationof roles from users that are currently logged in isnot allowed.

Explanation: The revocation of roles from users that are currentlylogged in is not allowed as these users may already have activated theroles being revoked in their current login session.

11167 16The role 'sybase_ts_role' cannot be granted to otherroles.

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.

1649



11201 -11299 Explanation: See Chapter 5, "Component Integration Services" for anexplanation of these error messages.

1650



11302 20Internal error: Lock structure overflowed whileexecuting the built-in function logschema() onobject '%d' in database '%d'. Please contact SybaseTechnical Support.

Explanation:

11303 16Failed to obtain locks while executing the built-infunction logschema() on object '%d' in database'%d'. Retry the operation.

Explanation:

11304 20Internal error: No free session descriptor isavailable for opening the user object '%d' indatabase '%d' while executing the built-in functionlogschema(). Please contact Sybase TechnicalSupport.

Explanation:

11305 16Failed 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:

11306 16The object '%d' cannot be found in sysobjects indatabase '%d'. Check the value o f the object IDand retry the operation.

Explanation:

11307 16The object '%d' in database '%d' is not a validparameter for the built-in function logschema().The object must be a user table or a storedprocedure.

Explanation:

1651



11308 20Internal Error: There is no row in sysusers indatabase '%d' for user with user ID '%d'. However,this user is the owner of the object '%d' in thisdatabase. Please contact Sybase Technical Support.

Explanation:

11309 16The built-in function logschema() failed forobject '%d' in database '%d'. See the othermessages printed along with this message for moreinformation.

Explanation:

11310 20Internal Error: The database '%d' in which theobject '%d' resides and the database '%d' in whichthe schema needs to be logged are different fora schema modification operation. Please contactSybase Technical Support.

Explanation:

11311 20Internal Error: The column count in the XOBJINFOlog record for object '%d' in database '%d' isdifferent from the number of XCOLINFO log recordsthat are logged. Please contact Sybase TechnicalSupport.

Explanation:

11312 20Permission denied. User cannot execute the built-infunction logschema() on object '%d' in database'%d'.

Explanation:

1652



11313 20Failed to write the replication log record forthe '%.*s' command for object '%.* s' in database'%S_DBID'. The '%.*s' command is aborted.

Explanation:

11314 17Failed to write the replication log record for the'%.*s' command in database '%S_DBID'. The '%.*s'command will not be replicated.



1653



11401 10The number of RPC parameters is %d.

Explanation:

11402 10DLL %s was successfully loaded.

Explanation:

11403 16Encountered an exception(%d) in ESP %s in DLL %s.If this is an user DLL check the code else contactSybase Technical Support.

Explanation:

11404 20ESP %s not found in DLL %s.

Explanation:

11405 19Illegal ESP priority specified. Setting it toprevious value %d.

Explanation:

11406 10DLLname = %s.

Explanation:

11407 10ESPname = %s.

Explanation:

11408 19Illegal DLL file name length specified. Name willbe truncated to %s.

Explanation:

11409 19Illegal ESP name length specified. Name will betruncated to %s.

Explanation:

11410 20Failed to register the XP Server log file %s.

Explanation:

1654



11411 20Failed to set specified STACK SIZE %d for XP Server.Check the valid range in the documentation.

Explanation:

11412 20Failed to set preemptive scheduling mode. Mostprobably Open Server does not support it on thisplatform.

Explanation:

11413 10%s just disconnected.

Explanation:

11414 10XP Server is shutting down.

Explanation:

11415 10XP Server is now running.

Explanation:

11416 20Failed to install the connection handler. Check theXP Server log file.

Explanation:

11417 20Failed to install the disconnect handler. Check theXP Server log file.

Explanation:

11418 20Failed to install the RPC handler. Check the XPServer log file.

Explanation:

11419 20Failed to install the stop handler. Check the XPServer log file.

Explanation:

11420 20Failed to get connection context. Check the XPServer log file.

Explanation:

1655



11421 20Failed to set version of Open Server. Check the XPServer log file.

Explanation:

11422 20Cannot determine XP Server name. XP Server shuttingdown.

Explanation:

11423 10The XP Server log file name exceeded the maximumlimit of %d characters.

Explanation:

11424 20Failed to set error handler for XP Server. Checkthe XP Server log file.

Explanation:

11425 20Failed to initialize XP Server. Check the XP Serverlog file.

Explanation:

11426 20Failed to register the Start Handler. Check the XPServer log file.

Explanation:

11427 20Failed to run XP Server. Check the XP Server logfile.

Explanation:

11428 10Normal exit thru return from srv_run.


11429 18Failed to free CS_CONTEXT structure. Check the XPServer log file.

Explanation: Internal error affecting current process. Contact your SA.

11430 10ESP priority set to %d.

Explanation:

1656



11431 10Default stack size for ESP is %d.

Explanation:

11432 10XP Server name is %s.

Explanation:

11433 19Invalid XP Server name length specified. This is aninternal error. XP Server is shutting down.

Explanation:

11434 10DLLs will be unloaded automatically.

Explanation:

11435 10Client impersonation context set for ESPs.

Explanation:

11436 10Entering main().

Explanation:

11437 10Debug mode detected.

Explanation:

11438 10NT Service Option detected. Starting service.

Explanation:

11439 10Attempting StartServiceCtrlDispatcher().

Explanation:

11440 20Could not start service. Failed inStartServiceCtrlDispatcher.

Explanation: Error affects XP Server operation. Contact your SA.

11441 16Authentication failed. Connection denied. XPServer does not accept direct connection.

Explanation:

1657



11442 20Invalid authentication. Please contact SybaseTechnical Support.


11443 10Authentication was successful.

Explanation:

11444 20Failed to register the service control handler.You may start the XP Server through command lineinterface.

Explanation:

11445 10Entered xp_srv_service_main.


11446 20Failed to create the service thread.


11447 20Failed to create the service event.


11448 20%s: Operating System Error: %d: %s.


11449 20%s: Open Server Error: %d/%d/%d: %s.


11450 18%s: Fatal XP Server Error: %d/%d/%d: %s.


11451 16%s: XP Server Error: %d/%d/%d: %s.

Explanation: Check command syntax/semantics.

11452 10%s just connected.

Explanation:

1658



11453 20Could not get TDS version in connection handler.This is an internal error. Please contact SybaseTechnical Support.

Explanation:

11454 20Invalid client or SQL Server TDS version. TDSversion 4.6 or higher required.

Explanation:

11455 20Failed to get thread type for connection handler.This is an internal error. Please contact SybaseTechnical Support.

Explanation:

11456 20Failed to get login authentication type. This isan internal error. Please contact Sybase TechnicalSupport.

Explanation:

11457 17Failed to get the time. Using random macro instead.

Explanation:

11458 10The DLL %s was successfully unloaded.


11459 20The system DLL %s was not successfully loaded.

Explanation:

11460 18Sybmail configuration failed. Use xp_startmail withparameters to start the SQL Server mail session.

Explanation: Problem affected XP Server operation. Take recommendedaction.

11461 18ESP configuration failed. Default Values are used.


11462 16Could not load the DLL %s.

Explanation: Contact your SA.

1659



11463 16Invalid number of parameters specified. Check thedocumentation for minimum and maximum number ofparameters.

Explanation:

11464 16Invalid parameter value specified. Refer thedocumentation for the correct value( s).

Explanation:

11465 18Event Log configuration failed.

Explanation: Contact your SA to report the problem.

11466 10Eventlog enable/disable flag is %d.

Explanation:

11467 20Invalid SQL server name length (-a). Please checkthe documentation. XP Server is shutting down.

Explanation: Error affects XP Server operation. Check the configurationguide.

11468 10SQL Server name is %s.

Explanation:

11469 20Error condition in ESP. Refer to the XP Server logfile for more information.

Explanation:

11470 10Stack size specified was too small. Using defaultsize.

Explanation:

11471 20Failed to set XP Server interfaces file %s. XPServer shutting down.


1660



11472 20The pathname specified for the interfaces filewas too long. Check documentation for the maximumvalue.

Explanation:

11473 10Interfaces file %s is being referred by XP Server.

Explanation:

11474 20XP Server can not determine the client type.


11475 10Direct connection to the XP Server is not allowed.

Explanation: You must communicate with XP Server using AdaptiveServer commands.

11476 20Could not install the signal handler for %s. Pleasecontact Sybase Technical Support.

Explanation:

11477 16A signal(%s) was raised while executing this ESP.If this is an user DLL check the code else contactSybase Technical Support.

Explanation:

11478 20Failed to set the service status. This is aninternal error. Please contact Sybase TechnicalSupport.

Explanation:

11479 20NT service manager-related internal error.

Explanation:

11480 10DLL for the extended stored procedure not found.Check entry in syscomments for this ESP.

Explanation:

1661



11481 10Unable to start XP Server startup task. The servercan continue running without this task, howevernotify Sybase Technical Support for this error.

Explanation:

11482 17Cannot allocate memory. Check the XP Server logfile.

Explanation:

11483 10XP Server configuration failed.


11484 10Sybmail configuration for XP Server failed.


11485 20XP Server name is required to start XP Server. XPServer shutting down.

Explanation:

11486 10Cannot unload DLL %s. Either there is an OperatingSystem error while unloading or the DLL was neverloaded.

Explanation:

11487 10Attempt to free DLL failed. Check XP Servererrorlog file for more information.

Explanation:

11488 14User access denied. Not a member of NTadministrators group.

Explanation: Check login/role permissions.

11489 10Event Log configuration for XP Server failed. CheckXP Server errorlog file for more information.

Explanation:

1662



11493 14User access denied. Failed to change the usercontext.


11494 16Invalid Domain Name. PLease enter the correctDomain name and re-run the command.


11495 16Failed to synchronize with the SQL Server. Shuttingdown the XP Server.


11496 16Cannot %S_MSG site '%S_SRVID'. Please checkthe XP Server error log file for detailed errordescription.


1663



11501 12Invalid data type. An integer value must besupplied for error number.

Explanation:

11502 12Invalid data type. A VARCHAR value must be suppliedfor message.

Explanation:

11503 12Invalid data type. A VARCHAR value must be suppliedfor type.

Explanation:

11504 16Error number must be equal to or greater than 50000.

Explanation:

11505 16Type must be 'informational', 'warning' or 'error'.

Explanation:

11506 17Internal error: cannot allocate memory.

Explanation:

11507 16Invalid number of parameters. Error number andmessage must be provided.

Explanation:

11508 17Event logging is not enabled. Cannot log event inevent log.

Explanation:

11513 10Event log computer name is %s.

Explanation:

11514 17Failed to log event in Event Log. The Event Log maybe FULL.

Explanation:

11515 18Failed to initialize Event Log.

Explanation:

1664



11516 20Failed to create mutex '%s' used by Sybmail. Referto other error messages for possible cause of theproblem.

Explanation:

11517 20The mail session was already active when %s wasinvoked. Invocation of this ESP will have noeffect.

Explanation:

11518 20Sybmail encountered CMC Error:%s.

Explanation:

11519 20The mail session was not active. Start the mailsession using xp_startmail before calling %s.

Explanation:

11520 20Failed to get the number of input parameters for %s.Please contact Sybase Technical Support.

Explanation:

11521 20The function %s received an invalid number ofparameters (%d). Check user documentation andre-enter command.

Explanation:

11522 20The call to srv_descfmt() failed in %s. Pleasecontact Sybase Technical Support.

Explanation:

11523 20The call to srv_xferdata() failed in %s. Pleasecontact Sybase Technical Support.

Explanation:

11524 20The function %s expected some recipients, but nonewere found. Re-enter command with a value for@recipient.

Explanation:

1665



11525 20Memory allocation in %s of size %d failed. Checkthat sufficient memory is available to XP Server.

Explanation:

11526 20No message retrieved and/or deleted because nonefound.

Explanation:

11527 20The call to sm_bindparamdata() failed for parameter%s. Please contact Sybase Technical Support.

Explanation:

11528 20The call to sm_bindretprmdata() failed for parameter%s. Please contact Sybase Technical Support.

Explanation:

11529 20Failed to load CMC Library. Check that the libraryexists in a known location and re-enter command.

Explanation:

11530 20Failed to get address of function '%s'.Pleasecontact Sybase Technical Support.

Explanation:

11531 20Invocation of function %s failed. Please contactSybase Technical Support.

Explanation:

11532 20Failed to create attach file. Error number fromWin32 System Service is %d.

Explanation:

11533 20Failed to write to attach file. Error number fromWin32 System Service is %d.

Explanation:

11534 20Invalid parameter '%s' received. Check userdocumentation and re-enter command.

Explanation:

1666



11535 20The data type of parameter %s is invalid. Checkuser documentation and re-enter command.

Explanation:

11536 20The combination of input parameters %s is invalid.Check user documentation and re-enter command.

Explanation:

11537 20The value of parameter %s is invalid. Check userdocumentation for correct value.

Explanation:

11538 20The result set obtained by executing the suppliedquery is invalid. Review the text of query batchand re-enter command.

Explanation:

11539 20Failed to get thread property in %s. Please contactSybase Technical Support.

Explanation:

11540 20Failed to obtain lock in function %s. Pleasecontact Sybase Technical Support.

Explanation:

11541 20Failed to unlock mutex in function %s. Pleasecontact Sybase Technical Support.

Explanation:

11542 20Invalid mail profile name received. Check'MailUserName' configuration parameter value for SQLServer login 'sybmail'.

Explanation:

11543 20The operation type passed to %s is invalid.

Explanation:

1667



11544 20There was an internal error during processing.Please refer to XP Server log file for moreinformation.

Explanation:

11545 20The result set type '%d' obtained by executing thesupplied query was invalid.

Explanation:

11546 20The parameter '%s' is not an output parameter.

Explanation:

11547 20The required parameter '%s' is missing. Check userdocumentation and re-enter command.

Explanation:

11548 20Invalid event log computer name length (-l). XPServer shutting down.

Explanation:

11549 20Failed to access include file %s. Error number fromfile access call is %d.

Explanation:

11550 20Failed to start mail session. To use defaultparameter values for xp_startmail, add the 'sybmail'user account and configure 'start mail session'configuration parameter.

Explanation:

1668



11601 18Instance does not have any data pointers forcounters. Restart SQL Server. If problem persists,contact Sybase Technical Support.

Explanation:

11602 18Failed to open file mapping in DLL to attach to SQLServer shared memory. SQL Server may not be runningor the machine is low on disk space. Otherwise,contact Sybase Tech nical Support.

Explanation:

11603 18Failed to MapViewOfFile of SQL Server shared memoryfile mapping. SQL Server may not be running or themachine is low on disk space. Otherwise, contactSybase Technical Support.

Explanation:

11604 20Failed during signature verification of SYBPERF_ENVmemory block of SQL Server. Restart SQL Server. Ifproblem persists, contact Sybase Technical Support.

Explanation:

11605 20Cannot allocate any more SYBPERF_COMPLEX_DEFs, arraytoo small. Too many SQL Server counter objects,counters, and instances. NT Performance Monitorwill not monitor this SQL Server. Please reducenumber of counter objects, counters, instances.

Explanation:

11606 20The performance monitor component of SQL Server isnot initialized correctly.

Explanation:

11607 10NT Performance Monitor has started monitoring SQLServer.

Explanation:

1669



11608 10Monitor Group %s not found.

Explanation:

11609 10Monitor Counter %s not found.

Explanation:

11610 10SYBPERF_OBJECT_TYPE %s not found.

Explanation:

11611 10No SQL Server is running with perform.exeintegration; therefore, there is nothing to monitor.

Explanation:

11612

Explanation:

1670



11701 15CREATE PROCEDURE for extended stored procedurecannot contain statements after DLLNAME.

Explanation:

11704 16The specified option '%.*s' is not valid forthis command. The option is valid for the LOADTRANSACTION command.

Explanation:

11706 16Time value '%.*s' in the LOAD TRANSACTION UNTIL_TIMEclause is not a legal value.

Explanation:

11707 16Incorrect time syntax in time string '%.*s'used in the LOAD TRANSACTION UNTIL_TI MEstatement. Correct format is month day, yearhour:minute:seconds:milliseconds[am | pm]

Explanation:

11710 16Subqueries are not allowed in a DEFAULT clause.


by message.

11711 16The REORG option '%.*s' requires a value greaterthan 0 to be specified.

Explanation:

11712 16You cannot specify a value with the REORG option'%.*s'.

Explanation:

11713 16Index name is not allowed in UPDATE PARTITIONSTATISTICS statement. Use partition number instead.

Explanation:

1671



11714 16Partition number is not allowed in UPDATE STATISTICSstatement. Use index name instead.

Explanation:

11715 16Options (index name, partition number) in UPDATE ALLSTATISTICS statement are ignored.

Explanation:

11717 16The quoted identifier '%.*s' is illegal because itsfirst character is '#', which is ambiguous. Pleaseuse another character instead.

Explanation:

11718 16%ld is not a valid partition number. Partitionnumber must be greater than 0.

Explanation:

11719 16Error converting %ld to IDENTITY_START value.

Explanation:

11720 16%.*s' is not a REORG subcommand. The validREORG subcommands are: REBUILD, FORWARDED_ROWS,RECLAIM_SPACE, and COMPACT.

Explanation:

11721 16Global variables not allowed as defaults.

Explanation:

11722 15The READPAST and HOLDLOCK object level lockingoptions are incompatible.

Explanation:

11723 16READPAST conflicts with AT ISOLATION LEVEL 3.

Explanation:

1672



11724 15Target variable '%.*s' may not appear in both theSET and WHERE clauses of the UPDATE statement, norin any subquery of the SET clause.


11725 15All result expressions in a CASE expression must notbe NULL.


11726 15A single coalesce element is illegal in a COALESCEexpression.



11727 15Subquery and aggregate function not supported in aCASE Expression.


11728 15SELECT INTO cannot be used in an INSERT statement topull values from tables.


11729 15The name '%.*s' is not a valid local variable name.


11730 15The PROXY option cannot be used in conjunction withother options in a SET command.


1673



11731 15Duplicate option has been specified to UPDATESTATISTICS command. One or many options have beenrepeated.

Explanation:

11732 10Warning : Ambiguous correlation names in the setclause

Explanation: This warning is raised when the user use more than onecorrelated name in the set clause at the left of the assign sign.

11733 10Warning : Ambiguous table to update; Using thetable specified in the update clause.

Explanation: This error is raised when Adaptive Server finds that thecorrelated 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.

11734 16The quoted identifier '%.*s' is illegal because itcontains an embedded period followed by an embeddeddouble quote. Please substitute another characterin place of one of these characters.

Explanation:

1674



11901 16Table '%.*s' was not found.

Explanation:

11902 16'%.*s' is not a table.

Explanation:

11903 16You cannot run REORG on a table which uses allpageslocking.


11904 16You cannot specify an index with this REORGsubcommand. Only the RECLAIM_SPACE subcommand canbe run on an index.

Explanation:

11906 16You cannot use the RESUME or TIME options with theREBUILD subcommand.

Explanation:

11910 16Index '%.*s' was not found.

Explanation:

11911 10Using time limit of %d minutes.

Explanation:

11913 10Warning: The RESUME option was specified, butno valid restart point was found. Starting frombeginning of object.

Explanation:

11915 10There are approximately %d pages to be processed.

Explanation:

11916 10%d pages have been processed.

Explanation:

1675



11917 16REORG REBUILD of systabstats is not allowed.

Explanation:

11918 16You cannot run REORG REBUILD on '%.*s' because thereare one or more isolation level 0 scans active onthe table.

Explanation:

11919 16You cannot run REORG REBUILD in this databasebecause the 'select into/bulkcopy' option is off.Please check with the DBO.

Explanation:

11920 10Beginning REORG %s of '%.*s'.

Explanation: This informational message is displayed when the REORGcommand starts executing. The first parameter is the subcommandname, for example RECLAIM_SPACE.

11921 10Beginning REORG RECLAIM_SPACE of index '%.*s' ontable '%.*s'.

Explanation: This informational message is printed when the REORGRECLAIM_SPACE command starts executing on an index.

11922 10Resuming REORG %s of '%.*s'.

Explanation: This informational message is printed when the REORGutility starts execution with the RESUME option. The first parameter isthe subcommand name, for example RECLAIM_SPACE.

11923 10Resuming REORG RECLAIM_SPACE of index '%.*s' ontable '%.*s'.

Explanation: This informational message is printed when the REORGRECLAIM_SPACE command starts executing on an index, with theRESUME option.

1676



11924 10REORG %s of '%.*s' completed.

Explanation: This informational message is printed when the REORGcommand completes execution. The first parameter is the subcommandname, for example RECLAIM_SPACE.

11925 10REORG RECLAIM_SPACE of index '%.*s' on table '%.*s'completed.

Explanation:

11926 10REORG %s of '%.*s' terminated due to error or userinterrupt.

Explanation: This message is raised when the REORG utility encounters

an error that causes termination, or when the user terminates REORG.

11927 10REORG RECLAIM_SPACE of index '%.*s' on table '%.*s'terminated due to error or user interrupt.

Explanation: This message is raised when the REORG utility encountersan error that causes termination, or when the user terminates REORG.

1677



12001 16Unable to find entry for class: %d, attribute: %d,value: %d.


12003 16Unable to allocate shared memory dump condition.All conditions (%d) already allocated.


12004 16Empty shared memory dump condition list head passed.


12005 16Cannot free shared memory dump condition. Entry0x%x not found.


by message.

12006 16An entry already exists for class: %d, attribute:%d, value: %d.


12007 16Cannot set shared memory dump condition. An invalidattribute value was recevied: %d.


1678



12008 16Directory name too long. The maximum directorylength is %d characters.


by message.

12009 16File name too long. The maximum length is %dcharacters.


12010 16Unable to set shared memory dump condition. Invalidrecord type: %d.


12011 16Configuration of shared memory dump conditions isnot available on this platform.


1679



12100 16Cannot execute a LOCK TABLE command on table '%.*s',because this table does not exist.

Explanation:

12101 16The object '%.*s' you've specified is not a usertable. Executing the LOCK TABLE command is onlypermitted on user tables.

Explanation:

12102 16The table '%.*s' you've specified is a temporarytable. Executing the LOCK TABLE command is notpermitted on temporary tables.

Explanation:

12103 10Table '%.*s' in database '%.*s' was not locked in'%.*s' mode because a covering lock in '%.*s' modewas found.

Explanation:

12104 16A LOCK TABLE command is not allowed outside thescope of a transaction on table ' %.*s' in thedatabase '%.*s'.

Explanation:

12106 16Invalid parameter in LOCK TABLE syntax: '%.*s'.

Explanation:

1680



12200 10Current session (spid = %ld) is holding a lockbelonging to a non-existent cursor. Please contactSybase Technical Support.

Explanation: This is an informational message. Unless otherwisespecified, no action is required. Contact your System Administratorabout any warning issued in the message. (Not raised in 11.9.2)

12201 20Lock found in lock cache not on global lock chain:dbid %d, objid %d, locktype %d, sufficiency class %d



12202 10Could not initiate lock wait checking becauseAdaptive Server has run out of alarms. If yourapplication uses this feature, try rebooting theserver.

Explanation:

12203 18Lock cache entry not found for spid %d, lock 0x%lx,type %d, suff class %d. Please notify your systemadministrator.

Explanation:

12204 18Attempted to redo deadlock search as a result ofa lock upgrade. Found too many SH_NKL lockrecs.Please contact Sybase Technical Support.

Explanation:

12205 17Could not acquire a lock within the specified waitperiod. %s level wait period=%d seconds, spid=%d,lock type=%s, dbid=%d, objid=%ld, pageno=%ld,rowno=%ld. Aborting the transaction.

Explanation:

1681



12206 20Internal Error in lock manager routine: Attemptedlock anti-inheritance when the parents sdes chaindoes not include the dbid and objid corresponding tothe child thread which are dbid=%d and objid=%d.

Explanation:

12207 10Could not acquire a lock within the specified waitperiod. %s level wait period=%d seconds, spid=%d,lock type=%s, dbid=%d, objid=%ld, pageno=%ld,rowno=%ld.

Explanation:

1682



12300 20Internal error: in table '%.*s', database %d, theforwarded row (%d, %d) pointed to by (%d, %d) isinvalid. Aborting the transaction.

Explanation:

12301 20Internal error: the index (id = %d) and the datafor row (%d, %d) in table '%.*s', database %d areinconsistent; data is marked deleted but index isnot. Aborting the tran saction.

Explanation:

12302 20Internal error: deleted row (%d, %d) erroneouslyqualified for table '%.*s', database %d.Terminating the scan.

Explanation:

12303 20Internal error: invalid scan branch type. Abortingthe transaction.

Explanation:

12304 10Index id %d cannot be used to access table id %d asit is SUSPECT. Please drop and re-create the index.Table-scan is being used instead.

Explanation:

12306 26No table lock on object '%.*s' in database '%.*s'.

Explanation:

12307 26Row %d of Page %ld in dbid %d is not locked.

Explanation:

12308 21Internal error : Invalid row id (Row %d, Page %ld)encountered in the table '%.*s ' in the database'%.*s'.

Explanation:

1683



12309 21Expanding update on object '%.*s' in database '%.*s'cannot succeed on page %ld. This is an internalerror.

Explanation:

12310 21Internal error: split or shrink propagation failedto commit after changing the page %ld of indexid %d of table '%S_OBJID' (id = %ld) in database'%S_DBID'. Xactid is (%l d,%d). Drop and re-createthe index.

Explanation:

12311 20Internal error: address lock request on page %ldof index id %d of table '%S_OBJID' (id = %ld) indatabase '%S_DBID' failed with status %d. No needto drop the index.

Explanation:

12312 20Index with id %d of table '%S_OBJID' (id = %ld) indatabase '%S_DBID' is already at the maximum allowedheight. It cannot grow any further. Try droppingand recreating the index.

Explanation:

12313 21Internal error: Insert into page id %ld of indexid %d of table '%S_OBJID' (id = %ld) in database'%S_DBID' tried to replace undeleted RID (%ld,%d) atslot %d and ridposn %d. Try dropping and recreatingthe index.

Explanation:

12314 21Bad child page pointer found on page %ld of indexwith 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:

1684



12315 21Corrupt page, Internal error: Mismatch between tailtimestamp '%04x' and the low two bytes of timestampin the page header '%04x' while accessing page '%ld'of object '%ld ' in database '%d'. Please contactSybase Technical Support.

Explanation:

12316 20Internal error: Attempt to garbage collect adeallocated data page %d in table '% .*s', database'%.*s'. Aborting the transaction.

Explanation:

12317 20Internal error: Insert of a key of size %ld intopage %ld of index id %d of table '%S_OBJID' (id= %ld) in database '%S_DBID' failed because pagehas freespace of size %ld . Try again or drop andrecreate the index.

Explanation:

12318 20Fatal internal error ecountered during scan onthe 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 contactSybase Technical Support.

Explanation:

12319 20Fatal internal error encountered during deferred dmlon table '%.*s' in database '%.*s'. All rows thatqualified during the first phase were not visitedduring second phase of dml.

Explanation:

12320 21Fatal internal error encountered when forwarding row(%d, %d) in table '%.*s', database '%.*s' duringupdate. Aborting the transaction.

Explanation:

1685



12321 20Internal error: No split point found for page %ldof index %d of object %ld. Old page : %d entries,free space = %d. Split point information : <(%d),(%d), (%d, %d, %d)>.

Explanation:

12322 21Row %d on DOL datapage %d in database '%.*s'has size %d and an invalid holesize %d. Page iscorrupted.

Explanation:

1686



12504 10Timestamp mismatch error was not generated on pagebecause page is marked for deallocation. Page#=%ld, object id = %ld, page timestamp=%04x %08lx.Log old timestamp=%04x %08lx.

Explanation:

12505 18could not open table '%d' in database '%d' by id

Explanation:

12506 18sysstatistics upgrade error in table '%.*s' index'%.*s' distribution page %d - bad page format - runupdate statistics on this table after upgrade

Explanation:

12507 18sysstatistics upgrade error in table '%.*s' index'%.*s' distribution page %d - nulls not a beginningof page - run update statistics on this table afterupgrade

Explanation:

12508 18sysstatistics upgrade error in table '%.*s'index '%.*s' distribution page %d - values not inascending order - run update statistics on thistable after upgrade

Explanation:

12509 18sysstatistics upgrade error in table '%.*s' index'%.*s' distribution page %d - cannot deallocate pagerun update statistics on this table after upgrade

Explanation:

12510 18sysstatistics upgrade error in table '%.*s' index'%.*s' distribution page %d - cannot read page - runupdate statistics on this table after upgrade

Explanation:

1687



12511 21During recovery, quiescent last log marker is notfound on database '%.*s'. The b ackward log scanwas started on marker (%d, %d).

Explanation:

12512 16Database '%.*s' (dbid %d): has incompletetransactions. Online database command for standbymode cannot be completed successfully. Please tryonline database command without any options.

Explanation:

12513 10Failed to delete the user specified recovery orderfor the dropped database '%.*s '. Inform systemadministrator. During next bootup of server, thismay turn off user specified recovery order.

Explanation:

12514 10Failed to read the user specified recovery orderinformation. Inform system administrator. Thedefault dbid order will be used. To fix, delete allthe user specified recovery order and reinstall themusing sp_setrecovery_order.

Explanation:

12515 18sysindexes.distribution for table '%.*s index '%.*s'does not contain a valid distribution page %d.

Explanation:

12516 21During undo processing a CLR could not be logged.The internal error number is %d .

Explanation:

12517 16During transaction rollback a CLR could not belogged. The internal error number is %d.Thisprocess will retry at intervals of one minute.

Explanation:

1688



12518 20Attempt to get an uninitialized page %d in databaseid %d during %s.

Explanation: This exception is raised when an uninitialized page isencountered during recovery or undo operation when the page is

expected to be allocated already.

12519 18sysstatistics upgrade error in table '%.*s' index'%.*s' distribution page %d - exception occurred -run update statistics on this table after upgrade

Explanation:

1689



12700 18Suspect Granularity: Bad suspect item type % ` d'( %` d') due to an internal error. Please contactSybase Technical Support.


12701 10Suspect Granularity: Command failed. No cachedsuspect list.



12702 18Suspect Granularity: Unable to delete suspectinformation from master..sysattributes table.


12703 18Suspect Granularity: Unable to starttransaction to delete suspect information frommaster..sysattributes table.


12704 18Suspect Granularity: Failed to access sysdatabasestable.


1690



12705 18Suspect Granularity: Failed to replace sysdatabasesrow.



12706 18Suspect Granularity: Failed to end update onsysdatabases table.


12707 18Suspect Granularity: Adding suspect informationrows is not allowed.


12708 18Suspect Granularity: Failed to read or change a bitin status2 field of sysdatabases row.


12709 18Suspect Granularity: Failed to clean up suspectinformation.


12710 18Suspect Granularity: Command failed because ofan unknown suspect attribute ( % ` d'). This is aninternal error. Please contact Sybase TechnicalSupport.



1691



12711 18Suspect Granularity: Command failed becausecached suspect information is missing. This is aninternal error and can be a serious problem. Youmay need to restart SQL Server. Contact your SystemAdministrator.


12712 18Suspect Granularity: Command failed because aninvalid action ( % ` d')was detected. This is aninternal error. Please contact Sybase TechnicalSupport.


12713 18Suspect Granularity: Command failed because asuspect page-to-object map was not availabledue to allocation page corruption. Contact yourSystemAdministrator.


12714 18Suspect Granularity: For the last suspect page inthe object, the delete of the suspect object entryfailed but sp_forceonline_page was successful.Usesp_forceonline_object to clean up the objectinformation.


1692



12715 18Suspect Granularity: Command failed and therequested operation did not complete. Inform yourSystem Administrator.


12716 17Data unavailable: Unable to complete because therequired data is currently unavailable. The commandfailed and the transaction aborted.Try again lateror contact your System Administrator.


12717 10Suspect data encountered: Database % ` .*s', object

%` .*s'Index ID % ` ld', page ID % ` ld'.


12718 10Suspect data encountered: Database: % ` .*s', Page:

%` ld' (object information not available).


12719 17Suspect Granularity: Drop of object % ` .*s' failedbecause master transaction is required to updatemaster..sysattributes table. Drop the table/indexwithin a master database transaction.



12720 17Suspect data encountered: Drop of object % ` .*s'failed because it contains suspect data.


1693



12721 10Suspect Granularity: Page % ` ld' of database % ` .*s'was made accessible to all users from previous state

%` .*s'.


12722 10Suspect Granularity: The access state of page

%` ld' of database % ` .*s' was changed from % ` .*s' to%` .*s'.


12723 10Suspect Granularity: Object % ` ld' with index % ` ld'of database % .*s' was made accessible to all usersfrom previous state % ` .*s'.


12724 10Suspect Granularity: The access state of object

%` ld' with index % ` d' of database % ` .*s' was changedfrom %` .*s' to % ` .*s'.


12725 18Suspect Granularity: Transaction failed duringcommit (putxact).


1694



12726 17Suspect Granularity: Dump database of % ` .*s'failed because some of the data in this database issuspect.


12727 17Suspect Granularity: Database % ` .*s' hassuspect data. Dump transaction with requestedoptions is disabled. Use dump transaction thatsaves the log OR SA can online all suspect data(sp_forceonline_page) before performing thisoperation.


12728 18Suspect Granularity: Drop of object % ` .*s' faileddue to an internal error. Consult the error log andInform your System Administrator.


12729 10Suspect Granularity: WARNING: The drop of % ` .*s'may fail if it has suspect pages because it requiresa transaction that started in the master database.


12730 10Suspect Granularity: Automatic truncation of logafter checkpoint has been disabled temporarilybecause some data in database % ` .*s' is suspect.Either truncate log without no_log or truncate_onlyoption, or online all suspect pages/objects.


1695



12731 17Recovery (Suspect Granularity): Reached suspectthreshold % d' for database % ` .*s'. Increasesuspect threshold using sp_setsuspect_threshold.


12732 18Recovery (Suspect Granularity): Unable tomark suspect object % ` ld'.Inform your SystemAdministrator.


12733 18Recovery (Suspect Granularity): Errorin getting suspect information row frommaster..sysattributes.Inform your SystemAdministrator.


12734 18Recovery (Suspect Granularity): Failed to insertrow into master..sysattributes table.


12735 18Recovery (Suspect Granularity): Failed to scanmaster..sysattributes table for suspect information.


1696



12736 10Recovery (Suspect Granularity): Allocation page %ldis corrupted.



12737 18Recovery (Suspect Granularity): Recovery abortedfor database % .*s' because the suspect items cannotbe isolated at this level.


12738 18Recovery (Suspect Granularity): Failed to readsuspect granularity from master..sysattributes fordatabase % .*s'.


12739 10Recovery (Suspect Granularity): Warning - suspectgranularity defaulted to database level for database

%` .*s'.


12740 18Recovery (Suspect Granularity): Failed to readsuspect threshold from master..sysattributes fordatabase % .*s'. Assumimg default ( % ` d' pages).


1697



12741 10Recovery (Suspect Granularity): No transactionavailable to write to master..sysattributes table.



12742 17Recovery (Suspect Granularity): Warning: Memorynot available to store suspect information. Usingdefault suspect granularity (database).


12743 10Recovery (Suspect Granularity): Page/object suspectinformation has been deleted.


12744 10Recovery (Suspect Granularity): Bad suspectgranularity % ` d' for database % ` .*s'.This is aninternal error. Contact Sybase Technical Support.


12745 10Recovery (Suspect Granularity): Warning - Failedto read error list for database:'%.*s'. Continuingwith hard coded error list.


1698



12746 10Recovery (Suspect Granularity): Warning - suspectgranularity defaulted to page level. Object levelis disabled in this release.


12747 10Recovery (Suspect Granularity): Suspect pageencountered: database % ` .*s', page % ` ld', session(%ld, %d), log row ID (%ld, %d).


12748 10Recovery (Suspect Granularity): Suspect object indatabase % .*s', object % ` .*s', index % ` ld'.


12749 10Recovery (Suspect Granularity): Suspect pages arepresent in database % ` .*s'.


12750 10Recovery (Suspect Granularity): Warning - Page toobject translation failed.


12751 18Recovery (Suspect Granularity): Failed to insertsuspect informationrow into master..sysattributestable.


1699



12752 18Recovery (Suspect Granularity): Failed to writesuspect list to master..sysattributes table.



12753 18Recovery (Suspect Granularity): Failed to writesuspect attribute to master..sysattributes table.


12754 18Recovery (Suspect Granularity): Failed to readsuspect attribute from master..sysattributes table.


12755 18Recovery (Suspect Granularity): Failed to readsuspect list from master..sysattributes table.


12756 18Recovery (Suspect Granularity): Recovery abortedwhile reading master..sysattributes. Inform yourSystem Administrator.


12757 18Recovery (Suspect Granularity): Write of suspectinformation to master..sysattributes failed. Informyour System Administrator.



1700



12758 10Recovery (Suspect Granularity): Settings fordatabase '%.*s'- Suspect Granularity: '%.*s',Suspect Threshold: %d, Online Option: '%.*s'.


12759 10Recovery (Suspect Granularity): Database % ` .*s' -begin list of pre-recovery suspect pages.


12760 10Recovery (Suspect Granularity): Database % ` .*s' -end list of pre-recovery suspect pages.


12761 10Recovery (Suspect Granularity): Page '%ld' ofdatabase '%.*s' is removed from suspect page listbecause it was unallocated at end of recovery due topage/extent deallocation. This page is clean and noaction is required.


12762 10Recovery (Suspect Granularity): Recovery ofdatabase % .*s' found %d suspect pages belonging to%d suspect objects.


1701



12763 10Recovery (Suspect Granularity): Database % ` .*s' isclean.



12767 10Suspect data encountered: Database: % ` .*s',Object: % ld'


12768 10Suspect Granularity: (for Testing only) Simulatederror to create suspect pages. Objid: '%ld',Indid: '%ld', Errtype: '%d', Logtype: '%d',Pagetype: '%d', PageNo: '%ld', Simulation Type:'%.*s'.


12769 10Recovery (Suspect Granularity): The database '%.*s'will come online in read only mode due to suspectpages/objects. Use sp_dboption to turn off readonly mode.

Explanation: Check and resolve any problems with suspect pages andobjects before making the database available for use. For details, refer tothe discussion of Recovery Fault Isolation in the chapter Encyclopediaof Tasks.

12770 10Suspect index encountered: database '%.*s', object'%.*s', index '%ld'.

Explanation:

1702



12801 12The object % .*s' is not a partitioned table. UPDATEPARTITION STATISTICS can only be run on partitionedtables.




12803 16CREATE VIEW failed because column %d in the viewdefinition has a null column name. Column namescannot be null.


12804 18Unable to change the logversion from %d to %d ondatabase '%S_DBID'.

Explanation:

12805 18Unable to bring the master database online due tolack for space. Please re-start the previous ofthe server, add more space and then reboot the newversion of the server. Shutting down.

Explanation:

12806 18cannot replace a tuple in sysstatistics

Explanation:

12807 18cannot delete a tuple in sysstatistics

Explanation:

12808 18Cannot write table '%.*s' statistics

Explanation:

1703



12809 16Duplicate column listed in update statistics.Column name '%.*s' for table '%.*s' listed more thanonce

Explanation:

12810 16Cannot resolve column name '%.*s' for table '%.*s'.This could be because the column does not belongto the table or it has an unknown datatype or aninternal error related to the system catalogs hashappened

Explanation:

12811 16Column name '%.*s' for table '%.*s' is one of TEXT,IMAGE or BIT datatype. This type of column cannotbe used in update statistics.

Explanation:

12813 18Failed to start an internal transaction. This willprevent information for index '%.*s' on table '%.*s'from being written out to SYSTABSTATS.

Explanation:

12814 18Failed to write information in SYSTABSTATS.

Explanation:

12815 18Failed to obtain lock on SYSTABSTATS.

Explanation:

12816 18Failed to delete a row in SYSTABSTATS for table'%.*s', because the row could not be located.

Explanation:

12817 16This form of UPDATE STATISTICS on table '%.*s' doesnot support the CONSUMERS option. Please rerun itwithout this option.

Explanation:

1704



12901 16This command is not allowed on an offline database'%S_DBID'.

Explanation:

12902 16Mime page chain starting at page %d has %d parts init's header %d parts were found.


by message.

12903 16Mime page chain starting at page %d has %d bytes init's header %d bytes were found.


12904 16Cannot find object with ID '%d'. Check the objectID and retry the command.

Explanation:

12905 16Index %ld of object %ld corrupt; key values in childpage %ld inconsistent for parent page %ld. Drop andrecreate the index.

Explanation:

12906 16Index %ld of object %ld has wrong level %d for page%ld, parent %ld is at level %d

Explanation:

12907 16The total number of data and control pages in thistable is %ld.

Explanation:

12908 16Index %ld of object %ld has orphan leaf page %ld.Drop and recreate the index.

Explanation:

1705



12909 16Table with object id=%ld (name = %S_OBJID)inconsistent after Large Scale Allocation. Page %ldin extent %ld is found reserved.

Explanation:

12910 16Page %ld in extent %ld in Table with object id %ld(name = %S_OBJID) and index %ld is in the process ofbeing allocated. To verify if the page is indeedallocated, run TABLEALLOC with the FIX option whenthere are no active transactions.

Explanation:

12911 10The extended header bit is not set in page %ld ofobject '%.*s' (ID %d) in database '%.*s' (ID %d).

Explanation:

12912 10Incorrect offset entry(s) in the offset table ofrow %d in page %ld of object '%. *s' (ID %d) indatabase '%.*s' (ID %d).

Explanation:

12913 10Incorrect column type in the offset table of row %din page %ld of object '%.*s' (ID %d) in database'%.*s' (ID %d).

Explanation:

12914 16EXP_ROW_SIZE value of %d is invalid. It must bebetween %d and %d.

Explanation:

12915 16Invalid Cachelet ID %d. Valid Cachelet ID valuesare between %d and %d.

Explanation:

12916 16Fixed spacebits (on allocation page) for DOLdatapage %ld, with insfs %d and expected row length%d. Were expected to be 0x%x, but were found to be0x%x.

Explanation:

1706



12917 16Non-contiguous free space %d in page header of DOLdatapage %ld is incorrect. This value cannot benegative.

Explanation:

12919 10Verifying faults for '%.*s'.


12920 16The last completed DBCC CHECKSTORAGE forthis database has been processed. You mustperform another DBCC CHECKSTORAGE beforeyou can use CHECKVERIFY or CHECKREPAIR. Usesp_dbcc_summary_report to view the DBCC operationsperformed.

Explanation: Adaptive Server could not perform the requested action.A completed and unverified CHECKSTORAGE operation must exist

before CHECKVERIFY can execute.

12921 16A problem was encountered while accessing the faultsrecorded in the dbccdb database. Please check thedbcc_faults and dbcc_fault_params tables in thedbccdb database.


12922 16A problem was encountered while updating the faultstatus in the dbcc_faults table. Please check thedbcc_faults and dbcc_fault_params tables in thedbccdb database.


12923 10Failed to get an '%s' lock on table '%.*s'. Thefaults for this table will not be processed.

Explanation: dbcc checkstorage could not verify the faults for this tableand its indexes because it was unable to block updates to the table.


1707



12924 10DBCC CHECKVERIFY for database '%.*s' encountered anerror. Correct the reported problem reported andexecute the CHECKVERIFY command again.

Explanation: This is an informational message. Correct the problemindicated in the preceeding messages or in the errorlog beforere-executing the command. Contact your System Administrator forassistance.

12925 10DBCC CHECKVERIFY for database '%.*s' sequence%d completed at %s. %d suspect conditions wereresolved as faults, and %d suspect conditions wereresolved as harmless. %d objects could not bechecked.


12926 20DBCC CHECKVERIFY could not acquire a lock on thetarget database.


12927 10Performing QUICK repairs to database '%.*s'.


12928 10DBCC CHECKREPAIR with the QUICK_REPAIRS option doesnot accept an object name. The parameter '%.*s'will be ignored.

Explanation: This is an informational message. The optional objectparameter should not be used with this command option.

12929 10DBCC CHECKREPAIR for database '%.*s' sequence%d completed at %s. %d faults were repaired,and %d faults were resolved without repair. %dobjects could not be processed and %d faults remainunrepaired.


1708



12930 10DBCC CHECKREPAIR for database '%.*s' encountered anerror. Correct the problems reported and executethe CHECKREPAIR command again.

Explanation: This is an informational message. Correct the problemindicated in the preceeding messages or in the errorlog beforere-executing the command. Contact your System Administrator forassistance.

12931 10The total number of empty pages (with all deletedrows) in this table is %ld.

Explanation:

12932 10The total number of pages which could be garbagecollected to free up some space is %ld.

Explanation:

12933 10DBCC CHECKSTORAGE not supported in this release ofAdaptive Server Enterprise.

Explanation: This dbcc feature is not supported in your version ofAdaptive Server.

12934 16Page %ld of object %ld, indid %ld undergoing change.Some pages of indid %ld may not be checked, retrythe command later.

Explanation:

1709



13001 10data page


13002 10index page


13003 10leaf page


13004 10last



13005 10root


13006 10read from


13007 10send to


13008 10receive


13009 10send



1710



13010 10read


13011 10wait


13012 10A USE DATABASE statement



13013 10a procedure or trigger


13014 10A DISTINCT clause


13015 10a view


13016 10An INTO clause


13017 10An ORDER BY clause



13018 10A COMPUTE clause


1711



13019 10a SELECT INTO statement


13020 10option


13021 10offset option



13022 10statistics option


13023 10parameter option


13024 10built-in function name


13025 10field


13026 10parameter



13027 10convert specification


1712



13028 10index


13029 10table


13030 10database



13031 10procedure


13032 10trigger


13033 10view


13034 10default


13035 10rule



13036 10system


1713



13037 10unknown type


13038 10SET command


13039 10column



13040 10type


13041 10character string


13042 10integer


13043 10identifier


13044 10number



13045 10integer value


1714



13046 10floating point value


13047 10object


13048 10column heading



13049 10constraint


13050 10Non-ANSI text


13051 10ANSI text procesed in non-ANSI way


13052 10a non-ANSI data type usage


13053 10Non-standard datatype TIMESTAMP



13054 10Non-standard or user datatype:


1715



13055 10ON <segment>


13056 10Alternate column names in CREATE VIEW


13057 10UNION in INSERT ... SELECT



13058 10FOR BROWSE


13059 10HOLD LOCK in SELECT statement


13060 10transaction name


13061 10Use of TRANSACTION key word instead of WORK


13062 10FROM clause in an UPDATE statement



13063 10More than one table in a from clause for DELETEstatement


1716



13064 10Named columns in an ORDER BY included in a UNION


13065 10Comparison operator !=


13066 10Comparison operator !<



13067 10Comparison operator !>


13068 10left equi-join operator


13069 10right equi-join operator


13070 10bitwise operator |


13071 10bitwise operator &



13072 10bitwise operator ^


1717



13073 10bitwise operator ~


13074 10modulo operator %


13075 10temporary table usage



13076 10a statement with assigned variables in the selectlist


13077 10aborted


13078 10data


13079 10log


13080 10A SYB_RESTREE statement


13081 10A CREATE SCHEMA statement


1718



13082 10dynamic PREPARE statement


13083 10The untyped variable ?


13084 10in a WHERE or UPDATE SET clauses



13084 10in a WHERE clause or the SET clause of an UPDATEstatement or the VALUES list of an INSERT statement


13085 10Optional procedure number


13086 10Parameter declaration list


13087 10Procedure option


13088 10owner


13089 10object type


1719



13090 10Backup Server


13091 10dump header


13092 10dump trailer



13093 10deadlock


13094 10user interrupt


13095 10suspended


13096 10explicit


13097 10implicit



1720



13098 10A pseudo table


13099 16IDENTITY function


1721



13100 16recalculating sysindexes.minlen


13101 16WITH <option> [=] <value>


13102 10remote server


13103 10primary



13104 10secondary


13105 10updatable


13106 10not updatable


13108 10AT ISOLATION


13109 10because table scans cannot be restarted



1722



13110 10due to an internal error


13111 10initializing new column sysindexes.maxrowsperpage tozero


13112 10checking database references in sysreferences


13113 10modifying index syscomments.syscomments


13114 10recalculating sysindexes.maxlen


13115 10dropping index


13116 10creating table


13117 10creating index


13118 10noting the present database upgrade level


1723



13119 10adding column


13120 10changing column name


13123 10Initializing systimeranges



13124 10first

Explanation: This is an informational message or a message header. Noaction is required. (Not raised in 11.9.2)

13125 16forced index


13126 16forced parallel


13127 16forced lru/mru


13128 16forced prefetch



13134 10initializing new column sysusers.sname


1724



13135 10initializing new column sysalternates.sname


13136 10initializing the new column sysobjects.suid


13137 10initializing new column syscomments.hiddentext toNULL


13138 10initializing new column sysprocedures.version


13139 10setting status column


13139 10Setting the value for the column to 1 for allsystem-defined roles so that they will be enabled onlogin.


13144 10Checking database timestamps


13145 10Verifying page header information


1725



13200 10executing SQL statement


13201 10initializing partition IDs for each extent


13202 10initializing partition statistics for eachpartitioned table


13203 15Variable


13204 15Aggregate function


13205 15check constraint


13206 10changing name of system table


13207 10new name:

Explanation:

13208 10standby-mode log

Explanation:

13209 10Begin upgrade of distribution pages

Explanation:

1726



13210 10Initialize systabstats with valid statistics

Explanation: This is an informational message. No action required.

13211 10Checking indstatus2 in sysindexes and correcting itif required

Explanation:

13212 10Creating/Updating the last chance threshold forlogsegment.

Explanation:

13213 10cache

Explanation:

1727



18404 16Procedure text source for procedure object %1! (id= %2!) exists.


18405 16Procedure text source for procedure object %1! (id= %2!) does not exist.


18406 16Procedure text source for procedure object %1! (id= %2!) is hidden.


by message.

1728

Glossary

allocation pagesDatabase-wide pages Adaptive Server uses to maintain the information about how each

unit of 256 contiguous database pages is used.

bufferA 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 headeris 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 indexAn 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.”

error logThe 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 configurationguide for details.

The Backup Server has its own error log file where Backup Server error messages arewritten. Refer to “Backup Server Error Logging” in the System AdministrationGuide for details.

The SQL Monitor Server has its own error log file where SQL Monitor Server errormessages are written. Refer to the Monitor Server Supplement for your platformfor details.

The Replication Server has its own error log file where Replication Server error messagesare written. Refer to the Replication Server Administration Guide for details.

The Navigation Server has its own error log file where Navigation Server error messagesare written. Refer to the Navigation Server Reference Manual for details.

extent

1729


Every 256-page allocation unit is divided into 32 structures called extents, eachcontaining 8 contiguous pages. Each extent contains information about those 8contiguous pages, including a bitmap showing pages in use and a bitmap showingpages to be deallocated.

foreign keyIn a table, a column whose data values correspond to the values of a key column in

another table.

index IDThe number Adaptive Server uses to uniquely identify (within a database) an index. The

following table shows the index types:

Index ID Meaning

0 Actual table data

1 Clustered index

2-250 Nonclustered indexes

255 Text or image page

leaf levelThe bottom of a clustered or nonclustered index. In a clustered index, the leaf level

contains the actual data pages of the table.

logical pageThe unique address for pages in the context of each database.

MASSBuffers are grouped together to form Memory Address Space Segments (MASSes). A

buffer cache consists of MASSes linked in MRU/LRU (most recently used/leastrecently used) chains.

nonclustered indexAn 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 250allocation 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 dataand index pages on that allocation page.

1730


A maximum of 263 OAM pages are allowed, supporting a maximum of 65,535 allocationunits for an object.

object IDThe 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 than100 and user tables have an object ID that is 100 or greater.

primary keyThe 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 descriptorsThe data structures used to manage access to Adaptive Server objects. Session

descriptors exist in three forms: user session descriptors (including worktablesession descriptors), system session descriptors, and worktable session descriptors(separate from user session descriptors).

system tableOne 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 wholeand about each user database. The master database contains some system tables thatare not in user databases. The “Sybase Adaptive Server System Tables Diagram,”available through Sybase Customer Support, shows which system tables are inmaster only and which system tables are in all databases. For details about eachsystem table, refer to the Adaptive Server Reference Supplement.

transaction logA system table (syslogs) in which all changes to the database are recorded.

virtual pageActual offset on a device for a page within a database.

♦Note For a more complete set of definitions, see the glossary in the AdaptiveServer System Administration Guide.

1731


1732

volume 3: sybase adaptive server™ enterprise ...dis.unal.edu.co/~icasta/man_sybase/svrtsg3.pdf ·...

Documents