0% found this document useful (0 votes)

479 views1,138 pages

IQ Error Message

IQ Error message

Uploaded by

Mau Vu Huu

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

479 views1,138 pages

IQ Error Message

IQ Error message

Uploaded by

Mau Vu Huu

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

About this guide

® ®
The SAP Sybase IQ Error Messages Guide is an reference for SAP Sybase IQ errors and
warnings.

Organization
This guide references SAP Sybase Error Codes on page 1 and SQL Preprocessor Errors on
page 3. Messages are organized by error number and include all attributes associated with
the message.

Other sources of information

• For additional information about Sybase IQ, see the Sybase IQ documentation set.
• The Getting Started CD, included with your software, contains documentation in PDF
format. To read or print documents on the Getting Started CD, you need Adobe Acrobat
Reader, which you can download for free from the Adobe Reader download site.
• The SAP Sybase Product Documentation Web site is provides online access to all of the
books in the SAP Sybase IQ documentation set. The SAP Sybase Web site also includes
links to SAP Sybase Product Download Center, Platform Certifications, and the SAP
Sybase Developer Network. Create a personal profile on the MySybase page to simplify
your browsing.

If you need help

Each SAP Sybase installation with a valid support contract should have one or more
designated people authorized to contact SAP Sybase Technical Support. If you cannot resolve
a problem using the manuals or online help, please have that designated person contact SAP
Sybase Technical Support or the SAP Sybase subsidiary in your area.

Messages
Messages are grouped by range and include all attributes associated with the error or warning.
To find information about a message, choose the appropriate page.

Row Name Description

Error or Warning Error number and full text of the message.
Constant Unique string constant for each message.

SAP Sybase IQ Error Messages 1

About this guide

Row Name Description

SAP Sybase Error Number SAP Sybase error numbers are a set of error codes used by all SAP
Sybase products.
For every error code returned by SAP Sybase IQ, there is a pair of
matching SQLCODE and SQLSTATE codes. Some error codes are not
unique. Many of the errors contain the characters %1, %2 and so on.
These are replaced by the parameters to the error message.
SQL State SQLSTATE error codes are defined by the SQL/92 standard. Each
SQLSTATE value is a 5-character string containing a 2-character class
followed by a 3-character subclass.
Each character can be one of the uppercase letters A through Z or the
digits 0 through 9. A class that begins with A through H or 0 through 4
has been defined by the ANSI standard; other classes are implemen-
tation defined. Similarly, subclasses of standard classes that start with
the same characters (A-H, 0-4) are standard. The subclass 000 always
means that no subclass code is defined. The most common SQLSTATE
value is 00000, which indicates successful completion.
SQL Code SQLCODE is a numeric code associated with an exception. Negative
codes are considered errors; positive codes are warnings.
If a SQLCODE has both a negative and a positive value, the first
message listed is 'Warning nnn' (the positive SQLCODE), then 'Error
nnn' (the negative SQLCODE). The SQLCODE 0 indicates successful
completion.
ODBC 2 State ODBCSTATE 2 is set to OK or ERROR.
ODBC 3 State ODBCSTATE 3 is set to OK or ERROR.
Severity Codes Each numbered error message has an associated severity level that
indicates the seriousness of the problem.
Parameters Many error messages contain the characters %1, %2, and so on. These
characters are replaced by the parameters to the error message.
Probable Cause Probable Cause tells you what the problem is, and may suggest how to
fix it.

Severity Codes
Severity codes indicate the degree and source of the error.
Num- Description Num- Description
ber ber
0 Comment. 17 Insufficient resources.

2 SAP Sybase IQ
About this guide

Num- Description Num- Description

ber ber
1 Information. 18 Non-fatal internal error detected.
10 Status information; warning. 19 Fatal error in resource.
11 Specified database object not found. 20 Fatal error in current process.
12 Wrong data type encountered. 21 Fatal error in database processes.
13 User transaction syntax error. 22 Fatal error: table integrity suspect.
14 Insufficient permission to execute 23 Hardware error or system table cor-
command. ruption.
15 Syntax error in SQL statement. 24 Hardware error or system table cor-
ruption.
16 Miscellaneous user error (non-fatal).

SQL Preprocessor Errors

SQL preprocessor errors occur in the C preprocessor.
Embedded SQL is a database programming interface for the C and C++ programming
languages. Embedded SQL consists of SQL statements intermixed with (embedded in) C or
C++ source code. These SQL statements are translated by a SQL preprocessor into C or C++
source code, which then need to be recompiled by the user. The Sybase IQ SQL preprocessor
utility sqlpp translates the SQL statements in an input file sqc into C language source that is
put into an output file .c.
SQL preprocessor errors are grouped by range. To find information about a specific error or
warning, choose the appropriate page.

SAP Sybase IQ Error Messages 3

About this guide

4 SAP Sybase IQ
Errors and Warnings

Errors and Warnings

0 - 263

Messages 0 through 91
Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 0 No message

Constant NOERROR

SAP Sybase Error Number 2000

SQL State 00000

SQL Code 0L

ODBC 2 State 00000

ODBC 3 State 00000

Severity Code 10 on page 2

Probable Cause This code indicates that there was no error or warning.

Error 72 "No database file specified"

Constant NO_DATABASE_FILE

SAP Sybase Error Number 2021

SQL State 08W39

SQL Code -72L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Probable Cause The database server was started but there was no specified database
file. The server is stopped.

SAP Sybase IQ Error Messages 5

Errors and Warnings

Error 74 "The selected database is currently inactive"

Constant DATABASE_NOT_ACTIVE

SAP Sybase Error Number 2013

SQL State 08W30

SQL Code -74L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 14 on page 2

Probable Cause The selected database is in an inactive state. The database may be in
the process of being started or shut down.

Error 75 "Request to start/stop database denied"

Constant START_STOP_DATABASE_DENIED

SAP Sybase Error Number 2014

SQL State 08W29

SQL Code -75L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 14 on page 2

Probable Cause You do not have permission to start or stop a database. The required
permission is determined on the server command line.

Error 76 "Request denied -- no active databases"

Constant REQUEST_DENIED_NO_DATABASES

SAP Sybase Error Number 2015

SQL State 08W28

SQL Code -76L

ODBC 2 State 08004

ODBC 3 State 08004

6 SAP Sybase IQ
Errors and Warnings

Error 76 "Request denied -- no active databases"

Severity Code 14 on page 2

Probable Cause The server has denied your request as there are currently no running
databases.

Error 77 "Database name not unique"

Constant ALIAS_CLASH

SAP Sybase Error Number 2016

SQL State 08W27

SQL Code -77L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause The database cannot be started as its name conflicts with a previously
started database.

Error 78 "Dynamic memory exhausted"

Constant DYNAMIC_MEMORY_EXHAUSTED

SAP Sybase Error Number 2024

SQL State 08W26

SQL Code -78L

ODBC 2 State S1001

ODBC 3 State HY001

Severity Code 17 on page 2

Probable Cause A failure occurred when the database server was trying to allocate
dynamic memory.

Error 79 "Invalid local database option"

Constant INVALID_LOCAL_OPTION

SAP Sybase Error Number 2017

Severity Code 11 on page 2

Probable Cause The database file you specified is invalid. The database server is
stopped.

Error 85 "Communication error"

Constant COMMUNICATIONS_ERROR

SAP Sybase Error Number 2022

SQL State 08W12

SQL Code -85L

ODBC 2 State 08S01

ODBC 3 State 08S01

Severity Code 21 on page 2

Probable Cause There is a communication problem between the application and the
server.

Error 86 "Not enough memory to start"

Constant NO_MEMORY

SAP Sybase Error Number 2025

10 SAP Sybase IQ
Errors and Warnings

Error 86 "Not enough memory to start"

SQL State 08W13

SQL Code -86L

ODBC 2 State S1001

ODBC 3 State HY001

Severity Code 17 on page 2

Probable Cause The database server started, but stopped because there was not
enough memory.

Error 87 "Database name required to start server"

Constant DATABASE_NAME_REQUIRED

SAP Sybase Error Number 2026

SQL State 08W14

SQL Code -87L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 17 on page 2

Probable Cause You did not supply a database name. A database name is required to
start a database server.

Error 88 "Client/server communications protocol version

mismatch"

Constant PROTOCOL_MISMATCH

SAP Sybase Error Number 2027

SQL State 08W15

SQL Code -88L

ODBC 2 State 08S01

ODBC 3 State 08S01

Severity Code 21 on page 2

SAP Sybase IQ Error Messages 11

Errors and Warnings

Error 88 "Client/server communications protocol version

mismatch"

Probable Cause The connection failed because the protocol versions of the client and
the server do not match. Ensure the client and server software are the
same version.

Error 89 "Database server not running in multi-user mode"

Constant ENGINE_NOT_MULTIUSER

SAP Sybase Error Number 2029

SQL State 08W16

SQL Code -89L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 17 on page 2

Probable Cause The database server was started for bulk loading (the -b option) and
cannot be used as a network server. Stop the database server, and start
again without -b.

Error 90 "Argument %1 of procedure '%2' cannot be NULL"

Constant ARGUMENT_CANNOT_BE_NULL

SAP Sybase Error Num- 2267

ber

SQL State WP000

SQL Code -90L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The argument number that cannot be NULL.

Parameter 2 The name of the procedure that cannot receive the NULL parameter.

Probable Cause You passed a NULL value to a procedure expecting a scalar argument.
For example, a Java procedure that has an 'int' argument cannot receive
a NULL value.

12 SAP Sybase IQ
Errors and Warnings

Error 91 "Procedure '%1' terminated with unhandled exception

'%2'"

Constant UNHANDLED_EXTENV_EXCEPTION

SAP Sybase Error Number 2268

SQL State WP001

SQL Code -91L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the procedure that returned the unhandled exception.

Parameter 2 The fully qualified Java class name of the unhandled exception.

Probable Cause A Java procedure terminated with an active exception, and this ex-
ception is reflected in SQL as an error status.

Messages 92 through 105

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 92 "'%1' is not a valid class file"

Constant BAD_CLASS_FILE

SAP Sybase Error Number 2269

SQL State WP002

SQL Code -92L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the invalid file.

Probable Cause A file passed to the INSTALL JAVA statement was not a valid Java
class file.

SAP Sybase IQ Error Messages 13

Errors and Warnings

Error 93 "Class '%1' has no public field '%2'"

Constant FIELD_NOT_FOUND

SAP Sybase Error Number 2273

SQL State WW013

SQL Code -93L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the class in which the named field could not be found.

Parameter 2 The name of the field that could not be found.

Probable Cause An expression referenced a field that either does not exist or is not
public.

Error 94 "Invalid type for field reference"

Constant INVALID_FIELD_REFERENCE

SAP Sybase Error Number 2274

SQL State WW014

SQL Code -94L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An expression attempted to reference a field or a method of a non-Java

value. Field references via . and >> are only valid when applied
to Java objects.

Error 95 "Parse error: %1"

Constant INVALID_PARSE_PARAMETER

SAP Sybase Error Number 2380

SQL State 08W49

SQL Code -95L

14 SAP Sybase IQ
Errors and Warnings

Error 95 "Parse error: %1"

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 18 on page 2

Parameter 1 Description of the parsing error.

Probable Cause An error occurred while parsing a connection string.

Error 96 "Database server already running"

Constant ENGINE_ALREADY_RUNNING

SAP Sybase Error Number 2028

SQL State 08W23

SQL Code -96L

ODBC 2 State S1000

ODBC 3 State HY000

Severity Code 18 on page 2

Probable Cause The database server was not able to start because a server with the
same name was already running.

Error 97 "Database page size too big: %1"

Constant PAGE_SIZE_TOO_BIG

SAP Sybase Error Num- 2031

ber

SQL State 08W22

SQL Code -97L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 14 on page 2

Parameter 1 Database name.

SAP Sybase IQ Error Messages 15

Errors and Warnings

Error 97 "Database page size too big: %1"

Probable Cause You attempted to start a database with a page size that exceeds the
maximum page size of the running server. Either restart the server and
include this database name on the command line, or restart the server
with the required page size.

Error 98 "Authentication violation"

Constant AUTHENTICATION_VIOLATION

SAP Sybase Error Number 2034

SQL State 08W21

SQL Code -98L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause You attempted to connect to a server that has been authenticated for
exclusive use with a specific application.

Error 99 "Connections to database have been disabled"

Constant CONNECTIONS_DISABLED

SAP Sybase Error Number 2035

SQL State 08W04

SQL Code -99L

ODBC 2 State 08005

ODBC 3 State 08005

Severity Code 16 on page 2

Probable Cause Connections to the network database server have been disabled. You
will receive this error until connections have been enabled.

Warning 100 "Row not found"

Constant NOTFOUND

SAP Sybase Error Number 2001

16 SAP Sybase IQ
Errors and Warnings

Warning 100 "Row not found"

SQL State 02000

SQL Code 100L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Probable Cause You positioned a cursor beyond the beginning or past the end of the
query. There is no row at that position.

Error 100 "Database server not found"

Constant ENGINE_NOT_RUNNING

SAP Sybase Error Number 2036

SQL State 08W01

SQL Code -100L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause The database server is not running, or is in the process of starting up or
shutting down, or the interface library is unable to find it.

Warning 101 "Value truncated"

Constant TRUNCATED

SAP Sybase Error Number 2002

SQL State 01004

SQL Code 101L

ODBC 2 State 01004

ODBC 3 State 01004

Severity Code 10 on page 2

Probable Cause You may have fetched data into a host variable or SQLDA variable not
large enough to receive the value.

SAP Sybase IQ Error Messages 17

Errors and Warnings

Error 101 "Not connected to a database"

Constant NOT_CONNECTED

SAP Sybase Error Number 2037

SQL State 08003

SQL Code -101L

ODBC 2 State 08003

ODBC 3 State 08003

Severity Code 16 on page 2

Probable Cause You are not connected to a database, or you executed the DISCON-
NECT statement and have not connected to a database again.

Warning 102 "Using temporary table"

Constant TEMPORARY_TABLE

SAP Sybase Error Number 2003

SQL State 01W02

SQL Code 102L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Probable Cause A temporary table has been created to satisfy the query. This warning
can only occur on an OPEN statement.

Error 102 "Database server connection limit exceeded"

Constant TOO_MANY_CONNECTIONS

SAP Sybase Error 2038

Number

SQL State 08W03

SQL Code -102L

ODBC 2 State 08004

ODBC 3 State 08004

18 SAP Sybase IQ
Errors and Warnings

Error 102 "Database server connection limit exceeded"

Severity Code 21 on page 2

Probable Cause You exceeded the number of computers allowed to connect to the server. If
you are running the network database server, the limit is specified in your
license agreement. The server may be running low on cache, and as a result it
cannot accept any more database connections. The personal database server
is restricted to 10 connections.

Warning 103 "Invalid data conversion"

Constant CANNOT_CONVERT

SAP Sybase Error Number 2004

SQL State 01W03

SQL Code 103L

ODBC 2 State 01S01

ODBC 3 State 01S01

Severity Code 10 on page 2

Probable Cause The database could not convert a value to the required type. The value
being converted was either supplied to the database on an insert,
update, or as a host bind variable, or was a value retrieved from the
database into a host variable or SQLDA.

Error 103 "Invalid user ID or password"

Constant INVALID_LOGON

SAP Sybase Error Number 2039

SQL State 28000

SQL Code -103L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 14 on page 2

Probable Cause You supplied an invalid user ID or an incorrect password.

SAP Sybase IQ Error Messages 19

Errors and Warnings

Warning 104 "Row has been updated since last time read"

Constant ROW_UPDATED_WARNING

SAP Sybase Error 2005

Number

SQL State 01W04

SQL Code 104L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause You fetched a row from a SCROLL cursor. The row was previously fetched
from the same cursor, and one or more columns in the row has been updated
since the previous fetch. The column(s) updated may or may not be fetched
by the cursor; this warning just indicates that the row from the table has
been updated. If the cursor involves more than one table, a row from one or
more of the tables has been updated.

Error 104 "Invalid user ID or password on preprocessed module"

Constant INVALID_MODULE_LOGON

SAP Sybase Error Number 2041

SQL State 28W01

SQL Code -104L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 14 on page 2

Probable Cause You specified an invalid user ID or password when a module was
preprocessed.

Warning 105 "Procedure has completed"

Constant PROCEDURE_COMPLETE

SAP Sybase Error Number 2006

SQL State 01W05

20 SAP Sybase IQ
Errors and Warnings

Warning 105 "Procedure has completed"

SQL Code 105L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause There are no more result sets available for this procedure. An OPEN
or a RESUME statement may have caused the procedure to execute to
completion.

Error 105 "Database cannot be started -- %1"

Constant UNABLE_TO_CONNECT

SAP Sybase Error Number 2042

SQL State 08001

SQL Code -105L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Reason that database cannot be started.

Probable Cause The specified database cannot be started. Either it does not exist, it is
not a database, it is corrupt, or it is an older, unsupported format.

Messages 106 through 116

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 106 "Value for column '%1' in table '%2' has changed"

Constant COLUMN_VALUE_CHANGED

SAP Sybase Error Number 2007

SQL State 01W06

SQL Code 106L

ODBC 2 State OK

SAP Sybase IQ Error Messages 21

Errors and Warnings

Warning 106 "Value for column '%1' in table '%2' has changed"

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Name of the column whose value has changed.

Parameter 2 Name of the table containing the column.

Probable Cause A replicated UPDATE has found a value in an updated column that
does not match the value when the original UPDATE was made.

Error 106 "Cannot open transaction log file -- %1"

Constant CANNOT_OPEN_LOG

SAP Sybase Error 2043

Number

SQL State 08W05

SQL Code -106L

ODBC 2 State 08003

ODBC 3 State 08003

Severity Code 16 on page 2

Parameter 1 Reason why the transaction log file cannot be opened.

Probable Cause The database server was unable to open the named transaction log file.
The transaction log file name may include an invalid device or directory. If
this is the case, you can use the Transaction Log utility (dblog) to find out
where the transaction log should be and perhaps change it.

Error 107 "Error writing to transaction log file"

Constant ERROR_WRITING_LOG

SAP Sybase Error Number 2044

SQL State 08W17

SQL Code -107L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 17 on page 2

22 SAP Sybase IQ
Errors and Warnings

Error 107 "Error writing to transaction log file"

Probable Cause The database server got an I/O error writing the transaction log file.
The disk may be full or the log file name could be invalid.

Warning 107 "Language extension detected in syntax near '%1' on line

%2"

Constant SYNTAX_EXTENSION_WARNING

SAP Sybase Error Number 2238

SQL State 01W07

SQL Code 107L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 The word or symbol where the syntax has been detected.

Parameter 2 Line number.

Probable Cause The statement you are executing contains syntax that is not allowed
with the current setting of the option SQL_FLAGGER_WARN-
ING_LEVEL. Modify the offending statement or set the
SQL_FLAGGER_WARNING_LEVEL option to a different value.

Error 108 "Connection not found"

Constant CONNECTION_NOT_FOUND

SAP Sybase Error Number 2045

SQL State 08W02

SQL Code -108L

ODBC 2 State 08003

ODBC 3 State 08003

Severity Code 16 on page 2

Probable Cause The specified connection name on a DISCONNECT or SET CON-

NECTION statement is invalid.

SAP Sybase IQ Error Messages 23

Errors and Warnings

Error 109 "There are still active database connections"

Constant STILL_ACTIVE_CONNECTIONS

SAP Sybase Error Number 2046

SQL State 08W06

SQL Code -109L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to shut down a database that still has active connec-
tions.

Warning 109 "Null value eliminated in aggregate function"

Constant NULL_VALUE_ELIMINATED

SAP Sybase Error Number 2241

SQL State 01003

SQL Code 109L

ODBC 2 State 01000

ODBC 3 State 01003

Severity Code 10 on page 2

Probable Cause The expression argument of the aggregate function evaluated to

NULL for one or more rows.

Error 110 "Item '%1' already exists"

Constant NAME_NOT_UNIQUE

SAP Sybase Error Number 2047

SQL State 52010

SQL Code -110L

ODBC 2 State S0001

ODBC 3 State 42S01

24 SAP Sybase IQ
Errors and Warnings

Error 110 "Item '%1' already exists"

Severity Code 16 on page 2

Parameter 1 Name of the item that already exists.

Probable Cause You attempted to create a file, table, view, column, constraint, foreign
key, or publication with the same name as an existing one.

Warning 110 "Transaction log backup page only partially full"

Constant BACKUP_PAGE_INCOMPLETE

SAP Sybase Error Number 2249

SQL State 01W10

SQL Code 110L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause A DB_LOG_BACKUP_READ_WAIT was issued against the trans-

action log and the page returned was not full. The application should
reissue the request for the same page.

Warning 111 "Statement cannot be executed"

Constant CANNOT_EXECUTE_STMT

SAP Sybase Error Num- 2008

ber

SQL State 01W08

SQL Code 111L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause You specified a SQL statement for the PREPARE...WITH EXECUTE
statement that cannot be executed. If you specified an output SQLDA, it
may contain a DESCRIBE of the prepared statement. It is normal for
this warning to appear in the request log during the successful execution
of a statement.

SAP Sybase IQ Error Messages 25

Errors and Warnings

Error 111 "Index name '%1' not unique"

Constant INDEX_NAME_NOT_UNIQUE

SAP Sybase Error Number 2048

SQL State 52W04

SQL Code -111L

ODBC 2 State S0011

ODBC 3 State 42S11

Severity Code 16 on page 2

Parameter 1 Name of the invalid index.

Probable Cause You attempted to create an index with the same name as an existing
index.

Error 112 "Table already has a primary key"

Constant EXISTING_PRIMARY_KEY

SAP Sybase Error Number 2049

SQL State 55013

SQL Code -112L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to add a primary key on a table that already has a
primary key defined. You must delete the current primary key before
adding a new one.

Warning 112 "More information required"

Constant MORE_INFO

SAP Sybase Error Number 2252

SQL State 01W09

SQL Code 112L

ODBC 2 State 37000

26 SAP Sybase IQ
Errors and Warnings

Warning 112 "More information required"

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause More information is required to complete the request. This is used
internally in the database interface library to process a unified login. It
should not be returned to an application.

Error 113 "Column '%1' in foreign key has a different definition than
primary key"

Constant INVALID_FOREIGN_KEY_DEF

SAP Sybase Error Number 2050

SQL State 53030

SQL Code -113L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the problematic column.

Probable Cause The data type of the column in the foreign key is not the same as the
data type of the column in the primary key. Change the definition of
one of the columns using ALTER TABLE.

Warning 113 "Database option '%1' for user '%2' has an invalid setting"

Constant INVALID_OPTION_ON_CONNECT

SAP Sybase Error Number 2255

SQL State 01W11

SQL Code 113L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 Name of the database option that has the invalid value.

Parameter 2 Name of the user attempting to connect.

SAP Sybase IQ Error Messages 27

Errors and Warnings

Warning 113 "Database option '%1' for user '%2' has an invalid setting"

Probable Cause Upon processing a connection request for a specific user, the server
processed a database option that has an invalid setting. The server will
use the default option value.

Error 114 "Number of columns defined for the view does not match
SELECT statement"

Constant VIEW_DEFINITION_ERROR

SAP Sybase Error Number 2051

SQL State 53011

SQL Code -114L

ODBC 2 State 21S02

ODBC 3 State 21S02

Severity Code 20 on page 2

Probable Cause You attempted to create a view, but the column list specified as part of
the CREATE VIEW statement does not correspond to the list of items
in the view's SELECT statement.

Warning 114 "Character set conversion to '%1' cannot be performed; '%2'

is used instead"

Constant CANNOT_PERFORM_CHAR_TRANSLATION

SAP Sybase Error Num- 2350

ber

SQL State 01W12

SQL Code 114L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 Name of character set the application requested.

Parameter 2 Name of character set the database will be using.

28 SAP Sybase IQ
Errors and Warnings

Warning 114 "Character set conversion to '%1' cannot be performed; '%2'

is used instead"

Probable Cause The server is unable to perform a character conversion from the char-
acter set the database is using to the character set the application re-
quested.

Warning 115 "Database server cannot convert data from/to character set
'%1', conversion may not be correct"

Constant UNSUPPORTED_CHARACTER_SET_WARNING

SAP Sybase Error Num- 2360

ber

SQL State 01W13

SQL Code 115L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 Name of the requested character set.

Probable Cause The database server cannot convert character data from/to the character
set requested by the application because the character set is not suppor-
ted. The connection succeeds, but character conversion may not be cor-
rect for all characters.

Error 116 "Table must be empty"

Constant TABLE_MUST_BE_EMPTY

SAP Sybase Error Number 2053

SQL State 55W02

SQL Code -116L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to modify a table, and the database server can only
perform the change if there are no rows in the table.

SAP Sybase IQ Error Messages 29

Errors and Warnings

Warning 116 "Language '%1' is not supported, '%2' will be used"

Constant UNSUPPORTED_LANGUAGE

SAP Sybase Error Number 2375

SQL State 01W14

SQL Code 116L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 Name of the language that was requested by the client.

Parameter 2 Name of the language that the server will use to send message strings.

Probable Cause The language that the application requested is not supported by the
server to which the application is connecting. Instead, the server will
send message strings in the language stated.

Messages 117 through 128

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 117 "Unsupported character set '%1' and unsupported language

'%2'; language used is '%3' instead"

Constant UNSUPPORTED_CHARSET_AND_LANGUAGE

SAP Sybase Error Num- 2376

ber

SQL State 01W15

SQL Code 117L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 Name of the character set that could not be supported.

Parameter 2 Name of the language that could not be supported.

Parameter 3 Name of the language that the server will use to send language strings.

30 SAP Sybase IQ
Errors and Warnings

Warning 117 "Unsupported character set '%1' and unsupported language

'%2'; language used is '%3' instead"

Probable Cause The character set that the application requested is not supported by the
server to which the application is connecting. The language that the
application requested is not supported either. Language strings will be
sent in the language specified.

Error 118 "Table '%1' has no primary key"

Constant NO_PRIMARY_KEY

SAP Sybase Error 2055

Number

SQL State 55008

SQL Code -118L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the table that does not have a primary key.

Probable Cause You attempted an operation that required the referenced table to have a
primary key. Examples of these operations include adding a foreign key,
or using the ON EXISTING clause of an INSERT statement, while re-
ferring to a table that does not have a primary key. You must add a primary
key to the referenced table.

Warning 118 "Illegal user selectivity estimate specified"

Constant INVALID_USER_ESTIMATE

SAP Sybase Error Number 2381

SQL State 01W16

SQL Code 118L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

SAP Sybase IQ Error Messages 31

Errors and Warnings

Warning 118 "Illegal user selectivity estimate specified"

Probable Cause You specified a user selectivity estimate that is either not a literal
constant or is outside the range 0.0 to 100.0 (estimates are specified as
percentages). The estimate has been ignored.

Error 119 "Primary key column '%1' already defined"

Constant PRIMARY_KEY_COLUMN_DEFINED

SAP Sybase Error Number 2056

SQL State 52009

SQL Code -119L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the column that is already in the primary key.

Probable Cause You listed the same column name twice in the definition of a primary
key.

Warning 119 "Unable to open backup log '%1'"

Constant UNABLE_TO_OPEN_BACKUP_LOG

SAP Sybase Error Num- 2412

ber

SQL State WB011

SQL Code 119L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Backup log file name.

Probable Cause The server was unable to open the backup log to record the execution of a
BACKUP or RESTORE statement. Check the settings of the environ-
ment variables used to locate the backup log file. The directory to con-
tain the log must already exist.

32 SAP Sybase IQ
Errors and Warnings

Error 120 "User '%1' already has GRANT permission"

Constant ALREADY_HAS_GRANT_PERMS

SAP Sybase Error Number 2065

SQL State 42W01

SQL Code -120L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the user that already has GRANT permission.

Probable Cause You attempted to give GRANT OPTION permission to a user that
already has it.

Warning 120 "'%1' is an unknown option"

Constant UNKNOWN_OPTION

SAP Sybase Error Number 2384

SQL State 01W17

SQL Code 120L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 The option that is unknown to the server.

Probable Cause You attempted to set the value of an option that is not known to the
server.

Error 121 "Permission denied: %1"

Constant PERMISSION_DENIED

SAP Sybase Error Number 2066

SQL State 42501

SQL Code -121L

SAP Sybase IQ Error Messages 33

Errors and Warnings

Error 121 "Permission denied: %1"

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Description of the type of permission required.

Probable Cause You do not have the required permission to perform the specified
action. The message specifies the actual permission required and the
object being acted upon.

Warning 121 "Cursor option values changed"

Constant CURSOR_OPTIONS_CHANGED

SAP Sybase Error Number 2500

SQL State 01S02

SQL Code 121L

ODBC 2 State 01S02

ODBC 3 State 01S02

Severity Code 10 on page 2

Probable Cause The database server could not support the requested cursor option
values for the associated query. Similar option settings were substi-
tuted.

Error 122 "Operation would cause a group cycle"

Constant GROUP_CYCLE

SAP Sybase Error Number 2067

SQL State 42W02

SQL Code -122L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to add a member to group that would result in a mem-
ber belonging to itself. The membership may be direct or indirect.

34 SAP Sybase IQ
Errors and Warnings

Warning 122 "The result returned is non-deterministic"

Constant NONDETERMINISTIC_RESULT

SAP Sybase Error Num- 2529

ber

SQL State 01W18

SQL Code 122L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Probable Cause FIRST or TOP n are used in a SELECT statement to limit the size of a
result. The statement must also have an ORDER BY if the result is to be
well-defined. If it does not have an ORDER BY, then the server is free to
return any subset of the result that has the requested number of rows.

Error 123 "User '%1' is not a user group"

Constant NOT_A_GROUP

SAP Sybase Error Number 2068

SQL State 42W03

SQL Code -123L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of user you thought was a group.

Probable Cause You attempted to add a member to group, but the user ID specified as a
group has not been granted GROUP permission.

Warning 124 "Invalid data conversion: NULL was inserted for column '%1'
on row %2"

Constant CANNOT_CONVERT_LOAD_TABLE

SAP Sybase Error Num- 2532

ber

SAP Sybase IQ Error Messages 35

Errors and Warnings

Warning 124 "Invalid data conversion: NULL was inserted for column '%1'
on row %2"

SQL State 01W01

SQL Code 124L

ODBC 2 State 07006

ODBC 3 State 07006

Severity Code 10 on page 2

Parameter 1 Name of the column where NULL was inserted.

Parameter 2 Row number in the data file where the invalid data conversion took
place.

Probable Cause The database could not convert a value to the required type. The value
being converted was supplied to the database in a data file and inserted
using LOAD TABLE. A NULL value has been inserted into the column.

Error 124 "Dropping all columns from table '%1' is not allowed"

Constant TOO_MANY_COLUMNS_DELETED

SAP Sybase Error Num- 2253

ber

SQL State 42W44

SQL Code -124L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the table from which the columns could not be dropped.

Probable Cause The number of columns in a table can never fall below one. Your
ALTER TABLE has more drop/delete column clauses than the current
number of columns in the table.

Error 125 "ALTER clause conflict"

Constant ALTER_CLAUSE_CONFLICT

SAP Sybase Error Number 2057

36 SAP Sybase IQ
Errors and Warnings

Error 125 "ALTER clause conflict"

SQL State 53W01

SQL Code -125L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause A primary key clause, foreign key clause, or a uniqueness clause must
be the only clause of an ALTER TABLE statement.

Warning 125 "An invalid multi-byte input character was encountered when
converting from %1 to %2"

Constant ILLEGAL_MULTIBYTE_WARNING

SAP Sybase Error Num- 2538

ber

SQL State 01WC1

SQL Code 125L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 The character set of the input string.

Parameter 2 The character set of the output string.

Probable Cause While the server was performing character set conversion on an input
string, an invalid multi-byte character was encountered. The illegal
character was directly copied without conversion. Data following the
illegal character may be misinterpreted. See on_charset_conver-
sion_failure option.

Error 126 "Table cannot have two primary keys"

Constant PRIMARY_KEY_TWICE

SAP Sybase Error Number 2058

SQL State 52W05

SAP Sybase IQ Error Messages 37

Errors and Warnings

Error 126 "Table cannot have two primary keys"

SQL Code -126L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You specified the primary key twice in a CREATE TABLE statement.

Error 127 "Cannot alter a column in an index"

Constant COLUMN_IN_INDEX

SAP Sybase Error 2059

Number

SQL State 53W05

SQL Code -127L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You may have attempted to delete or modify the definition of a column
that is part of a primary or foreign key. You may have attempted to delete a
column that has an index on it. In this case, DROP the index or key,
perform the ALTER statement, and then add the index or key again.

Warning 127 "Character substitution occurred when converting from

%1 to %2"

Constant SIMPLE_SUBSTITUTION_WARNING

SAP Sybase Error Number 2542

SQL State 01WC3

SQL Code 127L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 The character set of the input string.

38 SAP Sybase IQ
Errors and Warnings

Warning 127 "Character substitution occurred when converting from

%1 to %2"

Parameter 2 The character set of the output string.

Probable Cause While the server was performing character set conversion on an input
string, some characters could not be represented in the database
character set. Those characters were substituted. See on_char-
set_conversion_failure option.

Error 128 "Cannot drop a user that owns tables in runtime system"

Constant USER_OWNS_TABLES

SAP Sybase Error Num- 2060

ber

SQL State 55W03

SQL Code -128L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that owns tables while running the run-
time server. This operation would result in dropping tables. The run-
time server cannot drop tables. Use the full server.

Messages 129 through 140

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 129 "Plan may contain virtual indexes"

Constant USING_VIRTUAL_INDEXES

SAP Sybase Error Number 2549

SQL State 01W20

SQL Code 129L

ODBC 2 State 01S01

ODBC 3 State 01S01

Severity Code 10 on page 2

SAP Sybase IQ Error Messages 39

Errors and Warnings

Warning 129 "Plan may contain virtual indexes"

Probable Cause Virtual indexes are currently enabled in this connection. Any plans
that are generated may contain virtual indexes.

Warning 130 "A row was dropped because it could not be converted to the
new schema format"

Constant ROW_DROPPED_DURING_SCHEMA_UPGRADE

SAP Sybase Error Num- 2559

ber

SQL State 01W21

SQL Code 130L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause A row that was valid in the old schema is no longer valid. This could be
because a column domain changed and the old value cannot be cast to
the new domain. Rows are also dropped if a uniqueness or foreign key
constraint cannot be satisfied.

Error 130 "Invalid statement"

Constant INVALID_STATEMENT

SAP Sybase Error Number 2070

SQL State 07W02

SQL Code -130L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The prepared statement is invalid. In embedded SQL, an OPEN or

EXECUTE failed.

Error 131 "Syntax error near '%1' %2"

Constant SYNTAX_ERROR

40 SAP Sybase IQ
Errors and Warnings

Error 131 "Syntax error near '%1' %2"

SAP Sybase Error Number 2071

SQL State 42W04

SQL Code -131L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 The word or symbol where the syntax error has been detected.

Parameter 2 Line number.

Probable Cause The database server cannot understand the statement you are trying to
execute. If you used a keyword (such as DATE) for a column name, try
enclosing the keyword in quotation marks ("DATE").

Error 132 "SQL statement error"

Constant STATEMENT_ERROR

SAP Sybase Error Number 2073

SQL State 26501

SQL Code -132L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The prepared statement identifier is invalid. In embedded SQL, an

OPEN or EXECUTE failed.

Warning 132 "Cannot output the histogram for string column '%1'"

Constant CANNOT_DUMP_STRING_HISTOGRAM

SAP Sybase Error 2562

Number

SQL State 01W23

SQL Code 132L

SAP Sybase IQ Error Messages 41

Errors and Warnings

Warning 132 "Cannot output the histogram for string column '%1'"

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Name of the column containing string data.

Probable Cause You tried to get the histogram for a column containing strings. Histograms
on string information cannot be output in a readable format; as a result, no
information was retrieved. Consider using the ESTIMATE function to get
information on a specific value or range in the column.

Error 133 "Invalid prepared statement type"

Constant INVALID_STATEMENT_TYPE

SAP Sybase Error Number 2074

SQL State 07W03

SQL Code -133L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause This is an internal error. If it can be reproduced, it should be reported

to iAnywhere.

Warning 133 "UltraLite connection was restored"

Constant CONNECTION_RESTORED

SAP Sybase Error Number 2635

SQL State WW040

SQL Code 133L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause The connection attempt completed successfully and the transaction
was restored from a suspended state.

42 SAP Sybase IQ
Errors and Warnings

Error 134 "Feature '%1' not implemented"

Constant NOT_IMPLEMENTED

SAP Sybase Error 2075

Number

SQL State 0A000

SQL Code -134L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The unimplemented feature.

Probable Cause You attempted to carry out an operation or use a feature that is not imple-
mented in this version of SQL Anywhere. In UltraLite, this error often
occurs because you attempted to perform an unsupported operation on a
LONG VARCHAR or LONG BINARY column. For example, the SUB-
STRING function cannot be used with a LONG VARCHAR column. As
well, an index cannot be created on a LONG column.

Warning 134 "UltraLite cursor (or result set or table) was restored"

Constant CURSOR_RESTORED

SAP Sybase Error Number 2636

SQL State WW041

SQL Code 134L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause The cursor (or result set or table) was opened successfully and the
cursor position was restored from the suspended state.

Error 135 "Language extension"

Constant LANGUAGE_EXTENSION

SAP Sybase Error Number 2077

SAP Sybase IQ Error Messages 43

Errors and Warnings

Error 135 "Language extension"

SQL State 0AW01

SQL Code -135L

ODBC 2 State 37000

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You used a SQL statement that may be valid in some versions of SQL,
but not in SQL Anywhere.

Error 136 "Table '%1' is in an outer join cycle"

Constant OUTER_JOIN_CYCLE

SAP Sybase Error Number 2088

SQL State 52W14

SQL Code -136L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of a table in the cycle.

Probable Cause You specified outer joins that create a cycle of tables.

Warning 136 "The database was created"

Constant DATABASE_CREATED

SAP Sybase Error Number 2666

SQL State WW061

SQL Code 136L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

44 SAP Sybase IQ
Errors and Warnings

Warning 136 "The database was created"

Probable Cause The specified UltraLite database was created using the specified
schema when the connection was opened.

Error 137 "Table '%1' requires a unique correlation name"

Constant CORRELATION_NAME_NEEDED

SAP Sybase Error Number 2090

SQL State 52W15

SQL Code -137L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the table that needs a unique correlation name.

Probable Cause You specified a join that joins a table to itself. You need to use unique
correlation names to have multiple instances of a table.

Warning 137 "Row was dropped from table %1 to maintain referential

integrity"

Constant ROW_DELETED_TO_MAINTAIN_REFERENTIAL_INTEGRI-
TY

SAP Sybase Error Number 2690

SQL State 01W24

SQL Code 137L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the table.

Probable Cause A delete of a primary row during a download forced its foreign row(s)
to also be deleted to maintain referential integrity.

SAP Sybase IQ Error Messages 45

Errors and Warnings

Error 138 "Dbspace '%1' not found"

Constant DBSPACE_NOT_FOUND

SAP Sybase Error Number 2078

SQL State 52W13

SQL Code -138L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 Name of the dbspace that could not be found.

Probable Cause You tried to access a dbspace that the database server could not find.

Warning 138 "Publication predicates were not evaluated"

Constant PUBLICATION_PREDICATE_IGNORED

SAP Sybase Error Number 2761

SQL State 01W25

SQL Code 138L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause Publication predicates were not evaluated because UltraLite was in-
itialized without SQL support. The table will be uploaded as if no
publication predicate was specified for the table.

Error 139 "More than one table is identified as '%1'"

Constant CORRELATION_NAME_AMBIGUOUS

SAP Sybase Error Number 2079

SQL State 52012

SQL Code -139L

ODBC 2 State 37000

46 SAP Sybase IQ
Errors and Warnings

Error 139 "More than one table is identified as '%1'"

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Ambiguous correlation name.

Probable Cause You identified two tables in the same FROM clause with the same
correlation name.

Warning 139 "Option '%1' specified more than once"

Constant DUPLICATE_OPTION

SAP Sybase Error Number 2770

SQL State 01W26

SQL Code 139L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the duplicated option.

Probable Cause A particular option has been specified multiple times. Only the last
instance of the option is used; the previous ones are ignored.

Error 140 "User ID '%1' does not exist"

Constant UNKNOWN_USERID

SAP Sybase Error Number 2080

SQL State 08004

SQL Code -140L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 11 on page 2

Parameter 1 Name of the user that could not be found.

Probable Cause You used a user ID that does not exist.

SAP Sybase IQ Error Messages 47

Errors and Warnings

Messages 140 through 150

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 140 "Encryption has not been enabled."

Constant ENCRYPTION_NOT_ENABLED_WARNING

SAP Sybase Error Number 2817

SQL State 01005

SQL Code 140L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause An encryption key was provided, but encryption has not been ena-
bled, nor is the database encrypted.

Error 141 "Table '%1' not found"

Constant TABLE_NOT_FOUND

SAP Sybase Error Number 2081

SQL State 42W33

SQL Code -141L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 Name of the table that could not be found.

Probable Cause You misspelled the name of a table, or you did not qualify a table
name with the owner name. For example, you might have referred to
"Employees" instead of "DBA"."Employees".

Error 142 "Correlation name '%1' not found"

Constant CORRELATION_NAME_NOT_FOUND

SAP Sybase Error Number 2082

48 SAP Sybase IQ
Errors and Warnings

Error 142 "Correlation name '%1' not found"

SQL State 52W02

SQL Code -142L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the invalid correlation name.

Probable Cause You misspelled a correlation name, or you used a table name instead
of the correlation name.

Warning 142 "UltraLite database state was restored"

Constant DATABASE_STATE_RESTORED

SAP Sybase Error Number 2921

SQL State WW114

SQL Code 142L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause The database state was restored from the temporary file. This includes
suspended connections, transactions, and cursors.

Error 143 "Column '%1' not found"

Constant COLUMN_NOT_FOUND

SAP Sybase Error Number 2481

SQL State 52003

SQL Code -143L

ODBC 2 State S0002

ODBC 3 State 42S22

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 49

Errors and Warnings

Error 143 "Column '%1' not found"

Parameter 1 Name of the column that could not be found.

Probable Cause You misspelled the name of a column, or the column you are looking
for is in a different table.

Warning 143 "Retrying read of corrupt page (page '%1')"

Constant CORRUPT_PAGE_READ_RETRY

SAP Sybase Error Number 2922

SQL State WW115

SQL Code 143L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The page ID.

Probable Cause UltraLite detected a corrupt database page and will attempt the read
operation again. If a mirror file is enabled, it is used for the retry. If the
retry fails, an error will be signaled.

Error 144 "Column '%1' found in more than one table or it is used more
than once in the SELECT list -- it needs a correlation name"

Constant COLUMN_AMBIGUOUS

SAP Sybase Error Num- 2084

ber

SQL State 52002

SQL Code -144L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the ambiguous column.

50 SAP Sybase IQ
Errors and Warnings

Error 144 "Column '%1' found in more than one table or it is used more
than once in the SELECT list -- it needs a correlation name"

Probable Cause You have not specified a correlation name on a column which is found in
more than one of the tables referenced in a query block or which appears
more than once in the SELECT list of a query block. You need to add a
correlation name to the column.

Warning 144 "Mirror file requires higher checksum_level"

Constant MIRROR_FILE_REQUIRES_CHECKSUMS

SAP Sybase Error Number 2923

SQL State WW116

SQL Code 144L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause To effectively protect against media failures, page checksums must be
enabled when using the mirror file. Specify the checksum_level da-
tabase creation option.

Error 145 "Foreign key name '%1' not found"

Constant FOREIGN_KEY_NAME_NOT_FOUND

SAP Sybase Error Number 2085

SQL State 52W07

SQL Code -145L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the non-existing foreign key.

Probable Cause You misspelled the name of a foreign key, or the foreign key does not
exist.

SAP Sybase IQ Error Messages 51

Errors and Warnings

Warning 145 "Two rows with the same primary key have been downloaded for
table '%1'"

Constant DUPLICATE_ROW_FOUND_IN_DOWNLOAD

SAP Sybase Error 2943

Number

SQL State 01W27

SQL Code 145L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 Name of the table being downloaded.

Probable Cause The synchronization scripts are producing duplicate rows with the same
primary key in your download. Generally this behavior indicates a problem
with the synchronization scripts. No guarantees are made about which of the
downloaded rows will be applied to the database.

Error 146 "There is no way to join '%1' to '%2'"

Constant CANNOT_JOIN

SAP Sybase Error Number 2086

SQL State 53W04

SQL Code -146L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of first table that cannot be joined.

Parameter 2 Name of second table that cannot be joined.

Probable Cause You may have attempted a KEY JOIN between two tables and there is
no foreign key on one of the tables that references the primary key of
the other table. You may have attempted a NATURAL JOIN between
two tables that have no common column names.

52 SAP Sybase IQ
Errors and Warnings

Warning 146 "Event notification queue '%1' is full, notification

discarded"

Constant EVENT_NOTIFICATION_QUEUE_FULL

SAP Sybase Error Number 2947

SQL State WE011

SQL Code 146L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the event notification queue.

Probable Cause The named queue is full and will not receive any event notifications
until notifications are read from the queue. The pending notification
has been discarded.

Error 147 "There is more than one way to join '%1' to '%2'"

Constant AMBIGUOUS_JOIN

SAP Sybase Error 2087

Number

SQL State 52W08

SQL Code -147L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of first table that cannot be joined.

Parameter 2 Name of second table that cannot be joined.

Probable Cause You are attempting to KEY JOIN two tables, and there are two or more
foreign keys relating the two tables. There may be two foreign keys from
the first table to the second table. It may be that each table has a foreign key
to the other table. You must use a correlation name for the primary key table
that is the same as the role name of the desired foreign key relationship.

SAP Sybase IQ Error Messages 53

Errors and Warnings

Warning 147 "Event notifications lost on queue '%1'"

Constant EVENT_NOTIFICATIONS_LOST

SAP Sybase Error Number 2948

SQL State WE012

SQL Code 147L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the event notification queue.

Probable Cause Event notifications have been lost on the named queue. This behavior
occurs if there are pending notifications when the queue is destroyed.
The notifications are discarded.

Error 148 "Unknown function '%1'"

Constant UNKNOWN_FUNC

SAP Sybase Error Number 2091

SQL State 42W05

SQL Code -148L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Function name that is not a database function.

Probable Cause You misspelled the name of a database function (such as MAXIMUM
instead of MAX) in a query definition or in a query column name.

Warning 148 "Event notification queue '%1' not found warning"

Constant EVENT_NOTIFICATION_QUEUE_NOT_FOUND_WARN

SAP Sybase Error Number 2949

SQL State WE013

SQL Code 148L

54 SAP Sybase IQ
Errors and Warnings

Warning 148 "Event notification queue '%1' not found warning"

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the event notification queue.

Probable Cause The named event notification queue was not found. The operation will
be skipped.

Error 149 "Function or column reference to '%1' must also appear in a GROUP
BY"

Constant INVALID_GROUP_SELECT

SAP Sybase Er- 2092

ror Number

SQL State 53003

SQL Code -149L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the column referenced directly, or in an expression, that must be in the
GROUP BY clause.

Probable Cause You used a non-aggregate function or column reference in the SELECT list or in a
nested query block that does not appear in the GROUP BY clause. In a query using
GROUP BY, SELECT list items that are not aggregate functions must also appear
in the GROUP BY clause. If the SELECT list item is a column reference or an
alias, you may add the column name or alias to the GROUP BY clause. If the
SELECT list item is a scalar function, ensure that the function's arguments in the
GROUP BY clause match exactly with those in the SELECT list. You may be able
to use the MAX function (or another aggregate function) on the column name
instead of adding the column to the GROUP BY clause.

Warning 149 "Automatic database upgrade applied"

Constant DATABASE_UPGRADE_WARNING

SAP Sybase Error Number 2972

SAP Sybase IQ Error Messages 55

Errors and Warnings

Warning 149 "Automatic database upgrade applied"

SQL State WW234

SQL Code 149L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause The database is from an older version of the software. An automatic
database upgrade occurs during startup. Subsequently the database
can no longer be opened with the older version of the software.

Error 150 "Invalid use of an aggregate function"

Constant AGGREGATES_NOT_ALLOWED

SAP Sybase Error 2093

Number

SQL State 42W06

SQL Code -150L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted to use an aggregate function inappropriately. For example, a
SELECT statement cannot contain an aggregate function within a predicate in
the WHERE clause unless the aggregate function constitutes an outer refer-
ence. Other invalid uses include specifying an aggregate function in the SET
clause of an UPDATE statement, or using an aggregate function in a CHECK
constraint.

Warning 150 "Database contains no tables to synchronize"

Constant NO_TABLES_TO_SYNCHRONIZE

SAP Sybase Error Number 3173

SQL State 01W28

SQL Code 150L

ODBC 2 State OK

56 SAP Sybase IQ
Errors and Warnings

Warning 150 "Database contains no tables to synchronize"

ODBC 3 State OK

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You specified a UNION, INTERSECT, or EXCEPT, but the SELECT
statements involved in the operation do not have the same number of
columns in the SELECT list.

Error 154 "Wrong number of parameters to function '%1'"

Constant WRONG_PARAMETER_COUNT

SAP Sybase Error Number 2100

SQL State 37505

SQL Code -154L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the function.

Probable Cause You supplied an incorrect number of parameters to a database func-

tion.

58 SAP Sybase IQ
Errors and Warnings

Error 155 "Invalid host variable"

Constant VARIABLE_INVALID

SAP Sybase Error Number 2102

SQL State 42W07

SQL Code -155L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 17 on page 2

Probable Cause You supplied an invalid host variable to the database using the C
language interface. You may have supplied the variable as a host
variable or through a SQLDA.

Error 156 "Invalid expression near '%1'"

Constant EXPRESSION_ERROR

SAP Sybase Error Number 2103

SQL State 42W08

SQL Code -156L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The invalid expression.

Probable Cause You supplied an expression that the database server cannot under-
stand. For example, you may have tried to add two dates.

Error 157 "Cannot convert %1 to a %2"

Constant CONVERSION_ERROR

SAP Sybase Error Number 2104

SQL State 53018

SQL Code -157L

ODBC 2 State 07006

SAP Sybase IQ Error Messages 59

Errors and Warnings

Error 157 "Cannot convert %1 to a %2"

ODBC 3 State 07006

Severity Code 16 on page 2

Parameter 1 The value that could not be converted.

Parameter 2 The name of the type for the conversion.

Probable Cause An error occurred while trying to convert a value to another data type.

Error 158 "Value %1 out of range for destination"

Constant OVERFLOW_ERROR

SAP Sybase Error Number 2105

SQL State 22003

SQL Code -158L

ODBC 2 State 22003

ODBC 3 State 22003

Severity Code 16 on page 2

Parameter 1 The value that caused the overflow.

Probable Cause You supplied to or fetched from the database a value that is out of
range for the destination column or host variable. For example, the
value 10 may have been supplied for a DECIMAL(3,2) field.

Error 159 "Invalid column number"

Constant INVALID_COLUMN_NUMBER

SAP Sybase Error Number 2106

SQL State 42W13

SQL Code -159L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You gave an invalid column number, or the column you are looking
for is in a different table.

60 SAP Sybase IQ
Errors and Warnings

Error 160 "Can only describe a SELECT statement"

Constant DESCRIBE_NONSELECT

SAP Sybase Error Num- 2107

ber

SQL State 07005

SQL Code -160L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Probable Cause In the C language interface, you attempted to describe the SELECT list
of a statement other than a SELECT statement. In UltraLite this error
can result from trying to retrieve the schema of any statement other than
a SELECT.

Error 161 "Invalid type on DESCRIBE statement"

Constant INVALID_DESCRIBE_TYPE

SAP Sybase Error Number 2108

SQL State 07W01

SQL Code -161L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Probable Cause A Java type specified on a DESCRIBE statement has no correspond-

ing SQL type.

Error 162 "Cannot convert %1 to a %2. The bad value was supplied
for column '%3' on row %4 of the data file"

Constant CONVERSION_ERROR_LOAD_TABLE

SAP Sybase Error Number 2533

SQL State 53017

SQL Code -162L

SAP Sybase IQ Error Messages 61

Errors and Warnings

Error 162 "Cannot convert %1 to a %2. The bad value was supplied
for column '%3' on row %4 of the data file"

ODBC 2 State 07006

ODBC 3 State 07006

Severity Code 16 on page 2

Parameter 1 Value that could not be converted.

Parameter 2 Destination data type.

Parameter 3 Name of the column where the value was to be inserted.

Parameter 4 Line number of the data file where the invalid data occurred.

Probable Cause The data file supplied to LOAD TABLE contains a value that cannot
be converted to the required data type.

Error 163 "Derived table '%1' has no name for column %2"

Constant NO_COLUMN_NAME

SAP Sybase Error Number 2302

SQL State 52004

SQL Code -163L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the derived table.

Parameter 2 Number of the column for which there is no name.

Probable Cause The specified column of the derived table has no column name. Use a
SELECT list alias in the query specification or use a derived columns
specifier.

Error 164 "Namespace heap exhausted at internal function: %1"

Constant NAMESPACE_HEAP_EXHAUSTED

SAP Sybase Error Number 2310

SQL State WP007

62 SAP Sybase IQ
Errors and Warnings

Error 164 "Namespace heap exhausted at internal function: %1"

SQL Code -164L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The internal function is for debugging purposes.

Probable Cause The amount of space allocated for the Java Namespace is insufficient
to continue loading Java classes. Increase the size by using: SET
OPTION PUBLIC.java_namespace_size = nnnnnnnn.

Error 165 "Java VM heap exhausted at internal function: %1"

Constant JAVA_VM_HEAP_EXHAUSTED

SAP Sybase Error Num- 2311

ber

SQL State WP008

SQL Code -165L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The internal function is for debugging purposes.

Probable Cause The amount of space allocated for the Java VM is insufficient to con-
tinue allocating new objects. Increase the size by using: SET OPTION
PUBLIC.java_heap_size = nnnnnnnn.

Error 170 "Cursor has not been declared"

Constant CURSOR_NOT_DECLARED

SAP Sybase Error Number 2109

SQL State 24W01

SQL Code -170L

ODBC 2 State 24000

ODBC 3 State 24000

SAP Sybase IQ Error Messages 63

Errors and Warnings

Error 170 "Cursor has not been declared"

Severity Code 16 on page 2

Probable Cause You attempted to OPEN a cursor that has not been declared.

Error 171 "Error opening cursor"

Constant OPEN_CURSOR_ERROR

SAP Sybase Error Number 2110

SQL State 07003

SQL Code -171L

ODBC 2 State 24000

ODBC 3 State 24000

Severity Code 15 on page 2

Probable Cause You attempted to open a cursor on a statement that is not SELECT,
CALL or EXEC.

Error 172 "Cursor already open"

Constant CURSOR_ALREADY_OPEN

SAP Sybase Error Number 2111

SQL State 24502

SQL Code -172L

ODBC 2 State 24000

ODBC 3 State 24000

Severity Code 16 on page 2

Probable Cause You attempted to OPEN a cursor that is already open.

Error 180 "Cursor not open"

Constant CURSOR_NOT_OPEN

SAP Sybase Error Number 2112

SQL State 24501

SAP Sybase IQ Error Messages 65

Errors and Warnings

Error 183 "Cannot find index named '%1'"

Constant INDEX_NOT_FOUND

SAP Sybase Error Number 2063

SQL State 52W03

SQL Code -183L

ODBC 2 State S0012

ODBC 3 State 42S12

Severity Code 16 on page 2

Parameter 1 Name of the index that cannot be found.

Probable Cause You attempted to perform an operation using an index that does not
exist. Check for spelling errors. Check whether the index name must
be qualified with a user ID.

Error 184 "Column '%1' in table '%2' cannot be NULL. The invalid data was
supplied to LOAD TABLE in a data file on line %3"

Constant COLUMN_CANNOT_BE_NULL_LOAD_TABLE

SAP Sybase Error 2531

Number

SQL State 23501

SQL Code -184L

ODBC 2 State 23000

ODBC 3 State 23000

Severity Code 16 on page 2

Parameter 1 Name of the column that cannot be NULL.

Parameter 2 Name of the table containing the column.

Parameter 3 The line number of the data file containing the invalid data.

Probable Cause You either have not supplied a value where a value is required or a data
conversion was necessary that resulted in a NULL value. The column defi-
nition prohibits NULL values or the column is part of a NOT NULL foreign
key.

66 SAP Sybase IQ
Errors and Warnings

Error 185 "SELECT returns more than one row"

Constant TOO_MANY_RECORDS

SAP Sybase Error Number 2116

SQL State 21000

SQL Code -185L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You tried to use a SELECT statement without a cursor, but the state-
ment cursor returns more than one row. Only a single row SELECT
statement can be used in this context.

Error 186 "Subquery cannot return more than one row"

Constant SUBQUERY_RESULT_NOT_UNIQUE

SAP Sybase Error Num- 2117

ber

SQL State 21W01

SQL Code -186L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You used a subquery that returns more than one row, in a context where
only a single row can be used. If the subquery is in the WHERE clause,
you might be able to use the IN keyword.

Error 187 "Illegal cursor operation attempt"

Constant CURSOROP_NOT_ALLOWED

SAP Sybase Error Number 2118

SQL State 09W02

SQL Code -187L

ODBC 2 State 07005

SAP Sybase IQ Error Messages 67

Errors and Warnings

Error 187 "Illegal cursor operation attempt"

ODBC 3 State 07005

Severity Code 16 on page 2

Probable Cause You attempted an illegal cursor operation. For example, you may be
attempting to OPEN a cursor for a statement that is neither a SELECT
nor a BATCH.

Error 188 "Not enough values for host variables"

Constant NOT_ENOUGH_HOST_VARS

SAP Sybase Error Number 2119

SQL State 07001

SQL Code -188L

ODBC 2 State 07002

ODBC 3 State 07002

Severity Code 16 on page 2

Probable Cause You have not provided enough host variables for either the number of
bind variables, or the statement, or the number of SELECT list items.

Error 189 "Unable to find in index '%1' for table '%2'"

Constant NOT_FOUND_IN_INDEX

SAP Sybase Error Num- 2120

ber

SQL State WI005

SQL Code -189L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of invalid index.

Parameter 2 Name of table containing the invalid index.

68 SAP Sybase IQ
Errors and Warnings

Error 189 "Unable to find in index '%1' for table '%2'"

Probable Cause This is an internal error. If it can be reproduced, it should be reported to

iAnywhere. You should be able to work around the error by dropping
and recreating the index.

Error 190 "Cannot update an expression"

Constant NON_UPDATEABLE_COLUMN

SAP Sybase Error Number 2121

SQL State 53W02

SQL Code -190L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 14 on page 2

Probable Cause You tried to update a column in a query that is a database expression
rather than a column in a table.

Error 191 "Cannot modify column '%1' in table '%2'"

Constant CANNOT_MODIFY

SAP Sybase Error Number 2122

SQL State 42W32

SQL Code -191L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 14 on page 2

Parameter 1 Name of the column that cannot be changed.

Parameter 2 Name of the table containing the column.

Probable Cause You may have tried to modify a column that you do not have per-
mission to modify. You may have tried to modify a column defined as
an expression (such as column1+column2) in a view.

SAP Sybase IQ Error Messages 69

Errors and Warnings

Error 192 "Update operation attempted on non-updatable query"

Constant NON_UPDATEABLE_VIEW

SAP Sybase Error 2123

Number

SQL State 42W31

SQL Code -192L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted an insert, update, or delete operation on a query that is
implicitly read-only. Queries that contain DISTINCT, GROUP BY, HAV-
ING, EXCEPT, INTERSECT or UNION, or that contain aggregate func-
tions, or that involve a join, are implicitly read-only. If the query references
a view then the view may be non-updatable.

Parameter 2 Name of the table containing the column.

Probable Cause You have not supplied a value where a value is required. The column
definition prohibits NULL values or the column is part of a NOT
NULL foreign key.

Error 196 "Index '%1' for table '%2' would not be unique"

Constant INDEX_NOT_UNIQUE

SAP Sybase IQ Error Messages 71

Errors and Warnings

Error 196 "Index '%1' for table '%2' would not be unique"

SAP Sybase Error Num- 2127

ber

SQL State 23505

SQL Code -196L

ODBC 2 State 23000

ODBC 3 State 23000

Severity Code 16 on page 2

Parameter 1 Name of the index that would not be unique.

Parameter 2 Name of the table that contains the index.

Probable Cause You attempted to insert or update a row that has the same value as
another row in some column, and there is a constraint that does not
allow two rows to have the same value in that column.

Error 197 "No current row of cursor"

Constant NO_CURRENT_ROW

SAP Sybase Error Num- 2128

ber

SQL State 24503

SQL Code -197L

ODBC 2 State 24000

ODBC 3 State 24000

Severity Code 16 on page 2

Probable Cause You attempted to perform an operation on the current row of a cursor,
but the cursor is not positioned on a row. The cursor is before the first
row of the cursor, after the last row, or is on a row that has since been
deleted.

Error 198 "Primary key for row in table '%1' is referenced by foreign
key '%2' in table '%3'"

Constant PRIMARY_KEY_VALUE_REF

72 SAP Sybase IQ
Errors and Warnings

Error 198 "Primary key for row in table '%1' is referenced by foreign
key '%2' in table '%3'"

SAP Sybase Error Num- 2129

ber

SQL State 23W05

SQL Code -198L

ODBC 2 State 23000

ODBC 3 State 23000

Severity Code 16 on page 2

Parameter 1 The name of the table containing the row being modified.

Parameter 2 The name of the foreign index (or role) of the referencing table.

Parameter 3 The name of the foreign table referencing the primary row.

Probable Cause You attempted to delete or modify a row whose primary key value is
referenced elsewhere in the database.

Error 199 "INSERT/DELETE on cursor can modify only one table"

Constant ONLY_ONE_TABLE

SAP Sybase Error 2130

Number

SQL State 09W04

SQL Code -199L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted to insert into a cursor and have specified values for more
than one table, or you attempted to delete from a cursor that involves a
join. Insert into one table at a time. For DELETE, use the FROM clause to
specify the table you want to delete from.

Warning 200 "Warning: %1"

Constant WARNING

SAP Sybase IQ Error Messages 73

Errors and Warnings

Warning 200 "Warning: %1"

SAP Sybase Error Number 2009

SQL State 01000

SQL Code 200L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Warning message.

Probable Cause A warning has occurred. The message indicates the condition that
caused the warning.

Error 200 "Invalid option '%1' -- no PUBLIC setting exists"

Constant INVALID_OPTION

SAP Sybase Error Number 2167

SQL State 42W16

SQL Code -200L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the invalid option.

Probable Cause You may have misspelled the name of an option in the SET OPTION
statement. You can only define an option for a user if the database
administrator has supplied a PUBLIC value for that option.

Messages 201 through 220

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 201 "Invalid setting for option '%1'"

Constant INVALID_OPTION_SETTING

SAP Sybase Error Number 2168

74 SAP Sybase IQ
Errors and Warnings

Error 201 "Invalid setting for option '%1'"

SQL State 42W17

SQL Code -201L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the invalid option.

Probable Cause You supplied an invalid value for an option in the SET statement.
Some options allow only numeric values, while other options allow
only the values On and Off.

Warning 201 "The ICU collation '%1' has defaulted to another collation"

Constant COLLATION_DEFAULT_WARNING

SAP Sybase Error 2788

Number

SQL State 01WC4

SQL Code 201L

ODBC 2 State 01000

ODBC 3 State 01000

Severity Code 10 on page 2

Parameter 1 The ICU collation specifier.

Probable Cause The specified ICU collation is not available. Another collation was sub-
stituted, which may or may not produce suitable results. Due to the struc-
ture of ICU, the collation that was used is not known, but was the best
alternative to the specified collation. If this database is used on another
platform, a different collation may be chosen and the operation may gen-
erate different results.

Error 202 "Only PUBLIC settings are allowed for option '%1'"

Constant NOT_PUBLIC_ID

SAP Sybase Error Number 2251

SQL State 42W43

SAP Sybase IQ Error Messages 75

Errors and Warnings

Error 202 "Only PUBLIC settings are allowed for option '%1'"

SQL Code -202L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the option.

Probable Cause The option specified in the SET OPTION statement is PUBLIC only.
You cannot define this option for any other user.

Error 203 "Cannot set a temporary option for user '%1'"

Constant TEMPORARY_NOT_ALLOWED

SAP Sybase Error Num- 2254

ber

SQL State 42W45

SQL Code -203L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 User ID whose option was to be changed.

Probable Cause TEMPORARY options are set on a connection basis, and only for
specific options known to the database server. To change an option for
another user, do not specify TEMPORARY in the SET OPTION state-
ment.

Error 204 "You do not have '%1' system privilege or authority to set the
option '%2'"

Constant OPTION_REQUIRES_DBA

SAP Sybase Error Num- 2256

ber

SQL State 42W46

SQL Code -204L

76 SAP Sybase IQ
Errors and Warnings

Error 204 "You do not have '%1' system privilege or authority to set the
option '%2'"

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 14 on page 2

Parameter 1 Name of the system privilege or authority required to set the option.

Parameter 2 Name of the option that could not be set.

Probable Cause The option specified in the SET OPTION statement can only be set by a
user with DBA authority or by a user with SET ANY SYSTEM OP-
TION / SET ANY SECURITY OPTION / SET ANY PUBLIC OP-
TION depending on the option.

Error 205 "Integrated logins are not permitted"

Constant INVALID_STANDARD_LOGON

SAP Sybase Error Number 2257

SQL State 28W02

SQL Code -205L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause The login_mode database option is set to Standard, and you attempted
an integrated login. Change the option setting or supply an explicit
user ID.

Error 206 "Integrated logins are required, standard logins are not
permitted"

Constant INVALID_INTEGRATED_LOGON

SAP Sybase Error Number 2258

SQL State 28W03

SQL Code -206L

ODBC 2 State 28000

SAP Sybase IQ Error Messages 77

Errors and Warnings

Error 206 "Integrated logins are required, standard logins are not
permitted"

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause The login_mode database option is set to Integrated, and you attemp-
ted a standard login. Change the option setting or use an integrated
login.

Error 207 "Wrong number of values for INSERT"

Constant WRONG_NUM_OF_INSERT_COLS

SAP Sybase Error Num- 2133

ber

SQL State 53002

SQL Code -207L

ODBC 2 State 21S01

Error 210 "User '%1' has the row in '%2' locked"

Severity Code 21 on page 2

Parameter 1 Name of another user.

Parameter 2 Table that generates the error.

Probable Cause The operation failed because another connection holds a lock on the same
object you are attempting to modify. With INSERT, UPDATE, DELETE,
SELECT, or MERGE statements this error is typically caused by attempting to
read or write a row that is locked by another user, while the database option
'blocking' is set to Off. With data definition statements, including CREATE,
DROP, GRANT, REVOKE, REFRESH, or ALTER, this error can be gener-
ated when the connection executing the DDL statement is unable to obtain an
exclusive lock on the object to be modified (table, view, materialized view, or
index) so that the operation can proceed.

Error 211 "Not allowed while '%1' is using the database"

Constant MUST_BE_ONLY_CONNECTION

SAP Sybase Error Number 2170

SQL State 42W19

SQL Code -211L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Parameter 1 Name of the connection that is using the database.

Probable Cause You attempted a data definition language operation that cannot be
completed while another user is connected.

Error 212 "CHECKPOINT statement requires a rollback log"

Constant CHECKPOINT_REQUIRES_UNDO

SAP Sybase Error Number 2171

SQL State 42W20

SAP Sybase IQ Error Messages 81

Errors and Warnings

Error 215 "Procedure in use by '%1'"

SAP Sybase Error Number 2173

SQL State 42W23

SQL Code -215L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Parameter 1 Name of user.

Probable Cause You attempted to DROP a procedure that is being used by other active
users of the database.

Error 216 "The option '%1' can only be set as a temporary option"

Constant OPTION_IS_TEMP_ONLY

SAP Sybase Error Number 2351

SQL State 42W52

SQL Code -216L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 14 on page 2

Parameter 1 Name of the option that could not be set.

Probable Cause The option specified in the SET OPTION statement can only be set as
a temporary option.

Error 217 "The option '%1' cannot be set from within a procedure"

Constant OPTION_IN_PROCEDURE

SAP Sybase Error Number 2352

SQL State 42W53

SQL Code -217L

ODBC 2 State 42000

82 SAP Sybase IQ
Errors and Warnings

Error 217 "The option '%1' cannot be set from within a procedure"

ODBC 3 State 42000

Severity Code 14 on page 2

Parameter 1 Name of the option that could not be set.

Probable Cause The option specified in the SET OPTION statement cannot be set
from within a procedure.

Error 218 "Authentication failed"

Constant AUTHENTICATION_FAILED

SAP Sybase Error Number 2353

SQL State 08W48

SQL Code -218L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause You set the database_authentication or connection_authentication

option incorrectly.

Error 220 "Savepoint '%1' not found"

Constant SAVEPOINT_NOTFOUND

SAP Sybase Error Number 2174

SQL State 3B001

SQL Code -220L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of savepoint.

Probable Cause You attempted to rollback to a savepoint that does not exist.

SAP Sybase IQ Error Messages 83

Errors and Warnings

Messages 221 through 263

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 221 "ROLLBACK TO SAVEPOINT not allowed"

Constant ROLLBACK_NOT_ALLOWED

SAP Sybase Error Number 2175

SQL State 3B002

SQL Code -221L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted a ROLLBACK TO SAVEPOINT within an atomic

operation to a savepoint established before the atomic operation.

Error 222 "Result set not allowed from within an atomic compound
statement"

Constant RESULT_NOT_ALLOWED

SAP Sybase Error Number 2176

SQL State 3BW02

SQL Code -222L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You used a SELECT statement with no INTO clause or a RESULT
CURSOR statement within an atomic compound statement.

Error 230 "sqlpp/dblib version mismatch"

Constant PP_DBLIB_MISMATCH

SAP Sybase Error Number 2178

SQL State 08W18

84 SAP Sybase IQ
Errors and Warnings

Error 230 "sqlpp/dblib version mismatch"

SQL Code -230L

ODBC 2 State 08801

ODBC 3 State 08001

Severity Code 21 on page 2

Probable Cause Your executable has Embedded SQL source files that were prepro-
cessed with a version of sqlpp that does not match the database in-
terface library.

Error 231 "Client/database server version mismatch"

Constant DBLIB_ENGINE_MISMATCH

SAP Sybase Error Number 2179

SQL State 08W19

SQL Code -231L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 21 on page 2

Probable Cause Your executable uses a database interface library that does not match
the version number of the database server.

Error 240 "Unknown backup operation"

Constant UNKNOWN_BACKUP_OPERATION

SAP Sybase Error Number 2181

SQL State WB001

SQL Code -240L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 20 on page 2

Probable Cause You specified an invalid backup statement operation in a call to

db_backup.

SAP Sybase IQ Error Messages 85

Errors and Warnings

Error 241 "Database backup not started"

Constant BACKUP_NOT_STARTED

SAP Sybase Error Number 2182

SQL State WB002

SQL Code -241L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 20 on page 2

Probable Cause A database backup could not be started. Either a backup is already
running, or you do not have the required authority (BACKUP, DBA,
or REMOTE DBA).

Error 242 "Incomplete transactions prevent transaction log renaming"

Constant BACKUP_CANNOT_RENAME_LOG_YET

SAP Sybase Error Num- 2183

ber

SQL State WB003

SQL Code -242L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 20 on page 2

Probable Cause The last page in the transaction log was read by a call to db_backup. One
or more currently active connections have partially completed transac-
tions, preventing the transaction log file from being renamed. Reissue
the db_backup call.

Error 243 "Unable to delete database file"

Constant BACKUP_UNABLE_TO_DELETE_FILE

SAP Sybase Error Number 2184

SQL State WB004

Error 246 "Integrated logins are not supported for this database"

Constant INTEGRATED_LOGON_UNSUPPORTED

SAP Sybase Error Num- 2262

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause You attempted to map a login ID to either SYS or PUBLIC.

Error 249 "The login ID '%1' is already mapped to user ID '%2'"

Constant LOGON_MAPPED

SAP Sybase Error Number 2265

SQL State 28W08

SQL Code -249L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Parameter 1 Name of the login ID that is already mapped.

Parameter 2 Name of the user that the login ID is already mapped to.

Probable Cause You attempted to map a login ID twice.

Error 250 "Identifier '%1' too long"

Constant IDENTIFIER_TOO_LONG

SAP Sybase Error Number 2061

SQL State 54003

SQL Code -250L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 The identifier that is too long.

Probable Cause An identifier that was specified is longer than 128 bytes.

SAP Sybase IQ Error Messages 89

Errors and Warnings

Error 251 "Foreign key '%1' for table '%2' duplicates an existing
foreign key"

Constant DUPLICATE_FOREIGN_KEY

SAP Sybase Error Number 2062

SQL State 52W06

SQL Code -251L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The role name of the new foreign key.

Parameter 2 The table containing the foreign key.

Probable Cause You attempted to define a foreign key that already exists.

Error 260 "Variable '%1' not found"

Constant VARIABLE_NOT_FOUND

SAP Sybase Error Number 2139

SQL State 42W14

SQL Code -260L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the variable that could not be found.

Probable Cause You attempted to DROP or SET the value of a SQL variable that was
not created or was previously dropped.

Error 261 "There is already a variable named '%1'"

Constant VARIABLE_EXISTS

SAP Sybase Error Number 2140

SQL State 42W15

264 - 786

Messages 264 through 289

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 264 "Wrong number of variables in FETCH"

Constant WRONG_NUM_OF_FETCH_VARIABLES

SAP Sybase Error Num- 2143

ber

SQL State 42W26

SQL Code -264L

ODBC 2 State S1002

ODBC 3 State 07009

Severity Code 16 on page 2

Probable Cause You specified a number of variables in a FETCH statement that does
not match the number of SELECT list items.

Error 265 "Procedure '%1' not found"

Constant PROCEDURE_NOT_FOUND

SAP Sybase Error Number 2144

SQL State 52W09

SQL Code -265L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 Name of the procedure that could not be found.

92 SAP Sybase IQ
Errors and Warnings

Error 265 "Procedure '%1' not found"

Probable Cause You misspelled the name of a procedure, or you did not qualify a
procedure name with a user name.

Error 267 "COMMIT/ROLLBACK not allowed within atomic

operation"

Constant ATOMIC_OPERATION

SAP Sybase Error Number 2146

SQL State 42W28

SQL Code -267L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted a COMMIT or ROLLBACK statement while execut-

ing within an atomic operation.

Error 268 "Trigger '%1' not found"

Constant TRIGGER_NOT_FOUND

SAP Sybase Error Number 2147

SQL State 52W10

SQL Code -268L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 Name of the trigger that could not be found.

Probable Cause You misspelled the name of a trigger, or you did not qualify a trigger
name with a user name.

Error 269 "Cannot delete or rename a column referenced in a trigger

definition"

Constant COLUMN_IN_TRIGGER

SAP Sybase IQ Error Messages 93

Errors and Warnings

Error 269 "Cannot delete or rename a column referenced in a trigger

definition"

SAP Sybase Error Number 2148

SQL State 53W06

SQL Code -269L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to delete or rename a column referenced in a trigger

definition. Drop the trigger before performing the ALTER statement.

Error 270 "Cannot drop a user that owns procedures in runtime server"

Constant USER_OWNS_PROCEDURES

SAP Sybase Error Num- 2149

ber

SQL State 55W04

SQL Code -270L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that owns procedures while using the
runtime server. This operation would result in dropping procedures. The
runtime server cannot drop procedures. Use the full server.

Error 271 "Trigger definition conflicts with existing triggers"

Constant TRIGGER_DEFN_CONFLICT

SAP Sybase Error Number 2150

SQL State 52W11

SQL Code -271L

ODBC 2 State S0002

ODBC 3 State 42S01

94 SAP Sybase IQ
Errors and Warnings

Error 271 "Trigger definition conflicts with existing triggers"

Severity Code 15 on page 2

Probable Cause You attempted to create a trigger, but a trigger with the same name
already exists.

Error 272 "Invalid REFERENCES clause in trigger definition"

Constant INVALID_TRIGGER_COL_REFS

SAP Sybase Error 2151

Number

SQL State 52W12

SQL Code -272L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You supplied an invalid REFERENCES clause in a trigger definition. You
may have specified an OLD correlation name in a BEFORE INSERT
trigger, or a NEW correlation name in an AFTER DELETE trigger. In both
cases, the values do not exist and cannot be referenced.

Error 273 "COMMIT/ROLLBACK not allowed within trigger actions"

Constant INVALID_TRIGGER_STATEMENT

SAP Sybase Error Number 2152

SQL State 2D501

SQL Code -273L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted to execute a statement that is not allowed while per-
forming a trigger action. COMMIT and ROLLBACK statements
cannot be executed from a trigger.

SAP Sybase IQ Error Messages 95

Errors and Warnings

Error 274 "Procedure or trigger calls have nested too deeply"

Constant NESTING_TOO_DEEP

SAP Sybase Error Number 2153

SQL State 42W29

SQL Code -274L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You may have defined a procedure or trigger that causes unlimited
recursion.

Error 280 "Publication '%1' not found"

Constant PUBLICATION_NOT_FOUND

SAP Sybase Error Number 2155

SQL State 5RW01

SQL Code -280L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the publication that could not be found.

Probable Cause You misspelled the name of a publication, or you did not qualify a
publication name with a user name.

Error 281 "Table '%1' has publications"

Constant TABLE_HAS_PUBLICATIONS

SAP Sybase Error Number 2156

SQL State 5RW02

SQL Code -281L

ODBC 2 State S0002

96 SAP Sybase IQ
Errors and Warnings

Error 281 "Table '%1' has publications"

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the table that has publications.

Probable Cause You attempted to drop a table that has publications defined.

Error 282 "Subscription to '%1' for '%2' already exists"

Constant SUBSCRIPTION_NOT_UNIQUE

SAP Sybase Error Number 2157

SQL State 5RW03

SQL Code -282L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the publication.

Parameter 2 Name of the user.

Probable Cause You attempted to create a subscription that already exists.

Error 283 "Subscription to '%1' for '%2' not found"

Constant SUBSCRIPTION_NOT_FOUND

SAP Sybase Error Number 2158

SQL State 5RW04

SQL Code -283L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the publication.

Parameter 2 Name of the user.

SAP Sybase IQ Error Messages 97

Errors and Warnings

Error 283 "Subscription to '%1' for '%2' not found"

Error 288 "Remote statement failed"

Constant REMOTE_STATEMENT_FAILED

SAP Sybase Error 2163

Number

SAP Sybase IQ Error Messages 99

Errors and Warnings

Error 288 "Remote statement failed"

SQL State 5RW09

SQL Code -288L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Probable Cause This SQLSTATE can be signaled within a trigger to prevent the SQL
Remote Message Agent (dbremote) from displaying an error message in
the output. This exception will only occur when a trigger or procedure
signals it. This is useful for ignoring replication errors that are permitted
by design.

Error 289 "Multiple consolidated users cannot be defined"

Constant CONSOLIDATED_USER_ALREADY_EXISTS

SAP Sybase Error Number 2403

SQL State 5RW10

SQL Code -289L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Probable Cause You attempted to grant consolidated permissions when your database
already has a consolidated user, or attempted to grant consolidated
permissions to multiple users in a single statement.

Messages 294 through 503

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 294 "Format string argument number %1 is invalid"

Constant INVALID_FORMAT_STRING_ARG_NUM

SAP Sybase Error Num- 2166

ber

SQL State 53W08

100 SAP Sybase IQ

Errors and Warnings

Error 294 "Format string argument number %1 is invalid"

SQL Code -294L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Argument number.

Probable Cause You supplied an invalid argument number in the format string for a
PRINT or RAISERROR statement. The number must be between 1 and
20 and must not exceed the number of arguments provided.

Error 295 "Cannot uniquely identify rows in cursor"

Constant CANNOT_UNIQUELY_IDENTIFY_ROWS

SAP Sybase Error 2164

Number

SQL State 09W05

SQL Code -295L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You opened a UNIQUE cursor on a SELECT statement for which a set of
columns uniquely identifying each row cannot be generated. One of the
tables may not be defined with a primary key or uniqueness constraint, or
the SELECT statement may involve a UNION, INTERSECT, EXCEPT,
or GROUP BY.

Error 296 "Error number %1 for RAISERROR must not be less than
17000"

Constant ERROR_NUMBER_OUT_OF_RANGE

SAP Sybase Error Number 2165

SQL State 53W07

SQL Code -296L

ODBC 2 State 37000

SAP Sybase IQ Error Messages 101

Errors and Warnings

Error 296 "Error number %1 for RAISERROR must not be less than
17000"

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Error number.

Probable Cause You supplied an invalid error number in a RAISERROR statement.

The number must be greater than or equal to 17000.

Error 297 "User-defined exception signaled"

Constant USER_DEFINED_EXCEPTION

SAP Sybase Error 2186

Number

SQL State 99999

SQL Code -297L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A stored procedure or trigger signaled a user-defined exception. This error
state is reserved for use within stored procedures or triggers that contain
exception handlers, as a way of signaling an exception that can be guaran-
teed to not have been caused by the database server. Valid SQLSTATE values
range from 99000 to 99999 and are set by the user when executing the signal
SQL statement.

Error 298 "Attempted two active database requests"

Constant DOUBLE_REQUEST

SAP Sybase Error 2187

Number

SQL State 42W22

SQL Code -298L

ODBC 2 State ERROR

ODBC 3 State ERROR

102 SAP Sybase IQ

Errors and Warnings

Error 298 "Attempted two active database requests"

Severity Code 16 on page 2

Probable Cause In embedded SQL, you attempted to submit a database request while you
have another request in progress. You should either use a separate
SQLCA and connection for each thread accessing the database, or use
thread synchronization calls to ensure that a SQLCA is only accessed by
one thread at a time.

Error 299 "Statement interrupted by user"

Constant INTERRUPTED

SAP Sybase Error 2188

Number

SQL State 57014

SQL Code -299L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You canceled a statement during its execution. The database was able to stop
the operation without doing a rollback. If the statement is an INSERT, UP-
DATE, or DELETE, any changes made by the statement will be canceled. If
the statement is a data definition statement (for example CREATE TABLE),
the statement will be canceled, but the COMMIT that was done as a side
effect will not be canceled.

Error 300 "Run time SQL error -- %1"

Constant ERROR

SAP Sybase Error Number 2189

SQL State 40000

SQL Code -300L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 18 on page 2

SAP Sybase IQ Error Messages 103

Errors and Warnings

ODBC 3 State ERROR

Severity Code 24 on page 2

Parameter 1 A message describing the error that occurred.

Probable Cause SQL Anywhere has detected a problem with your hard disk. A
ROLLBACK statement has been automatically executed.

Error 306 "Deadlock detected"

Constant DEADLOCK

SAP Sybase Error Number 2194

SQL State 40001

SQL Code -306L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 13 on page 2

Probable Cause You attempted to read or write a row and it is locked by another user.
Also, the other user is blocked directly or indirectly on your own
transaction. This is a deadlock situation and your transaction has been
chosen as the one to rollback.

Error 307 "All threads are blocked"

Constant THREAD_DEADLOCK

SAP Sybase Error Num- 2195

ber

SQL State 40W06

SQL Code -307L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 13 on page 2

106 SAP Sybase IQ

Errors and Warnings

Error 307 "All threads are blocked"

Probable Cause You attempted to read or write a row and it is locked by another user.
Also, all other threads (see the -gn server option) are blocked waiting for
a lock to be released. This is a deadlock situation and your transaction has
been chosen as the one to rollback.

Error 308 "Connection was terminated"

Constant CONNECTION_TERMINATED

SAP Sybase Error 2196

Number

SQL State 40W07

SQL Code -308L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Your database connection has been terminated and your transaction has
been rolled back. The connection may have been terminated because a
DBA executed a DROP CONNECTION statement, or because the data-
base server was shut down, or because your network connection to the
database server was interrupted.

Error 309 "Memory error -- transaction rolled back"

Constant MEMORY_ERROR

SAP Sybase Error 2361

Number

SQL State 40W08

SQL Code -309L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 24 on page 2

SAP Sybase IQ Error Messages 107

Errors and Warnings

Error 309 "Memory error -- transaction rolled back"

Probable Cause The UltraLite runtime has received an unexpected error from the system
calls being used to store the UltraLite database. For example, a write to
persistent memory failed. This is an internal error and indicates faulty or
corrupt persistent storage on the device. A ROLLBACK statement has been
automatically executed.

Error 311 "Internal rollback log corrupted"

Constant LOG_CORRUPTED

SAP Sybase Error Number 2208

SQL State WI004

SQL Code -311L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 22 on page 2

Probable Cause While processing a COMMIT or ROLLBACK, corruption was found

in the internal rollback log. This is a fatal internal error.

Error 312 "User '%1' already has membership in group '%2'"

Constant ALREADY_HAS_GROUP_MEMBERSHIP

SAP Sybase Error Number 2069

SQL State 42W34

SQL Code -312L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the user that already has membership.

Parameter 2 Name of the group.

Probable Cause You attempted to give a membership in a group to a user that already
has such membership.

108 SAP Sybase IQ

Errors and Warnings

Error 313 "The login ID '%1' has not been mapped to any database user
ID"

Constant LOGON_UNMAPPED

SAP Sybase Error 2266

Number

SQL State 28W09

SQL Code -313L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Parameter 1 Name of the login ID that is not mapped.

Probable Cause You attempted to connect using a login ID that is not mapped to a database
user ID and there is no guest database user ID, or you attempted to revoke a
login ID that has not been mapped. This can also occur when attempting to
connect using an integrated login ID that is a member of more than one
mapped group.

Error 503 No message

Constant PREEMPTED

SAP Sybase Error Number 2260

SQL State WI006

SQL Code -503L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 109

Errors and Warnings

Messages 504 through 620

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 504 No message

Constant RETRY

SAP Sybase Error Number 2261

SQL State WI008

SQL Code -504L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause No additional information available.

Error 601 "'%1' is not a known file format for loading or unloading
tables"

Constant UNSUPPORTED_LOAD_FORMAT

SAP Sybase Error Number 2209

SQL State WL001

SQL Code -601L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The specified format.

Probable Cause An unsupported file format was specified for LOAD TABLE or UN-
LOAD TABLE.

Error 602 "Cannot access file '%1' -- %2"

Constant CANNOT_ACCESS_FILE

SAP Sybase Error Number 2210

110 SAP Sybase IQ

Errors and Warnings

Error 602 "Cannot access file '%1' -- %2"

SQL State WL002

SQL Code -602L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The file name.

Parameter 2 The cause of the error.

Probable Cause A file cannot be accessed. For example, a file referenced by LOAD
TABLE does not exist or cannot be read. The message will contain the
reason for the error.

Error 604 "A dbspace has reached its maximum file size"

Constant DBSPACE_FULL

SAP Sybase Error Number 2213

SQL State 04W07

SQL Code -604L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A dbspace has grown to its maximum number of disk pages, which is
usually limited by the maximum operating system file size. This is a
fatal error.

Error 605 "The server attempted to access a page beyond the end of the
maximum allowable dbspace file size"

Constant ACCESS_BEYOND_END_OF_MAX_DBSPACE

SAP Sybase Error 2214

Number

SQL State 04W08

SQL Code -605L

SAP Sybase IQ Error Messages 111

Errors and Warnings

Error 605 "The server attempted to access a page beyond the end of the
maximum allowable dbspace file size"

SQL State 22W03

SQL Code -608L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You supplied an invalid value as the TEXTPTR for a WRITETEXT or
READTEXT statement.

Error 609 "Invalid data type for column in WRITETEXT or

READTEXT"

Constant INVALID_TEXT_IMAGE_DATATYPE

SAP Sybase Error Number 2218

SQL State 53W09

SQL Code -609L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You referenced a column in a WRITETEXT or READTEXT state-

ment that is not defined for storing text or image data.

Error 610 "User message %1 already exists"

Constant MESSAGE_ALREADY_EXISTS

SAP Sybase Error Number 2064

SAP Sybase IQ Error Messages 113

Errors and Warnings

Error 610 "User message %1 already exists"

SQL State 52W16

SQL Code -610L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Error number of the user message that exists in the database.

Probable Cause The message with this error number already exists in the database.

Error 611 "Transact-SQL feature not supported"

Constant TSQL_FEATURE_NOT_SUPPORTED

SAP Sybase Error Number 2076

SQL State 0AW02

SQL Code -611L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted to use a Transact-SQL feature that is not supported in
SQL Anywhere.

Error 612 "User message %1 not found"

Constant MESSAGE_NOT_FOUND

SAP Sybase Error Number 2097

SQL State 52W17

SQL Code -612L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Message number.

114 SAP Sybase IQ

Errors and Warnings

Error 612 "User message %1 not found"

Probable Cause The message with this error number does not exist in the database.

Error 613 "User-defined type '%1' not found"

Constant USER_TYPE_NOT_FOUND

SAP Sybase Error Number 2098

SQL State 52W18

SQL Code -613L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the user-defined type.

Probable Cause The user-defined type with this name does not exist in the database.

Error 614 "Cannot drop a user that owns messages or data types"

Constant USER_OWNS_MESSAGES_OR_DATATYPES

SAP Sybase Error Number 2099

SQL State 55W05

SQL Code -614L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that is the creator of a message or user-
defined data type. The message or user-defined data type must be
dropped first.

Error 615 "Parameter '%1' not found in procedure '%2'"

Constant INVALID_PARAMETER_NAME

SAP Sybase Error Number 2101

SQL State 42W47

SAP Sybase IQ Error Messages 115

Errors and Warnings

Error 615 "Parameter '%1' not found in procedure '%2'"

SQL Code -615L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the parameter that was not found.

Parameter 2 Name of the procedure where the parameter was not found.

Probable Cause You supplied a procedure parameter name that does not match a
parameter for this procedure. Check the spelling of the parameter
name.

Error 616 "Too many columns in table"

Constant TOO_MANY_COLUMNS_IN_TABLE

SAP Sybase Error Num- 2219

ber

SQL State 52W20

SQL Code -616L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You executed a CREATE TABLE or ALTER TABLE statement that
attempted to add a column to a table. The resulting number of columns in
the table would exceed the limit for the current database page size.

Error 617 "Calling functions outside the database server is not

supported"

Constant EXTERNAL_CALLS_NOT_SUPPORTED

SAP Sybase Error 2220

Number

SQL State WW003

SQL Code -617L

116 SAP Sybase IQ

Errors and Warnings

Error 617 "Calling functions outside the database server is not

supported"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to call a stored procedure that, in turn, calls a function in a
dynamically loaded module. The operating system on which this stored
procedure was called does not support such an action.

Error 618 "Mismatch between external function platform specifier and

current operating system"

Probable Cause This error is usually caused by a failure to load a dynamic library
named in an external function call.

Messages 621 through 640

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 621 "Could not find '%1' in dynamic library '%2'"

Constant COULD_NOT_FIND_FUNCTION

SAP Sybase Error Number 2224

SQL State WW007

SQL Code -621L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 Name of the function that could not be found.

Parameter 2 Name of the dynamic library in which the function could not be
found.

118 SAP Sybase IQ

Errors and Warnings

Error 621 "Could not find '%1' in dynamic library '%2'"

Probable Cause The external function could not be found in the dynamic library.

Error 622 "Could not allocate resources to call external function"

Constant ERROR_CALLING_FUNCTION

SAP Sybase Error Number 2225

SQL State WW008

SQL Code -622L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause The external function could not be called due to a shortage of oper-
ating system resources. If the operating system supports threads, the
maximum thread count should be increased.

Error 623 "Data definition statements not allowed in procedures or

triggers"

Constant DDL_NOT_ALLOWED_IN_PROCEDURES

SAP Sybase Error Num- 2226

ber

SQL State 52W21

SQL Code -623L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause The procedure or trigger definition contains a data definition statement
(such as CREATE, DROP, GRANT, REVOKE, or ALTER). These
statements are not allowed within procedures or triggers.

Error 624 "Expression has unsupported data type"

Constant DATATYPE_NOT_ALLOWED

SAP Sybase IQ Error Messages 119

Errors and Warnings

Error 624 "Expression has unsupported data type"

SAP Sybase Error Num- 2227

ber

SQL State WW009

SQL Code -624L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Either an external function or Java method was declared with a pa-
rameter or result data type that is not supported, or a Java field reference
with an unsupported result type was attempted.

Error 625 "Too many parameters to this external procedure call"

Constant TOO_MANY_PARAMETERS

SAP Sybase Error Number 2228

SQL State WW010

SQL Code -625L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause There is a maximum of 256 parameters to an external function call in

32-bit Windows.

Error 626 "A thread used internally could not be started"

Constant THREAD_START_FAILURE

SAP Sybase Error Number 2229

SQL State WW011

SQL Code -626L

ODBC 2 State ERROR

ODBC 3 State ERROR

120 SAP Sybase IQ

Errors and Warnings

Error 626 "A thread used internally could not be started"

Severity Code 19 on page 2

Probable Cause This is a Windows 95 specific error. An operating system thread could
not be started that is required to execute external functions.

Error 627 "Disallowed language extension detected in syntax near

'%1' on line %2"

Constant INVALID_SYNTAX_EXTENSION

SAP Sybase Error Number 2230

SQL State 0AW03

SQL Code -627L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The word or symbol where the syntax has been detected.

Parameter 2 Line number.

Probable Cause The statement you are trying to execute contains syntax that is not
allowed with the current setting of the option sql_flagger_error_level.
Modify the offending statement or set the sql_flagger_error_level
option to a different value.

Error 628 "Division by zero"

Constant DIV_ZERO_ERROR

SAP Sybase Error Number 2231

SAP Sybase Error Number 2234

SQL State WW012

SQL Code -631L

122 SAP Sybase IQ

Errors and Warnings

Error 631 "RAISERROR executed: %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 RAISERROR message string.

Probable Cause A RAISERROR statement has been executed. The string associated
with the RAISERROR statement is included in the text of the error
message.

Error 632 "WITH CHECK OPTION violated for insert/update on base table
'%1'"

Constant WITH_CHECK_OPTION_VIOLATION

SAP Sybase Error 2235

Number

SQL State 44000

SQL Code -632L

ODBC 2 State S1000

ODBC 3 State 44000

Severity Code 16 on page 2

Parameter 1 Name of the base table being updated.

Probable Cause You attempted an insert or update operation on the indicated base table
through a view (possibly nested). However, one or more values in the modi-
fied row(s) triggered a WITH CHECK OPTION violation. This violation
occurs when a modified value causes one or more rows to fall outside the
range of the view by making the view's WHERE clause evaluate to FALSE or
UNKNOWN for that row.

Error 633 "Update operation attempted on a read-only cursor"

Constant READ_ONLY_CURSOR

SAP Sybase Error Number 2236

SQL State 42W30

SQL Code -633L

SAP Sybase IQ Error Messages 123

Errors and Warnings

Error 633 "Update operation attempted on a read-only cursor"

ODBC 2 State S1009

ODBC 3 State HY092

Severity Code 16 on page 2

Probable Cause You attempted an update operation on a cursor that was explicitly
declared as read-only.

Error 634 "Unterminated C string"

Constant UNTERMINATED_C_STR

SAP Sybase Error Number 2237

SQL State 22024

SQL Code -634L

ODBC 2 State 22024

ODBC 3 State 22024

Severity Code 16 on page 2

Probable Cause The last byte of a C string host variable must contain the null char-
acter.

Error 635 "GRANT of column permission on view not allowed"

Constant NO_COLUMN_PERMS_FOR_VIEWS

SAP Sybase Error Number 2240

SQL State 52W22

SQL Code -635L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You cannot grant permissions on columns for views.

Error 636 "Duplicate referencing column"

Constant DUPLICATE_REFERENCING_COLUMN

124 SAP Sybase IQ

Errors and Warnings

Error 636 "Duplicate referencing column"

SAP Sybase Error Number 2242

SQL State 42W40

SQL Code -636L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You supplied a duplicate column name in the list of referencing col-
umns.

Error 637 "Duplicate insert column"

Constant DUPLICATE_INSERT_COLUMN

SAP Sybase Error Number 2243

SQL State 42W41

SQL Code -637L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You supplied a duplicate column name in the list of insert columns.

Error 638 "Right truncation of string data"

Constant STRING_RIGHT_TRUNCATION

SAP Sybase Error Number 2244

SQL State 22001

SQL Code -638L

ODBC 2 State 22001

ODBC 3 State 22001

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 125

Errors and Warnings

Error 638 "Right truncation of string data"

Probable Cause Non-space characters were truncated upon the assignment of string
data.

Error 639 "Parameter name missing in call to procedure '%1'"

Constant PARAMETER_NAME_MISSING

SAP Sybase Error Number 2245

SQL State 42W42

SQL Code -639L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the procedure.

Probable Cause Positional parameters were specified after named parameters in a call
to this procedure.

Error 640 "Invalid descriptor index"

Constant INVALID_DESCRIPTOR_INDEX

SAP Sybase Error Number 2246

SQL State 07009

SQL Code -640L

ODBC 2 State S1002

ODBC 3 State 07009

Severity Code 26 on page 2

Probable Cause The index number used with respect to a descriptor area is out of
range.

126 SAP Sybase IQ

Errors and Warnings

Messages 641 through 660

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 641 "Error in assignment"

Constant ERROR_IN_ASSIGNMENT

SAP Sybase Error Number 2247

SQL State 22005

SQL Code -641L

ODBC 2 State 22005

ODBC 3 State 22018

Severity Code 20 on page 2

Probable Cause In a GET DESCRIPTOR statement, the data type of the host variable
must correspond to the data type of the descriptor item.

Error 642 "Invalid SQL descriptor name"

Constant INVALID_DESCRIPTOR_NAME

SAP Sybase Error Number 2248

SQL State 33000

SQL Code -642L

ODBC 2 State 33000

ODBC 3 State 33000

Severity Code 21 on page 2

Probable Cause You attempted to deallocate a descriptor that has not been allocated.

Error 643 "UNLOAD TABLE cannot be used to unload a view"

Constant CANNOT_UNLOAD_A_VIEW

SAP Sybase Error Number 2212

SQL State WL004

SQL Code -643L

SAP Sybase IQ Error Messages 127

Errors and Warnings

Error 643 "UNLOAD TABLE cannot be used to unload a view"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause UNLOAD TABLE was specified with the name of a view. UNLOAD
TABLE may only be used to unload tables.

Error 644 "Invalid database page size"

Constant PAGE_SIZE_INVALID

SAP Sybase Error Num- 2032

ber

SQL State 08W32

SQL Code -644L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 14 on page 2

Probable Cause You attempted to create a database with an invalid page size. The page
size for a SQL Anywhere database must be either 2048, 4096, 8192,
16384, or 32768 bytes. The page size for an UltraLite database must be
either 1024, 2048, 4096, 8192, or 16384 bytes.

Error 645 "Database creation failed: %1"

Constant DATABASE_NOT_CREATED

SAP Sybase Error Number 2033

SQL State 08W33

SQL Code -645L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 14 on page 2

Parameter 1 Reason that the database was not created.

Probable Cause Your attempt to initialize a file for a database failed.

128 SAP Sybase IQ

Errors and Warnings

Error 646 "Could not load the store DLL \"%1\No message

Constant STORE_NOT_LOADED

SAP Sybase Error Number 2270

SQL State 08W34

SQL Code -646L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 Name of the store DLL that could not be loaded.

Probable Cause An attempt to load the store DLL failed.

Error 647 "Could not execute store DLL (%1) entry point"

Constant STORE_ENTRY_NOT_FOUND

SAP Sybase Error Number 2271

SQL State 08W35

SQL Code -647L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 Name of the store DLL where the entry point failed.

Probable Cause An attempt to locate or execute the store DLL entry point failed.

Error 648 "Cannot create item (%1) in the specified dbspace"

Constant INVALID_DBSPACE_FOR_CREATE

SAP Sybase Error Num- 2272

ber

SQL State 08W36

SAP Sybase IQ Error Messages 131

Errors and Warnings

Error 653 "Cannot remove class '%1': member of JAR"

SAP Sybase Error Number 2279

Probable Cause The connection string could not be parsed. The string or connection
parameter file contains a syntax error.

Error 656 "Unable to connect to server '%1': %2"

Constant OMNI_CONNECT_ERROR

SAP Sybase Error Number 2282

SQL State WO001

SQL Code -656L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the server that could not be connected to.

Parameter 2 A more specific reason returned from the server class driver.

Probable Cause You attempted to connect to a remote server. Check that the remote
server is running.

Error 657 "Unable to connect, server definition is circular"

Constant OMNI_CIRCULAR_CONNECT

SAP Sybase Error Number 2552

SQL State WO002

SQL Code -657L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to connect to a remote server that maps to the local
database.

SAP Sybase IQ Error Messages 133

Errors and Warnings

Error 658 "Remote server '%1' is currently configured as read-only"

Constant OMNI_READONLY

SAP Sybase Error Number 2284

SQL State WO003

SQL Code -658L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the remote server.

Probable Cause You attempted to perform an update on an object located on a server

that is configured as read-only. Use ALTER SERVER to reconfigure
the remote server to be updatable.

Error 659 "Remote server '%1' could not be found"

Constant OMNI_SERVER_NOT_FOUND

SAP Sybase Error Number 2285

SQL State WO004

SQL Code -659L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of the remote server.

Probable Cause You attempted to define an object on a server that has not been added.
Use CREATE SERVER to add the remote server definition.

Error 660 "Server '%1': %2"

Constant OMNI_REMOTE_ERROR

SAP Sybase Error Number 2286

SQL State WO005

SQL Code -660L

134 SAP Sybase IQ

Errors and Warnings

Error 660 "Server '%1': %2"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the remote server.

Parameter 2 The message from the remote server.

Probable Cause A message was generated by a remote server. The message text is
included."

Messages 661 through 682

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 661 "Backward scrolling cursors are not supported for remote
objects"

Constant OMNI_BACKWARDS_CURSOR

SAP Sybase Error Number 2287

SQL State WO006

SQL Code -661L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Backward scrolling cursors are not supported for remote objects. Use
forward scrolling cursors only.

Error 662 "Cannot serialize Java object with class '%1'"

Constant JAVA_SERIALIZATION_ERROR

SAP Sybase Error Number 2288

SQL State WI009

SQL Code -662L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 135

Errors and Warnings

Error 662 "Cannot serialize Java object with class '%1'"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The class of the value that cannot be serialized.

Probable Cause The Java object cannot be serialized as a persistent database column.

Error 663 "Cannot deserialize Java object"

Constant JAVA_DESERIALIZATION_ERROR

SAP Sybase Error Number 2289

SQL State WW018

SQL Code -663L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The persistent Java object cannot be read from the database column.
Possibly, the class of the object has been removed or modified.

Error 664 "Database is active"

Constant DATABASE_ACTIVE

SAP Sybase Error Number 2290

SQL State 08W40

SQL Code -664L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The attempted operation (CREATE ENCRYPTED, CREATE DE-

CRYPTED, ALTER DATABASE) cannot be performed while the
database is running. Stop the database to perform the operation.

136 SAP Sybase IQ

Errors and Warnings

Error 665 "Database \"%1\" needs recovery"

Constant DATABASE_NEEDS_RECOVERY

SAP Sybase Error Number 2291

SQL State 08W41

SQL Code -665L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 21 on page 2

Parameter 1 The file name of the database that needs recovery.

Probable Cause The database quit abnormally the last time it was used. Database
recovery must be performed before proceeding.

Error 666 "The remote table '%1' could not be found"

Constant OMNI_RMT_TABLE_NOTFOUND

SAP Sybase Error Number 2292

SQL State WO007

SQL Code -666L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The complete name of the remote table.

Probable Cause The table could not be found on the remote server. Check the remote
table name and the user privileges on that table.

Error 667 "Could not access column information for the table '%1'"

Constant OMNI_RMT_COLUMNS_NOTFOUND

SAP Sybase Error Number 2293

SQL State WO008

SQL Code -667L

SAP Sybase IQ Error Messages 137

Errors and Warnings

Error 667 "Could not access column information for the table '%1'"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The complete name of the remote table.

Probable Cause Column information for the table could not be accessed. Check per-
missions for the table.

Error 668 "Cursor is restricted to FETCH NEXT operations"

Constant NO_SCROLL_CURSOR

SAP Sybase Error Num- 2294

ber

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 20 on page 2

Probable Cause Your attempt to upgrade a database failed. This could be caused by a
failure to locate one of the SQL script files used to define the system
table changes.

Error 673 "Database upgrade not possible"

Constant DATABASE_UPGRADE_NOT_POSSIBLE

SAP Sybase Error Number 2299

SQL State 08W43

SAP Sybase IQ Error Messages 139

Errors and Warnings

Error 673 "Database upgrade not possible"

SQL Code -673L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 21 on page 2

Probable Cause An attempt to upgrade a database failed. The database is too old to be
upgraded.

Error 674 "Statement's size limit is invalid"

Constant INVALID_CURSOR_RANGE

SAP Sybase Error Number 2300

SQL State 09W07

SQL Code -674L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause FIRST or TOP n are used in a SELECT statement to limit the size of a
result. The size limit must be a constant integer greater than 0 and less
than 32767.

Error 675 "External environment could not be started, '%1' could not
be found"

Constant EXTENV_NOT_STARTED

SAP Sybase Error Num- 2301

ber

SQL State WP006

SQL Code -675L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

140 SAP Sybase IQ

Errors and Warnings

Error 675 "External environment could not be started, '%1' could not
be found"

Parameter 1 The component (executable or file) that could not be found and is
needed to run the VM.

Probable Cause A problem was encountered starting the External Environment. A

component that is needed to run the environment could not be found.

Error 676 "The specified transaction isolation is invalid"

Constant INVALID_TRANSACTION_ISOLATION

SAP Sybase Error Number 2303

SQL State WJ003

SQL Code -676L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause The specified transaction isolation is invalid.

Error 677 "Table '%1' has a foreign key with a referential action"

Constant TABLE_HAS_REFACTION

SAP Sybase Error Number 2304

SQL State 56001

SQL Code -677L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the table with the referential action.

Probable Cause The table could not be renamed as it has a foreign key with a refer-
ential action. To rename the table, first drop the foreign key con-
straints.

SAP Sybase IQ Error Messages 141

Errors and Warnings

Error 678 "Index name '%1' is ambiguous"

Constant AMBIGUOUS_INDEX_NAME

SAP Sybase Error Number 2305

SQL State 52W40

SQL Code -678L

ODBC 2 State S0011

ODBC 3 State 42S11

Severity Code 16 on page 2

Parameter 1 Name of the ambiguous index.

Probable Cause A statement has referred to an index name that is not unique. Preface
the index name with the table and/or owner name.

Error 680 "Invalid expression in WHERE clause of Transact-SQL outer

join"

Constant INVALID_TSQL_OJ_EXPRESSION

SAP Sybase Error Num- 2307

ber

SQL State 52W23

SQL Code -680L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause An expression in the WHERE clause of a query that uses Transact-SQL
syntax contains a comparison of a column from the NULL-supplying
table with a subquery or an expression that references a column from
another table.

Error 681 "Invalid join type used with Transact-SQL outer join"

Constant INVALID_TSQL_JOIN_TYPE

SAP Sybase Error Number 2308

SQL State 52W24

142 SAP Sybase IQ

Errors and Warnings

Error 681 "Invalid join type used with Transact-SQL outer join"

SQL Code -681L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause An invalid join type was used with a query that contains Transact-
SQL outer join comparison operators.

Error 682 "%1"

Constant OMNI_DEBUG

SAP Sybase Error Number 2309

SQL State WO010

SQL Code -682L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Parameter 1 The debug message for the console.

Probable Cause This message is used for displaying component integration services
debug messages in the messages window.

Messages 683 through 710

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 683 "The cursor name '%1' already exists"

Constant DUPLICATE_CURSOR_NAME

SAP Sybase Error Number 2312

SQL State WJ004

SQL Code -683L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 143

Errors and Warnings

Error 683 "The cursor name '%1' already exists"

Severity Code 16 on page 2

Parameter 1 The name of the cursor.

Probable Cause You attempted to declare a cursor with a name that already exists.
Cursor names must be unique within a connection.

Error 684 "Rollback occurred due to deadlock during prefetch"

Constant ROLLBACK_ON_PREFETCH

SAP Sybase Error 2313

Number

SQL State WW019

SQL Code -684L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 13 on page 2

Probable Cause One of the cursors that was opened with prefetch enabled was performing
fetch operations, and a deadlock occurred during a prefetch. This is a dead-
lock situation and your transaction has been chosen as the one to rollback.
The request that received this error was not executed, unless the request was
to close the cursor, in which case the cursor was closed.

Error 685 "Resource governor for '%1' exceeded"

Constant RESOURCE_GOVERNOR_EXCEEDED

SAP Sybase Error Number 2314

SQL State WP009

SQL Code -685L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The resource whose limit has been exceeded.

144 SAP Sybase IQ

Errors and Warnings

Error 685 "Resource governor for '%1' exceeded"

Probable Cause The resource governor for the stated resource has determined that the
usage of the resource has exceeded its limit.

Error 686 "Insufficient cache to start Java VM"

Constant JAVA_VM_INSUFFICIENT_CACHE

SAP Sybase Error Number 2524

SQL State WP015

SQL Code -686L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Insufficient cache was available to start the Java VM. Restart the
database server with a larger cache size.

Error 687 "Syntax error, cannot specify IQ specific options without

specifying IQ PATH"

Constant IQ_PATH_SYNTAX_ERROR

SAP Sybase Error Number 2072

SQL State 42W48

SQL Code -687L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Error 689 "Input parameter index out of range"

Constant BAD_PARAM_INDEX

SAP Sybase Error Number 2317

SAP Sybase IQ Error Messages 145

Errors and Warnings

Error 689 "Input parameter index out of range"

SQL State WJ005

SQL Code -689L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The range for valid parameters is from 1 up to the number of host
variables specified in the prepared/callable statement.

Error 691 "Could not load the backup/restore DLL \"%1\No message

Constant BACKUP_NOT_LOADED

SAP Sybase Error Number 2319

SQL State 08W44

SQL Code -691L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The name of the DLL that could not be loaded.

Probable Cause An attempt to load the backup/restore DLL failed.

Error 692 "Could not execute backup/restore DLL (%1) entry point"

Constant BACKUP_ENTRY_NOT_FOUND

SAP Sybase Error Number 2320

SQL State 08W45

SQL Code -692L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The name of the entry point that could not be found.

146 SAP Sybase IQ

Errors and Warnings

Error 692 "Could not execute backup/restore DLL (%1) entry point"

Probable Cause An attempt to locate or execute the backup/restore DLL entry point
failed.

Error 697 "Error during backup/restore: %1"

Constant BACKUP_ERROR

SAP Sybase Error Number 2325

SQL State 08W46

SQL Code -697L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 21 on page 2

Parameter 1 A message describing the error that occurred.

Probable Cause An error occurred during a BACKUP or RESTORE statement.

Error 698 "The remote server does not support an auto-

incrementing data type"

Constant OMNI_AUTOINC_NOT_SUPPORTED

SAP Sybase Error Number 2329

SQL State WO011

SQL Code -698L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 12 on page 2

Probable Cause Auto-incrementing data types can only be supported in a proxy table
when the remote server supports this feature.

Error 700 "SQLDA fields inconsistent for a multi-row SQLDA"

Constant SQLDA_INCONSISTENT

SAP Sybase Error Number 2328

148 SAP Sybase IQ

Errors and Warnings

Error 703 "Cannot insert or update computed column '%1'"

Probable Cause Computed column values cannot be modified explicitly. Their value
is determined implicitly from the computed expression value.

Error 704 "Cannot create an index on Java class '%1'"

Constant CANNOT_INDEX_ON_JAVA_CLASS

SAP Sybase Error Number 2332

SQL State WW022

SQL Code -704L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the class.

Probable Cause An operation requiring an index was attempted in which an attempt

was made to create an index on a Java class type.

Error 705 "Return type of void from procedure '%1' cannot be used in
any expression"

Constant PROCEDURE_RETURNS_VOID

SAP Sybase Error Number 2333

SQL State 53019

SQL Code -705L

ODBC 2 State 07006

ODBC 3 State 07006

Severity Code 16 on page 2

Parameter 1 Name of the procedure.

Probable Cause The Java type void does not map onto any SQL type, hence a proce-
dure returning void cannot be used in any SQL expression.

SAP Sybase IQ Error Messages 149

Errors and Warnings

Error 706 "Remote server does not have the ability to support this
statement"

Constant OMNI_SERVER_NOT_CAPABLE

SAP Sybase Error Number 2334

SQL State WO012

SQL Code -706L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to execute a statement that requires a capability that is
not supported by a remote server.

Error 707 "Statement is not allowed in passthrough mode"

Constant STMT_NOT_ALLOWED_IN_PASSTHROUGH

SAP Sybase Error Number 2335

SQL State 0AW05

SQL Code -707L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You tried to execute a statement that cannot be executed while in
passthrough mode. For example, you may have executed a batch
statement.

Error 708 "READTEXT or WRITETEXT statement cannot refer to a

view"

Constant TEXT_OPERATION_ON_VIEW

SAP Sybase Error Number 2336

SQL State 42W50

SQL Code -708L

ODBC 2 State 37000

150 SAP Sybase IQ

Errors and Warnings

Error 708 "READTEXT or WRITETEXT statement cannot refer to a

view"

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause A Transact-SQL READTEXT or WRITETEXT statement cannot

refer to text columns in a view. Replace the view reference with the
name of a base table.

Error 709 "Computed columns are not supported in this database"

Constant COMPUTED_COLUMNS_NOT_SUPPORTED

SAP Sybase Error Num- 2337

ber

SQL State 0AW06

SQL Code -709L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The current database is an older database and does not have catalog
support for computed (materialized) columns. To use this feature, up-
grade your database to the most recent version.

Error 710 "Invalid comparison"

Constant INVALID_COMPARISON

SAP Sybase Error Num- 2338

ber

SQL State 52W25

SQL Code -710L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 151

Errors and Warnings

Error 710 "Invalid comparison"

Probable Cause An attempt was made to compare two arguments that do not support
comparison. For example, it is not valid to compare a Java object with
another Java object, unless the class of the object supports a valid
compareTo method.

Messages 711 through 732

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 711 "Incorrect database store DLL (%1) version"

Constant STORE_VERSION_MISMATCH

SAP Sybase Error Number 2340

SQL State 08W47

SQL Code -711L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The name of the database store DLL.

Probable Cause The database store DLL and server DLL versions do not match.

Error 712 "External login for server '%1' could not be found"

Constant OMNI_EXTLOGIN_NOT_FOUND

SAP Sybase Error Number 2339

SQL State WO013

SQL Code -712L

SAP Sybase Error Number 2346

SQL State WB008

SQL Code -717L

SAP Sybase Error Number 2349

154 SAP Sybase IQ

Errors and Warnings

Error 720 "VALIDATE statement must refer to a base table"

SQL State 42W51

SQL Code -720L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The VALIDATE statement must refer to a local base table; it cannot
refer to a view, an IQ table, or an object on a remote server.

Error 721 "The data type specified for column '%1' is not compatible
with the actual data type"

Constant OMNI_DATATYPE_MISMATCH

SAP Sybase Error Number 2354

SQL State WO015

SQL Code -721L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 12 on page 2

Parameter 1 The name of the column.

Probable Cause The data type of the column specified in the CREATE EXISTING
statement is not compatible with the actual data type of the column in
the remote table.

Error 722 "The column '%1' does not exist in the remote table"

Constant OMNI_NOSUCH_COLUMN

SAP Sybase Error Number 2355

SQL State WO016

SQL Code -722L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 155

Errors and Warnings

Error 722 "The column '%1' does not exist in the remote table"

Severity Code 11 on page 2

Parameter 1 The name of the column.

Probable Cause The column specified in the CREATE EXISTING statement does not
exist in the remote table.

Error 723 "The length specified for column '%1' is different than the
actual length"

Constant OMNI_LENGTH_MISMATCH

SAP Sybase Error Number 2356

SQL State WO017

SQL Code -723L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Parameter 1 The name of the column.

Probable Cause The length of the column specified in the CREATE EXISTING
statement is different than the length of the column in the remote
table.

Error 724 "NULL attribute mismatch for column '%1'"

Constant OMNI_NULL_MISMATCH

SAP Sybase Error Number 2357

SQL State WO018

SQL Code -724L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Parameter 1 The name of the column.

156 SAP Sybase IQ

Errors and Warnings

Error 724 "NULL attribute mismatch for column '%1'"

Probable Cause The NULL attribute of the column specified in the CREATE EX-
ISTING statement differs from the NULL attribute of the actual col-
umn.

Error 725 "Identity attribute mismatch for column '%1'"

Constant OMNI_IDENTITY_MISMATCH

SAP Sybase Error Number 2358

SQL State WO019

SQL Code -725L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Parameter 1 The name of the column.

Probable Cause The identity attribute of the column specified in the CREATE EX-
ISTING statement differs from the identity attribute of the actual
column.

Error 726 "The table specification '%1' identifies more than one
remote table"

Constant OMNI_RMT_TABLE_NOTUNIQUE

SAP Sybase Error Number 2359

SQL State WO020

SQL Code -726L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The complete name of the remote table.

Probable Cause More than one table was found on the remote server for the given table
specification. Add a database or owner name to the specification.

SAP Sybase IQ Error Messages 157

Errors and Warnings

Error 727 "The optimizer was unable to construct a valid access plan"

Constant CANNOT_OPTIMIZE_QUERY

SAP Sybase Error 2362

Number

SQL State WI010

SQL Code -727L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 18 on page 2

Probable Cause The database server was unable to construct a valid access plan for the
given request. This is a SQL Anywhere internal error. If it can be repro-
duced, it should be reported to iAnywhere. You may be able to work
around this problem by modifying the query statement.

Error 728 "Update operation attempted on non-updatable remote query"

Constant NON_UPDATEABLE_EXT_TAB

SAP Sybase Error 2372

Number

SQL State 42W35

SQL Code -728L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted an update or delete operation on a remote table that is cur-
rently not supported. Examples of such operations include positioned up-
dates or deletes and updates or deletes that involve a join between local and
proxy tables. Updates or deletes that involve a join between proxy tables on
different remote servers will also give this error.

Error 729 "The specified foreign key (%1) cannot be enforced"

Constant UNENFORCEABLE_FOREIGN_KEY

158 SAP Sybase IQ

Errors and Warnings

Error 729 "The specified foreign key (%1) cannot be enforced"

SAP Sybase Error Num- 2373

ber

SQL State 23507

SQL Code -729L

ODBC 2 State 23000

ODBC 3 State 23000

Severity Code 16 on page 2

Parameter 1 Name of the foreign key.

Probable Cause You attempted to create a foreign key that cannot be enforced. To be
enforceable, the primary and foreign table for the specified key must
exist on the same server. You can use the UNENFORCED keyword to
create a foreign key specification that is not to be enforced.

Error 730 "Invalid JAR file"

Constant BAD_JAR_FILE

SAP Sybase Error Number 2374

SQL State WP010

SQL Code -730L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A file passed to the INSTALL JAVA statement was not a valid JAR
file.

Error 731 "Cannot drop a user that owns objects involved in

replication"

Constant USER_OWNS_REPLICATED_OBJECTS

SAP Sybase Error Num- 2377

ber

SQL State 55W06

SAP Sybase IQ Error Messages 159

Errors and Warnings

Error 731 "Cannot drop a user that owns objects involved in

replication"

SQL Code -731L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that is the creator of a database object
involved in replication. For example, the user may own a table that is
part of a publication.

Error 732 "Creating remote tables with computed columns is not

supported"

Constant OMNI_COMPUTED_NOT_SUPPORTED

SAP Sybase Error Number 2366

SQL State WO021

SQL Code -732L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 12 on page 2

Probable Cause Computed columns are not supported in CREATE TABLE statements
that specify a remote location.

Messages 733 through 761

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 733 "Number of columns allowing NULLs exceeds limit"

Constant TOO_MANY_NULL_COLUMNS

SAP Sybase Error 2378

Number

SQL State 23504

SQL Code -733L

160 SAP Sybase IQ

Errors and Warnings

Error 733 "Number of columns allowing NULLs exceeds limit"

ODBC 2 State 23000

ODBC 3 State 23000

Severity Code 16 on page 2

Probable Cause You attempted to create or modify a table definition such that the number of
columns that allow NULLS is now more than the limit on such columns.
The limit is a function of database page size and is approximately 8*(page-
size - 30).

Error 734 "Cannot update or delete an all-NULL row from table '%1'"

Constant CANNOT_UPDATE_NULL_ROW

SAP Sybase Error 2379

Number

SQL State 09W08

SQL Code -734L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the table that cannot be modified.

Probable Cause You attempted to modify or delete a row in the specified table, which is part of
the NULL-supplying side of an outer join. However, the cursor is currently
positioned on a derived row that contains an all-NULL row for this table,
which is the result of the failure of one or more ON conditions to evaluate to
TRUE. Verify that the UPDATE or DELETE statement is correct.

Error 735 "Invalid parameter"

Constant INVALID_PARAMETER

SAP Sybase Error Number 2030

SQL State 08W24

SQL Code -735L

ODBC 2 State 08004

ODBC 3 State 08004

SAP Sybase IQ Error Messages 161

Errors and Warnings

Error 735 "Invalid parameter"

Severity Code 18 on page 2

Probable Cause An error occurred while evaluating a parameter.

Error 736 "The data type of column or variable '%1' is not supported"

Constant OMNI_UNSUPPORTED_DATATYPE

SAP Sybase Error Number 2367

SQL State WO022

SQL Code -736L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 12 on page 2

Parameter 1 The name of the column or variable.

Probable Cause The column is defined with a data type that is not supported for remote
tables or the variable is defined with a datatype that is not supported
for using and location clauses.

Error 737 "Signature '%1' does not match procedure parameters"

Constant SIGNATURE_MISMATCH

SAP Sybase Error Number 2382

SQL State 42W54

SQL Code -737L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The value of the signature.

Probable Cause The number of types in the signature must match the number of
procedure parameters. If a DYNAMIC RESULT SETS clause was
specified, the number of dynamic result sets must match the quantity
found in the signature.

162 SAP Sybase IQ

Errors and Warnings

Error 738 "Password must be at least %1 characters"

Constant PASSWORD_TOO_SHORT

SAP Sybase Error Number 2383

SQL State 54W07

SQL Code -738L

ODBC 2 State 37000

ODBC 3 State 54000

Severity Code 14 on page 2

Probable Cause The password is shorter than that allowed by the current min_pass-
word_length option setting.

Error 739 "db_init has not been called or the call to db_init failed"

Constant DB_INIT_NOT_CALLED

SAP Sybase Error Number 2386

SQL State 55W07

SQL Code -739L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The SQLCA passed to a dblib entry point has not been initialized by a
call to db_init or the call to db_init failed.

Error 740 "The communications environment could not be created"

Constant FAILED_TO_CREATE_STREAMS_ENV

SAP Sybase Error Num- 2385

ber

SQL State WW024

SQL Code -740L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 163

Errors and Warnings

Error 740 "The communications environment could not be created"

Severity Code 16 on page 2

Probable Cause The communications environment could not be created. Either there
are insufficient resources to create the environment or the language
resource file cannot be found.

Error 744 "Invalid IQ database command line option or parameter

value: %1"

Constant IQ_INVALID_COMMAND_LINE

SAP Sybase Error Number 2390

SQL State 08W51

SQL Code -744L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 18 on page 2

Parameter 1 The command line option that is invalid.

Probable Cause An invalid command line option was used. The option began with -iq,
but is either invalid or contained a bad parameter.

Error 745 "Cannot initialize IQ memory manager: %1"

Constant IQ_MEMORY_MANAGER_FAILED

SAP Sybase Error Number 2391

SQL State 08W52

SQL Code -745L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 18 on page 2

Parameter 1 A message describing the error that occurred.

Probable Cause System V shared memory was requested but could not be allocated.

164 SAP Sybase IQ

Errors and Warnings

Error 746 "Cannot allocate System V resources"

Constant IQ_SYSTEM_V_FAILURE

SAP Sybase Error Number 2392

SQL State 08W53

SQL Code -746L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 18 on page 2

Probable Cause IQ was unable to allocate System V resources. Delete unused System
V semaphores and shared memory segments or increase operating
system configuration values for these resources.

Error 749 "Feature not available with UltraLite"

Constant NOT_SUPPORTED_IN_ULTRALITE

SAP Sybase Error Number 2395

SQL State 0AW07

SQL Code -749L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to execute a statement or use a feature that is not
supported in an UltraLite database.

Error 750 "User owns procedures in use"

Constant USER_OWNS_PROCEDURES_IN_USE

SAP Sybase Error Number 2396

SQL State 42W55

SQL Code -750L

ODBC 2 State 40001

ODBC 3 State 40001

SAP Sybase IQ Error Messages 165

Errors and Warnings

Error 750 "User owns procedures in use"

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that owns a procedure being used by
other active users of the database.

Error 751 "User owns tables in use"

Constant USER_OWNS_TABLES_IN_USE

SAP Sybase Error Number 2397

SQL State 42W56

SQL Code -751L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Probable Cause You attempted to REVOKE CONNECT from a user that owns a table
being used by other active users of the database.

Error 754 "Parse error: %1"

Constant INVALID_DSN_NAME

SAP Sybase Error Number 2400

SQL State 08W54

SQL Code -754L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 18 on page 2

Parameter 1 The invalid data source name.

Probable Cause An invalid data source name was used in the connection string.

Error 755 "You cannot synchronize or upgrade with uncommitted

transactions"

Constant UNCOMMITTED_TRANSACTIONS

166 SAP Sybase IQ

Errors and Warnings

Error 755 "You cannot synchronize or upgrade with uncommitted

transactions"

SAP Sybase Error Number 2401

SQL State 0AW08

SQL Code -755L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to synchronize or upgrade the schema of an UltraLite

database and there are changes in the UltraLite database that have not
been committed.

Error 757 "Modifications not permitted for read-only database"

Constant READ_ONLY_DATABASE

SAP Sybase Error Number 2404

SQL State 55W08

SQL Code -757L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 14 on page 2

Probable Cause You attempted an update operation on a database that was declared as
read-only.

Error 759 "SQLDA data type invalid"

Constant SQLDA_INVALID_DATATYPE

SAP Sybase Error Number 2406

SQL State 07W05

SQL Code -759L

ODBC 2 State 07001

ODBC 3 State 07W05

SAP Sybase IQ Error Messages 167

Errors and Warnings

Error 759 "SQLDA data type invalid"

Severity Code 16 on page 2

Probable Cause The data type specified for a SQLDA variable is invalid.

Error 760 "Invalid SQL identifier"

Constant INVALID_SQL_IDENTIFIER

SAP Sybase Error Number 2407

SQL State 07W06

SQL Code -760L

ODBC 2 State 07001

ODBC 3 State 07W06

Severity Code 16 on page 2

Probable Cause An invalid identifier was supplied through the C language interface.
For example, you may have supplied a NULL string for a cursor
name.

Error 761 "Server capability name '%1' could not be found in the
database."

Constant CAPABILITY_NOT_FOUND

SAP Sybase Error Number 2343

SQL State WO014

SQL Code -761L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of server capability.

Probable Cause An ALTER SERVER statement was attempted on a capability that

was not defined.

168 SAP Sybase IQ

Errors and Warnings

Messages 764 through 786

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 764 "Server not found and unable to automatically start"

Constant UNABLE_TO_CONNECT_OR_START

SAP Sybase Error Number 2410

SQL State 08W55

SQL Code -764L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Probable Cause The client could not connect to a server, and was unable to automat-
ically start a server. The automatic start may have failed because no
database file was specified.

Error 765 "Synchronization message type '%1' not found"

Constant NOT_SYNC_TYPE

SAP Sybase Error Number 2411

SQL State 5RW11

SQL Code -765L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of synchronization message type.

Probable Cause You referred to a synchronization message type that is not defined in
this database.

Error 766 "View references '%1', which is a temporary object. Views

can only refer to permanent objects"

Constant VIEW_OVER_TEMP_OBJECT

SAP Sybase IQ Error Messages 169

Errors and Warnings

Error 766 "View references '%1', which is a temporary object. Views

can only refer to permanent objects"

SAP Sybase Error Number 2413

SQL State 42U00

SQL Code -766L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Temporary object name.

Probable Cause Views must refer only to permanent objects, not to temporary objects
such as local temporary tables.

Error 767 "Cannot find synchronization subscription with the name

'%1'"

Constant SYNCHRONIZATION_NOT_FOUND

SAP Sybase Error Number 2414

SQL State 5RW12

SQL Code -767L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the subscription.

Probable Cause You misspelled the name of a synchronization subscription or you did
not qualify it correctly with a user name.

Error 768 "Cannot subscribe to '%1'"

Constant CANNOT_SUBSCRIBE

SAP Sybase Error Number 2415

SQL State 5RW13

SQL Code -768L

170 SAP Sybase IQ

Errors and Warnings

Error 768 "Cannot subscribe to '%1'"

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the publication.

Probable Cause Some publications cannot be subscribed to, such as a synchronization

publication.

Error 769 "Cannot modify synchronization entry using ALTER

PUBLICATION"

Constant CANNOT_MODIFY_SYNC_AS_PUB

SAP Sybase Error Number 2416

SQL State 5RW14

SQL Code -769L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Probable Cause You attempted to modify a synchronization entry using an ALTER

PUBLICATION statement.

Error 770 "Cannot modify publication entry using ALTER

SYNCHRONIZATION"

Constant CANNOT_MODIFY_PUB_AS_SYNC

SAP Sybase Error Number 2417

SQL State 5RW15

SQL Code -770L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Probable Cause You attempted to modify a publication entry using an ALTER SYN-
CHRONIZATION statement.

SAP Sybase IQ Error Messages 171

Errors and Warnings

Error 771 "Event '%1' not found"

Constant EVENT_NOT_FOUND

SAP Sybase Error Number 2418

SQL State WE001

SQL Code -771L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of the event that could not be found.

Probable Cause You have attempted to reference an event with a name that does not
exist in the database.

Error 772 "Event '%1' already exists"

Constant EVENT_ALREADY_EXISTS

SAP Sybase Error Number 2419

SQL State WE002

SQL Code -772L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the event that already exists.

Probable Cause You have attempted to create an event with a name that already exists
in the database.

Error 773 "Schedule '%1' for event '%2' not found"

Constant SCHEDULE_NOT_FOUND

SAP Sybase Error Number 2420

SQL State WE003

SQL Code -773L

172 SAP Sybase IQ

Errors and Warnings

Error 773 "Schedule '%1' for event '%2' not found"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of the schedule that could not be found.

Parameter 2 Name of the event being scheduled.

Probable Cause You have attempted to reference a schedule with a name that does not
exist in the database for the named event.

Error 774 "Schedule '%1' for event '%2' already exists"

Constant SCHEDULE_ALREADY_EXISTS

SAP Sybase Error Number 2421

SQL State WE004

SQL Code -774L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the schedule that already exists.

Parameter 2 Name of the event being scheduled.

Probable Cause You have attempted to create a schedule with a name that already
exists in the database for the named event.

Error 777 "Cannot synchronize table '%1' since it does not have a
primary key"

Constant CANNOT_SYNC_TABLE_WITHOUT_PK

SAP Sybase Error Number 2424

SQL State 5RW16

SQL Code -777L

ODBC 2 State 42000

ODBC 3 State 42S02

SAP Sybase IQ Error Messages 173

Errors and Warnings

Error 777 "Cannot synchronize table '%1' since it does not have a
primary key"

Severity Code 16 on page 2

Parameter 1 Name of the table.

Probable Cause Tables being synchronized must contain a primary key.

Error 778 "Must include primary key for table '%1' in the
synchronization"

Constant PK_NOT_IN_SYNC_ARTICLE

SAP Sybase Error Number 2425

SQL State 5RW17

SQL Code -778L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the table.

Probable Cause The primary key of the table must be included in the synchronization
entry.

Error 779 "Cannot create synchronization entry for table '%1' with
BLOB primary key"

Constant BLOB_IN_SYNC_TABLE_PK

SAP Sybase Error Number 2426

SQL State 5RW18

SQL Code -779L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the table.

Probable Cause You attempted to create a synchronization entry on a table with a

BLOB primary key.

174 SAP Sybase IQ

Errors and Warnings

Error 780 "Cannot update primary key for table '%1' involved in a
publication"

Constant ARTICLE_PK_CANNOT_BE_UPDATED

SAP Sybase Error Num- 2427

ber

SQL State 5RW19

SQL Code -780L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the table.

Probable Cause The primary key of a table involved in a publication cannot be updated.
The prevent_article_pkey_update database option can be set to Off to
allow updates to the primary key of the table involved in the publica-
tion.

Error 782 "Cannot register '%1' since another exclusive instance is

running"

Constant SAME_EXCLUSIVE_APP_RUNNING

SAP Sybase Error Number 2429

SQL State 5RW21

SQL Code -782L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the application.

Probable Cause You attempted to start an application, but another exclusive instance
of the same application is already registered.

Error 783 "Cannot register another '%1' as an exclusive application"

Constant SAME_APP_RUNNING

SAP Sybase IQ Error Messages 175

Errors and Warnings

Error 783 "Cannot register another '%1' as an exclusive application"

SAP Sybase Error Number 2430

SQL State 5RW22

SQL Code -783L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the application.

Probable Cause You attempted to register an exclusive application but another in-
stance of the same application is already registered.

Error 784 "Cannot register connection because of invalid

application cookie"

Constant CANNOT_REG_CONN

SAP Sybase Error Number 2431

SQL State 5RW23

SQL Code -784L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Probable Cause Application registration cannot be found for the given cookie.

Error 785 "Cannot deregister application because of invalid cookie"

Constant DEREG_APP_NOT_FOUND

SAP Sybase Error Number 2432

SQL State 5RW24

SQL Code -785L

ODBC 2 State 42000

ODBC 3 State 42S02

176 SAP Sybase IQ

Errors and Warnings

Error 785 "Cannot deregister application because of invalid cookie"

Severity Code 16 on page 2

Probable Cause The application has not been registered successfully or it was previ-
ously deregistered.

Error 786 "Cannot deregister '%1' since active registered

connection exists"

Constant DEREG_APP_IN_USE

SAP Sybase Error Number 2433

SQL State 5RW25

SQL Code -786L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the application.

Probable Cause You attempted to deregister an application while there are still active
connections registered to that application.

787 - 1006

Messages 787 through 810

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 787 "Current connection is already registered to '%1' as '%2'"

Constant CONN_ALREADY_REGISTERED

SAP Sybase Error Number 2434

SQL State 5RW26

SQL Code -787L

ODBC 2 State 42000

ODBC 3 State 42S02

SAP Sybase IQ Error Messages 177

Errors and Warnings

Error 787 "Current connection is already registered to '%1' as '%2'"

Severity Code 16 on page 2

Parameter 1 Name of the application.

Parameter 2 Registered connection label.

Probable Cause You attempted to register this connection more than once.

Error 788 "Another connection has already registered as '%1'"

Constant NOT_UNIQUE_CONN_REG_LABEL

SAP Sybase Error Num- 2435

ber

SQL State 5RW27

SQL Code -788L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Registered connection label.

Probable Cause You attempted to register a connection with a label already in use for
the same application.

Error 789 "Cannot register '%1' since registration cookie exhausted"

Constant APP_REG_COOKIE_EXHAUSTED

SAP Sybase Error Number 2436

SQL State 5RW28

SQL Code -789L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the application.

Probable Cause Cannot register the application until one is unregistered.

178 SAP Sybase IQ

Errors and Warnings

Error 790 "Cannot register connection to '%1' since automatic label

exhausted"

Constant CONN_REG_AUTO_LABEL_EXHAUSTED

SAP Sybase Error Number 2437

SQL State 5RW29

SQL Code -790L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the application.

Probable Cause You may register using a specified label instead.

Error 791 "Invalid day of week or month '%1' for event '%2'"

Constant INVALID_EVENT_DAY

SAP Sybase Error Number 2438

SQL State WE005

SQL Code -791L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Day-of-week name or day-of-month number.

Parameter 2 Name of the event being scheduled.

Probable Cause You have attempted to create a schedule with an invalid day-of-week
name or day-of-month number.

Error 792 "Invalid time '%1' for event '%2'"

Constant INVALID_EVENT_TIME

SAP Sybase Error Number 2439

SQL State WE006

SAP Sybase IQ Error Messages 179

Errors and Warnings

Error 792 "Invalid time '%1' for event '%2'"

SQL Code -792L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Time value.

Parameter 2 Name of the event being scheduled.

Probable Cause You have attempted to create a schedule with an invalid start or stop
time.

Error 793 "Invalid start date/time for event '%1'"

Constant INVALID_EVENT_START

SAP Sybase Error Number 2440

SQL State WE007

SQL Code -793L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Name of the event being scheduled.

Probable Cause You have specified an event starting date that is invalid.

Error 794 "Synchronization server failed to commit the upload"

Constant UPLOAD_FAILED_AT_SERVER

SAP Sybase Error 2441

Number

SQL State 0AW09

SQL Code -794L

ODBC 2 State 37000

ODBC 3 State 42000

180 SAP Sybase IQ

Errors and Warnings

Error 794 "Synchronization server failed to commit the upload"

Severity Code 16 on page 2

Probable Cause You attempted to synchronize an UltraLite database. During the synchro-
nization session, a complete upload stream was sent that could not be com-
mitted to the consolidated database. The reason for the upload failure can be
found in the synchronization log file.

Error 797 "Synchronization option '%1' contains semicolon, equal

sign, curly brace, or is null"

Constant BAD_SYNC_OPTION_VALUE

SAP Sybase Error Number 2444

SQL State 5RW32

SQL Code -797L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 The name of the synchronization option.

Probable Cause You attempted to set a synchronization option with an invalid value.

Error 799 "DTC transactions are not supported on this platform"

Constant DTC_TRANSACTIONS_NOT_SUPPORTED

SAP Sybase Error Number 2446

SQL State 0AW10

SQL Code -799L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You tried to enlist a DTC transaction on a platform that does not
support this feature.

SAP Sybase IQ Error Messages 181

Errors and Warnings

Error 800 "Cannot commit or rollback while enlisted in a transaction"

Constant CANNOT_COMMIT_OR_ROLLBACK_WHILE_ENLISTED

SAP Sybase Error Num- 2447

ber

SQL State 55W09

SQL Code -800

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You tried to explicitly commit or rollback on a connection that is en-
listed in a transaction. You must use the Commit/Abort protocol of the
transaction instead.

Error 801 "Cannot enlist in a transaction while already enlisted in a

transaction"

Constant CANNOT_ENLIST_WHILE_ALREADY_ENLISTED

SAP Sybase Error Number 2448

SQL State 55W10

SQL Code -801L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You tried to enlist a second transaction on a connection that is already
enlisted in a transaction.

Error 802 "Cannot enlist in a transaction with uncommitted data

pending"

Constant CANNOT_ENLIST_WITH_UNCOMMITTED_DATA

SAP Sybase Error Number 2449

SQL State 55W11

SQL Code -802L

182 SAP Sybase IQ

Errors and Warnings

Constant SYNC_OPTION_NOT_FOUND

SAP Sybase Error Number 2452

SQL State 5RW33

SQL Code -805L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 The name of the synchronization option.

Probable Cause You attempted to delete an undefined synchronization option.

Error 806 "System event type '%1' not found"

Constant EVENT_TYPE_NOT_FOUND

SAP Sybase Error Number 2453

SQL State WE008

SQL Code -806L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of the system event type that could not be found.

Probable Cause You have attempted to create an event with a system event type name
that does not exist in the database.

Error 807 "Host variables must not be used within a batch"

Constant HOSTVARS_IN_BATCH

SAP Sybase Error Number 2454

SQL State 07W07

SQL Code -807L

ODBC 2 State ERROR

184 SAP Sybase IQ

Errors and Warnings

Error 807 "Host variables must not be used within a batch"

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You have attempted to execute a batch that contains host variable
references. Host variables are not supported within a batch.

Error 809 "Synchronization option is too long"

Constant SYNC_OPTION_TOO_LONG

SAP Sybase Error Number 2456

SQL State 5RW34

SQL Code -809L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Probable Cause Synchronization option list cannot be longer than the database page
size.

Error 810 "External object '%1' not found"

Constant EXTENV_OBJECT_NOT_FOUND

SAP Sybase Error Number 2457

SQL State 42W57

SQL Code -810L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the Java class or external object.

Probable Cause The Java class or external object with this name does not exist in the
database.

SAP Sybase IQ Error Messages 185

Errors and Warnings

Messages 811 through 830

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 811 "JAR '%1' not found"

Constant JAR_NOT_FOUND

SAP Sybase Error Number 2458

SQL State 42W58

SQL Code -811L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the JAR.

Probable Cause The JAR with this name does not exist in the database.

Error 812 "The SELECT list for the derived table '%1' has no
expression to match '%2'"

Constant NO_MATCHING_SELECT_ITEM

SAP Sybase Error Num- 2459

ber

SQL State 42W59

SQL Code -812L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the derived table.

Parameter 2 Name of the alias for which there is no matching expression.

Probable Cause The specified alias from the derived table's AS clause has no matching
expression from the SELECT statement for that derived table. Ensure
that each SELECT list item has a matching alias in the derived table's
AS clause, and vice-versa.

186 SAP Sybase IQ

Errors and Warnings

Error 813 "FOR UPDATE has been incorrectly specified for a READ ONLY
cursor"

Constant NON_UPDATEABLE_CURSOR

SAP Sybase Error 2460

Number

SQL State 42W36

SQL Code -813L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted to declare a cursor FOR UPDATE on a query that is not
updatable. Queries that contain DISTINCT, GROUP BY, HAVING, IN-
TERSECT, EXCEPT, or UNION, or that contain aggregate functions are
read-only. If the ansi_update_constraints option is on, then queries that
contain a join are read-only. If the query references a view then the view may
be non-updatable.

Error 814 "Cannot update column '%1' since it appears in the ORDER
BY clause"

Constant CANNOT_UPDATE_ORDER_BY_COLUMN

SAP Sybase Error Number 2461

SQL State 42W37

SQL Code -814L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the column that appears in the ORDER BY clause.

Probable Cause You attempted to update a column that appears in the ORDER BY
clause. The ansi_update_constraints option controls whether this up-
date is allowed.

SAP Sybase IQ Error Messages 187

Errors and Warnings

Error 815 "Cannot update column '%1' since it does not appear in the
SELECT clause"

Constant UPDATE_NOT_IN_SELECT

SAP Sybase Error Num- 2462

ber

SQL State 42W38

SQL Code -815L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the column that does not appear in the SELECT clause.

Probable Cause You attempted to update a column that does not explicitly appear in the
SELECT list. The ansi_update_constraints option controls whether
this update is allowed.

Error 816 "Specified database file already in use"

Constant FILE_IN_USE

SAP Sybase Error Number 2463

SQL State 08W56

SQL Code -816L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 14 on page 2

Probable Cause The database server could not start the specified database because the
file is already in use.

Error 817 "Too many temporary tables in connection"

Constant TOO_MANY_TEMP_TABLES

SAP Sybase Error 2464

Number

SQL State 52W41

188 SAP Sybase IQ

Errors and Warnings

Error 817 "Too many temporary tables in connection"

SQL Code -817L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A CREATE TABLE or DECLARE LOCAL TEMPORARY TABLE state-

ment attempted to create a temporary table, but the resulting number of
distinct table IDs used for temporary tables in the current connection would
exceed the limit.

Error 818 "Version 'V%1' interface used by external function call '%2' is not
supported for execution in the current context."

Constant INCOMPATIBLE_EXTERNAL_CALL

SAP Sybase Error 2465

Number

SQL State WW026

SQL Code -818L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 API version of the external function that is being called.

Parameter 2 Name of the external function that is being called.

Probable Cause You attempted to call an external function. The attempt to load the associated
library failed because of incompatibility with the server. Incompatibility may
arise because the dynamic library is using an external function API that is
either not supported by the server or is newer than the one supported by the
server. It may also arise if the external API is not compatible with the data in
the current context.

Error 819 "Table '%1' is part of a synchronization subscription and

can only be ALTERed within a synchronization schema
change"

Constant SYNC_CONTAINS_TABLE

SAP Sybase IQ Error Messages 189

Errors and Warnings

Error 819 "Table '%1' is part of a synchronization subscription and

can only be ALTERed within a synchronization schema
change"

SAP Sybase Error Number 2466

SQL State 5RW35

SQL Code -819L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 The name of the table.

Probable Cause A table belonging to a synchronization subscription cannot be altered

except within a synchronization schema change or by using
dbmlsync.

Error 820 "Invalid scroll position '%1'"

Constant INVALID_POSITION

SAP Sybase Error Number 2467

SQL State 24504

SQL Code -820L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The scroll position that is invalid.

Probable Cause You attempted to scroll to a position that is not supported. Scroll
positions must be between -2147483647 and 2147483646.

Error 821 "Dbspace for table '%1' not found"

Constant DBSPACE_FOR_TABLE_UNAVAILABLE

SAP Sybase Error Num- 2468

ber

SQL State 52W19

190 SAP Sybase IQ

Errors and Warnings

Error 821 "Dbspace for table '%1' not found"

SQL Code -821L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of the table whose dbspace could not be found.

Probable Cause You tried to access a table in a dbspace that the database server could
not find. You may need to change the file name associated with the
dbspace using the ALTER DBSPACE statement.

Error 822 "Table '%1' is already included"

Constant TABLE_ALREADY_INCLUDED

SAP Sybase Error Number 2469

SQL State 5RW36

SQL Code -822L

ODBC 2 State 42000

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 The name of the table.

Probable Cause You attempted to add or modify a publication or synchronization

definition such that the same table is included twice.

Error 823 "Cannot handle expressions involving remote tables

inside stored procedures"

Constant OMNI_EXPRESSION_IN_PROC

SAP Sybase Error Number 2470

SQL State WO023

SQL Code -823L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 191

Errors and Warnings

Error 823 "Cannot handle expressions involving remote tables

inside stored procedures"

Severity Code 12 on page 2

Probable Cause The server encountered an expression involving remote tables inside
a stored procedure. The expression was too complicated to process.

Error 824 "Illegal reference to correlation name '%1'"

Constant INVALID_CORRELATION_NAME_REFERENCE

SAP Sybase Error Number 2471

SQL State 42U01

SQL Code -824L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 15 on page 2

Parameter 1 The correlation name that is incorrectly referenced.

Probable Cause Your query contains a reference in a table expression to a correlation

name that is not contained in that table expression.

Error 825 "Previous error lost before RESIGNAL"

Constant PREVIOUS_ERROR_LOST

SAP Sybase Error Num- 2472

ber

SQL State WP011

SQL Code -825L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A RESIGNAL statement in an exception handler of a stored procedure

was executed but the context of the previous error was unavailable. A
possible cause of this error is a SELECT statement that returns a result
set in the exception handler.

192 SAP Sybase IQ

Errors and Warnings

Error 826 "Database upgrade not possible; RowGenerator table not

owned by user dbo"

Constant DBO_DOES_NOT_OWN_ROWGENERATOR

SAP Sybase Error Num- 2473

ber

SQL State 08W57

SQL Code -826L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 21 on page 2

Probable Cause An attempt to upgrade a database failed. The RowGenerator table is

not owned by user dbo.

Error 827 "Database upgrade not possible; user tables have table
IDs in system table range"

Constant USER_TABLES_IN_SYSTEM_RANGE

SAP Sybase Error Number 2474

SQL State 08W58

SQL Code -827L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 21 on page 2

Probable Cause An attempt to upgrade a database failed. User table IDs should not be
in system table ID range.

Error 828 "A conflict with the dbmlsync download phase was
detected"

Constant RECORDING_CONFLICT_DETECTED

SAP Sybase Error Number 2475

SQL State WW027

SQL Code -828L

SAP Sybase IQ Error Messages 193

Errors and Warnings

Error 828 "A conflict with the dbmlsync download phase was
detected"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Probable Cause Dbmlsync uses this error to detect download phase conflicts with
rows modified by other connections.

Error 829 "TLS handshake failure"

Constant TLS_HANDSHAKE_FAILED

SAP Sybase Error Number 2476

SQL State 08W59

SQL Code -829L

ODBC 2 State 08S01

ODBC 3 State 08S01

Severity Code 21 on page 2

Probable Cause The connection failed because of a failure in the TLS handshaking
process.

Error 830 "Alias '%1' is not unique"

Constant ALIAS_NOT_UNIQUE

SAP Sybase Error Number 2477

SQL State 42W60

SQL Code -830L

ODBC 2 State 37000

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Name of the alias.

Probable Cause The same alias is used more than once in a SELECT list.

194 SAP Sybase IQ

Errors and Warnings

Messages 831 through 855

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 831 "Definition for alias '%1' must appear before its first
reference"

Constant ALIAS_NOT_YET_DEFINED

SAP Sybase Error Number 2478

SQL State 42W61

SQL Code -831L

ODBC 2 State 37000

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Name of the alias.

Probable Cause An expression contains a reference to an alias, but the alias is defined
later in the SELECT list. The alias definition must appear before its
first reference.

Error 832 "Connection error: %1"

Constant CONNECTION_ERROR

SAP Sybase Error 2479

Number

SQL State 08W60

SQL Code -832L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 Description of the connection error.

SAP Sybase IQ Error Messages 195

Errors and Warnings

Error 832 "Connection error: %1"

Probable Cause An error occurred while attempting to establish a connection with the
database server, but before attempting to connect to a database. Failure to
initialize a communication link during the connection attempt is an exam-
ple of this error. Creating a debug log file using the LogFile connection
parameter may provide more information.

Error 833 "Row in table '%1' was modified or deleted in BEFORE

trigger"

Constant ROW_REMODIFIED_OR_DELETED

SAP Sybase Error Num- 2480

ber

SQL State 42W62

SQL Code -833L

ODBC 2 State 37000

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the table.

Probable Cause A BEFORE trigger has updated or deleted the row that caused the
trigger to fire, preventing the original operation from completing. The
trigger must be re-written so that it does not attempt to change the row
via UPDATE or DELETE statements.

Error 834 "Column '%1' not found in table '%2'"

Constant COLUMN_NOT_FOUND_IN_TABLE

SAP Sybase Error Num- 2083

ber

SQL State 52005

SQL Code -834L

ODBC 2 State S0002

ODBC 3 State 42S22

Severity Code 11 on page 2

196 SAP Sybase IQ

Errors and Warnings

Error 834 "Column '%1' not found in table '%2'"

Parameter 1 Name of the column that could not be found.

Parameter 2 Name of the table that was supposed to contain the column.

Probable Cause You misspelled the name of a column, or the column you are looking
for is in a different table.

Error 835 "Event '%1' in use"

Constant EVENT_IN_USE

SAP Sybase Error Number 2482

SQL State WE009

SQL Code -835L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the event that is in use.

Probable Cause You have attempted to drop an event that is currently in use.

Error 836 "Procedure '%1' is no longer valid"

Constant PROCEDURE_NO_LONGER_VALID

SAP Sybase Error Num- 2483

ber

SQL State 42W63

SQL Code -836L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the procedure.

Probable Cause A procedure definition cannot be loaded from the catalog. Check for
tables or columns that have been renamed or that may be reserved words.
If this procedure is an internal procedure, you may have an older version.
Database upgrade may be needed to run it successfully.

SAP Sybase IQ Error Messages 197

Errors and Warnings

Error 837 "Trigger or foreign key for table '%1' is no longer valid"

Constant TRIGGER_NO_LONGER_VALID

SAP Sybase Error Num- 2484

ber

SQL State 42W64

SQL Code -837L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the table.

Probable Cause A trigger definition cannot be loaded from the catalog. Check for tables
or columns that have been renamed or that may be reserved words. The
trigger may be a system-generated trigger to enforce the referential
actions of a foreign key.

Error 838 "TLS initialization on server failed"

Constant TLS_INIT_FAILED_ON_SRV

SAP Sybase Error Number 2485

SQL State 08W61

SQL Code -838L

ODBC 2 State 08S01

ODBC 3 State 08S01

Severity Code 21 on page 2

Probable Cause The connection failed because the initialization of the TLS library on
the server failed.

Error 839 "Download failed because of conflicts with existing rows"

Constant DOWNLOAD_CONFLICT

SAP Sybase Error 2486

Number

SQL State 0AW11

198 SAP Sybase IQ

Errors and Warnings

Error 839 "Download failed because of conflicts with existing rows"

SQL Code -839L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause During synchronization, there was a conflict between one or more rows in
the download stream and rows modified locally in the UltraLite database.
The download has been rolled back. You can avoid this error by coordi-
nating local database modifications with synchronization, or synchroniz-
ing again when the local modifications are complete.

Error 840 "Incorrect or missing encryption key"

Constant BAD_ENCRYPTION_KEY

SAP Sybase Error Number 2487

SQL State 08W62

SQL Code -840L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 21 on page 2

Probable Cause The database is encrypted with a key. There was no key given to start
the database, or the specified key was incorrect.

Error 843 "Cannot find synchronization user with the name '%1'"

Constant SYNC_SITE_NOT_FOUND

SAP Sybase Error Number 2490

SQL State 5RW37

SQL Code -843L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 16 on page 2

Parameter 1 Name of the synchronization user.

SAP Sybase IQ Error Messages 199

Errors and Warnings

Error 843 "Cannot find synchronization user with the name '%1'"

Probable Cause You misspelled the name of a synchronization site or you did not
qualify it correctly with a user name.

Error 845 "Owner '%1' used in a qualified column reference does not
match correlation name '%2'"

Constant INVALID_COLUMN_QUALIFICATION

SAP Sybase Error 2492

Number

SQL State 42U02

SQL Code -845L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 15 on page 2

Parameter 1 The owner name specified in the column reference.

Parameter 2 The correlation name that is incorrectly referenced.

Probable Cause Your query contains a qualified column reference to a table name, but
either a correlation name has been used for that table, or the owner of the
table does not match the owner name specified in the column reference.
Remove the owner qualification, and qualify column references only by
correlation name.

Error 846 "SET clause for column '%1' used incorrectly"

Constant INVALID_SET_CLAUSE

SAP Sybase Error Number 2493

SQL State 42U03

SQL Code -846L

ODBC 2 State S0002

ODBC 3 State 42S03

Severity Code 15 on page 2

Parameter 1 The SET clause that is invalid.

200 SAP Sybase IQ

Errors and Warnings

Error 846 "SET clause for column '%1' used incorrectly"

Probable Cause Your UPDATE statement contains an invalid SET clause, for exam-
ple, there are multiple SET clauses for the same column.

Error 849 "Referential integrity actions other than RESTRICT not

allowed for temporary tables"

Constant INVALID_FOREIGN_KEY_ACTION

SAP Sybase Error Number 2496

SQL State 42R01

SQL Code -849L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to specify an unsupported referential integrity action

for a temporary table.

Error 850 "Tables related by key constraint must both be permanent, or

both be temporary and not created with ON COMMIT DELETE
ROWS. For global temporary tables they must both be shared if
one is shared."

Constant INVALID_FOREIGN_KEY_TABLE

SAP Sybase Error 2497

Number

SQL State 42R02

SQL Code -850L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause Tables involved in a key constraint relationship must both be permanent user
tables or both be temporary tables not created with ON COMMIT DELETE
ROWS. Change the definition of one or both tables using ALTER TABLE.

SAP Sybase IQ Error Messages 201

Errors and Warnings

Error 851 "Decryption error: %1"

Constant DECRYPT_ERROR

SAP Sybase Error Number 2498

SQL State 08W63

SQL Code -851L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Description of the error that occurred.

Probable Cause An error occurred during decryption.

Error 852 "Table name '%1' is ambiguous"

Constant AMBIGUOUS_TABLE_NAME

SAP Sybase Error Number 2499

SQL State 52W42

SQL Code -852L

ODBC 2 State S0013

ODBC 3 State 42S13

Severity Code 16 on page 2

Parameter 1 Name of an ambiguous table.

Probable Cause A statement has referred to a table name that is not unique. Preface the
table name by an owner name.

Error 853 "Cursor not in a valid state"

Constant CURSOR_INVALID_STATE

SAP Sybase Error 2501

Number

SQL State 24000

SQL Code -853L

202 SAP Sybase IQ

Errors and Warnings

Error 853 "Cursor not in a valid state"

ODBC 2 State 24000

ODBC 3 State 24000

Severity Code 16 on page 2

Probable Cause You attempted to use a cursor that is not in a valid state for the attempted
operation. For example, the cursor may have encountered an error. In
UltraLite, this error occurs if you attempt to set parameters for a prepared
statement while a result set (cursor) is open for the statement.

Error 854 "Function or column reference to '%1' in the ORDER BY

clause is invalid"

Constant INVALID_ORDERBY_COLUMN

SAP Sybase Error Num- 2502

ber

SQL State 42W65

SQL Code -854L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the column referenced directly, or in an expression, in the

ORDER BY clause.

Probable Cause You specified a function or column reference in the ORDER BY clause
that is semantically invalid. For example, for DISTINCT queries the
ORDER BY clause may only refer to items in the query's SELECT list.

Error 855 "Trigger name '%1' is ambiguous"

Constant AMBIGUOUS_TRIGGER_NAME

SAP Sybase Error Number 2503

SQL State 42W66

SQL Code -855L

ODBC 2 State 37000

ODBC 3 State 42000

SAP Sybase IQ Error Messages 203

Errors and Warnings

Error 855 "Trigger name '%1' is ambiguous"

Severity Code 16 on page 2

Parameter 1 Name of the ambiguous trigger.

Probable Cause A statement has referred to a trigger name that is not unique. Qualify
the trigger name with the table and/or owner name.

Messages 856 through 877

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 856 "Invalid sqllen field in SQLDA"

Constant INVALID_SQLLEN

SAP Sybase Error Number 2504

SQL State 07W08

SQL Code -856L

ODBC 2 State HY090

ODBC 3 State HY090

Severity Code 16 on page 2

Probable Cause An invalid length was specified in a SQLDA sqllen field. All variable
length types must have a non-negative length. The DT_BINARY and
DT_VARCHAR types must have length greater than one.

Error 857 "Synchronization failed due to an error on the server: %1"

Constant SERVER_SYNCHRONIZATION_ERROR

SAP Sybase Error Number 2505

SQL State 0AW12

SQL Code -857L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The description of the error from the server.

204 SAP Sybase IQ

Errors and Warnings

Error 857 "Synchronization failed due to an error on the server: %1"

Probable Cause Synchronization failed at the server. More details can be found in the
synchronization log file.

Error 858 "CREATE/DROP STATISTICS statement cannot refer to virtual

tables"

Constant HISTOGRAMS_NOT_SUPPORTED_ON_OBJECT

SAP Sybase Error 2506

Number

SQL State 42W67

SQL Code -858L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to use CREATE/DROP STATISTICS to create/drop one or

more histograms on a virtual database object, such as a view or remote table.
The CREATE STATISTICS and DROP STATISTICS statements can only
refer to base tables, local temporary tables, or global temporary tables in the
SQL Anywhere database that you are connected to.

Error 860 "At least one of the specified dbspaces was not calibrated"

Constant DBSPACE_NOT_CALIBRATED

SAP Sybase Error Number 2509

SQL State WW028

SQL Code -860L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to calibrate a dbspace that was not open or was too
small.

SAP Sybase IQ Error Messages 205

Errors and Warnings

Error 861 "Aggregated expression '%1' contains multiple columns of

which one or more are outer references"

Constant MULTIPLE_AGGREGATE_COLUMNS

SAP Sybase Error Num- 2510

ber

SQL State 42W68

SQL Code -861L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 The aggregated expression in error.

Probable Cause A subselect within the nested query contains an aggregate function
whose parameters include an outer reference. In such cases, the outer
reference must be the only column referenced in the expression.

Error 862 "The aggregate expression '%1' must appear in either the
SELECT list or a HAVING clause subquery"

Constant INVALID_AGGREGATE_PLACEMENT

SAP Sybase Error Num- 2511

ber

SQL State 42W69

SQL Code -862L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 The aggregated expression in error.

Probable Cause An aggregated expression containing an outer reference must either ap-
pear in a SELECT list expression (a subselect), or in a HAVING clause
subquery in the query whose FROM clause contains the table with the
column being aggregated.

206 SAP Sybase IQ

Errors and Warnings

Error 863 "Grouped query contains more than one distinct aggregate
function"

Constant INVALID_DISTINCT_AGGREGATE

SAP Sybase Error Num- 2512

ber

SQL State 42W70

SQL Code -863L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause Two or more DISTINCT aggregate functions were specified in the same
grouped query. This is only permitted if the Hash Group By operator is
available. Any query block can only contain at most one DISTINCT
aggregate function if the Hash Group By operator is not available.

Error 864 "Statement contains an illegal usage of the NUMBER(*)

function"

Constant INVALID_NUMBER

SAP Sybase Error Number 2514

SQL State 42W71

SQL Code -864L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause The NUMBER and IDENTITY functions can only appear in the
SELECT list of the outer-most SELECT block. It cannot be used in
any subquery or in a predicate.

Error 865 "Key constraint between temporary tables requires a primary

key (not unique constraint)"

Constant INVALID_FOREIGN_KEY_INDEX

SAP Sybase IQ Error Messages 207

Errors and Warnings

Error 865 "Key constraint between temporary tables requires a primary

key (not unique constraint)"

SAP Sybase Error Num- 2515

ber

SQL State 42R03

SQL Code -865L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The key constraint between temporary tables requires a primary key (not
a UNIQUE constraint) if the database uses combined indexes. Change
the definition of the primary table using ALTER TABLE or rebuild the
database.

Error 866 "%1 returned a result set with a different schema than
expected"

Constant BAD_RESULT_SET

SAP Sybase Error 2516

Number

SQL State WP012

SQL Code -866L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 12 on page 2

Parameter 1 Name of the procedure that returned the incorrect result set.

Probable Cause When calling a procedure in the FROM clause of a SELECT statement, the
expected schema of the result is taken from the WITH clause. If no WITH
clause is given, the expected schema is taken from the system catalog. The
result set returned from the call must match the expected schema or it must
be possible to convert every column so that it matches.

208 SAP Sybase IQ

Errors and Warnings

Error 867 "Cannot change synchronization user_name when status of

the last upload is unknown"

Constant CANNOT_CHANGE_USER_NAME

SAP Sybase Error 2517

Number

SQL State 0AW13

SQL Code -867L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The MobiLink server uses the user_name to track synchronizations. If the
status of the previous upload is unknown then you must resolve this con-
dition before changing the user.

Error 868 "'%1' is an unknown character set encoding label"

Constant UNKNOWN_CHARSET

SAP Sybase Error Number 2518

SQL State WC001

SQL Code -868L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The character set encoding label that is not recognized.

Probable Cause The specified character set label is not recognized, so conversion
from/to that character set is not possible.

Error 869 "Database server cannot convert data from/to character

set '%1'"

Constant UNSUPPORTED_CHARACTER_SET_ERROR

SAP Sybase Error Number 2519

SQL State 08W64

SAP Sybase IQ Error Messages 209

Errors and Warnings

Error 869 "Database server cannot convert data from/to character

set '%1'"

SQL Code -869L

ODBC 2 State 08S01

ODBC 3 State 08S01

Severity Code 21 on page 2

Parameter 1 Name of the requested character set.

Probable Cause The database server cannot convert character data from/to the char-
acter set requested by the application because the character set is not
supported. The connection fails.

Error 870 "Cannot convert between requested character set '%1' and
database character set '%2'"

Constant FAILED_TO_START_CONVERTER

SAP Sybase Error 2520

Number

SQL State WC002

SQL Code -870L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the requested character set encoding.

Parameter 2 The name of the database character set encoding.

Probable Cause The server is unable to convert between the connection character set that
was specified and the database character set. This could happen when the
dbicu and dbicudt DLLs are not installed.

Error 872 "%1 does not return a result set"

Constant NO_RESULT_SET

SAP Sybase Error Number 2522

SQL State WP014

Probable Cause Unnamed columns cannot be used as XML element or attribute names.
Unnamed JSON columns can only be used within the top-level SELECT
where the tag and parent are defined. In this context, the unnamed column is
a directive to generate a JSON value rather than a JSON object for the given
column. Name unnamed columns in the SELECT list by using AS.

Error 875 "There is no way to join to '%1'"

Constant CANNOT_JOIN_TABEXPR

SAP Sybase Error 2527

Number

SQL State 42W73

SQL Code -875L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of table or view that cannot be joined.

Probable Cause The server cannot discover a valid join condition involving this table. If the
join is an outer join, you may be missing an ON clause. If the join is a KEY
JOIN, the server cannot discover a foreign key-primary key relationship with
this table that can be used to generate the join condition. If the join is a
NATURAL JOIN, the table has no common column names with the table
expression it is being joined to.

Error 876 "Client out of memory"

Constant CLIENT_OUT_OF_MEMORY

SAP Sybase Error Number 2528

SQL State 08W65

SQL Code -876L

ODBC 2 State S1001

ODBC 3 State HY001

212 SAP Sybase IQ

Errors and Warnings

Error 876 "Client out of memory"

Severity Code 17 on page 2

Probable Cause A failure occurred when the database client was trying to allocate
memory.

Error 877 "SETUSER not allowed in procedures, triggers, events, or

batches"

Constant SETUSER_NOT_IN_PROCEDURES

SAP Sybase Error Number 2534

SQL State 42W09

SQL Code -877L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The SETUSER statement is not allowed in stored procedures, triggers,
event handlers, or batches, and cannot be called from an EXECUTE
IMMEDIATE statement.

Messages 878 through 902

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 878 "Index '%1' cannot be clustered"

Constant CLUSTERED_INDEX_NOT_ALLOWED

SAP Sybase Error Number 2535

SQL State 42W74

SQL Code -878L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the index that could not be made clustered.

SAP Sybase IQ Error Messages 213

Errors and Warnings

Error 878 "Index '%1' cannot be clustered"

Probable Cause You attempted to create a clustered index (including key indexes) but
the new index cannot be created, for example, because the table al-
ready has a clustered index.

Error 879 "An invalid multi-byte input character was encountered

when converting from %1 to %2"

Constant ILLEGAL_MULTIBYTE_ERROR

SAP Sybase Error Number 2536

SQL State WC003

SQL Code -879L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The character set of the input string.

Parameter 2 The character set of the output string.

Probable Cause While the server was performing character set conversion on an input
string, an invalid multi-byte character was encountered. The opera-
tion was aborted.

Error 881 "Character substitution was required when converting

from %1 to %2"

Constant SIMPLE_SUBSTITUTION_ERROR

SAP Sybase Error Number 2540

SQL State WC005

SQL Code -881L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The character set of the input string.

Parameter 2 The character set of the output string.

214 SAP Sybase IQ

Errors and Warnings

Error 881 "Character substitution was required when converting

from %1 to %2"

Probable Cause While the server was performing character set conversion on an input
string, some characters could not be represented in the database char-
acter set. The operation was aborted. See on_charset_conversion_fail-
ure option.

Error 883 "Character conversion error or warning report is not available

when the single-byte converter is used"

Constant CHARACTER_CONVERSION_REPORT_NOT_AVAILABLE

SAP Sybase Error 2544

Number

SQL State WC007

SQL Code -883L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to set the on_charset_conversion_failure option to pro-

duce either a warning or error report. This setting is not available when the
single-byte to single-byte converter is used.

Error 887 "Virtual index creation with more than %1 columns"

Constant TOO_MANY_VIRTUAL_INDEX_COLUMNS

SAP Sybase Error Number 2548

SQL State 54W50

SQL Code -887L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The maximum number of virtual index columns.

Probable Cause You attempted to create a virtual index with more than the maximum
number of columns.

SAP Sybase IQ Error Messages 215

Errors and Warnings

Error 888 "XML parser error: %1"

Constant XML_PARSER_ERROR

SAP Sybase Error Number 2550

SQL State WX002

SQL Code -888L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The error message returned by the XML parser.

Probable Cause An XML instance will only parse correctly if it is well-formed as

defined by the XML 1.0 specification.

Error 889 "Statement contains an illegal usage of the non-deterministic

function '%1'"

Constant NONDETERMINISTIC_FUNCTION

SAP Sybase Error 2551

Number

SQL State 42W79

SQL Code -889L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 The name of the non-deterministic user-defined function used in error.

Probable Cause Non-deterministic functions cannot appear in a CHECK constraint, or any

other type of integrity constraint. They may appear anywhere within a
query, view, or derived table. However, if an aliased SELECT list expres-
sion contains a non-deterministic function, that alias cannot be referred to
elsewhere in the query.

Error 890 "Statement size or complexity exceeds server limits"

Constant SYNTACTIC_LIMIT

216 SAP Sybase IQ

Errors and Warnings

Error 890 "Statement size or complexity exceeds server limits"

SAP Sybase Error 2553

Number

SQL State 54W01

SQL Code -890L

ODBC 2 State 37000

ODBC 3 State 54000

Severity Code 19 on page 2

Probable Cause The statement contains one or more constructs whose size make it impossible
to process. Increasing the maximum cache size, page size, or stack size may
resolve this error. Consider rewriting the query so that the internal limit is not
exceeded. For example, if the query contains a large IN-list, consider inserting
the IN-list's values into a temporary table. Then rewrite the query to join this
temporary table to the other table(s) in the original statement.

Error 891 "Cannot convert between requested character sets '%1' and
'%2'"

Constant FAILED_TO_START_CONVERTER_2_CHARSETS

SAP Sybase Error 2554

Number

SQL State WC008

SQL Code -891L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the first requested character set encoding.

Parameter 2 The name of the second requested character set encoding.

Probable Cause The server is unable to convert between the two specified character sets.
This could happen when the dbicu and dbicudt DLLs are not installed.

Error 892 "XPath parser error: %1"

Constant XQUERY_PARSER_ERROR

SAP Sybase IQ Error Messages 217

Errors and Warnings

Error 892 "XPath parser error: %1"

SAP Sybase Error Number 2555

Probable Cause You tried to get the execution plan for a statement type that is not
supported.

Error 895 "Encryption error: %1"

Constant ENCRYPT_ERROR

SAP Sybase Error Number 2558

SQL State 08W66

SQL Code -895L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Description of the error that occurred.

Probable Cause An error occurred during encryption.

Error 896 "Cannot delete PUBLIC option '%1' since user settings
exist"

Constant UNSET_PUBLIC_ID

SAP Sybase Error Number 2560

SQL State 42W82

SQL Code -896L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the option.

Probable Cause You tried to delete a PUBLIC option, but there are user settings for the
same option. The user settings must be deleted before the PUBLIC
option is deleted.

SAP Sybase IQ Error Messages 219

Errors and Warnings

Error 897 "Illegal tag value: '%1'"

Constant BAD_FOR_XML_EXPLICIT_TAG

SAP Sybase Error Number 2563

SQL State WX005

SQL Code -897L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The illegal tag value.

Probable Cause FOR XML EXPLICIT and FOR JSON EXPLICIT tag values must be
greater than 0 and less than 256. NULL values are not allowed in the
Tag column.

Error 898 "Unknown FOR XML EXPLICIT directive: '%1'"

Constant BAD_FOR_XML_EXPLICIT_DIRECTIVE

SAP Sybase Error Number 2564

SQL State WX006

SQL Code -898L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The unknown directive.

Probable Cause Legal FOR XML EXPLICIT directives are: id, idref, idrefs, hide,
element, xml, and cdata. Legal FOR JSON EXPLICIT directives are:
hide, and element.

Error 899 "Illegal column name: '%1'"

Constant BAD_FOR_XML_EXPLICIT_COLUMN_NAME

SAP Sybase Error Number 2565

SQL State WX007

220 SAP Sybase IQ

Errors and Warnings

Error 899 "Illegal column name: '%1'"

SQL Code -899L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The reason the column name was illegal.

Probable Cause FOR XML EXPLICIT and FOR JSON EXPLICIT column names can
consist of up to four fields separated by exclamation marks. The first
two columns must be named Tag and Parent.

Error 900 "Parent not open: '%1'"

Constant EXPLICIT_TAG_NOT_OPEN

SAP Sybase Error Num- 2566

ber

SQL State WX008

SQL Code -900L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The parent tag ID that is not among the open tags.

Probable Cause FOR XML EXPLICIT and FOR JSON EXPLICIT require the parent tag
for a row to be opened when that row is read. Check the order of the rows
returned by the query with the FOR XML EXPLICIT or FOR JSON
EXPLICIT clause removed.

Error 901 "Undeclared tag ID: '%1'"

Constant UNDECLARED_FOR_XML_EXPLICIT_TAG

SAP Sybase Error Number 2567

SQL State WX009

SQL Code -901L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 221

Errors and Warnings

Error 901 "Undeclared tag ID: '%1'"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value of the undeclared tag ID.

Probable Cause Every value appearing in the Tag column of the table must be declared
in the TagNumber field of at least one column name.

Error 902 "Too few columns"

Constant FOR_XML_EXPLICIT_TOO_FEW_COLUMNS

SAP Sybase Error Number 2568

Error 910 "System command failed with return code %1"

Constant SYSTEM_COMMAND_FAILED

SAP Sybase Error Number 2575

SQL State 38W01

SQL Code -910L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Return code value.

Probable Cause A non-zero return code resulted when executing a system command.

Error 911 "Control character in XML output"

Constant CONTROL_CHARACTER_IN_XML_OUTPUT

SAP Sybase Error 2576

Number

SQL State WX015

SQL Code -911L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A non-space character less than hex 20 was encountered while generating
XML content. Consider base64 encoding strings that contain control char-
acters before using them as XML content. This can be accomplished in a
FOR XML query or SQLX function by casting the string to a type such as
LONG BINARY.

Error 912 "Insufficient memory for OPENXML query"

Constant XQUERY_MEMORY_ERROR

SAP Sybase IQ Error Messages 225

Errors and Warnings

Error 912 "Insufficient memory for OPENXML query"

SAP Sybase Error 2577

Number

SQL State WX016

SQL Code -912L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 17 on page 2

Probable Cause The memory used by an OPENXML query may be proportional to the maxi-
mum distance between elements or attributes returned by a single row. For
example, a query where some row uses the value from both the first and last
element in the document may use memory proportional to the size of the
document. One solution is to increase the cache size. Another is to break a
query that refers to distant elements into several queries that refer to nearby
elements and join the results.

Error 913 "A transaction log file is required for auditing"

Constant AUDITING_WITHOUT_TRANSACTION_LOG

SAP Sybase Error Number 2578

SQL State 42W91

SQL Code -913L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause This database is running without a transaction log file. You must use
the Transaction Log utility (dblog) to create a transaction log file
before using auditing.

Error 914 "Cycle in common table expression references"

Constant COMMON_TABLE_EXPRESSION_CYCLE

SAP Sybase Error Number 2579

SQL State 42W93

226 SAP Sybase IQ

Errors and Warnings

Error 914 "Cycle in common table expression references"

SQL Code -914L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause Cycles involving multiple common table expressions are not allowed.

Error 915 "Service type required for CREATE SERVICE"

Constant SERVICE_TYPE_REQUIRED

SAP Sybase Error Number 2580

SQL State 42W92

SQL Code -915L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The CREATE SERVICE statement requires a service type to be

specified.

Error 916 "'%1' is an unrecognized service type"

Constant UNKNOWN_SERVICE_TYPE

SAP Sybase Error Number 2581

SQL State 42W94

SQL Code -916L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The service type that is unrecognized.

Probable Cause An unrecognized service type was specified.

SAP Sybase IQ Error Messages 227

Errors and Warnings

Error 918 "A user name must be specified if AUTHORIZATION is Off"

Constant SERVICE_REQUIRES_USER_NAME

SAP Sybase Error Number 2583

SQL State 42W96

SQL Code -918L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A valid user name must be specified if AUTHORIZATION is Off.

Error 919 "Service '%1' already exists"

Constant SERVICE_ALREADY_EXISTS

SAP Sybase Error Number 2584

SQL State 42W97

SQL Code -919L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the service that already exists.

Probable Cause You have attempted to create a service with a name that already exists
in the database.

Error 920 "Service '%1' not found"

Constant SERVICE_NOT_FOUND

SAP Sybase Error Number 2585

SQL State 42W98

SQL Code -920L

ODBC 2 State ERROR

ODBC 3 State ERROR

228 SAP Sybase IQ

Errors and Warnings

Error 920 "Service '%1' not found"

Severity Code 16 on page 2

Parameter 1 Name of the specified service that could not be found.

Probable Cause You have attempted to reference a service with a name that does not
exist in the database.

Error 921 "Invalid recursive query"

Constant INVALID_RECURSION

SAP Sybase Error 2586

Number

SQL State 42W99

SQL Code -921L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause A recursive query must consist of the UNION ALL of an initial query and an
iteration query. The only set operation allowed in the iteration query is UN-
ION ALL. A recursive reference to the name of the common table expression
can only appear in the iteration query, and must not be in a SELECT that uses
DISTINCT, ORDER BY, or an aggregate function. A recursive reference also
cannot appear on the NULL-supplying side of an outer join, or in a subquery.

Error 922 "No column list for recursive query"

Constant NO_RECURSIVE_COLUMN_LIST

SAP Sybase Error Number 2587

SQL State 42W9A

SQL Code -922L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause A common table expression defining a recursive query must have a
column list.

SAP Sybase IQ Error Messages 229

Errors and Warnings

Error 923 "Too many recursive iterations"

Constant TOO_MANY_RECURSIVE_ITERATIONS

SAP Sybase Error Number 2588

SQL State 57015

SQL Code -923L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A recursive query ran for more iterations than allowed by the current
max_recursive_iterations option setting.

Error 924 "Service '%1' in use"

Constant SERVICE_IN_USE

SAP Sybase Error Number 2582

SQL State 55W15

SQL Code -924L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the service that is in use.

Probable Cause You have attempted to drop a service that is currently in use.

Messages 925 through 945

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 925 "Invalid service name '%1'"

Constant INVALID_SERVICE_NAME

SAP Sybase Error Number 2589

SQL State 42W95

230 SAP Sybase IQ

Errors and Warnings

Error 925 "Invalid service name '%1'"

SQL Code -925L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the service.

Probable Cause You have attempted to create a service with an invalid name. The
name may contain characters that are not allowed, or it may conflict
with the URL PATH setting specified for the service.

Error 926 "Host variable reference in service definition must be

named"

Constant HOSTVAR_MUST_BE_NAMED

SAP Sybase Error Number 2590

SQL State 42W9B

SQL Code -926L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You have attempted to create a service with an unnamed host variable
reference.

Error 927 "Service statement definition is inconsistent with service

type"

Constant SERVICE_STATEMENT_MISMATCH

SAP Sybase Error Number 2591

SQL State 42W9C

SQL Code -927L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 231

Errors and Warnings

Error 927 "Service statement definition is inconsistent with service

type"

Probable Cause Either no statement was provided for a service whose type requires
one, or a statement was provided when the service type does not allow
one to be defined.

Error 928 "Constant expressions must not appear in GROUP BY clause"

Constant NO_CONSTANTS_IN_GROUP_BY

SAP Sybase Error 2592

Number

SQL State 42W9D

SQL Code -928L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You used a constant in the GROUP BY clause. Constants must not appear in
the GROUP BY clause for a query. References to columns in a view that are
constant are permitted in a GROUP BY clause. Also, expressions that use a
view column that is constant are permitted.

Error 929 "Constraint '%1' not found"

Constant CONSTRAINT_NOT_FOUND

SAP Sybase Error Number 2593

SQL State 42U04

SQL Code -929L

ODBC 2 State S0002

ODBC 3 State 42S23

Severity Code 16 on page 2

Parameter 1 Name of the constraint that could not be found.

Probable Cause You misspelled the name of a constraint, or the constraint you are
looking for is on a different table.

232 SAP Sybase IQ

Errors and Warnings

Error 930 "Attempt to alter unnamed column constraint when named

constraints exist"

Constant AMBIGUOUS_CONSTRAINT

SAP Sybase Error Number 2594

SQL State 42U05

SQL Code -930

ODBC 2 State S0002

ODBC 3 State 42S24

Severity Code 16 on page 2

Probable Cause You have asked for an unnamed column constraint to be altered, but
there is at least one named constraint.

Error 931 "Service definition requires a statement when

authorization is off"

Constant SERVICE_AUTH_REQUIRED

SAP Sybase Error Number 2595

SQL State 42W9E

SQL Code -931L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The service definition for the specified service type requires a state-
ment to be specified when authorization is set to Off.

Error 933 "A log is required for IQ databases"

Constant IQ_LOG_REQUIRED

SAP Sybase Error Number 2597

SQL State 0AQ48

SQL Code -933L

ODBC 2 State 37000

SAP Sybase IQ Error Messages 233

Errors and Warnings

Error 933 "A log is required for IQ databases"

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause IQ databases require the use of a transaction log file.

Error 934 "Unable to start specified database: Server must be upgraded

to start database %1"

Constant UNABLE_TO_START_DATABASE_VER_NEWER

SAP Sybase Error 2598

Number

SQL State 08W67

SQL Code -934L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Name of the database that could not be started, if known.

Probable Cause The database server was unable to start the database since the database
version is newer than the server version. The server must be upgraded to at
least the version of the database to be able to start the database.

Error 935 "Unable to start specified database: Log file error"

Constant UNABLE_TO_START_DATABASE_LOG_ERROR

SAP Sybase Error Num- 2599

ber

SQL State 08W68

SQL Code -935L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

234 SAP Sybase IQ

Errors and Warnings

Error 935 "Unable to start specified database: Log file error"

Probable Cause The database server was unable to start the database since the log file is
missing, for a different database, or some other reason. Check the server
messages window for more details.

Error 936 "Too many constraints in database"

Constant TOO_MANY_CONSTRAINTS

SAP Sybase Error Number 2600

SQL State 54W02

SQL Code -936L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt to create a new constraint failed because the correspond-
ing system table is full. Reloading the database will reclaim any
unused space.

Error 937 "Invalid reference to or operation on constraint '%1'"

Constant INVALID_CONSTRAINT_REF

SAP Sybase Error Number 2601

SQL State 42U06

SQL Code -937L

ODBC 2 State S0002

ODBC 3 State 42S23

Severity Code 16 on page 2

Parameter 1 Name of the constraint that cannot be used for the specified purpose.

Probable Cause You specified an invalid operation on a constraint. For example, you
tried to alter a primary key constraint.

Error 938 "Recursion is not allowed without the RECURSIVE

keyword"

Constant RECURSIVE_KEYWORD_REQUIRED

SAP Sybase IQ Error Messages 235

Errors and Warnings

Error 938 "Recursion is not allowed without the RECURSIVE

keyword"

SAP Sybase Error Number 2602

SQL State 42WA0

SQL Code -938L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The common table expressions for a recursive query must be defined
using a WITH RECURSIVE clause.

Error 939 "Invalid setting for HTTP option '%1'"

Constant INVALID_HTTP_OPTION_SETTING

SAP Sybase Error Number 2603

SQL State 42W83

SQL Code -939L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the invalid HTTP option.

Probable Cause You supplied an invalid value for an HTTP option. Some options
allow only numeric values, while other options allow only the values
On and Off.

Error 940 "Invalid setting for HTTP header '%1'"

Constant INVALID_HTTP_HEADER_SETTING

SAP Sybase Error Number 2604

SQL State 42W84

SQL Code -940L

ODBC 2 State 37000

236 SAP Sybase IQ

Errors and Warnings

Error 940 "Invalid setting for HTTP header '%1'"

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the invalid HTTP header.

Probable Cause You supplied an invalid value for an HTTP header.

Error 941 "jConnect does not support encryption"

Constant NO_ENCRYPTION_FOR_JCONNECT

SAP Sybase Error Number 2605

SQL State 08W69

SQL Code -941L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 18 on page 2

Probable Cause You supplied an encryption type for a connection using jConnect.
jConnect does not support encryption.

Error 942 "A workload capture (%1) is already in progress"

Constant WORKLOAD_CAPTURE_ALREADY_EXISTS

SAP Sybase Error Number 2606

SQL State WW029

SQL Code -942L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the workload capture that is already in progress.

Probable Cause You have tried to initiate a workload capture when one is already in
progress. You need to wait for the other capture to complete.

SAP Sybase IQ Error Messages 237

Errors and Warnings

Error 943 "No workload capture currently exists"

Constant WORKLOAD_CAPTURE_DOES_NOT_EXIST

SAP Sybase Error Number 2607

SQL State WW030

SQL Code -943L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You have tried to stop, pause, resume, or get the status of a workload
capture, but no workload captures exist.

Error 944 "Too many expressions in GROUP BY list for ROLLUP, CUBE, or
GROUPING SETS operation"

Constant TOO_MANY_GROUPING_EXPRESSIONS

SAP Sybase Error 2608

Number

SQL State 42WA1

SQL Code -944L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You specified too many expressions in the GROUP BY list for the requested
ROLLUP, CUBE, or GROUPING SETS operation. The current environ-
ment where SQL Anywhere is executing cannot support this number of
expressions in the GROUP BY list for the requested operation.

Error 945 "Recursive column %1: conversion from '%2' to '%3' loses
precision"

Constant BAD_RECURSIVE_COLUMN_CONVERSION

SAP Sybase Error Number 2609

SQL State 42WA2

SAP Sybase Error Number 2612

SQL State 42WA4

SQL Code -948L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the window.

Probable Cause When an existing window name is referenced from an inline window
specification, the inline specification must not have a PARTITION
BY clause.

Error 949 "ORDER BY not allowed in window '%1'"

Constant ORDERBY_NOT_ALLOWED

SAP Sybase Error Number 2613

SQL State 42WA5

SQL Code -949L

ODBC 2 State ERROR

240 SAP Sybase IQ

Errors and Warnings

Error 949 "ORDER BY not allowed in window '%1'"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the window.

Probable Cause When an existing window name is referenced from an inline window
specification, either the inline window or the referenced window may
have an ORDER BY, but not both.

Error 950 "Frame not allowed for window '%1'"

Constant FRAME_NOT_ALLOWED

SAP Sybase Error Number 2614

SQL State 42WA6

SQL Code -950L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the window.

Probable Cause Frames are not allowed on windows referenced from inline window
specifications.

Error 951 "Cannot access schema file '%1'"

Constant CANNOT_ACCESS_SCHEMA_FILE

SAP Sybase Error Number 2615

SQL State WW031

SQL Code -951L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the file or indication that no name was given.

SAP Sybase IQ Error Messages 241

Errors and Warnings

Error 951 "Cannot access schema file '%1'"

Probable Cause UltraLite requires a schema file to perform the current operation.
Either no schema file was specified or the one specified was not
accessible or was corrupt.

Error 952 "The status of the last synchronization upload is

unknown"

Constant SYNC_STATUS_UNKNOWN

SAP Sybase Error Number 2616

SQL State WW032

SQL Code -952L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The status of the last synchronization upload is unknown. The current
operation cannot proceed until a successful upload is synchronized.

Error 953 "A schema upgrade is not currently allowed"

Constant SCHEMA_UPGRADE_NOT_ALLOWED

SAP Sybase Error Number 2617

SQL State WW033

SQL Code -953L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A schema upgrade cannot proceed because of concurrent use of the
database. For example, all cursors must be closed before a schema
upgrade can occur.

Error 954 "The database '%1' was not found"

Constant ULTRALITE_DATABASE_NOT_FOUND

SAP Sybase Error Number 2618

242 SAP Sybase IQ

Errors and Warnings

Error 954 "The database '%1' was not found"

SQL State WW034

SQL Code -954L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the database specified or the default database name.

Probable Cause The named database was not found. Ensure your connection string
properly names the desired database.

Error 955 "This connection already exists"

Constant CONNECTION_ALREADY_EXISTS

SAP Sybase Error Number 2619

SQL State WW035

SQL Code -955L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A connection with the given SQLCA and name (or no name) already
exists. Before connecting you must disconnect the existing connec-
tion, or specify a different connection name.

Error 956 "Information for synchronization is incomplete or invalid,

check '%1'"

Constant SYNC_INFO_INVALID

SAP Sybase Error Num- 2620

ber

SQL State WW036

SQL Code -956L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 243

Errors and Warnings

Error 956 "Information for synchronization is incomplete or invalid,

check '%1'"

Severity Code 16 on page 2

Parameter 1 The name of the parameter not properly initialized.

Probable Cause Information for synchronization is incomplete or invalid. Correct the

indicated parameter before attempting to synchronize again. If 'init_ver-
ify' is indicated, the InitSyncInfo function was not called.

Error 957 "Invalid preceding or following size in OLAP function"

Constant INVALID_FRAME_BOUNDARY

SAP Sybase Error Number 2621

SQL State 22X13

SQL Code -957L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The expression for the preceding or following size evaluated to
NULL or a negative value.

Error 958 "Password cannot be longer than %1 characters"

Constant PASSWORD_TOO_LONG

SAP Sybase Error Number 2622

SQL State 54W08

SQL Code -958L

ODBC 2 State 37000

ODBC 3 State 54000

Severity Code 15 on page 2

Probable Cause The password is longer than that allowed by the server.

Error 959 "Compression error: %1"

Constant COMPRESSION_ERROR

244 SAP Sybase IQ

Errors and Warnings

Error 959 "Compression error: %1"

SAP Sybase Error Number 2623

SQL State WW037

SQL Code -959L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An error occurred during compression.

Error 960 "Decompression error: %1"

Constant DECOMPRESSION_ERROR

SAP Sybase Error Number 2624

SQL State WW038

SQL Code -960L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An error occurred during decompression.

Error 961 "Input string is not base64-encoded"

Constant BASE64_DECODING_ERROR

SAP Sybase Error Number 2625

SQL State WW039

SQL Code -961L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An error occurred during base64 decoding.

SAP Sybase IQ Error Messages 245

Errors and Warnings

Error 962 "Argument to GROUPING aggregate must be a grouping

column in the GROUP BY clause"

Constant INVALID_GROUPING_AGGREGATE

SAP Sybase Error Num- 2626

ber

SQL State 42WA7

SQL Code -962L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause Only a grouping column is permitted as an argument to the GROUP-

ING aggregate function. An argument that contains anything other than
a single grouping column expression will not be accepted.

Error 963 "Password contains an illegal character"

Constant ILLEGAL_PASSWORD

SAP Sybase Error Number 2627

SQL State 08005

SQL Code -963L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 11 on page 2

Probable Cause The specified password contains an illegal character.

Error 964 "Window function used in predicate"

Constant ILLEGAL_WINDOW_PREDICATE

SAP Sybase Error Num- 2628

ber

SQL State 42WA8

SQL Code -964L

ODBC 2 State ERROR

246 SAP Sybase IQ

Errors and Warnings

Error 964 "Window function used in predicate"

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A window function was used in the WHERE or HAVING clause of a
SELECT statement. Consider making the SELECT into a derived table,
putting the window function in the SELECT list of the derived table, and
changing the predicate to reference the derived column.

Error 965 "Window function requires ORDER BY"

Constant OBSOLETE_ORDERBY_REQUIRED

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the user that already has EXECUTE permission.

Probable Cause You attempted to give EXECUTE permission on a stored procedure

to a user that already has EXECUTE permission on that procedure.

Error 969 "Required operators excluded"

Constant REQUIRED_OPERATORS_EXCLUDED

248 SAP Sybase IQ

Errors and Warnings

Error 969 "Required operators excluded"

SAP Sybase Error Num- 2633

ber

SQL State WI011

SQL Code -969L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 18 on page 2

Probable Cause The database server was unable to construct a valid access plan for the
given request because required data flow operators were excluded by
the exclude_operators option. Re-enable the required operators to ex-
ecute the statement.

Error 970 "Invalid hint specified for table '%1'"

Constant INVALID_HINT

SAP Sybase Error Number 2634

SQL State 42U07

SQL Code -970L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 The name of the table for which the hint was specified.

Probable Cause A hint was specified for the current statement is not valid in this
context. In a single statement, all references to a table must specify the
same hint or none at all.

Error 971 "Checksums are not enabled in this database"

Constant CHECKSUMS_NOT_ENABLED

SAP Sybase Error Number 2637

SQL State WW042

SQL Code -971L

SAP Sybase IQ Error Messages 249

Errors and Warnings

Error 971 "Checksums are not enabled in this database"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt was made to perform checksum validation but the data-
base does not have checksums enabled.

Error 972 "Database page size too small: %1"

Constant PAGE_SIZE_TOO_SMALL

SAP Sybase Error Number 2638

SQL State 54W03

SQL Code -972L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 14 on page 2

Parameter 1 Database name.

Probable Cause You attempted to load statistics that were too large for the current
database page size. Rebuilding this database with a larger page size
could prevent this error.

Error 973 "The string is too long (%1)"

Constant STRING_PARM_TOO_LONG

SAP Sybase Error Number 2639

SQL State 54W06

SQL Code -973L

ODBC 2 State 37000

ODBC 3 State 54000

Severity Code 15 on page 2

Parameter 1 The string that is longer than that allowed by the server.

Probable Cause The string is longer than that allowed by the server.

250 SAP Sybase IQ

Errors and Warnings

Error 974 "File I/O failed for '%1'"

Constant DEVICE_IO_FAILED

SAP Sybase Error Number 2640

SQL State WW043

SQL Code -974L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The file name.

Probable Cause An error occurred while trying to access the file. If the file is located
on a removable media card, the card may have been removed.

Error 975 "Incorrect volume ID for '%1'"

Constant INCORRECT_VOLUME_ID

SAP Sybase Error Number 2641

SQL State WW044

SQL Code -975L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The file name.

Probable Cause The file can be accessed, but the volume ID has changed. Insert the
original removable media card.

Error 976 "Could not load the encryption DLL \"%1\No message

Constant MISSING_ENCRYPTION_DLL

SAP Sybase Error Number 2643

SQL State 08W70

SQL Code -976L

SAP Sybase IQ Error Messages 251

Errors and Warnings

Error 976 "Could not load the encryption DLL \"%1\No message

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The name of the encryption DLL that could not be loaded.

Probable Cause An attempt to load the encryption DLL failed.

Error 978 "Directory for output file does not exist"

Constant DIRECTORY_INACCESSIBLE

SQL Code -981L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The URI referencing the remote host.

Probable Cause A connection could not be initiated to the remote server.

Error 982 "Connection timed out"

Constant REMOTE_CONNECTION_TIMED_OUT

SAP Sybase Error Number 2649

SQL State WW051

SQL Code -982L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

SAP Sybase IQ Error Messages 253

Errors and Warnings

Error 982 "Connection timed out"

Probable Cause The connection to the remote host timed out due to inactivity.

Error 983 "HTTP request failed. Status code '%1'"

Constant HTTP_REQUEST_FAILED

SAP Sybase Error Number 2650

SQL State WW052

SQL Code -983L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The HTTP status code.

Probable Cause The HTTP request returned a status code that indicated failure.

Error 984 "Could not initialize the encryption DLL: '%1'"

Constant ENCRYPTION_INITIALIZATION_FAILED

SAP Sybase Error Number 2651

SQL State WW053

SQL Code -984L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 Reason the initialization failed, if known.

Probable Cause An attempt to initialize the encryption DLL failed.

Error 985 "The database name 'utility_db' is reserved for the utility
database."

Constant DB_ALIAS_RESERVED_UTILDB

SAP Sybase Error Number 2845

SQL State 08W20

254 SAP Sybase IQ

Errors and Warnings

Error 985 "The database name 'utility_db' is reserved for the utility
database."

SQL Code -985L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause You are attempting to start a database with the name "utility_db". This
name is reserved for the utility database.

Error 986 "Invalid procedure type '%1'"

Constant INVALID_PROCEDURE_TYPE

SAP Sybase Error Number 2653

SQL State WW055

SQL Code -986L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The procedure type.

Probable Cause A procedure or function was specified with an invalid type.

Messages 987 through 1006

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 987 "Invalid procedure subtype '%1' for type '%2'"

Constant INVALID_PROCEDURE_SUBTYPE

SAP Sybase Error Number 2654

SQL State WW056

SQL Code -987L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 255

Errors and Warnings

Error 987 "Invalid procedure subtype '%1' for type '%2'"

Severity Code 16 on page 2

Parameter 1 The procedure subtype.

Parameter 2 The procedure type.

Probable Cause A procedure or function was specified with an invalid subtype for the
given procedure type.

Error 988 "Invalid response from the HTTP server"

Constant INVALID_HTTP_RESPONSE

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The attribute on the procedure.

Parameter 2 The attribute value or cause of failure.

Probable Cause The attribute value specified on the procedure is not valid.

Error 992 "The specified listener could not be registered"

Constant CANNOT_REGISTER_LISTENER

SAP Sybase Error Number 2659

SQL State 54W04

SQL Code -992L

SAP Sybase IQ Error Messages 257

Errors and Warnings

Error 992 "The specified listener could not be registered"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 17 on page 2

Probable Cause The specified listener could not be registered because the maximum
number of listeners has been reached, the class name is already in use,
or system resources are not available.

Error 993 "LOAD TABLE not allowed on temporary table with ON

COMMIT DELETE ROWS"

Constant INVALID_TEMP_TABLE_COMMIT_ACTION

SAP Sybase Error Num- 2660

ber

SQL State WL007

SQL Code -993L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The LOAD TABLE statement automatically commits at completion. If

a temporary table being loaded was declared with ON COMMIT DE-
LETE ROWS, the rows are discarded at completion.

Error 994 "Too many arguments for function or procedure '%1'"

Constant TOO_MANY_ARGUMENTS

SAP Sybase Error Num- 2661

ber

SQL State 42WAC

SQL Code -994L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

258 SAP Sybase IQ

Errors and Warnings

Error 994 "Too many arguments for function or procedure '%1'"

Parameter 1 The name of the function or procedure.

Probable Cause You supplied an argument list that the database server cannot handle.
This can happen if the argument list of the function or stored procedure is
too long. Rebuilding the database with a larger page size could prevent
this error.

Error 995 "Warning detected when optimizing SELECT INTO is treated

as an error"

Constant SELECT_INTO_WARNING_TREATED_AS_ERROR

SAP Sybase Error Num- 2662

ber

SQL State WP016

SQL Code -995L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The SELECT...INTO #TEMPTABLE statement cannot proceed if a

warning is detected while optimizing the query. To fix the problem, test
the query by removing the INTO clause, and resolve the reported
warning.

Error 996 "Specified local connection ID not found"

Constant LOCAL_CONNECTION_NOT_FOUND

SAP Sybase Error Number 2663

SQL State WO024

SQL Code -996L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause There is no connection with the specified connection ID.

SAP Sybase IQ Error Messages 259

Errors and Warnings

Error 997 "Local connection ID does not refer to the current

database"

Constant LOCAL_CONNECTION_NOT_TO_CURRENT_DB

SAP Sybase Error Number 2664

SQL State WO025

SQL Code -997L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The specified connection ID is for a connection to a database other

than the current database.

Error 998 "Cannot close a remote JDBC connection that is not the
current connection"

Constant CANNOT_CLOSE_JDBC_CONNECTION

SAP Sybase Error Num- 2665

ber

SQL State WO026

SQL Code -998L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause When attempting to close a remote JDBC connection, the specified
connection must be the local connection.

Error 999 "Invalid request log format on line %1"

Constant INVALID_REQUEST_LOG_FORMAT

SAP Sybase Error Number 2667

SQL State WW020

SQL Code -999L

ODBC 2 State ERROR

260 SAP Sybase IQ

Errors and Warnings

Error 999 "Invalid request log format on line %1"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The line number in the log file.

Probable Cause The request log file format is invalid. The request log may have been
created with an older version of the software.

Error 1000 "Temporary space limit exceeded"

Constant TEMP_SPACE_LIMIT

SAP Sybase Error 2668

Number

SQL State 54W05

SQL Code -1000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause The connection has exceeded its temporary-space usage limit. This limit is
based in part on the amount of free-space remaining on the drive containing
the temporary file. Try deleting unused files from the drive, or placing the
temporary file on a drive with more space available. See the -dt server option
to specify a directory for temporary files.

Error 1001 "Parameter '%1' in procedure or function '%2' does not

have a default value"

Constant NO_DEFAULT_FOR_PARM

SAP Sybase Error Number 2669

SQL State 08W71

SQL Code -1001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 261

Errors and Warnings

Error 1001 "Parameter '%1' in procedure or function '%2' does not

have a default value"

Parameter 1 The name of the parameter.

Parameter 2 The name of the procedure or function.

Probable Cause An attempt was made to use DEFAULT as a procedure or function

argument, but the corresponding parameter does not have a default
value.

Error 1002 "The option '%1' is not recognized"

Constant UNRECOGNIZED_OPTION

SAP Sybase Error Number 2670

SQL State WW062

SQL Code -1002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the option.

Probable Cause The specified option was not recognized. The option may have been
spelled incorrectly.

Error 1003 "Too many distinct group mappings for integrated user"

Constant INTEGRATED_LOGON_TOO_MANY_MAPPINGS

SAP Sybase Error 2671

Number

SQL State 28W10

SQL Code -1003L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

262 SAP Sybase IQ

Errors and Warnings

Error 1003 "Too many distinct group mappings for integrated user"

Probable Cause The integrated user does not have an explicit mapping in the database but
does have group mappings. There are too many distinct group mappings.
You must either reduce the number of distinct group mappings or add an
explicit mapping for the user.

Error 1004 "Unable to start specified database: '%1' is not a database"

Constant FILE_NOT_DB

SAP Sybase Error Number 2672

SQL State 08W85

SQL Code -1004L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the database file.

Probable Cause The specified file is not a valid database file.

Error 1005 "Unable to start specified database: '%1' was created by a

different version of the software"

Constant FILE_WRONG_VERSION

SAP Sybase Error Number 2673

SQL State 08W86

SQL Code -1005L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the database file.

Probable Cause The specified database file was created by a different version of the
software, and it cannot be read by this version.

SAP Sybase IQ Error Messages 263

Errors and Warnings

Error 1006 "Unable to start specified database: '%1' is not a valid

database file"

Constant FILE_BAD_DB

SAP Sybase Error Number 2674

SQL State 08W87

SQL Code -1006L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the database file.

Probable Cause The specified file is not a valid database.

1007 - 1218

Messages 1007 through 1029

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1007 "Unable to start specified database: '%1' is an invalid

transaction log"

Constant CORRUPT_REDO

SAP Sybase Error Number 2675

SQL State 08W88

SQL Code -1007L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log file.

Probable Cause The specified file is not a valid transaction log.

264 SAP Sybase IQ

Errors and Warnings

Error 1008 "Unable to start specified database: '%1' is an invalid

transaction log mirror"

Constant CORRUPT_REDO_MIRROR

SAP Sybase Error Number 2676

SQL State 08W72

SQL Code -1008L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log mirror file.

Probable Cause The specified file is not a valid transaction log mirror.

Error 1009 "Unable to start specified database: The transaction log

'%1' or its mirror '%2' is invalid"

Constant CORRUPT_REDO_OR_MIRROR

SAP Sybase Error Number 2677

SQL State 08W73

SQL Code -1009L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log file.

Parameter 2 The name of the transaction log mirror file.

Probable Cause The transaction log differs from the transaction log mirror. Either the
transaction log or its mirror is invalid.

Error 1010 "Unable to start specified database: '%1' not expecting any
operations in transaction log"

Constant EXPECTING_NO_REDO

Errors and Warnings

Error 1012 "Unable to start specified database: '%1' must be

upgraded to start with this server (capability %2 missing)"

Severity Code 11 on page 2

Parameter 1 The name of the database file.

Parameter 2 The capability that is missing from the database file.

Probable Cause The specified database must be upgraded to start with this server.

Error 1016 "Unable to start specified database: Cannot use log file
'%1' since it has been used more recently than the
database file"

Constant LOG_NEWER_THAN_DB

SAP Sybase Error Number 2684

SQL State 08W80

SQL Code -1016L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log mirror file.

Probable Cause The transaction log file has been used more recently than the database
file.

Error 1017 "Unable to start specified database: '%1': transaction log

file not found"

Constant LOG_NOT_FOUND

SAP Sybase Error Number 2685

SQL State 08W81

SQL Code -1017L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log file.

SAP Sybase IQ Error Messages 267

Errors and Warnings

Error 1017 "Unable to start specified database: '%1': transaction log

file not found"

Probable Cause The transaction log file was not found.

Error 1018 "Unable to start specified database: Cannot use log file
'%1' since the offsets do not match the offsets in the
database file"

Constant LOG_OFFSETS_DONT_MATCH

SAP Sybase Error Number 2686

SQL State 08W82

SQL Code -1018L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log file.

Probable Cause The transaction log file has an offset that does not match the offset
expected by the database file.

Error 1019 "Unable to start specified database: Cannot use log file
'%1' since the database file has been used more recently"

Constant LOG_OLDER_THAN_DB

SAP Sybase Error Number 2687

SQL State 08W83

SQL Code -1019L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log file.

Probable Cause The database file has been used more recently than the transaction log
file.

268 SAP Sybase IQ

Errors and Warnings

Error 1020 "Unable to start specified database: Cannot use log file
'%1' since it is shorter than expected"

Constant LOG_TOO_SHORT

SAP Sybase Error Number 2688

SQL State 08W84

SQL Code -1020L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the transaction log file.

Probable Cause The transaction log file is shorter than expected.

Error 1021 "Invalid backup operation"

Constant INVALID_BACKUP_OPERATION

SAP Sybase Error Number 2689

SQL State WB013

SQL Code -1021L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The specified backup operation is not valid because of previous
backup operation(s).

Error 1022 "Invalid value for attribute '%1' in service"

Constant SERVICE_PARM_INVALID_VALUE

SAP Sybase Error Number 2691

SQL State 42WAD

SQL Code -1022L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 269

Errors and Warnings

Error 1022 "Invalid value for attribute '%1' in service"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the invalid attribute.

Probable Cause The service definition contains a USING, FORMAT, or GROUP

attribute with an invalid value.

Error 1023 "Missing value for attribute '%1' in service"

Constant SERVICE_PARM_MISSING_VALUE

SAP Sybase Error Number 2692

SQL State 42WAE

SQL Code -1023L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the invalid attribute.

Probable Cause The service definition contains a USING, FORMAT, or GROUP

attribute with a missing value.

Error 1024 "Unsupported property '%1' in service USING attribute"

Constant SERVICE_PARM_UNSUPPORTED_PROPERTY

SAP Sybase Error Number 2693

SQL State 42WAF

SQL Code -1024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the unsupported property.

Probable Cause The service definition contains a USING attribute with an unsuppor-
ted property.

270 SAP Sybase IQ

Errors and Warnings

Error 1025 "Duplicate attribute '%1' in service"

Constant SERVICE_PARM_DUPLICATE_PROPERTY

SAP Sybase Error Number 2694

SQL State 42WB0

SQL Code -1025L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the duplicate attribute.

Probable Cause The service definition contains a duplicate attribute.

Error 1026 "USING attribute cannot coexist with FORMAT or GROUP

attributes"

Constant SERVICE_ATTR_COEXIST

SAP Sybase Error Number 2695

SQL State 42WB1

SQL Code -1026L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The service definition for the specified service type cannot specify a
USING attribute along with a FORMAT or GROUP attribute.

Error 1027 "Service type does not allow '%1' attribute"

Constant SERVICE_ATTR_NOT_ALLOWED

SAP Sybase Error Number 2696

SQL State 42WB2

SQL Code -1027L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 271

Errors and Warnings

Error 1027 "Service type does not allow '%1' attribute"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the attribute that is not allowed.

Probable Cause The service definition for the specified service type does not allow the
given attribute to be specified

Error 1028 "Connection attempting BACKUP has uncommitted

transactions"

Constant BACKUP_HAS_UNCOMMITTED_TRANS

SAP Sybase Error Number 2697

SQL State WB014

SQL Code -1028L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A connection attempting to perform a BACKUP...WAIT BEFORE

START or BACKUP...WAIT AFTER END has uncommitted trans-
actions. A COMMIT or ROLLBACK must be performed before ex-
ecuting the backup.

Error 1029 "Support for materialized views is not available for this
database"

Constant MAT_VIEWS_NOT_SUPPORTED

SAP Sybase Error Num- 2698

ber

SQL State 0AW15

SQL Code -1029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

272 SAP Sybase IQ

Errors and Warnings

Error 1029 "Support for materialized views is not available for this
database"

Probable Cause The statement being executed requires support for materialized views,
but the database being used does not have the materialized view capa-
bility.

Messages 1030 through 1051

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1030 "Secure HTTP connections are not supported on this

platform"

Constant SECURE_CONNECTION_UNAVAILABLE

SAP Sybase Error Number 2699

SQL State WW063

SQL Code -1030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause A Secure HTTP connection was attempted, but is not supported on
this platform.

Error 1031 "Syntax error near '%1' -- Materialized view definition must
not use the following construct: '%2'"

Constant MATVIEW_SYNTAX_ERROR

SAP Sybase Error Number 2700

SQL State 42WB3

SQL Code -1031L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Location of the feature used that is not permitted.

SAP Sybase IQ Error Messages 273

Errors and Warnings

Error 1031 "Syntax error near '%1' -- Materialized view definition must
not use the following construct: '%2'"

Parameter 2 The feature used that is not permitted.

Probable Cause You attempted to create a materialized view whose definition violates
one of the restrictions.

Error 1032 "Syntax error near '%1' -- The materialized view cannot be
changed to immediate because its definition contains an
illegal construct: '%2'"

Constant UPDATABLE_MATVIEW_SYNTAX_ERROR

SAP Sybase Error Number 2701

SQL State 42WB4

SQL Code -1032L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Location of the feature used that is not permitted.

Parameter 2 The feature used that is not permitted.

Probable Cause You attempted to change the refresh type to immediate for a materi-
alized view whose definition violates one of the restrictions.

Error 1033 "Unable to start database server: Server fatal error"

Constant UNABLE_TO_START_ENGINE_FATAL_ERROR

SAP Sybase Error 2702

Number

SQL State 08W89

SQL Code -1033L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 17 on page 2

274 SAP Sybase IQ

Errors and Warnings

Error 1033 "Unable to start database server: Server fatal error"

Probable Cause The database server failed to start because a fatal error or assertion failure
occurred. More information may be available in the Windows event log or
Unix system log or by manually starting the database server.

Error 1034 "The '%1' attribute is not valid with procedure type '%2'"

Constant INVALID_ATTRIBUTE_WITH_TYPE

SAP Sybase Error Number 2703

SQL State WW064

SQL Code -1034L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The attribute on the procedure.

Parameter 2 The procedure type.

Probable Cause This attribute is not applicable to the given procedure type.

Error 1035 "LOAD TABLE ... WITH FILE NAME LOGGING not permitted
on mirrored database"

Constant LOAD_TABLE_ON_MIRRORED_DB

SAP Sybase Error Number 2704

SQL State WL008

SQL Code -1035L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause LOAD TABLE ... WITH FILE NAME LOGGING statements are not
permitted when a database is being mirrored, since the file being
loaded might not be accessible by the other server.

SAP Sybase IQ Error Messages 275

Errors and Warnings

Error 1036 "The DBN/DBF parameters do not match the database for
this alternate server name"

Constant WRONG_DB_ON_ALT_SERVER_NAME

SAP Sybase Error Num- 2705

ber

SQL State 08W90

SQL Code -1036L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Probable Cause The DBN or DBF parameters specified do not match the database using
the specified alternate server name.

Error 1037 "Cannot drop or modify object '%1' because at least one other
object ( %2 '%3') depends upon it"

Constant OBJECT_HAS_DEPENDENTS

SAP Sybase Error 2706

Number

SQL State 55W16

SQL Code -1037L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the object that could not be dropped or modified.

Parameter 2 The type of the object that depends on the object that could not be dropped or
modified.

Parameter 3 The name of the object that depends on the object that could not be dropped
or modified.

Probable Cause You attempted to drop or modify an object, such as a table or a column, that is
used by another object, such as a materialized view, that cannot be auto-
matically invalidated. The dependent object must be disabled or dropped
before a drop or modification can be permitted.

276 SAP Sybase IQ

Errors and Warnings

Error 1038 "Cannot use view '%1' because it has been disabled"

Constant VIEW_DISABLED

SAP Sybase Error Number 2707

SQL State 55W17

SQL Code -1038L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the view.

Probable Cause You attempted to reference a view that has been disabled. The view
must be enabled before it can be used again.

Error 1039 "Cannot connect to mirror server. Use server name '%1' to
find the primary server"

Constant CONNECTED_TO_MIRROR_SERVER

SAP Sybase Error Number 2708

SQL State 08W91

SQL Code -1039L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The server name for the mirroring system.

Probable Cause You have attempted to connect to the mirror server in a mirroring
system. You should change your connection string or DSN to use the
server name for the mirroring system.

Error 1040 "Cannot use view '%1' because it is invalid"

Constant VIEW_INVALID

SAP Sybase Error Number 2709

SQL State 55W18

SAP Sybase IQ Error Messages 277

Errors and Warnings

Error 1040 "Cannot use view '%1' because it is invalid"

SQL Code -1040L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the view.

Probable Cause You attempted to reference an invalid view. The view must be enabled
before it can be used again.

Error 1041 "Materialized View '%1' not found"

Constant MATVIEW_NOT_FOUND

SAP Sybase Error Num- 2710

ber

SQL State 42WB5

SQL Code -1041L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 Name of the materialized view that could not be found.

Probable Cause You misspelled the name of a materialized view, or you did not qualify a
materialized view name with a user name. For example, you might have
referred to "Employees" instead of "DBA"."Employees".

Error 1042 "Cannot add a comment to a table declared as LOCAL

TEMPORARY"

Constant COMMENT_NOT_ALLOWED

SAP Sybase Error Number 2711

SQL State WW065

SQL Code -1042L

ODBC 2 State ERROR

ODBC 3 State ERROR

278 SAP Sybase IQ

Errors and Warnings

Error 1042 "Cannot add a comment to a table declared as LOCAL

TEMPORARY"

Severity Code 11 on page 2

Probable Cause You attempted to add a comment to a table that has been declared as
LOCAL TEMPORARY. This is not allowed.

Error 1043 "Request interrupted due to timeout"

Constant REQUEST_TIMEOUT

SAP Sybase Error 2712

Number

SQL State 57W01

SQL Code -1043L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current request was canceled during its execution since it ran for longer
than the request_timeout database option value. The database was able to stop
the operation without doing a rollback. If the statement is an INSERT, UP-
DATE, or DELETE, any changes made by the statement will be canceled. If the
statement is a data definition statement (for example CREATE TABLE), the
statement will be canceled, but the COMMIT that was done as a side effect will
not be canceled.

Error 1044 "Invalid password: %1"

Constant INVALID_NEW_PASSWORD

SAP Sybase Error Number 2713

SQL State 28W11

SQL Code -1044L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 279

Errors and Warnings

Error 1044 "Invalid password: %1"

Probable Cause The attempt to create a new user ID or change a password failed. The
function specified by the verify_password_function option disal-
lowed the password.

Error 1045 "Invalid backup parameter value"

Constant INVALID_BACKUP_PARM_VALUE

SAP Sybase Error Number 2714

SQL State WB015

SQL Code -1045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause One or more of the parameters supplied to the backup operation has
an invalid value.

Error 1046 "Illegal column definition: %1"

Constant ILLEGAL_COLUMN_DEFINITION

SAP Sybase Error Number 2715

SQL State 55W19

SQL Code -1046L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 A message describing the error that occurred.

Probable Cause You are attempting to define a column in a way that is not allowed.

Error 1047 "This database does not support encrypted tables"

Constant ENCRYPTED_TABLES_NOT_SUPPORTED

SAP Sybase Error Number 2716

280 SAP Sybase IQ

Errors and Warnings

Error 1047 "This database does not support encrypted tables"

SQL State 55W20

SQL Code -1047L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You tried to create an encrypted table in a database that does not
support them.

Error 1050 "Cannot return NULL result as requested data type"

Constant VALUE_IS_NULL

SAP Sybase Error Number 2719

SQL State 22030

SQL Code -1050L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You tried to retrieve a value from the database that was NULL and
assign it to a variable that cannot be NULL.

Error 1051 "Cannot create a materialized view because option '%1'

has an inappropriate setting"

Constant CANNOT_CREATE_MATVIEW

SAP Sybase Error Number 2720

SQL State 42WB6

SQL Code -1051L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the option with the incorrect setting.

SAP Sybase IQ Error Messages 281

Errors and Warnings

Error 1051 "Cannot create a materialized view because option '%1'

has an inappropriate setting"

Probable Cause You attempted to create a materialized view, but one of the database
options is currently set to a value not permitted while creating a ma-
terialized view.

Messages 1052 through 1076

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1052 "Cannot update materialized view because option '%1' has an
inappropriate setting"

Constant CANNOT_UPDATE_MATVIEW

SAP Sybase Error 2721

Number

SQL State 42WB7

SQL Code -1052L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the option with the incorrect setting.

Probable Cause You attempted to update/refresh a materialized view but one of the da-
tabase options is currently set to a value that is not permitted while up-
dating a materialized view, or, the option's setting does not match the
value when the view was created.

Error 1053 "'%1' is an invalid value for '%2'"

Constant INVALID_OPTION_VALUE

SAP Sybase Error Number 2722

SQL State 42W85

SQL Code -1053L

ODBC 2 State 37000

ODBC 3 State 42000

282 SAP Sybase IQ

Errors and Warnings

Error 1053 "'%1' is an invalid value for '%2'"

Severity Code 16 on page 2

Parameter 1 The invalid value.

Parameter 2 Name of the option.

Probable Cause You supplied an invalid value for an option. Some options only allow
numeric values and some options only allow true or false. Also, many
options do not permit the empty string as a value.

Error 1054 "Snapshot isolation disabled or pending"

Constant SNAPSHOT_ISOLATION_DISABLED

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A snapshot transaction attempted to use a table that was created or
altered after the transaction began.

Error 1062 "Statement not allowed during snapshot"

Constant STATEMENT_NOT_ALLOWED_IN_SNAPSHOT

SAP Sybase Error Number 2731

284 SAP Sybase IQ

Errors and Warnings

Error 1062 "Statement not allowed during snapshot"

SQL State 42WB9

SQL Code -1062L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A connection with an outstanding snapshot attempted to use CRE-

ATE INDEX, DROP INDEX, ALTER INDEX or ALTER TABLE.
Make sure all cursors for the connection are closed.

Error 1063 "Unable to start database %1: Cannot use read-only mode
if auditing is enabled"

Constant AUDITING_DB_READ_ONLY

SAP Sybase Error Number 2732

SQL State 08W93

SQL Code -1063L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Name of the database.

Probable Cause The specified database has auditing enabled, and cannot be started
read-only.

Error 1064 "Update conflict on snapshot transaction"

Constant SNAPSHOT_UPDATE_CONFLICT

SAP Sybase Error Number 2733

SQL State 42WBA

SQL Code -1064L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 285

Errors and Warnings

Error 1064 "Update conflict on snapshot transaction"

Severity Code 16 on page 2

Probable Cause A snapshot transaction attempted to update or delete a row that was
changed by another transaction after the snapshot began.

Error 1065 "Attempt to use snapshot isolation in a non-snapshot

transaction"

Constant NON_SNAPSHOT_TRANSACTION

SAP Sybase Error Number 2734

SQL State 42WBB

SQL Code -1065L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A transaction tried to use snapshot isolation but did not begin with
snapshot isolation.

Error 1066 "File system error: %1"

Constant OMNI_FILE_SYSTEM_ERROR

SAP Sybase Error Number 2735

SQL State WO027

SQL Code -1066L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 12 on page 2

Parameter 1 Error description.

Probable Cause This error results from an error in the underlying file system that was
encountered while accessing a file directory as a proxy table.

Error 1068 "Default dbspace '%1' not found"

Constant DEFAULT_DBSPACE_NOT_FOUND

286 SAP Sybase IQ

Errors and Warnings

Error 1068 "Default dbspace '%1' not found"

SAP Sybase Error Number 2737

SQL State 52W43

SQL Code -1068L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 Name of the default dbspace that could not be found.

Probable Cause You tried to create a table with the default_dbspace option set to a
dbspace that could not be found.

Error 1069 "Kerberos login failed"

Constant KERBEROS_LOGON_FAILED

SAP Sybase Error 2738

Number

SQL State 28W12

SQL Code -1069L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause The Kerberos login failed due to a failure of the client to authenticate the user's
principal with the KDC or a failure of the server to authenticate the client. The
most likely causes are the Kerberos principal may not be signed in, the prin-
cipal's ticket may have expired, or the client, server, or KDC's system time are
not within a few minutes of each other. The LogFile connection parameter or
the server's -z option may provide more information.

Error 1070 "Kerberos logins are not supported"

Constant KERBEROS_LOGONS_UNSUPPORTED

SAP Sybase Error 2739

Number

SQL State 28W13

SAP Sybase IQ Error Messages 287

Errors and Warnings

Error 1070 "Kerberos logins are not supported"

SQL Code -1070L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause The client and/or server does not support Kerberos logins. Kerberos may not
be supported by the platform, the Kerberos client software including the
GSS-API runtime may not be installed or found on the client, or Kerberos
was not enabled on the server. The LogFile connection parameter or the
server's -z option may provide more information.

Error 1071 "The %1 algorithm is not available in FIPS mode"

Constant FIPS_NOT_AVAILABLE

SAP Sybase Error Number 2740

SQL State 0AW16

SQL Code -1071L

ODBC 2 State ERROR

ODBC 3 State 08001

Severity Code 19 on page 2

Parameter 1 Name of the algorithm.

Probable Cause The specified algorithm is not available when the server is running in
FIPS mode.

Error 1072 "'%1' is not a valid character set encoding for use with
collation '%2'"

Constant INVALID_ENCODING_FOR_COLLATION

SAP Sybase Error Number 2741

SQL State WC009

SQL Code -1072L

ODBC 2 State ERROR

ODBC 3 State ERROR

288 SAP Sybase IQ

Errors and Warnings

Error 1072 "'%1' is not a valid character set encoding for use with
collation '%2'"

Severity Code 16 on page 2

Parameter 1 The character set encoding that is invalid.

Parameter 2 The collation for which the character set encoding is invalid.

Probable Cause The specified character set cannot be used with the specified colla-
tion.

Error 1073 "'%1' cannot be used as the NCHAR collation: only UCA
and UTF8BIN may be used"

Constant INVALID_NCHAR_COLLATION

SAP Sybase Error Num- 2742

ber

SQL State WC010

SQL Code -1073L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The collation that cannot be used as the NCHAR collation.

Probable Cause The specified collation cannot be used as the NCHAR collation.
NCHAR always uses UTF-8, so the collation must be either UCA or
UTF8BIN.

Error 1074 "Login mode '%1' not permitted by login_mode setting"

Constant LOGON_MODE_NOT_PERMITTED

SAP Sybase Error 2743

Number

SQL State 28W14

SQL Code -1074L

ODBC 2 State 28000

ODBC 3 State 28000

SAP Sybase IQ Error Messages 289

Errors and Warnings

Error 1074 "Login mode '%1' not permitted by login_mode setting"

Severity Code 16 on page 2

Parameter 1 Name of the login mode not included in the current login_mode database
option setting.

Probable Cause You attempted to connect using a login mode not included in the current
login_mode database option setting. Change the option setting or connect
using a different login mode.

Error 1075 "Failed to convert from character set '%1' to '%2'"

Constant FAILED_TO_CONVERT_CHARSET

SAP Sybase Error Number 2744

SQL State WC011

SQL Code -1075L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The character set of the input string.

Parameter 2 The character set of the output string.

Probable Cause The server failed to convert between the two specified character sets.
This could happen when the dbicu and dbicudt DLLs are not installed.

Error 1076 "dbicu libraries are required but not installed"

Constant ICU_NOT_AVAILABLE

SAP Sybase Error Number 2745

SQL State WC012

SQL Code -1076L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The server is unable to load ICU components that are required by this
database. Ensure that the dbicu and dbicudt DLLs are installed.

290 SAP Sybase IQ

Errors and Warnings

Messages 1077 through 1097

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1077 "Cannot use materialized view '%1' because it has not yet been
initialized"

Constant CANNOT_USE_MATVIEW

SAP Sybase Error 2746

Number

SQL State 42WBC

SQL Code -1077L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the materialized view.

Probable Cause You attempted to use a materialized view but it has not yet been initialized.
In order for a materialized view to become available for first use after being
created or enabled, it must be initialized at least once using the REFRESH
MATERIALIZED VIEW statement.

Error 1078 "Cycle in computed column dependencies"

Constant COMPUTED_COLUMN_CYCLE

SAP Sybase Error Number 2747

SQL State 42WBD

SQL Code -1078L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The table has a cycle in the dependencies between its computed col-
umns. Cycles are not allowed.

SAP Sybase IQ Error Messages 291

Errors and Warnings

Error 1079 "Backup is unable to open database file '%1'"

Constant BACKUP_UNABLE_TO_OPEN_FILE

SAP Sybase Error Number 2748

SQL State WB017

SQL Code -1079L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the file.

Probable Cause The database file cannot be opened by the backup. It may have been
erased or otherwise corrupted.

Error 1080 "Cannot revoke these permissions while user '%1' is

actively replicating transactions"

Constant MUST_NOT_BE_REPLICATING

SAP Sybase Error Number 2749

SQL State 42WBE

SQL Code -1080L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Parameter 1 The name of the user.

Probable Cause You attempted to revoke permissions from a user while there are
transactions currently being replicated for that user. This is not al-
lowed.

Error 1081 "Could not refresh tracing: at least one enabled tracing
level must be specified"

Constant NO_TRACING_LEVELS

SAP Sybase Error Number 2750

SQL State 55W24

292 SAP Sybase IQ

Errors and Warnings

Error 1081 "Could not refresh tracing: at least one enabled tracing
level must be specified"

SQL Code -1081L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Table sa_diagnostic_tracing_level contains no rows (tracing levels)

or no tracing levels are enabled.

Error 1082 "Could not refresh tracing: invalid tracing specification on

sa_diagnostic_tracing_level row %1"

Constant INVALID_TRACING_SPEC

SAP Sybase Error 2751

Number

SQL State WW066

SQL Code -1082L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The primary key of the row that is invalid.

Probable Cause You specified an invalid combination of values for the tracing level. Some
invalid combinations are: specified condition is not valid for the tracing type,
or specified tracing type is not valid for the scope.

Error 1083 "Could not refresh tracing: failed to find object %1 on row %2"

Constant TRACING_OBJ_NOT_FOUND

SAP Sybase Error 2752

Number

SQL State WW067

SQL Code -1083L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 293

Errors and Warnings

Error 1083 "Could not refresh tracing: failed to find object %1 on row %2"

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The specified name of the object.

Parameter 2 The primary key of the row on which the check failed.

Probable Cause You misspelled the object name, or you did not qualify the name with user
(and, possibly, table) name. For example, you might have referred to Em-
ployees instead of "DBA"."Employees", or you might have referred to
Employees_trigger instead of "DBA"."Employees"."Employees_trigger".

Error 1084 "Use of feature '%1' is not allowed"

Constant SECURE_FEATURE

SAP Sybase Error Number 2753

SQL State 57W02

SQL Code -1084L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the SQL statement or feature.

Probable Cause You have attempted to use a feature that was disabled by the server
administrator when the database server was started.

Error 1085 "Duplicate key column (%1)"

Constant DUPLICATE_KEY_COLUMN

SAP Sybase Error Number 2754

SQL State 42WC0

SQL Code -1085L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

294 SAP Sybase IQ

Errors and Warnings

Error 1085 "Duplicate key column (%1)"

Parameter 1 The name of the duplicate column.

Probable Cause You supplied a duplicate column name in the list of columns for the
key of a primary key, foreign key, or unique constraint, or an index.

Error 1087 "Could not refresh tracing: volatile_statistics have to be

collected in order for %1 specified on row %2 to be
collected"

Constant NO_VOLATILE_LEVEL_SPEC

SAP Sybase Error Number 2756

SQL State WW068

SQL Code -1087L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The tracing level that caused the error.

Parameter 2 The primary key of the row on which the check failed.

Probable Cause Volatile statistics have to be collected in order for the non-volatile and
connection statistics to be collected.

Error 1088 "ATTACH TRACING TO LOCAL DATABASE cannot be used

with a strongly encrypted database"

Constant NO_LOCAL_CONNECTIONS_TO_ENCRYPTED

SAP Sybase Error Num- 2757

ber

SQL State WW069

SQL Code -1088L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 295

Errors and Warnings

Error 1088 "ATTACH TRACING TO LOCAL DATABASE cannot be used

with a strongly encrypted database"

Probable Cause The local database is strongly encrypted, so you cannot use the LOCAL
DATABASE clause of the ATTACH TRACING statement. You must
specify a connection string with the encryption key for the database.

Error 1089 "Invalid commit action for shared temporary table"

Constant INVALID_SHARED_COMMIT_ACTION

SAP Sybase Error Number 2758

SQL State 52W26

SQL Code -1089L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A global shared temporary table must be declared as ON COMMIT

PRESERVE ROWS or NOT TRANSACTIONAL.

Error 1090 "Function '%1' has invalid parameter '%2' ('%3')"

Constant INVALID_PARAMETER_W_PARM

SAP Sybase Error Number 2759

SQL State 08W94

SQL Code -1090L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 18 on page 2

Parameter 1 The name of the function.

Parameter 2 The name of the parameter.

Parameter 3 Information about the parameter that caused the error.

Probable Cause An error occurred while evaluating a parameter.

296 SAP Sybase IQ

Errors and Warnings

Error 1091 "Constraint '%1' violated: Invalid value in table '%2'"

Constant TABLE_CONSTRAINT_VIOLATED

SAP Sybase Error Num- 2760

ber

SQL State 23508

SQL Code -1091L

ODBC 2 State 42000

ODBC 3 State 23000

Severity Code 16 on page 2

Parameter 1 Name of the constraint (if defined) that was violated by an invalid
value.

Parameter 2 Name of the table containing the column.

Error 1092 "The method you attempted to invoke was not enabled for
your application"

Constant FEATURE_NOT_ENABLED

SAP Sybase Error 2762

Number

SQL State 0A001

SQL Code -1092L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to call a method or use a feature that has not been enabled.
In UltraLite, features are enabled using ULEnable functions or by using
ULInitDatabaseManager instead of ULInitDatabaseManagerNoSQL.

SAP Sybase IQ Error Messages 297

Errors and Warnings

Error 1093 "The size of the character column, variable, or value data
type exceeds 32767"

Constant CHAR_FIELD_SIZE_EXCEEDED

SAP Sybase Error Number 2763

SQL State 54W09

SQL Code -1093L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause The declaration or conversion has specified a character type with byte
length greater than 32767.

Error 1094 "The HTTP header '%1' is reserved and cannot be

modified"

Constant HTTP_HEADER_ATTRIBUTE_RESERVED_XXX

SAP Sybase Error Number 2764

SQL State WW070

SQL Code -1094L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The header causing the failure.

Probable Cause The specified HTTP header is reserved and cannot be modified.

Error 1095 "The specified HTTP header contains illegal or non-ASCII

characters"

Constant HTTP_HEADER_ATTRIBUTE_ASCII

SAP Sybase Error Number 2765

SQL State WW071

SQL Code -1095L

298 SAP Sybase IQ

Errors and Warnings

Error 1095 "The specified HTTP header contains illegal or non-ASCII

characters"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause HTTP headers must contain printable ASCII characters.

Error 1096 "The specified HTTP header is malformed"

Constant HTTP_HEADER_ATTRIBUTE_MALFORMED

SAP Sybase Error Number 2766

SQL State WW072

SQL Code -1096L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The HTTP header is missing the colon delimiter or a folding construct
is malformed.

Error 1097 "ATTACH TRACING could not connect to the tracing

database"

Constant ATTACH_TRACING_FAILED

SAP Sybase Error Num- 2767

ber

SQL State 08W95

SQL Code -1097L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 299

Errors and Warnings

Error 1097 "ATTACH TRACING could not connect to the tracing

database"

Probable Cause A connection to the tracing database could not be established. Check
your connection string and verify that other clients can connect. Note that
if you are trying to attach tracing to another server, perhaps the connec-
tion is being blocked by a firewall.

Messages 1098 through 1118

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1098 "A tracing connection is already active"

Constant TRACING_ALREADY_ATTACHED

SAP Sybase Error Num- 2768

ber

SQL State 08W96

SQL Code -1098L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause This database is already participating in a tracing connection, either as

the sender (the database being traced) or as the receiver (the tracing
database). A database can only send or receive one stream of tracing data
at a time.

Error 1099 "Transact-SQL outer joins are currently disabled"

Constant TSQL_OUTER_JOINS_DISABLED

SAP Sybase Error Num- 2769

ber

SQL State 55W25

SQL Code -1099L

ODBC 2 State ERROR

ODBC 3 State ERROR

300 SAP Sybase IQ

Errors and Warnings

Severity Code 16 on page 2

Probable Cause A partial download was not found for the synchronizing user. This error
could occur if trying to resume from a non-existent partial download or
trying to rollback a non-existent partial download.

Error 1104 "Too many users in database"

Constant TOO_MANY_USERS

302 SAP Sybase IQ

Errors and Warnings

Error 1104 "Too many users in database"

SAP Sybase Error Num- 2775

ber

SQL State 54W10

SQL Code -1104L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You have exceeded the maximum number of users permitted to access
the database. The maximum number of users that are allowed granted
access to a single UltraLite database is four.

Error 1106 "Too many publications specified for operation"

Constant TOO_MANY_PUBLICATIONS

SAP Sybase Error Num- 2777

ber

SQL State WW077

SQL Code -1106L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You have specified too many publications for the required operation.
For example, when retrieving the last download timestamp, you are
only allowed to select one publication.

Error 1107 "Too many references to a BLOB"

Constant TOO_MANY_BLOB_REFS

SAP Sybase Error Num- 2778

ber

SQL State 54W11

SQL Code -1107L

SAP Sybase IQ Error Messages 303

Errors and Warnings

Error 1107 "Too many references to a BLOB"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You have exceeded the maximum number of references to a particular
BLOB. In UltraLite you may have at most 256 references to any one
particular BLOB.

Error 1108 "Unable to access the file system on the device"

Constant CANNOT_ACCESS_FILESYSTEM

SAP Sybase Error Number 2779

SQL State WW078

SQL Code -1108L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause On a Palm device, you have tried to utilize the VFS file system, but
that feature has not been enabled on the device.

Error 1109 "Unable to perform requested operation since this database

uses keyless encryption"

Constant KEYLESS_ENCRYPTION

SAP Sybase Error Num- 2780

ber

SQL State WW079

SQL Code -1109L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

304 SAP Sybase IQ

Errors and Warnings

Error 1109 "Unable to perform requested operation since this database

uses keyless encryption"

Probable Cause The operation you requested on the encryption key failed since the Ul-
traLite database uses keyless encryption. This can occur when you try to
change the encryption key for a database that uses keyless encryption
(obfuscation for example).

Error 1110 "UltraLite cannot synchronize because a synchronization is

already running"

Constant SYNC_NOT_REENTRANT

SAP Sybase Error 2781

Number

SQL State WW080

SQL Code -1110L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to synchronize an UltraLite database which is already syn-
chronizing. You must wait until the current synchronization completes before
starting another. UltraLite allows most operations to run concurrently with
synchronization, but only a single synchronization can be active at a time. This
is generally caused by two different threads attempting a synchronize call or
statement at the same time.

Error 1111 "Information for synchronization was not provided"

Constant SYNC_INFO_REQUIRED

SAP Sybase Error Number 2782

SQL State WW081

SQL Code -1111L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 305

Errors and Warnings

Error 1111 "Information for synchronization was not provided"

Probable Cause You must supply information for synchronization in the synchroni-
zation call.

Error 1112 "Specified file system volume not found for database '%1'"

Constant FILE_VOLUME_NOT_FOUND

SAP Sybase Error Number 2783

SQL State WW082

SQL Code -1112L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the database.

Probable Cause The file system volume you specified in the database file name was
not found. Check the volume name or ordinal.

Error 1113 "Correlation name '%1' is not valid for use with the ROWID
function"

Constant INVALID_CORRELATION_FOR_ROWID

SAP Sybase Error 2784

Number

SQL State 42WBF

SQL Code -1113L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Name of the invalid correlation name.

Probable Cause The correlation name used was not valid for the ROWID function. Only the
correlation names of base tables, temporary tables, global temporary tables
or proxy tables may be used with the ROWID function. The argument of a
ROWID function should not refer to a view, derived table, common table
expression, or a procedure.

306 SAP Sybase IQ

Errors and Warnings

Error 1114 "Invalid setting for SOAP header '%1'"

Constant INVALID_SOAP_HEADER_SETTING

SAP Sybase Error Number 2785

SQL State 42W86

SQL Code -1114L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the invalid SOAP header.

Probable Cause You supplied an invalid value for a SOAP header.

Error 1115 "Table '%1' contains an invalid reference to the ROWID

function"

Constant INVALID_ROWID_PLACEMENT

SAP Sybase Error Number 2786

SQL State 42WC1

SQL Code -1115L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Name of the table that contains the invalid reference.

Probable Cause The ROWID function cannot be used in a computed column expres-
sion or in a CHECK constraint.

Error 1116 "Collation '%1' not supported on this platform"

Constant COLLATION_NOT_SUPPORTED

SAP Sybase Error Number 2787

SQL State WC013

Severity Code 16 on page 2

Probable Cause The MobiLink server uses the remote ID to track synchronization pro-
gress. If the status of the previous upload is unknown then you must resolve
this condition before changing the remote ID.

Messages 1119 through 1138

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1119 "The '%1' property is no longer supported"

Constant UNSUPPORTED_PROPERTY

SAP Sybase Error Number 2791

SQL State 42WC2

SQL Code -1119L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the invalid property.

Probable Cause The specified property is not supported in the current release.

Error 1120 "The dbspace '%1' cannot be dropped because it contains

tables or indexes"

Constant DBSPACE_CONTAINS_TABLES

SAP Sybase Error Number 2792

SQL State 55W26

SQL Code -1120L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 309

Errors and Warnings

Error 1120 "The dbspace '%1' cannot be dropped because it contains

tables or indexes"

Parameter 1 Name of the dbspace

Probable Cause You attempted to drop the named dbspace, but it contains tables or
indexes. You must drop the tables and/or indexes before dropping the
dbspace.

Error 1121 "Not enough free space on device to grow dbspace '%1' by
requested amount"

Error 1124 "The dbicu library and server versions do not match."

Constant ICU_DLL_VERSION_MISMATCH

SAP Sybase Error Number 2796

SQL State WC014

SQL Code -1124L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The server is unable to load ICU components that are required by this
database. Ensure that the correct version of the dbicu libraries are
installed.

Error 1125 "Conflicting INSTEAD OF trigger and WITH CHECK OPTION

on view '%1'"

Constant CHECK_TRIGGER_CONFLICT

SAP Sybase IQ Error Messages 311

Errors and Warnings

Error 1125 "Conflicting INSTEAD OF trigger and WITH CHECK OPTION

on view '%1'"

SAP Sybase Error Num- 2797

ber

SQL State 42W39

SQL Code -1125L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the view with an INSTEAD OF trigger

Probable Cause You attempted an operation that involves a WITH CHECK OPTION
clause that conflicts with an INSTEAD OF trigger. A view defined with
the WITH CHECK OPTION clause cannot refer to a view (possibly
nested) with an INSTEAD OF trigger.

Error 1126 "Operation failed because table or view '%1' has an

INSTEAD OF trigger"

Constant INSTEAD_TRIGGER

SAP Sybase Error Number 2798

SQL State 42W3A

SQL Code -1126L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Name of the view or table with an INSTEAD OF trigger

Probable Cause You attempted an operation that cannot succeed because an IN-
STEAD OF trigger is defined on a target table or view (possibly
nested in another view).

Error 1127 "Positioned update operation attempted on a view with an

INSTEAD OF trigger"

Constant INSTEAD_TRIGGER_POSITIONED

312 SAP Sybase IQ

Errors and Warnings

Error 1127 "Positioned update operation attempted on a view with an

INSTEAD OF trigger"

SAP Sybase Error Num- 2799

ber

SQL State 42W3B

SQL Code -1127L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted a positioned update, positioned delete, put, or wide insert
operation that would involve an INSTEAD OF trigger on a view (pos-
sibly nested). These operations are not supported with INSTEAD OF
triggers on views.

Error 1128 "Start date/time for non-recurring event '%1' is in the past"

Constant EVENT_START_TIME_IN_PAST

SAP Sybase Error Num- 2800

ber

SQL State WE010

SQL Code -1128L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 Name of the event being scheduled.

Probable Cause You have specified an event starting date or time that has already
passed, and the event is not recurring.

Error 1129 "The '%1' attribute contains mismatched parentheses

within '%2'"

Constant INVALID_ATTRIBUTE_MISMATCH_BRACES

SAP Sybase Error Number 2801

SQL State WW086

SAP Sybase IQ Error Messages 313

Errors and Warnings

Error 1129 "The '%1' attribute contains mismatched parentheses

within '%2'"

SQL Code -1129L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The attribute on the procedure.

Parameter 2 The value of the attribute.

Probable Cause The value of the attribute is not valid due to mismatched parenthesis
(or possibly braces if specifying a port option).

Error 1130 "The '%1' attribute is missing a comma within '%2'"

Constant INVALID_ATTRIBUTE_MISSING_COMMA

SAP Sybase Error Number 2802

SQL State WW087

SQL Code -1130L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The attribute on the procedure.

Parameter 2 The value of the attribute.

Probable Cause The value of the attribute is not valid due to a missing comma.

Error 1131 "The attribute '%1' sets an option '%2' that is incompatible
with '%3'"

Constant INVALID_ATTRIBUTE_OPTIONS

SAP Sybase Error Number 2803

SQL State WW088

SQL Code -1131L

ODBC 2 State ERROR

314 SAP Sybase IQ

Errors and Warnings

Error 1131 "The attribute '%1' sets an option '%2' that is incompatible
with '%3'"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The attribute on the procedure.

Parameter 2 The first option of the attribute.

Parameter 3 The second option of the attribute.

Probable Cause The options specified for this attribute are not compatible.

Error 1132 "Maximum row size for table '%1' would be exceeded"

Constant MAX_ROW_SIZE_EXCEEDED

SAP Sybase Error Num- 2804

ber

SQL State WW089

SQL Code -1132L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Table name.

Probable Cause You tried to create or alter a table with a maximum row size greater than
64 KB. In UltraLite, tables must be defined such that the maximum row
size (the sum of the bytes required to store each column) is less than 64
KB.

Error 1133 "Invalid trigger type for view '%1'"

Constant INVALID_TRIGGER_VIEW

SAP Sybase Error Number 2805

SQL State 42W3C

SQL Code -1133L

ODBC 2 State 42000

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 315

Errors and Warnings

Error 1133 "Invalid trigger type for view '%1'"

Severity Code 14 on page 2

Parameter 1 Name of the view

Probable Cause You attempted to create a trigger on a view, but the type of trigger is
supported on base tables only. Only INSTEAD OF triggers can be
created on views.

Error 1134 "Triggers cannot be created on materialized view '%1'"

Constant INVALID_TRIGGER_MATVIEW

SAP Sybase Error Number 2806

SQL State 42W3D

SQL Code -1134L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the materialized view

Probable Cause You attempted to create a trigger on a materialized view. A materi-

alized view is not a valid target for a trigger.

Error 1135 "Invalid regular expression: %1 in '%2'"

Constant INVALID_REGULAR_EXPRESSION

SAP Sybase Error Number 2808

SQL State 2201B

SQL Code -1135L

ODBC 2 State S1000

ODBC 3 State 2201B

Severity Code 16 on page 2

Parameter 1 The reason the regular expression is invalid.

Parameter 2 The invalid regular expression.

Probable Cause The specified regular expression is invalid.

316 SAP Sybase IQ

Errors and Warnings

Error 1136 "Invalid use of escape character '%1'"

Constant INVALID_USE_OF_ESCAPE_CHARACTER

SAP Sybase Error Number 2809

SQL State 2200C

SQL Code -1136L

ODBC 2 State S1000

ODBC 3 State 2200C

Severity Code 16 on page 2

Parameter 1 The escape character that is invalid.

Probable Cause The specified escape character cannot be used.

Error 1137 "Escape character conflict '%1'"

Constant ESCAPE_CHARACTER_CONFLICT

SAP Sybase Error Number 2810

SQL State 2200B

SQL Code -1137L

ODBC 2 State S1000

ODBC 3 State 2200B

Severity Code 16 on page 2

Parameter 1 The escape character that is invalid.

Probable Cause The specified escape character cannot be used.

Error 1138 "The mirror '%1' does not match database '%2'"

Constant MIRROR_FILE_MISMATCH

SAP Sybase Error Num- 2811

ber

SQL State WW090

SQL Code -1138L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 317

Errors and Warnings

Error 1138 "The mirror '%1' does not match database '%2'"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the mirror file

Parameter 2 The name of the database file

Probable Cause The named mirror file does not correspond to the database file. This
could happen if the database was not shut down properly, or if the wrong
mirror file was specified. The mirror file must be moved or discarded
before proceeding, or a different mirror specified.

Messages 1139 through 1158

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1139 "The remote data access feature is not supported on this
platform"

Constant OMNI_FEATURE_NOT_SUPPORTED

SAP Sybase Error Number 2812

SQL State 0AW18

SQL Code -1139L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause You attempted to use a remote data access feature; however, remote
data access are not supported on this platform.

Error 1140 "Unable to start database \"%1\": CHAR collation or

tailoring not supported on this platform"

Constant CHAR_COLLATION_NOT_SUPPORTED

SAP Sybase Error Number 2813

SQL State WC015

SQL Code -1140L

318 SAP Sybase IQ

Errors and Warnings

Error 1140 "Unable to start database \"%1\": CHAR collation or

tailoring not supported on this platform"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The database name.

Probable Cause The specified CHAR collation is not supported on the current plat-
form.

Error 1141 "Unable to start database \"%1\": NCHAR collation or

tailoring not supported on this platform"

Constant NCHAR_COLLATION_NOT_SUPPORTED

SAP Sybase Error Number 2814

SQL State WC016

SQL Code -1141L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The database name.

Probable Cause The specified NCHAR collation is not supported on the current plat-
form.

Error 1142 "Use of statement '%1', which requires feature '%2', is not
allowed"

Constant SECURE_STATEMENT

SAP Sybase Error Number 2815

SQL State 57W04

SQL Code -1142L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 319

Errors and Warnings

Error 1142 "Use of statement '%1', which requires feature '%2', is not
allowed"

Parameter 1 Name of the SQL statement.

Parameter 2 Name of the feature.

Probable Cause You have attempted to use a statement which requires a feature that
was disabled by the server administrator when the database server
was started.

Error 1143 "Encryption has not been enabled."

Constant ENCRYPTION_NOT_ENABLED

SAP Sybase Error Number 2816

SQL State 55W27

SQL Code -1143L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to use encryption without first enabling it. Call ULE-
nableAesDBEncryption or ULEnableAesFipsDBEncryption to ena-
ble encryption.

Error 1144 "'%1' cannot be used as the encoding specification for '%2'
data"

Constant INVALID_OPENSTRING_ENCODING

SAP Sybase Error Num- 2818

ber

SQL State WC017

SQL Code -1144L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The encoding that has been specified

320 SAP Sybase IQ

Errors and Warnings

Error 1144 "'%1' cannot be used as the encoding specification for '%2'
data"

Parameter 2 The data type for which the encoding has been specified

Probable Cause The specified encoding cannot be used for interpreting the given data.
For CHAR data, the encoding must be the database's CHAR character
encoding and for NCHAR data, it must be the database's NCHAR char-
acter encoding.

Error 1145 "Unable to connect: The server did not accept the requested
encryption type"

Constant ENCRYPTION_TYPE_NOT_ACCEPTED

SAP Sybase Error 2819

Number

SQL State 08W97

SQL Code -1145L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause The server only accepts certain encryption types, and the connection's
encryption type is not one of the accepted types. The -ec server option is
used to configure the encryption types that the server accepts.

Error 1146 "LOAD TABLE not allowed on temporary table which has
foreign key references from another table"

Constant INVALID_LOAD_TABLE_WITH_FOREIGN_KEY

SAP Sybase Error Num- 2820

ber

SQL State WL009

SQL Code -1146L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 321

Errors and Warnings

Error 1146 "LOAD TABLE not allowed on temporary table which has
foreign key references from another table"

Probable Cause The LOAD TABLE statement removes all rows in a temporary table
upon failure. If a temporary table being loaded caused an error then the
foreign rows would be orphaned.

Error 1147 "Database '%1' cannot be started on this platform. See http://
ianywhere.com/developer/product_manuals/sqlanywhere/notes/
en/endian_corruption_warning.html"

Constant POSSIBLE_DATABASE_CORRUPTION

SAP Sybase Error 2821

Number

SQL State 08W98

SQL Code -1147L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the database.

Probable Cause It was determined that the database may be corrupt. More information and
instructions on how to proceed are available at: http://ianywhere.com/devel-
oper/product_manuals/sqlanywhere/notes/en/endian_corruption_warn-
ing.html

Error 1148 "Feature not supported by the client version or the client
interface"

Constant NOT_SUPPORTED_BY_CLIENT

SAP Sybase Error 2824

Number

SQL State 0AW19

SQL Code -1148L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

322 SAP Sybase IQ

Errors and Warnings

Error 1148 "Feature not supported by the client version or the client
interface"

Probable Cause You have attempted to use a feature which the server supports but the
client does not. To use the feature, you must upgrade the client library or
use a different client interface. Some features are not supported by the
jConnect or Open Client client interfaces.

Error 1149 "Database '%1' cannot be started on this platform. See http://
ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/
endian_cant_change_platform.html"

Constant DATABASE_ENDIAN_FAILURE

SAP Sybase 2825

Error Number

SQL State 08W99

SQL Code -1149L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 The name of the database.

Probable It was determined that the database cannot be started on the current platform
Cause because doing so could possibly cause an endian related database file corruption. It
will continue to start without problems on a platform with the opposite endian.
More information and instructions on how to proceed are available at: http://ia-
nywhere.com/developer/product_manuals/sqlanywhere/notes/en/endi-
an_cant_change_platform.html

Error 1150 "The SQL scripts DLL cannot be loaded"

Constant INVALID_SCRIPT_DLL

SAP Sybase Error Number 2826

SQL State WW091

SQL Code -1150L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 323

Errors and Warnings

Error 1150 "The SQL scripts DLL cannot be loaded"

Severity Code 16 on page 2

Probable Cause The SQL scripts DLL cannot be loaded. The DLL might be missing or
the version found might not match the version of the database server
being used.

Error 1151 "The logging type ( '%1' ) specified is invalid, not supported or
incompatible"

Constant INVALID_LOAD_LOGGING_TYPE

SAP Sybase Error Num- 2827

ber

SQL State WL010

SQL Code -1151L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Parameter 1 The specified logging type.

Probable Cause The logging type specified for LOAD TABLE is not supported for the
version of the database being used, is incompatible with other specifi-
cations of the statement or is not supported for the specific table being
loaded into.

Error 1152 "Password has expired"

Constant PASSWORD_EXPIRED

SAP Sybase Error Number 2828

SQL State 08WA0

SQL Code -1152L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

324 SAP Sybase IQ

Errors and Warnings

Error 1152 "Password has expired"

Probable Cause You attempted to connect using a valid user ID, but with an expired
password. You can change your password by supplying the New-
Password connection parameter along with the current expired pass-
word.

Error 1153 "Password has expired but cannot be changed because the
database is read-only"

Constant PASSWORD_EXPIRED_READONLY_DB

SAP Sybase Error 2829

Number

SQL State 08WA1

SQL Code -1153L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause You attempted to connect to a read-only database using a valid user ID, but
with an expired password. The password cannot be changed unless the
database is started without the -r option on the database server command
line. Removing -r will permit modifications to the database.

Error 1154 "Traced query (%1, %2) does not exist"

Constant INVALID_TRACED_PLAN

SAP Sybase Error Num- 2830

ber

SQL State 55W28

SQL Code -1154L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Parameter 1 The specified logging session ID.

Parameter 2 The specified query ID.

SAP Sybase IQ Error Messages 325

Errors and Warnings

Error 1154 "Traced query (%1, %2) does not exist"

Probable Cause You attempted to generate a graphical plan for a query saved by diag-
nostic tracing, identified by a logging_session_id and query ID. How-
ever, no such query exists in this database. If it was traced, it was sent to
a different database.

Error 1155 "Unable to close the cursor on table \"%1\". LOAD TABLE cannot
be executed."

Constant CANNOT_LOAD_TEMP_WITH_CURSOR

SAP Sybase Error 2831

Number

SQL State WL011

SQL Code -1155L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the table.

Probable Cause You cannot perform LOAD TABLE on a temporary table that has an open
cursor on it. An attempt to close the cursor failed. A failed LOAD TABLE
would cause all of the rows in the temporary table to be deleted thereby
invalidating the cursor.

Error 1156 "Argument \"%1\" must be a column reference."

Constant TEXT_BAD_COLUMN_REFERENCE

SAP Sybase Error Number 2832

SQL State WT001

SQL Code -1156L

Error 1159 "Non-constant or unknown text query string."

Constant TEXT_QUERY_NOT_KNOWN

SAP Sybase Error Number 2835

SQL State WT004

SAP Sybase IQ Error Messages 327

Errors and Warnings

Error 1159 "Non-constant or unknown text query string."

SQL Code -1159L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The query string argument to a CONTAINS query must be a constant,
or a non-null value in a variable.

Error 1160 "Text configuration \"%1\".\"%2\" not found."

Constant TEXT_CONFIG_NOT_FOUND

SAP Sybase Error Number 2836

SQL State WT005

SQL Code -1160L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The text configuration creator.

Parameter 2 The text configuration name.

Probable Cause The specified text configuration does not exist.

Error 1161 "Text configuration \"%1\" already exists."

Constant TEXT_CONFIG_ALREADY_EXISTS

SAP Sybase Error Number 2837

SQL State WT006

SQL Code -1161L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The text configuration name.

328 SAP Sybase IQ

Errors and Warnings

Error 1161 "Text configuration \"%1\" already exists."

Probable Cause The specified text configuration name already exists.

Error 1162 "Term length outside allowed range."

Constant TEXT_BAD_TERM_LENGTH

SAP Sybase Error Number 2838

SQL State WT007

SQL Code -1162L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The minimum and maximum term lengths must both be greater than 0
and less than or equal to 60 characters.

Error 1163 "Invalid collation: \"%1\"."

Constant TEXT_BAD_COLLATION

SAP Sybase Error Number 2839

SQL State WT008

SQL Code -1163L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The invalid collation string.

Probable Cause The collation was not found, or the tailoring options were invalid.

Error 1164 "Text query parser error: %1"

Constant TEXT_PARSER_ERROR

SAP Sybase Error Number 2840

SQL State WT009

SQL Code -1164L

SAP Sybase IQ Error Messages 329

Errors and Warnings

Error 1164 "Text query parser error: %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The error message returned by the text query parser.

Probable Cause The text query could not be parsed.

Error 1165 "Error creating text index \"%1\" on table \"%2\No message

Constant TEXT_INDEX_CREATION_ERROR

SAP Sybase Error Number 2841

SQL State WT010

SQL Code -1165L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the text index.

Parameter 2 The name of the table.

Probable Cause There was an internal error creating a text index.

Error 1166 "Text indexes are not supported for this database."

Constant TEXT_UPGRADE_REQUIRED

SAP Sybase Error Number 2842

SQL State WT011

SQL Code -1166L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for text indexes.
To use this feature, upgrade your database to the most recent version.

330 SAP Sybase IQ

Errors and Warnings

Error 1167 "Cannot drop a user that owns text configurations"

Constant USER_OWNS_TEXT_CONFIG

SAP Sybase Error Number 2843

SQL State 55W12

SQL Code -1167L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that is the creator of a text configuration.
The text configuration must be dropped first.

Error 1168 "Cannot alter or drop a text configuration referenced by a text

index."

Constant TEXT_CANNOT_ALTER_CONFIG

SAP Sybase Error 2844

Number

SQL State WT012

SQL Code -1168L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause It is not possible to alter or drop a text configuration referenced by a popu-
lated text index or currently being used by a text procedure. Either copy the
configuration and alter the copy, or close all cursors on text procedures and
truncate all indexes that use the configuration.

Error 1169 "Cannot access a table that is part of a text index."

Constant TEXT_CANNOT_USE_TEXT_INDEX

SAP Sybase Error Number 2846

SQL State WT013

SQL Code -1169L

SAP Sybase IQ Error Messages 331

Errors and Warnings

Error 1169 "Cannot access a table that is part of a text index."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause It is not possible to directly manipulate tables created as part of a text
index.

Error 1170 "The materialized view %1 cannot be changed to immediate

because it has already been initialized"

Constant IMMEDIATE_MV_REFRESH_NOT_ALLOWED

SAP Sybase Error Num- 2847

ber

SQL State 42WC3

SQL Code -1170L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the materialized view.

Probable Cause You attempted to change the refresh type to immediate for a material-
ized view which is already in an initialized state. Truncate the view
before changing the refresh type.

Error 1171 "Client application does not allow transfer of data ('%1')"

Constant CLIENT_TRANSFER_NO_VALIDATION

SAP Sybase Error Num- 2848

ber

SQL State WW092

SQL Code -1171L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

332 SAP Sybase IQ

Errors and Warnings

Error 1171 "Client application does not allow transfer of data ('%1')"

Parameter 1 The name of the object being transferred to/from the application.

Probable Cause The client application does not allow the transfer of server initiated data.
To allow transfer of server initiated data, the application must register a
validation callback mechanism with the client library.

Error 1172 "Client application disallowed the transfer of data ('%1')"

Constant CLIENT_TRANSFER_DISALLOWED

SAP Sybase Error 2849

Number

SQL State WW093

SQL Code -1172L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the object being transferred to/from the application.

Probable Cause The client application rejected the transfer of server initiated data. To
allow transfer of server initiated data, the application registered a vali-
dation callback which rejected the transfer of requested data.

Error 1173 "Client library reported an error accessing data during

transfer ('%1')"

Constant CLIENT_TRANSFER_ACCESS_ERROR

SAP Sybase Error 2850

Number

SQL State WW094

SQL Code -1173L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the object being transferred to/from the application.

SAP Sybase IQ Error Messages 333

Errors and Warnings

Error 1173 "Client library reported an error accessing data during

transfer ('%1')"

Probable Cause The client application reported an error while attempting to access the data
for a transfer request from the server. Reasons could include the client
application lacking permissions to the data object or other operating sys-
tem reported errors.

Error 1174 "Cannot create text configuration '%1' because option '%2'
has an inappropriate setting"

Constant TEXT_BAD_OPTION

SAP Sybase Error Num- 2851

ber

SQL State WT014

SQL Code -1174L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the configuration.

Parameter 2 Name of the option with the incorrect setting.

Probable Cause You attempted an operation that needs to create or alter the database
options settings for a text configuration, but one of the options is cur-
rently set to a value not permitted for a text configuration.

Error 1175 "Unable to acquire table locks in specified time"

Constant LOCK_TIMEOUT

SAP Sybase Error Number 2852

SQL State 42WC4

SQL Code -1175L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 21 on page 2

334 SAP Sybase IQ

Errors and Warnings

Error 1175 "Unable to acquire table locks in specified time"

Probable Cause The LOCK TABLE statement could not acquire all the locks in
specified time period

Error 1176 "Plan not available. NOEXEC Plan cannot be generated for
this type of statement"

Constant STMT_NOT_ALLOWED_FOR_NOEXEC_PLAN

SAP Sybase Error Number 2853

SQL State 0AW20

SQL Code -1176L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You tried to get the NOEXEC plan for a statement type for which IQ
cannot generate a NOEXEC plan.

Error 1177 "No plan. HTML_PLAN function is not supported for this type
of statement or database."

Constant HTML_PLAN_NOT_SUPPORTED

SAP Sybase Error 2854

Number

SQL State 0AW21

SQL Code -1177L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You tried to get the HTML plan for a query which is either a SQL Any-
where query or a remote data access/CIS decomposed query.
HTML_PLAN is supported for a pure IQ query.

SAP Sybase IQ Error Messages 335

Errors and Warnings

Error 1178 "Transaction log mirroring cannot be used with database

mirroring"

Constant MIRROR_LOG_WITH_DB_MIRROR

SAP Sybase Error Num- 2855

ber

SQL State WW095

SQL Code -1178L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Transaction log mirroring cannot be used with database mirroring. Use
the dblog utility to disable transaction log mirroring.

Messages 1179 through 1198

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1179 "Unable to start database server: missing license file"

Constant UNABLE_TO_START_ENGINE_MISSING_LICENSE

SAP Sybase Error Num- 2856

ber

SQL State 08WA2

SQL Code -1179L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 17 on page 2

Probable Cause It was not possible to start the database server because the server license
file was not found. The server license file has the same name as the server
executable with the extension ".lic".

Error 1180 "Cannot set database option \"%1\" because it is on the

options watch list"

Constant OPTION_ON_WATCH_LIST

336 SAP Sybase IQ

Errors and Warnings

Error 1180 "Cannot set database option \"%1\" because it is on the

options watch list"

SAP Sybase Error Num- 2857

ber

SQL State WW096

SQL Code -1180L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the option.

Probable Cause An attempt was made to set a database option that is on the options watch
list. The options watch list is used to help find references to options that
have been removed or deprecated.

Error 1181 "The materialized view cannot be changed to immediate

because its definition must not contain more than one query
block"

Constant UPDATABLE_MATVIEW_MULTIBLE_BLOCK_ERR

SAP Sybase Error Num- 2858

ber

SQL State 42WC5

SQL Code -1181L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a material-
ized view whose definition contains more than one query block.

Error 1182 "Statement not allowed on IMMEDIATE REFRESH text

index"

Constant TEXT_IMMEDIATE_NOT_ALLOWED

SAP Sybase IQ Error Messages 337

Errors and Warnings

Error 1182 "Statement not allowed on IMMEDIATE REFRESH text

index"

SAP Sybase Error Num- 2859

ber

SQL State WT015

SQL Code -1182L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You cannot use REFRESH TEXT INDEX or TRUNCATE TEXT IN-
DEX on an index that is created with immediate refresh. You cannot
alter a text index to use or stop using immediate refresh.

Error 1183 "Support for permissions on dbspaces is not available for this
database"

Constant DBSPACE_PERMS_NOT_SUPPORTED

SAP Sybase Error 2860

Number

SQL State 0AW22

SQL Code -1183L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause The statement being executed requires support for permissions on dbspaces,
but the database being used does not have this capability. The database must be
recreated or upgraded using a version of the server that supports permissions
on dbspaces.

Error 1184 "Cannot drop last unique index of an immediate materialized

view"

Constant DELETE_UPDATABLE_MATVIEW_INDEX_ERR

SAP Sybase Error Num- 2861

ber

338 SAP Sybase IQ

Errors and Warnings

Error 1184 "Cannot drop last unique index of an immediate materialized

view"

SQL State 55W21

SQL Code -1184L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to drop the last unique index on non-nullable columns of
an immediate materialized view. Immediate materialized view needs at
least one unique index on non-nullable columns to be valid.

Error 1185 "Index validation failed for table %1, index %2 with code:
%3"

Constant CORRUPT_ULTRALITE_INDEX

SAP Sybase Error Number 2862

SQL State WI002

SQL Code -1185L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 The name of the table.

Parameter 2 The name of the index.

Parameter 3 The specific kind of corruption that was found.

Probable Cause UltraLite database validation failed while validating the specified
index. The code provides more specific information on the validation
failure.

Error 1186 "Database page validation failed with code: %1"

Constant CORRUPT_ULTRALITE_DATABASE

SAP Sybase Error Number 2863

SQL State WI003

SAP Sybase IQ Error Messages 339

Errors and Warnings

Error 1186 "Database page validation failed with code: %1"

SQL Code -1186L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 The specific kind of corruption that was found.

Probable Cause UltraLite database validation failed while validating the database
pages. The code provides more specific information on the validation
failure.

Error 1187 "Cannot append when using compression or encryption"

Constant UNLOAD_CANNOT_APPEND

SAP Sybase Error Num- 2864

ber

SQL State WL012

SQL Code -1187L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The UNLOAD statement cannot append to a file when using com-
pression or encryption. Either the compressed or encrypted keywords
were specified, or the file being appended to is compressed or encryp-
ted.

Error 1188 "LOAD TABLE error: %1"

Constant LOAD_TABLE_ERROR

SAP Sybase Error Number 2865

SQL State WL013

SQL Code -1188L

ODBC 2 State ERROR

ODBC 3 State ERROR

340 SAP Sybase IQ

Errors and Warnings

Error 1188 "LOAD TABLE error: %1"

Severity Code 16 on page 2

Parameter 1 Description of the failure encountered

Probable Cause The LOAD TABLE statement failed. The message specifies the ac-
tual problem that occurred.

Error 1189 "The UTF-16 endian specified does not match the Byte Order
Mark found in the data"

Constant UTF16_ENDIAN_MISMATCH

SAP Sybase Error Num- 2866

ber

SQL State WC004

SQL Code -1189L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The specified UTF-16 encoding explicitly specifies the expected endian
of the data; however, the Byte Order Mark found at the beginning of the
data indicates that the data is encoded in the opposite endian.

Error 1190 "LOAD TABLE is not allowed on a materialized view %1"

Constant LOAD_TABLE_ON_MATVIEW_ERROR

SAP Sybase Error Number 2867

SQL State WL014

SQL Code -1190L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the materialized view on which load was attempted.

Probable Cause LOAD TABLE statement is not allowed on a materialized view.

SAP Sybase IQ Error Messages 341

Errors and Warnings

Error 1191 "LOAD TABLE not allowed: initialized immediate

materialized view %1 depends on %2"

Constant LOAD_TABLE_WITH_IMV

SAP Sybase Error Number 2868

SQL State WL015

SQL Code -1191L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the dependent initialized immediate materialized view.

Parameter 2 Name of the table on which load was performed.

Probable Cause LOAD TABLE is not permitted on any table that has dependent ini-
tialized immediate materialized views.

Error 1192 "Cannot update multiple tables immediate materialized view

%1 depends on"

Constant CANNOT_UPDATE_TWO_TABLES_IMV

SAP Sybase Error 2869

Number

SQL State 55W29

SQL Code -1192L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the view that depends on two or more tables in the update
statement.

Probable Cause You attempted to simultaneously update two or more tables initialized
immediate materialized view depends on. No more than one base table an
immediate materialized view depends on can be updated in a statement.

342 SAP Sybase IQ

Errors and Warnings

Error 1193 "TRUNCATE TABLE not allowed: initialized immediate

materialized view %1 depends on %2"

Constant TRUNCATE_TABLE_WITH_IMV

SAP Sybase Error Number 2870

SQL State 55W30

SQL Code -1193L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the dependent initialized immediate materialized view.

Parameter 2 Name of the table on which TRUNCATE TABLE was performed.

Probable Cause TRUNCATE TABLE is not permitted on any table that has dependent
initialized immediate materialized views.

Error 1194 "Login policy \"%1\" already exists"

Constant LOGIN_POLICY_ALREADY_EXISTS

SAP Sybase Error Number 2871

SQL State WW097

SQL Code -1194L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the login policy.

Probable Cause An attempt was made to create a login policy that already exists in the
database.

Error 1195 "Login policy \"%1\" not found"

Constant LOGIN_POLICY_NOT_FOUND

SAP Sybase Error Number 2872

SQL State WW098

344 SAP Sybase IQ

Errors and Warnings

Error 1197 "Login policy \"%1\" in use"

Probable Cause The named login policy is associated with a user in the database. Any
users associated with the login policy must be assigned a different
login policy before the named login policy can be dropped.

Error 1198 "User \"%1\" already exists"

Constant USER_ALREADY_EXISTS

SAP Sybase Error Number 2875

SQL State WW101

SQL Code -1198L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the user.

Probable Cause An attempt was made to create a user that already exists in the data-
base.

Messages 1199 through 1218

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1199 "The materialized view cannot be changed to immediate

because COUNT(*) must be part of the SELECT list."

Constant UPDATABLE_MATVIEW_MISSING_COUNT

SAP Sybase Error Number 2876

SQL State 42WC6

SQL Code -1199L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

SAP Sybase IQ Error Messages 345

Errors and Warnings

Error 1199 "The materialized view cannot be changed to immediate

because COUNT(*) must be part of the SELECT list."

Probable Cause You attempted to change the refresh type to immediate for a materi-
alized view whose definition does not include COUNT(*) in the
SELECT list.

Error 1200 "Client library reported a permissions error accessing object

('%1') during transfer"

Constant CLIENT_TRANSFER_PERMS_ERROR

SAP Sybase Error 2877

Number

SQL State WW103

SQL Code -1200L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the object being transferred to/from the application.

Probable Cause The client application reported a permissions error while attempting to
access the object for a data transfer request from the server. The client
application likely does not have the necessary operating system authori-
zation required to access the object.

Error 1201 "Client library reported an error opening object ('%1') during
transfer"

Constant CLIENT_TRANSFER_OPEN_ERROR

SAP Sybase Error Num- 2878

ber

SQL State WW102

SQL Code -1201L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

346 SAP Sybase IQ

Errors and Warnings

Error 1201 "Client library reported an error opening object ('%1') during
transfer"

Parameter 1 The name of the object being transferred to/from the application.

Probable Cause The client application reported an error while attempting to open the
object for a data transfer request from the server. Reasons could include
an invalid name for the object or a missing object.

Error 1202 "Operation not allowed on a table with dependent immediate

materialized views"

Constant INVALID_OPERATION_FOR_TBL_WITH_IMV

SAP Sybase Error Num- 2879

ber

SQL State 55W31

SQL Code -1202L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Requested operation cannot be applied to a table with dependent im-
mediate materialized views.

Error 1203 "WRITETEXT not allowed: immediate materialized view %1

depends on %2"

Constant WRITETEXT_TABLE_WITH_IMV

SAP Sybase Error Num- 2880

ber

SQL State 55W32

SQL Code -1203L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the dependent immediate materialized view.

Parameter 2 Name of the base table.

SAP Sybase IQ Error Messages 347

Errors and Warnings

Error 1203 "WRITETEXT not allowed: immediate materialized view %1

depends on %2"

Probable Cause WRITETEXT is not allowed on base tables that have dependent initial-
ized immediate materialized views. No operation that does not fire trig-
gers is allowed on base tables with dependent initialized immediate
materialized views.

Error 1204 "INSERT...ON EXISTING UPDATE not allowed: immediate

materialized view %1 depends on %2"

Constant UPDATE_ON_EXISTING_DEP_IMV

SAP Sybase Error Num- 2881

ber

SQL State 55W33

SQL Code -1204L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of dependent immediate materialized view.

Parameter 2 The name of the base table into which the insert was performed.

Probable Cause Insert statement with ON EXISTING clause is not permitted on a base
table if the base table has dependent initialized immediate materialized
view.

Error 1205 "External environment '%1' could not be found"

Constant EXTERN_ENV_NOT_FOUND

SAP Sybase Error Number 2882

SQL State WJ030

SQL Code -1205L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 Name of the external environment.

348 SAP Sybase IQ

Errors and Warnings

Error 1205 "External environment '%1' could not be found"

Probable Cause You attempted to define an object for an external environment that has
not been added.

Error 1206 "External environments are not supported for this

database"

Constant EXTERN_ENV_UPGRADE

SAP Sybase Error Number 2883

SQL State WW104

SQL Code -1206L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for external en-
vironments. To use this feature, upgrade your database to the most
recent version.

Error 1207 "Invalid use of NEAR operator in text query."

Constant TEXT_INVALID_NEAR

SAP Sybase Error Number 2884

SQL State WT016

SQL Code -1207L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause Only terms and prefixes are allowed as arguments to a NEAR oper-
ator.

Error 1208 "Invalid partition bound value '%1'"

Constant BAD_PARTITION_BOUND_VALUE

SAP Sybase Error Number 2885

SAP Sybase IQ Error Messages 349

Errors and Warnings

Error 1208 "Invalid partition bound value '%1'"

SQL State WW105

SQL Code -1208L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The partition bound value.

Probable Cause The partition bound value is invalid and cannot be used.

Error 1209 "Cannot convert value '%1' to an %2"

Constant PARTITION_BOUND_VALUE_CONVERSION

SAP Sybase Error Number 2886

SQL State WW106

SQL Code -1209L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The partition bound value.

Parameter 2 The type of the partition key.

Probable Cause The value is not compatible with the type of the partition key.

Error 1210 "Partition bound value '%1' out of order"

Constant PARTITION_BOUND_VALUE_ORDER

SAP Sybase Error Number 2887

SQL State WW107

SQL Code -1210L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

350 SAP Sybase IQ

Errors and Warnings

Error 1210 "Partition bound value '%1' out of order"

Parameter 1 The partition bound value.

Probable Cause Range partition bound values must be provided in ascending order.

Error 1211 "MERGE statement ANSI cardinality violation on table

'%1'"

Constant MERGE_CARDINALITY_VIOLATION

SAP Sybase Error Number 2888

SQL State 23509

SQL Code -1211L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the table being updated

Probable Cause You have attempted to execute the MERGE statement and the same
row is the target of a WHEN MATCHED clause more than once

Error 1212 "Connection disallowed by login policy for this user"

Constant CONNECTION_DISALLOWED_BY_LOGIN_POLICY

SAP Sybase Error Number 2889

SQL State 28W15

SQL Code -1212L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A connection attempt was disallowed based on the login policy for the
user. It may be necessary for a user with DBA authority to reset this
user via the ALTER USER statement.

352 SAP Sybase IQ

Errors and Warnings

Error 1215 "External library '%1' not loaded"

Parameter 1 The external library that is not loaded

Probable Cause The external library cannot be unloaded as it is not current loaded.

Error 1216 "The arguments to this procedure must be literal strings."

Constant TEXT_NEED_CONSTANT_ARGUMENT

SAP Sybase Error Number 2894

SQL State WT017

SQL Code -1216L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause This procedure only accepts literal strings as arguments.

Error 1217 "Synchronization profile '%1' not found"

Constant SYNC_PROFILE_NOT_FOUND

SAP Sybase Error Number 2895

SQL State 42W75

SQL Code -1217L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the synchronization profile.

Probable Cause You tried to access a synchronization profile that the database could
not find.

Error 1218 "The materialized view cannot be changed to immediate because

it does not have a unique index on non-aggregate, non-nullable
columns"

Constant UPDATABLE_MATVIEW_NON_AGGR_INDEX

SAP Sybase IQ Error Messages 353

Errors and Warnings

Error 1218 "The materialized view cannot be changed to immediate because

it does not have a unique index on non-aggregate, non-nullable
columns"

SAP Sybase Error 2896

Number

SQL State 42WC7

SQL Code -1218L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized
view which does not have a unique index on non-aggregate non-nullable
columns. Create a unique index on the materialized view before changing the
refresh type.

1219 - 1428

Probable Cause You have specified one of the options more than once when executing
the CREATE DATABASE statement.

Error 1222 "Multiplex Server '%1' not found"

Constant IQ_MULTIPLEX_SERVER_NOT_FOUND

SAP Sybase Error Number 2900

SQL State WW110

SQL Code -1222L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 355

Errors and Warnings

Error 1222 "Multiplex Server '%1' not found"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of Multiplex Server.

Probable Cause Multiplex Server with this name does not exist.

Error 1223 "Synchronization profile '%1' already exists"

Constant SYNC_PROFILE_ALREADY_EXISTS

SAP Sybase Error Number 2901

SQL State 42W76

SQL Code -1223L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the synchronization profile.

Probable Cause You tried to create a synchronization profile that already exists.

Error 1224 "Synchronization profile '%1' has invalid parameter '%2'"

Constant SYNC_PROFILE_INVALID

SAP Sybase Error Number 2902

SQL State 42W77

SQL Code -1224L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the synchronization profile that is invalid.

Parameter 2 Name of the parameter in the profile that has the problem.

Probable Cause You tried to create or alter a synchronization profile using a string
containing an invalid parameter setting.

356 SAP Sybase IQ

Errors and Warnings

Error 1225 "Synchronization profiles are not supported for this

database"

Constant SYNC_PROFILE_UPGRADE

SAP Sybase Error Number 2903

SQL State 42W78

SQL Code -1225L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for synchroniza-
tion profiles. To use this feature, upgrade your database to the most
recent version.

Error 1226 "Foreign key columns do not match the primary key or a
uniqueness constraint in \"%1\No message

Constant NO_MATCHING_INDEX

SAP Sybase Error Number 2904

SQL State 42R04

SQL Code -1226L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the primary table.

Probable Cause An attempt was made to create a foreign key, but the columns speci-
fied do not match the primary key or a uniqueness constraint for the
referenced table.

Error 1227 "Internal error. Contact Sybase IQ support. %1."

Constant IQ_MPX_INTERNAL_ERROR

SAP Sybase Error Number 2905

SQL State WI111

SAP Sybase IQ Error Messages 357

Errors and Warnings

Error 1227 "Internal error. Contact Sybase IQ support. %1."

SQL Code -1227L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The error description.

Probable Cause The multiplex DDL statement (CREATE/ALTER/DROP) failed with

internal error due to specified reason.

Error 1228 "Syntax error, cannot specify IQ specific options (%1)

when creating a table in an SA database"

Constant IQ_ONLY_SYNTAX_ERROR

SAP Sybase Error Number 2907

SQL State 42W72

SQL Code -1228L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 IQ option used.

Probable Cause An attempt was made to use IQ specific create table syntax when
creating a table in an SA database

Error 1229 "Reorganize table is already being run on table \"%1\No

message

Constant REORG_ALREADY_IN_PROGRESS

SAP Sybase Error Number 2908

SQL State 54W51

SQL Code -1229L

ODBC 2 State 54000

ODBC 3 State 54000

358 SAP Sybase IQ

Errors and Warnings

Error 1229 "Reorganize table is already being run on table \"%1\No

message

Severity Code 16 on page 2

Parameter 1 The name of the table.

Probable Cause There is already a REORGANIZE TABLE statement being run on

this table. Only one such statement can be executing on a table at any
time.

Error 1230 "Too many open cursors"

Constant TOO_MANY_CURSORS

SAP Sybase Error Number 2909

SQL State 54W12

SQL Code -1230L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 17 on page 2

Probable Cause You exceeded the number of cursors that can be open on a single
UltraLite database. Check to ensure you are freeing statements when
you are done with them.

Error 1231 "Statement timed out: '%1!s!'"

Constant STATEMENT_TIMEOUT

SAP Sybase Error Number 2910

SQL State 57W05

SQL Code -1231L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Statement type

Probable Cause The statement failed because it did not complete within the allotted or
specified time.

SAP Sybase IQ Error Messages 359

Errors and Warnings

Error 1232 "Attempt to start a second snapshot in a transaction"

Constant SNAPSHOT_ALREADY_STARTED

SAP Sybase Error Number 2911

SQL State 42WC9

SQL Code -1232L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A transaction tried to start a snapshot (for example, using the BEGIN
SNAPSHOT statement) while another snapshot was already active.

Error 1233 "The materialized view %1 cannot be changed to immediate

because it does not have a unique index on non-nullable
columns."

Constant IMMEDIATE_MV_NO_UNIQUE_INDEX

SAP Sybase Error 2912

Number

SQL State 42WCA

SQL Code -1233L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the materialized view.

Probable Cause You attempted to change the refresh type to immediate for a materialized
view which does not have a unique index on non-nullable columns. Create a
unique index on the materialized view before changing the refresh type.

Error 1234 "Dbspace file with name or path '%1' already exists."

Constant IQ_DBSPACEFILE_UPDATE_ERROR

SAP Sybase Error Number 2913

SQL State 42W7A

360 SAP Sybase IQ

Errors and Warnings

Error 1234 "Dbspace file with name or path '%1' already exists."

SQL Code -1234L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Parameter 1 Logical file name or physical path from CREATE/ALTER

DBSPACE SQL statement.

Probable Cause Error code to use for catalog update errors in IQ code.

Error 1235 "Too many columns in SELECT list"

Constant TOO_MANY_COLUMNS_IN_SELECT

SAP Sybase Error Number 2914

SQL State 54W13

SQL Code -1235L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You executed a statement with too many expressions in the SELECT
list. The number of expressions within a SELECT list is limited to
60000.

Error 1236 "Too many expressions in GROUP BY list"

Constant TOO_MANY_COLUMNS_IN_GROUPBY

SAP Sybase Error Number 2915

SQL State 54W14

SQL Code -1236L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 361

Errors and Warnings

Error 1236 "Too many expressions in GROUP BY list"

Probable Cause You executed a statement with too many expressions in the GROUP
BY list. The number of expressions within a GROUP BY list is limi-
ted to 60000.

Error 1237 "Too many columns in procedure result set"

Constant TOO_MANY_COLUMNS_IN_PROC_RES

SAP Sybase Error 2916

Number

SQL State 54W15

SQL Code -1237L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You executed a statement with too many expressions in the GROUP BY list.
The number of expressions within a GROUP BY list is limited to 60000. You
executed a CREATE PROCEDURE or ALTER PROCEDURE statement.
The resulting number of columns in the result set of the procedure would
exceed the server's limit.

Error 1239 "Partition name '%1' is not part of table '%2'"

Constant UNKNOWN_PARTITION_NAME

SAP Sybase Error Number 2918

SQL State WW113

SQL Code -1239L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The partition name.

Parameter 2 The table name.

Probable Cause This partition name is not part or this table.

362 SAP Sybase IQ

Errors and Warnings

Messages 1240 through 1261

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1240 "The provided stoplist is too long."

Constant TEXT_STOPLIST_TOO_LONG

SAP Sybase Error Number 2920

SQL State WT018

SQL Code -1240L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A text configuration stop list must be less than 8000 bytes.

Error 1241 "Value-sensitive cursor used after a TRUNCATE"

Constant HOLD_CURSOR_AFTER_TRUNCATE

SAP Sybase Error Number 2924

SQL State 24001

SQL Code -1241L

ODBC 2 State 24000

ODBC 3 State 24000

Severity Code 16 on page 2

Probable Cause You attempted to use a value-sensitive cursor opened WITH HOLD
after a TRUNCATE or after a COMMIT removed all rows from a
temporary table declared as ON COMMIT DELETE ROWS.

Error 1242 "Parameter ('%1') is already in the configuration

specification of the specified Multiplex Server"

Constant IQ_MULTIPLEX_ALTERTOSAMECONFIG

SAP Sybase Error Number 2925

SQL State WW117

SAP Sybase IQ Error Messages 363

Errors and Warnings

Error 1242 "Parameter ('%1') is already in the configuration

specification of the specified Multiplex Server"

Constant CANNOT_USE_PARTITION_NAME

SAP Sybase Error Number 2928

SQL State WW221

SQL Code -1245L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The partition name.

Probable Cause This partition name has already been used.

Error 1246 "Partition '%1' is not adjacent to or before partition '%2'"

Constant PARTITIONS_NOT_ADJACENT

SAP Sybase Error Number 2929

SQL State WW222

SQL Code -1246L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The partition name.

Parameter 2 The partition name.

Probable Cause These partitions are not adjacent - they cannot be merged.

Error 1253 "The text index %1 needs to be refreshed"

Constant TEXT_MATCHING_INDEX_NOT_REFRESHED

SAP Sybase Error Number 2936

SQL State WT019

SQL Code -1253L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the text index that needs to be refreshed.

SAP Sybase IQ Error Messages 367

Errors and Warnings

Error 1253 "The text index %1 needs to be refreshed"

Probable Cause There is a text index that matches the query, but it needs to be re-
freshed before it is used.

Error 1254 "MERGE statement for table '%1' failed because of a

RAISERROR specification in the statement"

Constant MERGE_USER_SPECIFIED_ERROR

SAP Sybase Error 2937

Number

SQL State 23510

SQL Code -1254L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the table being merged into

Probable Cause You have attempted to execute a MERGE statement that contains the
RAISERROR clause in one or more merge operation branches and one of
the input rows satisfies the conditions for one of these branches

Error 1255 "Cannot merge partition '%1' into '%2' for column '%3'"

Constant CANNOT_MERGE_COLUMN_PARTITION

SAP Sybase Error Number 2938

SQL State WW228

SQL Code -1255L

ODBC 2 State ERROR

ODBC 3 State ERROR

SQL State 42WD2

SQL Code -1258L

SAP Sybase IQ Error Messages 369

Errors and Warnings

Error 1258 "'<' or '<=' operator can only be used in the event condition
with this event type"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Event of this type can be defined with a condition having < or <=
operator only.

Error 1259 "Hash error: %1"

Constant HASH_ERROR

SAP Sybase Error Number 2942

SQL State 08W92

SQL Code -1259L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Description of the error that occurred.

Probable Cause An error occurred during hashing.

Error 1260 "This server is not licensed to support the '%1' feature"

Errors and Warnings

Error 1263 "Event notification queue '%1' not found"

SAP Sybase Error Number 2950

SQL State WE014

SQL Code -1263L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The name of the event notification queue

Probable Cause The named event notification queue was not found. The operation
failed.

Error 1264 "Event object name '%1' is not valid"

Constant INVALID_EVENT_OBJECT_NAME

SAP Sybase Error Number 2951

SQL State WE015

SQL Code -1264L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the event object

Probable Cause The given name is not valid for an event object (notification queue or
user event). Names are limited in length to 32 characters (bytes), and
cannot contain certain characters such as '*' or '@'.

Error 1265 "Event object named '%1' already exists"

Constant EVENT_OBJECT_ALREADY_EXISTS

SAP Sybase Error Number 2952

SQL State WE016

SQL Code -1265L

Error 1268 "The materialized view cannot be changed to immediate

because its definition contains an illegal construct."

Constant UPDATABLE_MATVIEW_ERR

SAP Sybase Error Number 2955

SQL State 42WCB

SQL Code -1268L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materi-
alized view whose definition contains an illegal construct.

Error 1269 "Service statement definition is invalid or unsupported"

Constant SERVICE_STATEMENT_INVALID

SAP Sybase Error Number 2956

SQL State 42WCC

SQL Code -1269L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Either the statement provided is invalid or it is unsupported within the
context of a service.

Error 1270 "Must own table '%1' to make an immediate view reference it"

Constant NO_PERMS_FOR_IMV

SAP Sybase Error 2957

Number

SQL State 42WD3

SQL Code -1270L

ODBC 2 State ERROR

374 SAP Sybase IQ

Errors and Warnings

Error 1270 "Must own table '%1' to make an immediate view reference it"

SQL Code -1273L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the table.

Probable Cause You attempted to create a table without columns.

Error 1274 "Index '%1' has no columns"

Constant INDEX_HAS_NO_COLUMNS

SAP Sybase Error Number 2961

SQL State 0EW01

SQL Code -1274L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the index.

Probable Cause You attempted to create an index without columns.

Error 1275 "Invalid domain '%1'"

Constant INVALID_DOMAIN

SAP Sybase Error Number 2962

SQL State 54W52

Errors and Warnings

Error 1277 "Parameter '%1' cannot be null"

Probable Cause The specified parameter cannot be null.

Error 1278 "Operation is not allowed"

Constant ULTRALITEJ_OPERATION_NOT_ALLOWED

SAP Sybase Error Number 2965

SQL State WW230

SQL Code -1278L

ODBC 2 State ERROR

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The requested operation is not allowed while schema is being modi-
fied.

Error 1279 "Operation '%1' failed for reason: '%2'"

Constant ULTRALITEJ_OPERATION_FAILED

SAP Sybase Error Number 2966

SQL State WW231

SQL Code -1279L

ODBC 2 State ERROR

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The name of the operation.

Parameter 2 The cause of the failure.

Probable Cause The requested operation failed.

Error 1280 "Underflow when converting '%1'"

Constant UNDERFLOW

SAP Sybase Error Number 2967

SQL State WW232

378 SAP Sybase IQ

Errors and Warnings

Error 1280 "Underflow when converting '%1'"

SQL Code -1280L

ODBC 2 State ERROR

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The type being converted.

Probable Cause An underflow occurred when converting the specified type. The
source type may be too small (for example zero length binary) or
value may be too small to be represented by the destination type.

Error 1281 "Another connection has the row in '%1' locked"

Constant ROW_LOCKED

SAP Sybase Error Number 2968

SQL State 42W80

SQL Code -1281L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 21 on page 2

Parameter 1 Table that generates the error.

Probable Cause You attempted modify or delete a row that is locked by another con-
nection. The row will be unlocked once that connection commits or
rolls back.

Messages 1283 through 1302

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1283 "A CONTAINS query is not allowed on the view or derived table
'%1'."

Constant TEXT_INVALID_VIEW_FOR_CONTAINS

SAP Sybase Error 2970

Number

SAP Sybase IQ Error Messages 379

Errors and Warnings

Error 1283 "A CONTAINS query is not allowed on the view or derived table
'%1'."

SQL State WT020

SQL Code -1283L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the view or derived table that cannot be queried with CON-
TAINS.

Probable Cause A view or derived table can only be queried using CONTAINS if it does not
use TOP, FIRST, DISTINCT, GROUP BY, or FOR XML. In addition, the list
of columns to search must all come from a single base table in the FROM
clause of the view. They cannot come from multiple tables, or from another
view or derived table in the FROM clause.

Error 1284 "Invalid partition key specification: must use '%1'. "

Constant CANNOT_CHANGE_PARTITION_KEY

SAP Sybase Error Number 2971

SQL State WW233

SQL Code -1284L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The partition key column name.

Probable Cause Partition key cannot be changed for ALTER TABLE ADD PARTI-
TION. It must specify the same partition key column as the CREATE
TABLE did.

Error 1285 "%1 -- Transaction rolled back"

Constant IQ_TRANSACTION_ROLLBACK

SAP Sybase Error Number 2973

SQL State 40W09

380 SAP Sybase IQ

Errors and Warnings

Error 1285 "%1 -- Transaction rolled back"

SQL Code -1285L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Error because of which the transaction rolled back.

Probable Cause This transaction has been rolled back because the server encountered
an error during a critical operation.

Error 1286 "Immediate materialized view definition cannot contain a

SUM function over a nullable expression."

Constant UPDATABLE_MATVIEW_SUM_NULL_EXPR

SAP Sybase Error Num- 2974

ber

SQL State 42WCD

SQL Code -1286L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized
view whose definition contains a SUM function over a nullable expres-
sion.

Error 1287 "Operation not allowed on global temporary table %1 as it

is in use. Reconnect and try again."

Constant IQ_GTT_ALTER_DROP_NOTALLOWED

SAP Sybase Error Number 2975

SQL State 55W35

SQL Code -1287L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 381

Errors and Warnings

Error 1287 "Operation not allowed on global temporary table %1 as it

is in use. Reconnect and try again."

Severity Code 16 on page 2

Parameter 1 Name of the table.

Probable Cause A global temporary table cannot be modified if it is in use. The user
must reconnect and re-execute the statement.

Error 1288 "'%1' statement is not allowed on a mirrored database"

Constant STMT_NOT_ALLOWED_WITH_MIRRORING

SAP Sybase Error Number 2976

SQL State WW120

SQL Code -1288L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Statement that generates the error.

Probable Cause You attempted to execute a statement that is not allowed when using a
mirrored database.

Error 1289 "LOAD TABLE option '%1' not allowed with FORMAT %2"

Constant INVALID_LOAD_TABLE_OPTION

SAP Sybase Error Number 2977

SQL State WL016

SQL Code -1289L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the option.

Parameter 2 The load table format.

382 SAP Sybase IQ

Errors and Warnings

Error 1289 "LOAD TABLE option '%1' not allowed with FORMAT %2"

Probable Cause The specified LOAD TABLE option is not meaningful for the LOAD
TABLE FORMAT.

Error 1290 "FOR UPDATE or FOR READ ONLY clause must be specified
on PREPARE (not on DECLARE CURSOR)"

Constant CURSOR_UPDATABILITY_CHANGED

SAP Sybase Error Num- 2978

ber

SQL State 42WD4

SQL Code -1290L

ODBC 2 State S1009

ODBC 3 State HY092

Severity Code 16 on page 2

Probable Cause You specified the FOR UPDATE or FOR READ ONLY clause on a
DECLARE CURSOR statement. The FOR UPDATE or FOR READ
ONLY clause must be specified on the PREPARE statement and not the
DECLARE CURSOR statement.

Error 1291 "Column '%1' Partition '%2' may not be assigned to a

dbspace because partitioning is not supported for
datatype '%3'."

Constant INVALID_COL_PARTITION_PLACEMENT

SAP Sybase Error Number 2979

SQL State WW235

SQL Code -1291L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The column name

Parameter 2 The partition name

Parameter 3 The data type

SAP Sybase IQ Error Messages 383

Errors and Warnings

Error 1291 "Column '%1' Partition '%2' may not be assigned to a

dbspace because partitioning is not supported for
datatype '%3'."

Probable Cause The column storage for certain datatypes (such as the BIT datatype)
cannot be assigned to a dbspace.

Error 1292 "Column '%1' may not be assigned to a dbspace because

partitioning is not supported for datatype '%2'."

Constant INVALID_COL_PLACEMENT

SAP Sybase Error Number 2980

SQL State WW236

SQL Code -1292L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The column name

Parameter 2 The data type

Probable Cause The column storage for certain datatypes (such as the BIT datatype)
cannot be assigned to a dbspace.

Error 1293 "Partition key of '%1' is unsupported."

Constant UNSUPPORTED_PARTITION_KEY

SAP Sybase Error Number 2981

SQL State WW237

SQL Code -1293L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The column datatype

Probable Cause Partitioning over the specified datatype is not supported.

384 SAP Sybase IQ

Errors and Warnings

Error 1294 "Parameter (%1) length has exceeded its limit (%2)."

Constant IQ_PARAM_LENGTH_EXCEED_LIMIT

SAP Sybase Error Number 2983

SQL State WW122

Parameter 1 Parameter name.

Probable Cause Specified value for a given parameter already exist in the multiplex
configuration.

Error 1297 "No of servers in multiplex setup has reached to the

maximum limit."

Constant IQ_MULTIPLEX_SERVER_LIMIT_EXCEEDED

SAP Sybase Error Number 2986

SQL State WW125

SQL Code -1297L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause No of servers in multiplex setup has reached to the maximum limit.
User cannot add any more secondary servers.

Error 1298 "Cannot alter multiplex failover node and other multiplex
server properties in the same statement."

Constant IQ_INVALID_CONFIG_FAILOVER_COMBINATION

SAP Sybase Error Number 2987

SQL State WW126

SQL Code -1298L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Users are not allowed to alter the multiplex failover node status and
other multiplex server properties in the same statement.

386 SAP Sybase IQ

Errors and Warnings

Error 1299 "Drop multiplex server is allowed only in a multiplex

setup."

Constant IQ_DROP_MPX_ALLOWED_ONLY_IN_MPX

SAP Sybase Error Number 2988

SQL State WW127

SQL Code -1299L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Drop multiplex server is allowed only in a multiplex setup.

Error 1300 "Cannot add first multiplex server with excluded status."

Constant IQ_FIRST_SECONDARY_SERVER_CANNOT_BE_EXCLU-
DED

ODBC 2 State 37000

ODBC 3 State 54000

Severity Code 19 on page 2

Probable Cause You executed a MESSAGE...FOR CONNECTION statement and the

maximum number of messages for the connection have already been
queued.

388 SAP Sybase IQ

Errors and Warnings

Error 1304 "Could not create a new text index for this table with the
same settings as \"%1\No message

Constant TEXT_INDEX_SAME_SETTING_IDX

SAP Sybase Error Number 2992

SQL State WT021

SQL Code -1304L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the other text index with the same settings.

Probable Cause Two text indexes with the same column list and configuration settings
cannot be created for a table.

Error 1305 "MobiLink communication error -- code: %1, parameter:

%2, system code: %3"

Constant MOBILINK_COMMUNICATIONS_ERROR

SAP Sybase Error Number 2993

SQL State 0AWD5

SQL Code -1305L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 The MobiLink communication error code.

Parameter 2 The parameter to the MobiLink communication error if one exists.

Parameter 3 The system error code.

Probable Cause An error was encountered while communicating with a MobiLink

server.

Error 1306 "IN DBSPACE clause cannot be used for column '%1' since
table '%2' is a partitioned table."

Constant IN_DBSPACE_NOT_ALLOWED

SAP Sybase IQ Error Messages 389

Errors and Warnings

Error 1306 "IN DBSPACE clause cannot be used for column '%1' since
table '%2' is a partitioned table."

SAP Sybase Error Number 2994

SQL State WW238

SQL Code -1306L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The column name

Parameter 2 The table name

Probable Cause Entire column cannot be assigned to a dbspace using the IN

DBSPACE clause, if the table is a partitioned table.

Error 1307 "Database mirroring options are not supported for this
database"

Constant MIRRORING_OPTIONS_NOT_SUPPORTED

SAP Sybase Error Num- 2995

ber

SQL State WW130

SQL Code -1307L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for database mir-
roring servers and options. To use this feature, upgrade your database
to the most recent version.

Error 1308 "Mirror server \"%1\" not found"

Constant MIRROR_SERVER_NOT_FOUND

SAP Sybase Error Number 2996

SQL State WW131

390 SAP Sybase IQ

Errors and Warnings

Error 1308 "Mirror server \"%1\" not found"

SQL Code -1308L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the mirror server.

Probable Cause The named mirror server was not found in the database.

Error 1309 "Mirror server \"%1\" already exists"

Constant MIRROR_SERVER_ALREADY_EXISTS

SQL State WW135

SQL Code -1312L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the mirror server.

Probable Cause An attempt was made to define a parent for a mirror server that would
result in a cycle.

Error 1313 "Maximum string length exceeded"

Constant MAX_STRING_LENGTH_EXCEEDED

SAP Sybase Error Number 2969

392 SAP Sybase IQ

Errors and Warnings

Error 1313 "Maximum string length exceeded"

SQL State 54W17

SQL Code -1313L

ODBC 2 State 37000

ODBC 3 State 54000

Severity Code 15 on page 2

Probable Cause A string operation attempted to create a string longer than the maxi-
mum allowed by the server.

Error 1314 "Cannot force failover when current server is marked as

preferred"

Constant CANNOT_FORCE_FAILOVER_ON_PREFERRED

SAP Sybase Error Num- 3001

ber

SQL State WW136

SQL Code -1314L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt was made to execute ALTER DATABASE SET PARTNER
FAILOVER but the current server is marked as preferred. Attempting to
force a failover in this situation is not allowed.

Error 1315 "Script file missing statement \"go\" delimiter on a separate

line"

Constant SCRIPT_MISSING_DELIMITER

SAP Sybase Error Number 2931

SQL State WW046

SQL Code -1315L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 393

Errors and Warnings

Error 1315 "Script file missing statement \"go\" delimiter on a separate

line"

Severity Code 15 on page 2

Probable Cause For UltraLite, all non-comment SQL statements in a script file (in-
cluding the final one) must be followed by "go" on a line by itself. For
strings, you can use "\ngo" to end a statement.

Error 1316 "Unsupported load column specification used for a

catalog store table."

Constant IQ_LOAD_TABLE_UNSUPPORTED_COLUMN_SPEC

SAP Sybase Error Number 2930

SQL State 0AW25

SQL Code -1316L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause For catalog store tables, only some of the load column specifications
(for example, filler) are permitted.

Error 1317 "Multiplex server '%1' is shutting down due to a successful

configuration change"

Constant MPX_CONFIG_CHANGES_SRV_SHUTDOWN

SAP Sybase Error 2919

Number

SQL State WW239

SQL Code -1317L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the multiplex server.

394 SAP Sybase IQ

Errors and Warnings

Error 1317 "Multiplex server '%1' is shutting down due to a successful

configuration change"

Probable Cause Successful execution of certain statements to change multiplex config-

uration forces a server shutdown. You will get the above error if you issue
such a command.

Error 1318 "More articles are being dropped from publication '%1' than
are defined"

Constant TOO_MANY_ARTICLES_DELETED

SAP Sybase Error Num- 2890

ber

SQL State 42W89

SQL Code -1318L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the publication from which the article could not be dropped.

Probable Cause The number of articles in a publication can never fall below one. Your
ALTER PUBLICATION has more drop/delete article clauses than the
current number of articles in the publication.

Error 1319 "Synchronization schema changes and script versions are

not supported for this database"

Constant SYNC_SCHEMA_UPGRADE

SAP Sybase Error Num- 3002

ber

SQL State WW137

SQL Code -1319L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 395

Errors and Warnings

Error 1319 "Synchronization schema changes and script versions are

not supported for this database"

Probable Cause The current database does not have catalog support for synchroniza-
tion schema changes and script versions. To use this feature, upgrade
your database to the most recent version.

Error 1320 "Error raised by user-defined function: %1"

Constant EMSG_UDF_RAISED_ERROR

SAP Sybase Error Number 2822

SQL State QFA62

SQL Code -1320L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Error message provided by UDF to accompany UDF SQLCODE.

Error 1324 "Connection is not allowed to have table locks when executing
this statement"

Constant CONNECTION_HAS_LOCKS

SAP Sybase IQ Error Messages 397

Errors and Warnings

Error 1324 "Connection is not allowed to have table locks when executing
this statement"

SAP Sybase Error 3007

Number

SQL State WW142

SQL Code -1324L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt was made to execute a statement by a connection that is hold-
ing table locks. Because the statement could release all locks, including
those held before the statement started, the locks must be released before
the statement can be executed.

Error 1325 "Column subset for table '%1' in publication '%2' does not
match that specified in publication '%3'"

Constant COLUMN_SUBSET_MISMATCH

SAP Sybase Error Number 3003

SQL State WW138

SQL Code -1325L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of table

Parameter 2 Name of first publication

Parameter 3 Name of second publication

Probable Cause The columns included for a table must be identical for all subscribed
publications which reference the table.

Error 1326 "Subscription '%1' not found"

Constant SUBSCRIPTION_NAME_NOT_FOUND

398 SAP Sybase IQ

Errors and Warnings

Error 1326 "Subscription '%1' not found"

SAP Sybase Error Number 3008

SQL State 5RW40

SQL Code -1326L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of subscription

Probable Cause You attempted to ALTER, DROP, or otherwise reference a subscrip-

tion that does not exist.

Error 1327 "The materialized view cannot be changed to immediate because

its SELECT list contains a SUM function over a nullable
expression and it doesn't contain a COUNT function over the
same expression"

Constant UPDATABLE_MATVIEW_COUNT_NULL_EXPR

SAP Sybase Error 3009

Number

SQL State 42WCE

SQL Code -1327L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized view
whose definition contains a SUM function over a nullable expression but it
doesn't contain COUNT function over the same expression.

Error 1328 "Table '%1' must synchronize to be in publication '%2'"

Constant TABLE_MUST_SYNCHRONIZE_IN_PUB

SAP Sybase Error 3010

Number

SQL State WW143

SAP Sybase IQ Error Messages 399

Errors and Warnings

Error 1328 "Table '%1' must synchronize to be in publication '%2'"

SQL Code -1328L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of table

Parameter 2 Name of publication

Probable Cause A publication cannot contain a table with a SYNCHRONIZE OFF con-
straint; all tables in a publication must synchronize. You attempted to add
a table with a SYNCHRONIZE OFF constraint to a publication, or to alter
a table to use SYNCHRONIZE OFF when the table is already in a pub-
lication.

Error 1329 "This operation is only allowed within a synchronization

schema change"

Constant REQUIRES_SYNC_SCHEMA_CHANGE

SAP Sybase Error Number 3011

SQL State 5RW41

SQL Code -1329L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted an operation that is only allowed within a synchroni-
zation schema change.

Error 1330 "The function '%1' does not allow use of the '%2' clause"

Constant FUNCTION_DOES_NOT_ALLOW

SAP Sybase Error Num- 2823

ber

SQL State 42WE0

SQL Code -1330L

400 SAP Sybase IQ

Errors and Warnings

Error 1330 "The function '%1' does not allow use of the '%2' clause"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the function.

Parameter 2 The SQL clause not allowed.

Probable Cause You have attempted to use the specified SQL clause within the context of
a function that does not permit such use. Note that the function may have
been used directly in the query or indirectly within a named window.

Error 1331 "The function '%1' requires the use of the '%2' clause"

Constant FUNCTION_REQUIRES

SAP Sybase Error Number 2807

SQL State 42WE1

SQL Code -1331L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the function.

Parameter 2 The SQL clause required.

Probable Cause You have attempted to invoke the specified function without the use of
a mandatory SQL clause within the context of the function. Note that
the function may have been used directly in the query or indirectly
within a named window.

Error 1332 "Feature '%1' is unknown or invalid"

Constant FEATURE_UNKNOWN_OR_INVALID

SAP Sybase Error Number 3012

SQL State WW144

SQL Code -1332L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 401

Errors and Warnings

Error 1332 "Feature '%1' is unknown or invalid"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Feature name

Probable Cause You attempted to lock or unlock an unknown feature.

Error 1333 "Feature '%1' was not locked by this connection"

Constant FEATURE_NOT_LOCKED

SAP Sybase Error Number 3013

SQL State WW145

SQL Code -1333L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Feature name

Probable Cause You attempted to unlock a feature that was not previously locked by
this connection.

Error 1334 "Feature '%1' is locked by another connection"

Constant FEATURE_LOCKED

SAP Sybase Error Number 3014

SQL State WW146

SQL Code -1334L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Feature name

Probable Cause You attempted to use a feature that was previously locked by another
connection.

402 SAP Sybase IQ

Errors and Warnings

Error 1335 "Type '%1' does not support method calls (near '%2')."

Constant METHOD_ON_NON_EXT

SAP Sybase Error Number 3015

SQL State 42X00

SQL Code -1335L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The name of the data type.

Parameter 2 The invalid expression.

Probable Cause You attempted to invoke a method on a value of a data type that does
not define any methods.

Error 1336 "Type '%1' has no method named '%2' (near '%3')."

Constant METHOD_NOT_FOUND

SAP Sybase Error Number 3016

SQL State 42X01

SQL Code -1336L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The name of the type with the unmatched method.

Parameter 2 Name of the method that could not be matched.

Parameter 3 The invalid expression.

Probable Cause When attempting to match a method invocation, no method was

found with the appropriate name. Check for spelling errors.

Error 1337 "Method invocation '%1' does not match an overload (near
'%2'). Available overloads are '%3'."

Constant METHOD_NO_OVERLOAD

SAP Sybase IQ Error Messages 403

Errors and Warnings

Error 1337 "Method invocation '%1' does not match an overload (near
'%2'). Available overloads are '%3'."

SAP Sybase Error Number 3017

SQL State 42X02

SQL Code -1337L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The method name and data types used in the method invocation.

Parameter 2 The invalid expression.

Parameter 3 The available method overloads.

Probable Cause When attempting to match a method invocation, none of the defined
overloads was found to match the provided argument types. You may
need to use CAST to select the appropriate call.

Error 1338 "Type '%1' is not instantiable (near '%2')"

Constant METHOD_NO_CONSTRUCTOR

SAP Sybase Error Number 3018

SQL State 42X03

SQL Code -1338L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The name of the type that is not instantiable.

Parameter 2 The invalid expression.

Probable Cause A NEW expression was used for a data type that does not define any
constructor methods.

Error 1339 "Method '%1' cannot be called with %2 arguments (near

'%3')"

Constant METHOD_NO_OVERLOAD_N_ARGS

404 SAP Sybase IQ

Errors and Warnings

Error 1339 "Method '%1' cannot be called with %2 arguments (near

'%3')"

SAP Sybase Error Number 3019

SQL State 42X04

SQL Code -1339L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The name of the method.

Parameter 2 The number of arguments supplied.

Parameter 3 The invalid expression.

Probable Cause No overload of the specified method can be called with the number of
arguments provided.

Error 1340 "Type '%1' cannot be instantiated with %2 arguments (near

'%3')"

Constant METHOD_NO_CONSTRUCTOR_N_ARGS

SAP Sybase Error Number 3020

SQL State 42X05

SQL Code -1340L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The name of the type that cannot be instantiated.

Parameter 2 The number of arguments supplied.

Parameter 3 The invalid expression.

Probable Cause A NEW expression was used for a data type that does not define any
constructor methods.

SAP Sybase IQ Error Messages 405

Errors and Warnings

Error 1341 "The instantiation '%1' does not match an overload (near
'%2'). Available overloads are '%3'."

Constant METHOD_NO_CONSTRUCTOR_OVERLOAD

SAP Sybase Error Number 3021

SQL State 42X06

SQL Code -1341L

ODBC 2 State S0002

ODBC 3 State 42S02

Severity Code 11 on page 2

Parameter 1 The type name and data types used in the new specification.

Parameter 2 The invalid expression.

Parameter 3 The available constructor overloads.

Probable Cause When attempting to match a new specification, none of the defined
constructor overloads was found to match the provided argument
types. You may need to use CAST to select the appropriate call.

Error 1342 "Data modifications are not allowed in a synchronization

schema change"

Constant SYNC_SCHEMA_CHANGE_DISALLOWS_DML

SAP Sybase Error Number 3022

SQL State 5RW42

SQL Code -1342L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted a data modification operation within a synchroniza-

tion schema change.

406 SAP Sybase IQ

Errors and Warnings

Messages 1343 through 1366

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1343 "Feature '%1' is locked because synchronization is in

progress"

Constant FEATURE_LOCKED_SYNC

SAP Sybase Error Number 3023

SQL State WW147

SQL Code -1343L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Feature name

Probable Cause You attempted to use a feature that was previously locked because a
synchronization is in progress.

Error 1344 "Rollback occurred due to blocking_others_timeout"

Constant BLOCKING_OTHERS_ROLLBACK

SAP Sybase Error 3024

Number

SQL State WW148

SQL Code -1344L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 13 on page 2

Probable Cause This connection has been rolled back because another connection was
blocked on this connection for longer than the blocking_others_timeout
option setting. All requests on this connection will get this error until it is
disconnected.

SAP Sybase IQ Error Messages 407

Errors and Warnings

Error 1347 "Use of authority '%1' is not supported on the current

database"

Constant OLIN_AUTHORITIES_UNSUPPORTED

SAP Sybase Error Number 2776

SQL State 28W16

SQL Code -1347L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Parameter 1 The unsupported authority.

Probable Cause The current database is an older database and does not have the ca-
pability to support given authority. You must upgrade your database
to use this authority.

Error 1348 "Mirror server name '%1' does not match current server
name"

Constant INVALID_CHILD_SERVER_NAME

SAP Sybase Error Number 3027

SQL State WW151

SQL Code -1348L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The server name

Probable Cause The server name specified in a CREATE MIRROR SERVER state-
ment must match the current server name when the statement is exe-
cuted on a child server.

Error 1349 "The parent of this mirror server is not currently

connected"

Constant PARENT_NOT_CONNECTED

408 SAP Sybase IQ

Errors and Warnings

Error 1349 "The parent of this mirror server is not currently

connected"

SAP Sybase Error Number 3028

SQL State WW152

SQL Code -1349L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The statement being executed requires a connection from this mirror
server to its parent, but the parent is not currently connected.

Error 1350 "The parent of this mirror server is not the primary server"

Constant PARENT_NOT_PRIMARY

SAP Sybase Error 3029

Number

SQL State WW153

SQL Code -1350L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The statement being executed requires a connection from this mirror
server to the primary server, but the parent is not the primary server. The
connection string to this server's parent does not match the connection
string for the primary server.

Error 1351 "Mirror child server creation failed"

Constant CHILD_SERVER_CREATION_FAILED

SAP Sybase Error Number 3030

SQL State WW154

SQL Code -1351L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 409

Errors and Warnings

Error 1351 "Mirror child server creation failed"

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The creation of a child server on the primary server failed or was
disallowed.

Error 1352 "Mirror server with type '%1' is already defined"

Constant MIRROR_SERVER_TYPE_ALREADY_DEFINED

SAP Sybase Error Number 3031

SQL State WW155

SQL Code -1352L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The server type

Probable Cause A CREATE MIRROR SERVER statement specified a server type that
has already been defined.

Error 1353 "Invalid operation '%2' on sequence '%1'"

Constant INVALID_SEQUENCE_OPERATION

SAP Sybase Error Number 3033

SQL State 52W46

SQL Code -1353L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the operation attempted.

Parameter 2 Name of the sequence.

Probable Cause An invalid operation has been attempted on a sequence object. The
only valid operations on a sequence are currval and nextval.

410 SAP Sybase IQ

Errors and Warnings

Error 1354 "Sequence '%1' already exists"

Constant SEQUENCE_ALREADY_EXISTS

SAP Sybase Error Number 3034

SQL State 52W47

SQL Code -1354L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause A sequence with the specified name already exists.

Error 1355 "No more values available in sequence %1"

Constant SEQUENCE_EXHAUSTED

SAP Sybase Error Number 3035

SQL State 52W48

SQL Code -1355L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause No more values can be supplied by the sequence; the next value to be
supplied would be either larger than the maximum value, or smaller
than the minimum value, and this sequence has been specified with
NO CYCLE.

Error 1356 "Definition for sequence '%1' is invalid"

Constant INVALID_SEQUENCE_DEFINITION

SAP Sybase Error Number 3036

SQL State 52W49

SQL Code -1356L

SAP Sybase IQ Error Messages 411

Errors and Warnings

Error 1356 "Definition for sequence '%1' is invalid"

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause An invalid combination of modifiers has been used for the sequence.
Make sure that the MAXVAL is greater than the MINVAL and that
START WITH is between MINVAL and MAXVAL.

Error 1357 "Multiple settings of same option specified for sequence

'%1'"

Constant DUPLICATE_SEQUENCE_OPTION

SAP Sybase Error Number 3037

SQL State 52W50

SQL Code -1357L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause Multiple settings of the same sequence option have been specified in
the sequence definition. Even if the setting is the same, you can only
specify each option once.

Error 1358 "Sequence name '%1' is ambiguous"

Constant AMBIGUOUS_SEQUENCE_NAME

SAP Sybase Error Number 3038

SQL State 52W45

SQL Code -1358L

ODBC 2 State S0013

ODBC 3 State 42S13

Severity Code 16 on page 2

412 SAP Sybase IQ

Errors and Warnings

Error 1358 "Sequence name '%1' is ambiguous"

Parameter 1 Name of an ambiguous sequence.

Probable Cause A statement has referred to a sequence name that is not unique. Pref-
ace the sequence name by an owner name.

Error 1359 "Sequence '%1' not found"

Constant SEQUENCE_NOT_FOUND

SAP Sybase Error Number 3039

SQL State 52W44

SQL Code -1359L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause The sequence with this name does not exist in the database.

Error 1360 "Cannot assign automatic mirror server parent"

Constant CANNOT_ASSIGN_AUTO_PARENT

SAP Sybase Error Num- 3040

ber

SQL State WW156

SQL Code -1360L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A CREATE MIRROR SERVER or ALTER MIRROR SERVER state-

ment requested that a mirror parent be automatically assigned, but a
parent server could not be found. The auto_add_server option may not
be set, or might be set to an invalid server name.

SAP Sybase IQ Error Messages 413

Errors and Warnings

Error 1361 "TREAT AS can only be used with extended types. Cannot
treat %1 as a %2."

Constant TREAT_AS_ONLY_EXTENDED

SAP Sybase Error Number 3041

SQL State 53020

SQL Code -1361L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value that could not be converted.

Parameter 2 The name of the type for the conversion.

Probable Cause An error occurred while trying to treat a value as another data type.

Error 1362 "Cannot treat value '%1' as type %2. The dynamic type is
%3."

Constant TREAT_AS_DYNAMIC_MISMATCH

SAP Sybase Error Number 3042

SQL State 53021

SQL Code -1362L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value that could not be converted.

Parameter 2 The name of the type for the conversion.

Parameter 3 The type of the value that could not be converted.

Probable Cause An error occurred while trying to treat a value as another data type.
The dynamic type of the value does not match the destination type.

414 SAP Sybase IQ

Errors and Warnings

Error 1363 "The 'currval' operator is not defined yet for sequence '%1'
for this connection"

Constant SEQUENCE_CURRVAL_NOT_DEFINED

SAP Sybase Error Number 3043

SQL State 52W51

SQL Code -1363L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause The currval operator of a sequence generator is only defined once
nextval has been called for the sequence within the current connec-
tion.

Error 1366 "Sequence '%1' in use by another connection"

Constant SEQUENCE_IN_USE

SAP Sybase Error Number 3046

SQL State 42WE3

SQL Code -1366L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Parameter 1 Name of user.

Probable Cause You have attempted to drop a sequence that is currently being used by
another connection.

SAP Sybase IQ Error Messages 415

Errors and Warnings

Messages 1367 through 1387

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1367 "User owns sequences in use"

Constant USER_OWNS_SEQUENCES_IN_USE

SAP Sybase Error Number 3047

SQL State 42WE2

SQL Code -1367L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Probable Cause You attempted to drop a user that owns a sequence being used by other
active users of the database.

Error 1369 "Sequence generators are not supported for this

database"

Constant SEQUENCES_NOT_SUPPORTED

SAP Sybase Error Number 3049

SQL State 52W52

SQL Code -1369L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for sequence
generators. To use this feature, upgrade your database to the most
recent version.

Error 1370 "Text queries cannot contain more than 300 terms."

Constant TEXT_QUERY_TOO_LONG

SAP Sybase Error Number 3050

416 SAP Sybase IQ

Errors and Warnings

Error 1370 "Text queries cannot contain more than 300 terms."

SQL State WT022

SQL Code -1370L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A text query should contain 300 terms or less.

Error 1371 "The materialized view cannot be changed to immediate

because the ON conditions must refer to both sides of the
OUTER JOIN."

Constant UPDATABLE_MATVIEW_PSNS_ON_CONDITION

SAP Sybase Error 3051

Number

SQL State 42WE4

SQL Code -1371L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized
view whose definition contains an illegal ON condition.

Error 1372 "The server is not able to establish TCP/IP connections."

Constant TCP_CONNECTIONS_NOT_ENABLED

SAP Sybase Error 2736

Number

SQL State 08WA3

SQL Code -1372L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 417

Errors and Warnings

Error 1372 "The server is not able to establish TCP/IP connections."

SAP Sybase Error Number 3055

SQL State 5RW46

SQL Code -1376L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The database server failed to make a connection to the dbmlsync
server

Error 1377 "The SYNCHRONIZE statement timed out"

Constant SYNCCMD_TIMEOUT

SAP Sybase IQ Error Messages 419

Errors and Warnings

Error 1377 "The SYNCHRONIZE statement timed out"

SAP Sybase Error Number 3056

SQL State 5RW47

SQL Code -1377L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The SYNCHRONIZE statement did not complete within the timeout
value specified. Check the results of the call to sp_get_last_syn-
chronize_result() for more information.

Error 1378 "The database server failed to shut down the dbmlsync
server"

Constant SYNCCMD_SHUTDOWN_FAIL

SAP Sybase Error Number 3057

SQL State 5RW48

SQL Code -1378L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The database server started a new dbmlsync server to process the
SYNCHRONIZE statement, but encountered an error while attempt-
ing to shut the process down.

Error 1379 "The dbmlsync server failed to shut down in a timely manner"

Constant SYNCCMD_SHUTDOWN_SLOW

SAP Sybase Error Num- 3058

ber

SQL State 5RW49

SQL Code -1379L

ODBC 2 State ERROR

420 SAP Sybase IQ

Errors and Warnings

Error 1379 "The dbmlsync server failed to shut down in a timely manner"

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The database server started a new dbmlsync server to process the SYN-
CHRONIZE statement, was successful in requesting that the process shut
down, but the process did not shut down within the timeout value that was
specified.

Error 1380 "Client redirected more than once"

Constant TOO_MANY_REDIRECTS

SAP Sybase Error Number 3059

SQL State 08WA4

SQL Code -1380L

ODBC 2 State 08S01

ODBC 3 State 08S01

Severity Code 21 on page 2

Probable Cause The connection was redirected by the primary server to another serv-
er, which also attempted to redirect the connection.

Error 1381 "Database server name '%1' cannot be the same as either
the primary or mirror server"

Constant MIRROR_SERVER_NAME_CONFLICT

SAP Sybase Error Number 3060

SQL State WW159

SQL Code -1381L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The server name

Probable Cause The mirror servers defined with type PRIMARY or MIRROR cannot
have names that match actual server names.

SAP Sybase IQ Error Messages 421

Errors and Warnings

Error 1382 "Download failed due to an invalid or unsupported row

value"

Constant INVALID_DOWNLOAD_VALUE

SAP Sybase Error Number 3061

SQL State 0AW26

SQL Code -1382L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The synchronization download failed because a downloaded row

contained a column value that was either invalid or not supported.

Error 1383 "The licensed maximum number of mirror servers with type
COPY has been exceeded"

Constant MIRROR_COPY_SERVER_LIMIT_EXCEEDED

SAP Sybase Error 3062

Number

SQL State WW160

SQL Code -1383L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The maximum number of mirror servers with type COPY that may be
defined is limited by the database server license. An attempt was made to
create a new mirror server with type COPY when the maximum allowed
number of such servers already existed.

Error 1384 "Unable to stop specified database: %1"

Constant UNABLE_TO_STOP_DATABASE

SAP Sybase Error Number 2728

SQL State 08WA5

422 SAP Sybase IQ

Errors and Warnings

Error 1384 "Unable to stop specified database: %1"

SQL Code -1384L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 11 on page 2

Parameter 1 Reason the database could not be stopped, if known.

Probable Cause The database server was unable to stop the specified database.

Error 1385 "Synchronization failed. Check the dbmlsync log file for
more details."

Constant MLA_SYNC_FAILED

SAP Sybase Error Number 3063

SQL State WW161

SQL Code -1385L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The synchronization was not successful. Check the dbmlsync log file
for more details.

Error 1386 "Failed to connect to the dbmlsync server. Check the

dbmlsync log file for more details."

Constant MLA_SYNC_CONNECT_SERVER_FAIL

SAP Sybase Error Number 3064

SQL State WW162

SQL Code -1386L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 423

Errors and Warnings

Error 1386 "Failed to connect to the dbmlsync server. Check the

dbmlsync log file for more details."

Probable Cause The MobiLink agent adapter failed to make a connection to the
dbmlsync server. Check the dbmlsync log file for more details.

Error 1387 "Failed to shut down the dbmlsync server. Check the
dbmlsync log file for more details."

Constant MLA_SYNC_SHUTDOWN_FAIL

SAP Sybase Error Number 3065

SQL State WW163

SQL Code -1387L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The MobiLink agent adapter encountered an error while attempting
to shut down the server. Check the dbmlsync log file for more details.

not possible when handles are exhausted. You need to rebuild the text
index before you can use incremental refresh.

SAP Sybase IQ Error Messages 425

Errors and Warnings

Error 1391 "Invalid stoplist value."

Constant TEXT_INVALID_STOPLIST_VALUE

SAP Sybase Error Number 2725

SQL State WT025

SQL Code -1391L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The value specified for the stoplist is not valid.

Error 1392 "Unique indexes with the clause WITH NULLS NOT DISTINCT
are not supported for this database"

Constant UNIQUE_INDEX_NULLS_NOT_DISTINCT_NOT_SUPPORTED

SAP Sybase Error 3067

Number

SQL State 52W53

SQL Code -1392L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have support for unique indexes with the
clause WITH NULLS NOT DISTINCT. To use this feature, upgrade your
database to the most recent version.

Error 1393 "Error initializing external term breaker"

Constant ERROR_INITIALIZING_EXT_TERMBREAKER

SAP Sybase Error Number 2717

SQL State WT028

SQL Code -1393L

SAP Sybase Error Number 2718

SAP Sybase IQ Error Messages 427

Errors and Warnings

Constant SLERR_INVALID_RELATE_MATRIX

SAP Sybase Error Number 3069

SQL State 2FF04

SQL Code -1399L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The intersection matrix string.

Probable Cause The provided value is not a valid intersection matrix string. A valid
string contains nine characters, each is one of T, F, *, 0, 1, or 2.

Error 1400 "Point is duplicated %1"

Constant SLERR_DUPLICATE_POINT

SAP Sybase Error Number 3070

SQL State 2FF05

SQL Code -1400L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The duplicated point

Probable Cause A linestring or circularstring geometry contains two adjacent points

that are identical. This represents an invalid geometry.

Error 1401 "Element is an empty set (near '%1')"

Constant SLERR_ELEMENT_IS_EMPTY

SAP Sybase IQ Error Messages 429

Errors and Warnings

Error 1401 "Element is an empty set (near '%1')"

SAP Sybase Error Num- 3071

ber

SQL State 2FF06

SQL Code -1401L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value or method where the empty geometry has been detected.

Probable Cause An element of a geometry is the empty set. Empty geometries cannot be
used as the points in linestrings or circularstrings; empty curves cannot be
used as elements of compoundcurves; empty curves cannot be used as
rings of polygons.

Error 1402 "Mixed spatial reference systems %1 and %2 (near %3)"

Constant SLERR_MIXED_SRS

SAP Sybase Error Number 3072

SQL State 2FF10

SQL State 2FF15

SQL Code -1405L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 431

Errors and Warnings

Error 1405 "Failed to transform geometry (error %1)"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The error code from the projection library.

Probable Cause An error occurred when performing a transform from one spatial reference
system to another. This error may occur if a point in the first geometry is
outside of the bounds for the transform definition. The error may also be
reported for particular transform definitions. The integer error code from the
transform library may be used to diagnose the transform definition.

Error 1406 "Error parsing well-known-text (WKT) scanning '%1' at

offset %2"

Constant SLERR_WKT_PARSE_NEAR

SAP Sybase Error Num- 3076

ber

SQL State 2FF22

SQL Code -1406L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The text where the problem was detected.

Parameter 2 The offset within the input string where the problem was detected.

Probable Cause An error was detected while parsing the well-known text of a geom-
etry.

Error 1407 "Error parsing well-known-binary (WKB) at offset %1"

Constant SLERR_WKB_PARSE

SAP Sybase Error Number 3077

SQL State 2FF23

SQL Code -1407L

ODBC 2 State ERROR

432 SAP Sybase IQ

Errors and Warnings

Error 1407 "Error parsing well-known-binary (WKB) at offset %1"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The byte offset within the binary string where the error was detected.

Probable Cause An error was detected while parsing the well-known binary of a
geometry.

Messages 1408 through 1428

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1408 "Mixed coordinate dimensions"

Constant SLERR_MIXED_DIM

SAP Sybase Error Number 3078

SQL State 2FF25

SQL Code -1408L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The method contains geometries that have a mixture of coordinate
dimensions (Z and M values).

Error 1409 "Unknown spatial reference system (%1)"

Constant SLERR_SRID_UNKNOWN

SAP Sybase Error Number 3079

SQL State 2FF59

SQL Code -1409L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The spatial reference system identifier.

SAP Sybase IQ Error Messages 433

Errors and Warnings

Error 1409 "Unknown spatial reference system (%1)"

Probable Cause The provided SRID does not match a defined spatial reference sys-
tem.

Error 1410 "An ST_CircularString cannot be constructed from %1

points (near '%2')"

Constant SLERR_CIRC_NUM_POINTS

SAP Sybase Error Num- 3080

ber

SQL State 2FF71

SQL Code -1410L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The incorrect number of points given.

Parameter 2 The value or method where the error was detected.

Probable Cause A circularstring geometry should consist of three points followed op-
tionally by an arbitrary number of pairs of points.

Error 1411 "Cannot convert from %1 to %2 (near %3)."

Constant SLERR_ST_TO_XXX_FAILN

SAP Sybase Error Number 3081

SQL State 2FF16

SQL Code -1411L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The geometry type of the value.

Parameter 2 The geometry type of the target.

Parameter 3 The value or method where the error was detected.

434 SAP Sybase IQ

Errors and Warnings

Error 1411 "Cannot convert from %1 to %2 (near %3)."

Probable Cause The value could not be converted to the specified target type.

Error 1412 "Support for spatial is not available for this database"

Constant SLERR_NEED_UPGRADE

SAP Sybase Error Number 3082

SQL State 2FW02

SQL Code -1412L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Operations involving spatial support cannot be used with this data-
base because it needs to be upgraded to use spatial features.

Error 1413 "Spatial feature %1 is not supported"

Constant SLERR_NYI

SAP Sybase Error Number 3083

SQL State 2FW03

SQL Code -1413L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the unsupported feature.

Probable Cause The specified feature is not supported.

Error 1414 "Error parsing well-known-text (WKT): inconsistent

dimensions at offset %1"

Constant SLERR_WKT_PARSE_INCONSISTENT_ZM

SAP Sybase Error 3084

Number

SAP Sybase IQ Error Messages 435

Errors and Warnings

Error 1414 "Error parsing well-known-text (WKT): inconsistent

dimensions at offset %1"

SQL State 2FW05

SQL Code -1414L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The offset within the well-known text string where the error was detected.

Probable Cause There was a mixture of coordinate dimensions detected at the specified
offset. For example, one geometry in a collection might have a Z value
while another doesn't.

Error 1415 "Error parsing geometry internal serialization at offset %1"

Constant SLERR_SERIAL_PARSE

SAP Sybase Error Number 3085

SQL State 2FW06

SQL Code -1415L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The byte offset within the internal serialization.

Probable Cause There was an error parsing the internal serialization string.

Error 1417 "Error parsing well-known-binary (WKB): type code %1 at

offset %2 is invalid"

Constant SLERR_WKB_PARSE_TYPE

SAP Sybase Error Num- 3087

ber

SQL State 2FW08

SQL Code -1417L

ODBC 2 State ERROR

436 SAP Sybase IQ

Errors and Warnings

Error 1417 "Error parsing well-known-binary (WKB): type code %1 at

offset %2 is invalid"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The unsupported type code value.

Parameter 2 The byte offset within the binary string where the error was detected.

Probable Cause The well-known binary string contains a type code that is not suppor-
ted.

Error 1418 "Error parsing well-known-binary (WKB): type code %1 at offset

%2 is not a valid subtype of the parent"

Constant SLERR_WKB_PARSE_TYPE_NOT_PERMITTED

SAP Sybase Error 3088

Number

SQL State 2FW09

SQL Code -1418L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The unsupported type code value.

Parameter 2 The byte offset within the binary string where the error was detected.

Probable Cause The well-known binary string contains a child geometry within a parent ge-
ometry and the child is not one of the types allowed by the parent.

Error 1419 "Error parsing well-known-binary (WKB): unexpected end

of input"

Constant SLERR_WKB_PARSE_UNEXPECTED_EOF

SAP Sybase Error Number 3089

SQL State 2FW10

SQL Code -1419L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 437

Errors and Warnings

Error 1419 "Error parsing well-known-binary (WKB): unexpected end

of input"

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A well-known binary string was shorter than expected.

Error 1420 "Error parsing well-known-binary (WKB): inconsistent

dimensions at offset %1"

Constant SLERR_WKB_PARSE_INCONSISTENT_ZM

SAP Sybase Error 3090

Number

SQL State 2FW11

SQL Code -1420L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The byte offset within the binary string where the error was detected.

Probable Cause The well-known binary string contains geometries with different numbers
of coordinate dimensions. For example, it could contain a point with a Z
value and another without a Z value.

Error 1421 "Error parsing well-known-binary (WKB): invalid byte order

mark %1 at offset %2"

Constant SLERR_WKB_PARSE_INVALID_BOM

SAP Sybase Error Num- 3091

ber

SQL State 2FW12

SQL Code -1421L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

438 SAP Sybase IQ

Errors and Warnings

Error 1421 "Error parsing well-known-binary (WKB): invalid byte order

mark %1 at offset %2"

Parameter 1 The value of the byte-order mark.

Parameter 2 The byte offset within the binary string where the error was detected.

Probable Cause The well-known binary string has an invalid byte order mark. This could
happen if a binary string that is not in the well-known binary format is
used.

Error 1422 "Error parsing shapefile record"

Constant SLERR_SHAPE_PARSE

SAP Sybase Error Number 3092

SQL State 2FW13

SQL Code -1422L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The shapefile contains an invalid record.

Error 1423 "Error parsing shapefile attributes"

Constant SLERR_SHAPE_PARSE_ATTRIBUTES

SAP Sybase Error Number 3093

SQL State 2FW14

SQL Code -1423L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The shapefile contains invalid attributes.

Error 1424 "Invalid shapefile filename"

Constant SLERR_SHAPE_INVALID_FILENAME

SAP Sybase IQ Error Messages 439

Errors and Warnings

Error 1424 "Invalid shapefile filename"

SAP Sybase Error Number 3094

SQL State 2FW15

SQL Code -1424L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The specified shapefile filename is not valid.

Error 1425 "The multi patch shapefile shape is not supported"

Constant SLERR_SHAPE_MULTIPATCH

SAP Sybase Error Number 3095

SQL State 2FW16

SQL Code -1425L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The shapefile contains a multi patch object; this type is not supported.

Error 1426 "The embedded SRID (%1) conflicts with the provided
SRID (%2)."

Constant SLERR_SRID_CONFLICT_EMBED_PARAM

SAP Sybase Error Number 3096

SQL State 2FW19

SQL Code -1426L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The SRID within the parsed string.

440 SAP Sybase IQ

Errors and Warnings

Error 1426 "The embedded SRID (%1) conflicts with the provided
SRID (%2)."

Parameter 2 The SRID provided as a parameter.

Probable Cause A call to a spatial method had a string with an embedded SRID that
differed from the SRID parameter to the method.

Error 1427 "The embedded SRID are inconsistent (%1 and %2)."

Constant SLERR_SRID_CONFLICT_EMBED_EMBED

SAP Sybase Error Number 3097

SQL State 2FW20

SQL Code -1427L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The first SRID.

Parameter 2 The second SRID.

Probable Cause A geometry in a string representation contains objects from different

spatial reference systems.

Error 1428 "The format type '%1' is not recognized."

Constant SLERR_FMT_UNKNOWN

SAP Sybase Error Number 3098

SQL State 2FW21

SQL Code -1428L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The invalid format type.

Probable Cause The specified format type is not recognized.

SAP Sybase IQ Error Messages 441

Errors and Warnings

1429 - 1630

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The format specification is invalid.

Error 1432 "The format specification option '%1' is not recognized."

Constant SLERR_INVALID_FORMAT_SPECIFICATION_OPTION

SAP Sybase Error Number 3102

SQL State 2FW25

SQL Code -1432L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The invalid option.

Probable Cause The named option is not supported for the format specification.

Error 1433 "The value '%2' is not a valid setting for the '%1' format
specification option."

Constant SLERR_INVALID_FORMAT_SPECIFICATION_OPTION_VAL-
UE

SAP Sybase Error Number 3103

SQL State 2FW26

SQL Code -1433L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 443

Errors and Warnings

Error 1433 "The value '%2' is not a valid setting for the '%1' format
specification option."

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The invalid value.

Parameter 2 The format specification option.

Probable Cause The value is not accepted by the specification option.

Error 1434 "The data is not in a recognized format."

Constant SLERR_UNKOWNN_FORMAT

SAP Sybase Error Number 3104

SQL State 2FW27

SQL Code -1434L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The provided string is not in a recognized format to parse a geometry.

Error 1435 "A geometry with SRID=%1 is not supported for method %2."

Constant SLERR_ROUND_EARTH_UNSUPPORTED

SAP Sybase Error 3105

Number

SQL State 2FW28

SQL Code -1435L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The SRID of the geometry.

Parameter 2 The name of the method that does not support this SRID.

444 SAP Sybase IQ

Errors and Warnings

Error 1435 "A geometry with SRID=%1 is not supported for method %2."

Probable Cause The named method does not support geometries in the specified spatial
reference system. For example, the method might not support round-
Earth data.

Error 1436 "A geometry with SRID=%1 is not supported when

computing distance between non-point geometries."

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The invalid configuration name.

Probable Cause The named configuration is not supported.

Error 1440 "The comparison '%1' cannot be used with geometries."

Constant SLERR_COMPARISON_PREDICATE

SAP Sybase Error Number 3110

SQL State 2FW33

SQL Code -1440L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The type of comparison relation.

Probable Cause Geometry values cannot be compared with operators such as < or >.
Geometries can only be compared with = and <>.

Error 1441 "Invalid spatial reference system well-known-text (WKT)."

Constant SLERR_SRS_PARSE_ERROR

SAP Sybase Error Number 3111

SQL State 2FW34

SQL Code -1441L

ODBC 2 State ERROR

446 SAP Sybase IQ

Errors and Warnings

Error 1441 "Invalid spatial reference system well-known-text (WKT)."

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The provided string does not represent a valid spatial reference sys-
tem definition in well-known text format.

Error 1442 "Invalid transform definition '%1'."

Constant SLERR_INVALID_TRANSFORM_DEF

SAP Sybase Error Number 3112

SQL State 2FW35

SQL Code -1442L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The invalid transform definition string.

Probable Cause The provided string does not represent a valid transform definition.

Error 1443 "Transform definition is too long."

Constant SLERR_TRANSFORM_DEF_TOO_LONG

SAP Sybase Error Number 3113

SQL State 2FW36

SQL Code -1443L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The provided transform definition is too long.

Error 1444 "Transform from SRID %1 to %2 not supported."

Constant SLERR_NO_XFORM_DEF

SAP Sybase Error Number 3114

SAP Sybase IQ Error Messages 447

Errors and Warnings

Error 1444 "Transform from SRID %1 to %2 not supported."

SQL State 2FW37

SQL Code -1444L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The SRID of the value.

Parameter 2 The SRID of the destination.

Probable Cause There is no way to transform from the value's spatial reference system
to the specified target.

Error 1445 "Transform from SRID %1 not supported."

Constant SLERR_NO_SRC_XFORM_DEF

SAP Sybase Error Number 3115

SQL State 2FW38

SQL Code -1445L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The SRID of the value.

Probable Cause There is no way to transform from values of the specified spatial
reference system.

Error 1446 "Unit of measure \"%1\" is not a linear unit."

Constant SLERR_UOM_NOT_LINEAR

SAP Sybase Error Number 3116

SQL State 2FW39

SQL Code -1446L

ODBC 2 State ERROR

448 SAP Sybase IQ

Errors and Warnings

Error 1446 "Unit of measure \"%1\" is not a linear unit."

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the invalid unit of measure.

Probable Cause The specified unit of measure is not a linear unit of measure.

Error 1447 "Unit of measure \"%1\" is not an angular unit."

Constant SLERR_UOM_NOT_ANGULAR

SAP Sybase Error Number 3117

SQL State 2FW40

SQL Code -1447L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the invalid unit of measure.

Probable Cause The specified unit of measure is not a linear unit of measure.

Error 1448 "Invalid polygon format '%1'"

Constant SLERR_INVALID_POLY_ORD

SAP Sybase Error Number 3118

SQL Code -1451L

ODBC 2 State ERROR

450 SAP Sybase IQ

Errors and Warnings

Error 1451 "Invalid polygon: multiple exterior rings"

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause There are multiple exterior rings that do not form a single valid pol-
ygon.

Error 1452 "Table '%1' contains a spatial column '%2' and no primary
key"

Constant SLERR_UPDDEL_NO_PK

SAP Sybase Error Number 3122

SQL State 2FW45

SQL Code -1452L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The table name.

Parameter 2 The spatial column name.

Probable Cause An update or delete statement cannot be performed for a table that
contains a spatial column unless there is a primary key defined for the
table.

Error 1453 "Spatial column '%1' cannot be included in a primary key

or unique index"

Constant SLERR_CREATE_INDEX_UNIQUE

SAP Sybase Error Number 3123

SQL State 2FW46

SQL Code -1453L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the spatial column.

SAP Sybase IQ Error Messages 451

Errors and Warnings

Error 1453 "Spatial column '%1' cannot be included in a primary key

or unique index"

Probable Cause A spatial column cannot be included in a primary key or unique index.

Error 1454 "Spatial column '%1' cannot be included in an index because

it is not constrained to a single SRID"

Constant SLERR_CREATE_INDEX_NOSRID

SAP Sybase Error Num- 3124

ber

SQL State 2FW47

SQL Code -1454L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the spatial column.

Probable Cause The named spatial column cannot be included in a spatial index because
the column is not constrained to have values from a single spatial ref-
erence system. The column definition should be of the form "col
ST_Geometry(SRID=0)".

Error 1455 "The CONVERT USING clause must be specified when

creating a unit of measure"

Constant SLERR_DDL_UOM_NOFACT

SAP Sybase Error Number 3125

SQL State 2FW48

SQL Code -1455L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A CREATE SPATIAL UNIT OF MEASURE statement was used

without including the CONVERT USING clause.

Error 1458 "Unit of measure '%1' not found"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The unit of measure name.

Probable Cause The named unit of measure is not defined.

Error 1459 "Spatial reference system '%1' not found"

Constant SLERR_DDL_NO_SRS

SAP Sybase Error Number 3129

SQL State 2FW52

SQL Code -1459L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the spatial reference system.

Probable Cause The named spatial reference system is not defined.

Error 1460 "Unit of measure '%1' already exists"

Constant SLERR_DDL_UOM_EXISTS

SAP Sybase Error Number 3130

SQL State 2FW53

SQL Code -1460L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the unit of measure.

Probable Cause The named unit of measure is already defined.

454 SAP Sybase IQ

Errors and Warnings

Error 1461 "Spatial reference system '%1' already exists"

Constant SLERR_DDL_SRS_EXISTS

SAP Sybase Error Number 3131

SQL State 2FW54

SQL Code -1461L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the spatial reference system.

Probable Cause The named spatial reference system already exists.

Error 1462 "Spatial reference system must specify the SRID to use"

Constant SLERR_DDL_SRS_NOSRID

SAP Sybase Error Number 3132

SQL State 2FW55

SQL Code -1462L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause When creating a spatial reference system, the statement must specify
IDENTIFIED BY to specify the SRID to use.

Error 1463 "Error parsing definition string '%1'"

Constant SLERR_DDL_SRS_BADWKT

SAP Sybase Error Number 3133

SQL State 2FW56

SQL Code -1463L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 455

Errors and Warnings

Error 1463 "Error parsing definition string '%1'"

Severity Code 16 on page 2

Parameter 1 Coordinate system name

Probable Cause The provided definition string is not a valid well known text of the
coordinate system.

Error 1464 "The spatial reference system type is not supported ('%1')"

Constant SLERR_DDL_SRS_BAD_SRS_TYPE

SAP Sybase Error Num- 3134

ber

SQL State 2FW57

SQL Code -1464L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The unsupported spatial reference system type.

Probable Cause The specified spatial reference system type is not supported.

Error 1465 "Ellipsoid parameters missing for geographic spatial reference

system"

Constant SLERR_DDL_SRS_NOELLIPSOID

SAP Sybase Error 3135

Number

SQL State 2FW58

SQL Code -1465L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause When creating a geographic spatial reference system, the ellipsoid param-
eters must be specified, either in the DEFINITION clause or explicitly.
These parameters are used to calculate the distance between points.

456 SAP Sybase IQ

Errors and Warnings

Error 1466 "Ellipsoid parameters specified for non-geographic

spatial reference system"

Constant SLERR_DDL_SRS_ELLIPSOID

SAP Sybase Error Number 3136

SQL State 2FW59

SQL Code -1466L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The ELLIPSOID parameters can only be specified for geographic
spatial reference systems.

Error 1467 "Coordinate bounds missing for coordinate %1"

Constant SLERR_DDL_SRS_MUSTBOUND

SAP Sybase Error Number 3137

SQL State 2FW60

SQL Code -1467L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The coordinate name.

Probable Cause No bounds were specified for the named coordinate.

Error 1468 "The specified axis order is not supported for this type of
spatial reference system"

Constant SLERR_DDL_SRS_AXISORD

SAP Sybase Error Number 3138

SQL State 2FW61

SQL Code -1468L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 457

Errors and Warnings

Error 1468 "The specified axis order is not supported for this type of
spatial reference system"

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The specified axis order is not supported for this type of spatial ref-
erence system.

Error 1469 "The specified polygon format '%1' is not supported for
this type of spatial reference system"

Constant SLERR_DDL_SRS_POLYFORMAT

SAP Sybase Error Number 3139

SQL State 2FW62

SQL Code -1469L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The polygon format string.

Probable Cause The specified polygon format is not supported for this type of spatial
reference system.

Messages 1470 through 1490

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1470 "Invalid storage format '%1'"

Constant SLERR_DDL_SRS_STGFORMAT

SAP Sybase Error Number 3140

SQL State 2FW63

SQL Code -1470L

ODBC 2 State ERROR

ODBC 3 State ERROR

458 SAP Sybase IQ

Errors and Warnings

Error 1470 "Invalid storage format '%1'"

Severity Code 16 on page 2

Parameter 1 The invalid storage format string.

Probable Cause The specified storage format string is not valid.

Error 1471 "Spatial reference system %1 cannot be modified because

it is in use"

Constant SLERR_DDL_SRS_INUSE

SAP Sybase Error Number 3141

SQL State 2FW64

SQL Code -1471L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The coordinate system name

Probable Cause The coordinate system is currently in use and cannot be dropped.

Error 1472 "Spatial reference system \"%1\" is reserved"

Constant SLERR_DDL_SRS_RESERVED

SAP Sybase Error Number 3142

SQL State 2FW65

SQL Code -1472L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the reserved spatial reference system.

Probable Cause The named spatial reference system is reserved for system use.

Error 1473 "Spatial unit of measure \"%1\" is reserved"

Constant SLERR_DDL_UOM_RESERVED

SAP Sybase IQ Error Messages 459

Errors and Warnings

Error 1473 "Spatial unit of measure \"%1\" is reserved"

SAP Sybase Error Number 3143

SQL State 2FW66

SQL Code -1473L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the reserved unit of measure.

Probable Cause The named unit of measure is reserved for system use.

Error 1474 "SRID %1 is referenced by column '%2' of table '%3'"

Constant SLERR_SRS_INUSE_TAB

SAP Sybase Error Number 3144

SQL State 2FW67

SQL Code -1474L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The spatial reference system identifier.

Parameter 2 The name of the referencing column.

Parameter 3 The name of the referencing table.

Probable Cause The specified spatial reference system is in use by the column of a
table, and it cannot be modified.

Error 1475 "SRID %1 is referenced by parameter '%2' of procedure

'%3'"

Constant SLERR_SRS_INUSE_PROC

SAP Sybase Error Number 3145

SQL State 2FW68

460 SAP Sybase IQ

Errors and Warnings

Error 1475 "SRID %1 is referenced by parameter '%2' of procedure

'%3'"

SQL Code -1475L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The spatial reference system identifier.

Parameter 2 The referencing parameter name.

Parameter 3 The referencing procedure name.

Probable Cause The specified spatial reference system is in use by the parameter of a
procedure, and it cannot be modified.

Error 1476 "SRID %1 is referenced by domain \"%3\".\"%2\No

message

Constant SLERR_SRS_INUSE_TYPE

SAP Sybase Error Number 3146

SQL State 2FW69

SQL Code -1476L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The spatial reference system identifier.

Parameter 2 The owner of the domain.

Parameter 3 The name of the domain.

Probable Cause The specified spatial reference system is in use by a user-defined

domain, and it cannot be modified.

Error 1477 "The SRID %1 does not identify a geographic spatial

reference system"

Constant SLERR_NOT_GEOGRAPHIC

SAP Sybase Error Number 3147

SAP Sybase IQ Error Messages 461

Errors and Warnings

Error 1477 "The SRID %1 does not identify a geographic spatial

reference system"

SQL State 2FW70

SQL Code -1477L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The spatial reference system identifier.

Probable Cause The methods ST_Lat() and ST_Long() can only be used for geo-
graphic spatial reference systems.

Error 1478 "ST_Geometry arguments not supported by SQL function

%1"

Constant SLERR_SPATIAL_IN_BUILTIN

SAP Sybase Error Number 3148

SQL State 2FW71

SQL Code -1478L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the SQL function.

Probable Cause The specified SQL function does not support geometry parameters.

Error 1479 "An expression of type %1 is not union-compatible with

type %2"

Constant SLERR_NOT_UNION_COMPAT

SAP Sybase Error Number 3149

SQL State 2FW72

SQL Code -1479L

ODBC 2 State ERROR

462 SAP Sybase IQ

Errors and Warnings

Error 1479 "An expression of type %1 is not union-compatible with

type %2"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The type of expression 1.

Parameter 2 The type of expression 2.

Probable Cause The two types cannot be combined, for example in a set operation
such as UNION or in a SQL function such as COALESCE.

Error 1480 "An internal error has occurred in the spatial library"

Constant SLERR_INTERNAL_ERROR

SAP Sybase Error Number 3150

SQL State 2FW73

SQL Code -1480L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An unexpected error occurred.

Error 1482 "Curve contains nearly antipodal points %1 and %2 (near

'%3')"

Constant SLERR_NEARLY_ANTIPODAL

SAP Sybase Error Number 3152

SQL State 2FW77

SQL Code -1482L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The first point.

Parameter 2 The second point.

SAP Sybase IQ Error Messages 463

Errors and Warnings

Error 1482 "Curve contains nearly antipodal points %1 and %2 (near

'%3')"

Parameter 3 The value or method where the error was detected.

Probable Cause A curve contains two points that are nearly antipodal. These define an
ambiguous segment in a round-Earth spatial reference system.

Error 1483 "LineString must contain at least 2 points (near '%1')"

Constant SLERR_LINESTRING_MIN_POINTS

SAP Sybase Error Number 3153

SQL State 2FW78

SQL Code -1483L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value or method where the error was detected.

Probable Cause The linestring contains only a single point.

Error 1484 "Value %1 out of range for coordinate %2 (SRS bounds [%3,
%4] exceeded by more than 50%)"

Constant SLERR_OBJECT_OUT_OF_SRS_BOUNDS

SAP Sybase Error 3154

Number

SQL State 2FW79

SQL Code -1484L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value is out of the defined bounds.

Parameter 2 The coordinate name that is out of range.

Parameter 3 The minimum value allowed by the spatial reference system.

464 SAP Sybase IQ

Errors and Warnings

Error 1484 "Value %1 out of range for coordinate %2 (SRS bounds [%3,
%4] exceeded by more than 50%)"

Parameter 4 The maximum value allowed by the spatial reference system.

Probable Cause The geometry contains a point outside of the bounds specified by the
spatial reference system.

Error 1485 "Invalid polygon: ring is not closed (near '%1')"

Constant SLERR_INVALID_POLY_RING_CLOSE

SAP Sybase Error Number 3155

SQL State 2FW80

SQL Code -1485L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value or method where the error was detected.

Probable Cause One of the provided curves is not a closed ring.

Error 1486 "Invalid polygon: ring has zero area (near '%1')"

Constant SLERR_INVALID_POLY_EMPTY_RING

SAP Sybase Error Number 3156

SQL State 2FW81

SQL Code -1486L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The value or method where the error was detected.

Probable Cause One of the provided rings has zero area and cannot be a valid polygon
ring.

SAP Sybase IQ Error Messages 465

Errors and Warnings

Error 1487 "Invalid polygon: curve is not a ring"

Constant SLERR_INVALID_POLY_NON_RING

SAP Sybase Error Number 3157

SQL State 2FW82

SQL Code -1487L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause One of the curves is not a ring and cannot be used to form a polygon.

Error 1488 "Invalid polygon: ring is larger than allowed for SRID=%1
(near '%2')"

Constant SLERR_INVALID_POLY_RE_SIZE

SAP Sybase Error Number 3158

SQL State 2FW83

SQL Code -1488L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The spatial reference system identifier.

Parameter 2 The value or method where the error was detected.

Probable Cause One of the rings is larger than the specified spatial reference system
supports.

Error 1489 "Position %1 is invalid (should be between %2 and %3)"

Constant SLWARN_INVALID_POSITION

SAP Sybase Error Number 3159

SQL State 01F01

SQL Code -1489L

466 SAP Sybase IQ

Errors and Warnings

Error 1489 "Position %1 is invalid (should be between %2 and %3)"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The provided position.

Parameter 2 The minimum supported position.

Parameter 3 The maximum supported position.

Probable Cause The provided position is not valid. It should be between the specified
minimum and maximum.

Error 1490 "Polygon ring order has been reoriented"

Constant SLWARN_POLYGON_RING_REORIENTED

SAP Sybase Error Number 3160

SQL State 01FW1

SQL Code -1490L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The rings of a polygon were automatically reoriented on input. This is
a notification only.

Messages 1491 through 1510

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1491 "CircularString with 3 points has been converted to use 5

points"

Constant SLWARN_CIRCULARSTRING_3POINT

SAP Sybase Error Number 3161

SQL State 01FW2

SQL Code -1491L

SAP Sybase IQ Error Messages 467

Errors and Warnings

Error 1491 "CircularString with 3 points has been converted to use 5

points"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A curve containing a CircularString with a 3-point circle has been
converted to use a 5-point circle. This is a notification only.

Error 1492 "Could not create a text index without external prefilter
library on column \"%1\No message

Constant TEXT_INDEX_NO_PREFILTER

SAP Sybase Error Number 2652

SQL State WT030

SQL Code -1492L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the column for which external prefilter library is re-
quired.

Probable Cause A text configuration object with a specified external prefilter library is
required to build a text index on a binary column.

Error 1493 "Could not create a text index with external prefilter library
on column \"%1\No message

Constant TEXT_INDEX_PREFILTER_NOT_ALLOWED

SAP Sybase Error Num- 2644

ber

SQL State WT031

SQL Code -1493L

ODBC 2 State ERROR

ODBC 3 State ERROR

468 SAP Sybase IQ

Errors and Warnings

Error 1493 "Could not create a text index with external prefilter library
on column \"%1\No message

Severity Code 16 on page 2

Parameter 1 The name of the column for which external prefilter library is not al-
lowed.

Probable Cause A text configuration object without external prefilter library is required
if any column in the text index is not of a binary or string data type.

Error 1494 "Geometries with CircularString not supported (near

\"%1\")"

Constant SLERR_CIRCULAR_METHOD

SAP Sybase Error Number 3162

SQL State 2FW84

SQL Code -1494L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The method or context where the CircularString was detected.

Probable Cause The method or operation does not support geometries with Circular-
String elements.

Error 1495 "Geometries with CircularString are not supported in

spatial reference system %1"

Constant SLERR_CIRCULAR_SRS

SAP Sybase Error Number 3163

SQL State 2FW85

SQL Code -1495L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The SRID of the round-Earth spatial reference system.

SAP Sybase IQ Error Messages 469

Errors and Warnings

Error 1495 "Geometries with CircularString are not supported in

spatial reference system %1"

Probable Cause The method does not support geometries with CircularString ele-
ments.

Error 1496 "LOAD TABLE error: Invalid content encountered on row %1

of the data file"

Constant LOAD_TABLE_DATA_FILE_ERROR

SAP Sybase Error Num- 3164

ber

SQL State WL017

SQL Code -1496L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Line number of the data file where the invalid content occurred.

Probable Cause The LOAD TABLE statement failed because a scanning error occurred
on the indicated line of the data file specified in the statement. This error
can occur if a line is truncated or if delimiters are missing.

Error 1497 "The synchronization failed because MobiLink returned

authentication status '%1' with value '%2'"

Constant MOBILINK_AUTHENTICATION_FAILED

SAP Sybase Error 3165

Number

SQL State 28W17

SQL Code -1497L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 14 on page 2

Parameter 1 The authentication status number.

Parameter 2 The authentication value number.

470 SAP Sybase IQ

Errors and Warnings

Error 1497 "The synchronization failed because MobiLink returned

authentication status '%1' with value '%2'"

Severity Code 16 on page 2

Parameter 1 The invalid tolerance.

Probable Cause The specified tolerance cannot be used with the spatial reference
system. The tolerance must be selected based on the bounds of space.

Error 1501 "Invalid bounds for coordinate %1 (near \"BETWEEN %2

AND %3\")"

Constant SLERR_INVALID_BOUNDS

SAP Sybase Error Number 3169

SQL State 2FW88

SQL Code -1501L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The coordinate with the invalid bounds.

Parameter 2 The first value of the invalid bounds.

Parameter 3 The second value of the invalid bounds.

Probable Cause The specified coordinate bounds are not valid.

Error 1502 "ST_MultiSurface contains elements with an invalid

intersection (near \"%1\")"

Constant SLERR_INVALID_MULTISURF_I

472 SAP Sybase IQ

Errors and Warnings

Error 1502 "ST_MultiSurface contains elements with an invalid

intersection (near \"%1\")"

SAP Sybase Error 3170

Number

SQL State 2FW89

SQL Code -1502L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The method or context where the invalid ST_MultiSurface was detected.

Probable Cause The interiors of any two ST_Surface values in an ST_MultiSurface shall
not intersect. The boundaries of any two elements in an ST_MultiSurface
may intersect at a finite number of points (and not, for example, in a line
segment).

Error 1503 "Operation not supported for ST_GeomCollection with

intersecting elements (near \"%1\")"

Constant SLERR_GEOM_COLL_INTERSECT

SAP Sybase Error Num- 3171

ber

SQL State 2FW90

SQL Code -1503L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The method or context where the invalid ST_GeomCollection was de-
tected.

Probable Cause The ST_GeomCollection contains elements that intersect in a way that is
not valid for an ST_MultiSurface. The operation is not supported for this
kind of geometry.

SAP Sybase IQ Error Messages 473

Errors and Warnings

Error 1504 "Error from external library: -%1: %2"

Constant TEXT_USER_SPECIFIED_ERROR

SAP Sybase Error Number 2642

SQL State WT032

SQL Code -1504L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Error number specified by the external library

Parameter 2 Error message specified by the external library

Probable Cause The external library used by the text index has reported the specified
error.

Error 1505 "Mirror server \"%1\" defined with type COPY does not
include a parent definition"

Constant COPY_SERVER_NEEDS_PARENT

SAP Sybase Error Number 3172

SQL State 42WE6

SQL Code -1505L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The mirror server name

Probable Cause In a CREATE MIRROR SERVER statement for a server with type
COPY, a parent server is not defined.

Error 1506 "Unknown collation '%1'"

Constant UNKNOWN_COLLATION

SAP Sybase Error Number 3174

SQL State WC018

474 SAP Sybase IQ

Errors and Warnings

Error 1506 "Unknown collation '%1'"

SQL Code -1506L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name that is not a database collation.

Probable Cause The specified collation is unknown. Ensure the name is spelled cor-
rectly.

Error 1507 "The materialized view cannot be changed to immediate

because the ON conditions refer to tables which are not in the
null-supplying and preserved sides of the OUTER JOINs."

Constant UPDATABLE_MATVIEW_OUTERREFERENCE_ON_CONDITION

SAP Sybase Error 3175

Number

SQL State 42WE7

SQL Code -1507L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized
view whose definition contains an illegal ON condition.

Error 1508 "The materialized view cannot be changed to immediate

because at least one non-nullable column from any null-
supplying side of an OUTER JOIN must exist in the SELECT
list."

Constant UPDATABLE_MATVIEW_ISNOTNULL

SAP Sybase Error 3176

Number

SQL State 42WE8

SQL Code -1508L

SAP Sybase IQ Error Messages 475

Errors and Warnings

Error 1508 "The materialized view cannot be changed to immediate

because at least one non-nullable column from any null-
supplying side of an OUTER JOIN must exist in the SELECT
list."

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized
view whose SELECT list doesn't contain at least one non-nullable column
for any null-supplying side of an OUTER JOIN.

Error 1509 "The materialized view cannot be changed to immediate

because the primary key columns of any table in the
preserved side of an OUTER JOIN must exist in the SELECT
list."

Constant UPDATABLE_MATVIEW_PK

SAP Sybase Error 3177

Number

SQL State 42WE9

SQL Code -1509L

ODBC 2 State 42000

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause You attempted to change the refresh type to immediate for a materialized
view whose SELECT list doesn't contain the primary key columns of any
table in the preserved side of an OUTER JOIN.

Error 1510 "Cannot specify range that excludes next value for sequence
%1"

Constant INVALID_ALTER_SEQUENCE

SAP Sybase Error Num- 3178

ber

SQL State 52W54

SQL Code -1510L

476 SAP Sybase IQ

Errors and Warnings

Error 1510 "Cannot specify range that excludes next value for sequence
%1"

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Parameter 1 Name of the sequence.

Probable Cause You attempted to modify either the MINVAL or MAXVAL boundary of a
sequence to a value that would make the next invocation of the nextval
expression for the sequence invalid. If you want to change the range
boundaries to these values, you must also specify a RESTART WITH
clause and supply a value within the new range.

Messages 1511 through 1530

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1511 "Text indexes are not allowed across server types."

Constant TEXT_NOT_ALLOWED_ACROSS_SERVERS

SAP Sybase Error Number 2596

SQL State WT033

SQL Code -1511L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Text indexes are not allowed across server types if the query is pro-
cessed in full-passthrough mode.

Error 1512 "Text index with external prefilter cannot contain both binary
and string columns"

Constant TEXT_INDEX_MIXED_COLUMNS

SAP Sybase Error 2561

Number

SQL State WT034

SAP Sybase IQ Error Messages 477

Errors and Warnings

Error 1512 "Text index with external prefilter cannot contain both binary
and string columns"

SQL Code -1512L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause One or more, but not all, of the columns specified for the text index is of type
binary, and the text configuration object has a prefilter library specified. Text
indexes using a prefilter library can contain either binary columns or string
data type columns, but not both.

Error 1513 "Sysam License Manager initialization failed."

Constant IQ_LICENSE_INITIALIZATION_FAILURE

SAP Sybase Error Number 2547

SQL State 0A005

SQL Code -1513L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Sysam License Manager initialization failed.

Error 1514 "Failed to checkout an IQ core license."

Constant IQ_CORE_LICENSE_CHECKOUT_FAILURE

SAP Sybase Error Number 2546

SQL State 0A006

SQL Code -1514L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Sysam License Manager was unable to obtain a valid IQ_CORE
license.

478 SAP Sybase IQ

Errors and Warnings

Error 1515 "Support for spatial is not available for this CPU."

Constant SLERR_CPU_NEED_SSE

SAP Sybase Error Number 3179

SQL State 2FW91

SQL Code -1515L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Spatial data support for 32-bit Windows and 32-bit Linux requires a
CPU that supports the SSE2 instructions.

Error 1516 "The intermediate point (%3) of the ST_CircularString segment

between %1 and %2 is collinear with but not between the start
and end points."

Constant SLERR_CIRC_COLLINEAR_MIDPOINT

SAP Sybase Error 3180

Number

SQL State 2FF72

SQL Code -1516L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The start point of the ST_CircularString segment

Parameter 2 The end point of the ST_CircularString segment

Parameter 3 The specified intermediate point of the ST_CircularString segment

Probable Cause When the intermediate point of a ST_CircularString segment is collinear

with the start and end point the result is interpreted as a straight line between
the start and the end point. In this case, the intermediate point must be
located on the line segment between the start and end point.

SAP Sybase IQ Error Messages 479

Errors and Warnings

Error 1517 "Logical Server \"%1\" not found"

Constant LOGICAL_SERVER_NOT_FOUND

SAP Sybase Error Number 2545

SQL State WQ001

SQL Code -1517L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the logical server.

Probable Cause The named logical server was not found in the database.

Error 1518 "Logical Server Policy \"%1\" does not allow coordinator
membership in logical servers."

Constant LS_COORD_MEMBERSHIP_NOT_ALLOWED

SAP Sybase Error Number 2543

SQL State WQ002

SQL Code -1518L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the logical server policy.

Probable Cause Logical server policy does not allow coordinator as a member of
logical server.

Error 1519 "Cannot determine the logical server context due to

overlapping logical server memberships for login policy
\"%1\"."

Constant LS_MEMBERSHIP_OVERLAP_NOT_ALLOWED

SAP Sybase Error Number 2541

SQL State WQ003

480 SAP Sybase IQ

Errors and Warnings

Error 1519 "Cannot determine the logical server context due to

overlapping logical server memberships for login policy
\"%1\"."

SQL Code -1519L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the login policy.

Probable Cause Cannot determine the logical server context for named login policy.
Specify the logical server in the connection string

Error 1520 "Cannot recreate an already existing logical server

membership."

Constant LS_MEMBERSHIP_ALREADY_EXISTS

SAP Sybase Error Number 2539

SQL State WQ004

SQL Code -1520L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Multiplex server which is to be added as a member is already a mem-

ber of logical server.

Error 1521 "Cannot drop a non-existing logical server membership."

Constant LS_MEMBERSHIP_NOT_FOUND

SAP Sybase Error Number 2537

SQL State WQ005

SQL Code -1521L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 481

Errors and Warnings

Error 1521 "Cannot drop a non-existing logical server membership."

Probable Cause Multiplex server membership about to be dropped was not found.

Error 1522 "Database needs to be upgraded to support the use of

external libraries with text indexes."

Constant TEXT_EXT_UPGRADE_REQUIRED

SAP Sybase Error Num- 2530

ber

SQL State WT035

SQL Code -1522L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for prefilter and
term breaker external libraries. To use this feature, upgrade your da-
tabase to the most recent version.

Error 1523 "Cannot reassign logical server '%1' to login policy '%2'."

Constant LS_LP_ASSIGNMENT_EXISTS

SAP Sybase Error Number 2507

SQL State WQ006

SQL Code -1523L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the logical server.

Parameter 2 The name of the login policy.

Probable Cause Logical Server - Login Policy assignment already exists.

482 SAP Sybase IQ

Errors and Warnings

Error 1524 "Cannot drop a non-existing assignment between logical

server '%1' and login policy '%2'."

Constant LS_LP_NON_EXISTING_ASSIGNMENT

SAP Sybase Error Number 2508

SQL State WQ007

SQL Code -1524L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the logical server.

Parameter 2 The name of the login policy.

Probable Cause Logical Server - Login Policy assignment does not exist.

Error 1525 "Cannot perform specified operation, number of

administrators for role '%1' falls below min_role_admins
option value"

Constant MIN_ROLE_ADMIN_VIOLATION

SAP Sybase Error 3181

Number

SQL State 55W36

SQL Code -1525L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the role that violates minimum number of administrators con-
dition

Probable Cause Specified operation cannot be performed because it will make the number
of administrators for the specified role go below the threshold value set
through database option min_role_admins.

SAP Sybase IQ Error Messages 483

Errors and Warnings

Error 1526 "Text index %1 cannot be used with text procedure %2"

Constant TEXT_INVALID_INDEX_FOR_PROC

SAP Sybase Error Num- 2010

ber

SQL State WT036

SQL Code -1526L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the text index.

Parameter 2 The name of the procedure for which the specified index is invalid.

Probable Cause The specified text procedure cannot be used with the text index. The
text procedure charset has to correspond to the charset of the text index
it is accessing.

Error 1527 "Task '%1' is not allowed"

Constant SYSPRIV_CREATION_NOT_ALLLOWED

SAP Sybase Error Number 3182

SQL State 28W18

SQL Code -1527L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the internal task that was provided by the user.

Probable Cause Creation of system privilege is an internal task, allowed only during
database creation or upgrade.

Error 1528 "No more role grant permitted"

Constant ROLE_GRANT_ID_NOT_AVAILABLE

SAP Sybase Error Num- 3183

ber

484 SAP Sybase IQ

Errors and Warnings

Error 1528 "No more role grant permitted"

SQL State 28W19

SQL Code -1528L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Maximum limit for role grants has been reached. No more role grants
are permitted. Remove some role grants and try again.

Error 1529 "Outer reference not permitted in DML derived table"

Constant SELECT_DML_OUTER_REFERENCE

SAP Sybase Error Num- 3184

ber

SQL State 42U09

SQL Code -1529L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Outer references are not permitted in derived tables based on INSERT,
UPDATE, DELETE, or MERGE statements. These derived tables may
only appear in subqueries that are uncorrelated.

Error 1530 "Format '%1' is not supported in the UNLOAD statement"

Constant UNSUPPORTED_UNLOAD_FORMAT

SAP Sybase Error Number 3185

SQL State WL018

SQL Code -1530L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

SAP Sybase IQ Error Messages 485

Errors and Warnings

Error 1530 "Format '%1' is not supported in the UNLOAD statement"

Parameter 1 The specified format.

Probable Cause An unsupported file format was specified for the UNLOAD state-
ment.

Messages 1531 through 1550

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1531 "Geometry expressions cannot be used in the ORDER BY

specification (near '%1')"

Constant SLERR_GEOM_ORDER_BY

SAP Sybase Error 3186

Number

SQL State 2FW92

SQL Code -1531L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The geometry expression.

Probable Cause Geometry expressions cannot be used in the ORDER BY clause. The
ST_LinearHash() method may be used in the ORDER BY specification to
order geometry values using the same rules used for spatial indexes, or a
conversion method such as ST_AsText() may be used to order the rows by
their string representation.

Error 1532 "Failed to transform point %1 (error %2)"

Constant SLERR_TRANSFORM_POINT_FAIL

SAP Sybase Error 3187

Number

SQL State 2FF17

SQL Code -1532L

ODBC 2 State ERROR

486 SAP Sybase IQ

Errors and Warnings

Error 1532 "Failed to transform point %1 (error %2)"

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The point that could not be transformed.

Parameter 2 The error code from the projection library.

Error 1533 "Logical server policy \"%1\" not found"

Constant LS_POLICY_NOT_FOUND

SAP Sybase Error Number 2445

SQL State WQ008

SQL Code -1533L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the logical server policy.

Probable Cause The named logical server policy was not found in the database.

Error 1534 "Logical server operations not allowed on a simplex

database."

Constant LS_OPS_DISALLOWED_ON_SIMPLEX

SAP Sybase Error Number 2443

SQL State WQ009

SQL Code -1534L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 487

Errors and Warnings

Error 1534 "Logical server operations not allowed on a simplex

database."

Probable Cause Logical server operations are disallowed on a simplex database.

Error 1535 "System Privileges and Roles feature is not supported in

this database"

Constant ROLES_NOT_SUPPORTED

SAP Sybase Error Num- 3188

ber

SQL State 0AW27

SQL Code -1535L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause The current database is an older database and does not have catalog
support for System Privileges and Roles feature. To use this feature,
upgrade your database to the most recent version.

Error 1536 "Invalid user ID or role name '%1' specified"

Constant INVALID_USER_ROLE_NAME

SAP Sybase Error Number 3189

SQL State 28000

SQL Code -1536L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the invalid user or role that was specified.

Probable Cause You supplied an invalid name for a user or role.

Error 1537 "Role \"%1\" already exists"

Constant ROLE_ALREADY_EXISTS

488 SAP Sybase IQ

Errors and Warnings

Error 1537 "Role \"%1\" already exists"

SAP Sybase Error Number 3190

Severity Code 14 on page 2

Parameter 1 The name of the role.

Probable Cause WITH NO SYSTEM PRIVILEGE INHERITANCE OPTION can be

specified only with user defined roles corresponding to legacy non-
inheritable authorities.

Error 1540 "Operation would cause a role cycle"

Constant ROLE_CYCLE

SAP Sybase Error Number 3193

SQL State 28000

SQL Code -1540L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause You attempted to grant role to a grantee that would result in a grantee
belonging to itself. Role membership may be direct or indirect.

Error 1541 "Specified System Privilege '%1' is Invalid"

Constant INVALID_SYSTEM_PRIVILEGE

SAP Sybase Error Number 3194

SQL State 28000

SQL Code -1541L

ODBC 2 State ERROR

Error 1544 "Login disallowed. User does not have sufficient authority
to access SERVER logical server."

SAP Sybase Error Number 2423

SQL State WQ012

SQL Code -1544L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Accessing SERVER logical server requires either DBA or MULTI-
PLEX ADMIN authority.

Error 1545 "Cannot create logical server named '%1'. Choose another
name for logical server."

Constant INVALID_LS_NAME

SAP Sybase Error Number 2422

SQL State WQ013

SQL Code -1545L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of logical server.

Probable Cause Logical server names ALL, NONE, SERVER, OPEN, DEFAULT and
COORDINATOR are reserved for the current or future releases.

Error 1546 "Cannot drop Multiplex server '%1' as it is part of a Logical

Server. Use the \"WITH DROP MEMBERSHIP\" clause."

Constant IQ_MPX_SRV_IS_LS_MEMBER

SAP Sybase Error Num- 2387

ber

SQL State WQ014

SQL Code -1546L

492 SAP Sybase IQ

Errors and Warnings

Error 1546 "Cannot drop Multiplex server '%1' as it is part of a Logical

Server. Use the \"WITH DROP MEMBERSHIP\" clause."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of multiplex server.

Probable Cause If an MPX server is part of a Logical Server then the DROP MPX
command should have WITH MEMBERSHIP clause to drop it.

Error 1547 "Cannot drop Multiplex server '%1' without dropping all the
logical servers as it will convert the Multiplex to Simplex. Use the
\"WITH DROP LOGICAL SERVER\" clause."

Constant IQ_MPX_SRV_IS_LAST_SEC_MEMBER

SAP Sybase Error 2371

Number

SQL State WQ015

SQL Code -1547L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of multiplex server.

Probable Cause If dropping the secondary server will result in conversion from MPX to SPX
then all the user created logical servers should be dropped.

Error 1548 "Cannot drop Multiplex server '%1'. This is not the last
secondary server. Remove the \"WITH DROP LOGICAL SERVER
\" clause."

Constant IQ_MPX_SRV_IS_NOT_LAST_SEC_MEMBER

SAP Sybase Error 2370

Number

SQL State WQ016

SQL Code -1548L

SAP Sybase IQ Error Messages 493

Errors and Warnings

Error 1548 "Cannot drop Multiplex server '%1'. This is not the last
secondary server. Remove the \"WITH DROP LOGICAL SERVER
\" clause."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of multiplex server.

Probable Cause WITH DROP LOGICAL SERVER clause should be used ONLY when
dropping the last secondary Server.

Error 1549 "Cannot set the '%1' option as Login Policy option '%2' is set to
off."

Constant LS_LP_MODIFY_OPT_NOT_ALLOWED

SAP Sybase Error 2369

Number

SQL State WQ017

SQL Code -1549L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the temporary option

Parameter 2 The name of the Login Policy Option.

Probable Cause If an option of the login policy is set to off then user cannot set the tem-
porary option which is directly depending on it. For example, if the login
policy option DQP_ENABLED is set to Off, then the temporary option
DQP_ENABLED cannot be set to On.

Error 1550 "Overriding ROOT login policy options for logical servers
is not allowed."

Constant LS_ROOT_LP_OVERRIDE_NOT_ALLOWED

SAP Sybase Error Number 2368

SQL State WQ018

494 SAP Sybase IQ

Errors and Warnings

Error 1550 "Overriding ROOT login policy options for logical servers
is not allowed."

SQL Code -1550L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A user cannot override login policy options of ROOT login policy for
logical servers.

Messages 1551 through 1570

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1551 "Login redirection is required to complete the connection, but it

is not supported by the client"

Constant LOGIN_REDIRECTION_REQUIRED

SAP Sybase Error 3195

Number

SQL State 08WA6

SQL Code -1551L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause The connection needs to be redirected to another server, but the version of
the client library does not support login redirection. You must upgrade the
client library to use login redirection. Alternatively, you can connect to a
different server or change the logical server configuration.

Error 1552 "Invalid text index type for the materialized view"

Constant TEXT_MV_INVALID_COMBO

SAP Sybase Error Number 3196

SQL State WT037

SQL Code -1552L

SAP Sybase IQ Error Messages 495

Errors and Warnings

Error 1552 "Invalid text index type for the materialized view"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Text index with the specified refresh type cannot be created on the
materialized view. Only IMMEDIATE REFRESH text indexes are
allowed on materialized views.

Error 1553 "Cannot perform specified operation, set user condition

violated"

Constant SET_USER_VIOLATION

SAP Sybase Error Number 3197

SQL State 55W37

SQL Code -1553L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Specified operation cannot be performed because it will invalidate the
on going SET USER statements in the database.

Error 1554 "Specified LDAP server '%1' is not found"

Constant UNKNOWN_LDAP_SERVER

SAP Sybase Error Number 3198

SQL State 28000

SQL Code -1554L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The name of the LDAP server.

Probable Cause The LDAP server specified does not exist in the database.

496 SAP Sybase IQ

Errors and Warnings

Error 1555 "Statement not allowed on text index for a materialized view"

Constant TEXT_MV_TIND_NOT_ALLOWED

SAP Sybase Error 3199

Number

SQL State WT038

SQL Code -1555L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You cannot use REFRESH TEXT INDEX or TRUNCATE TEXT INDEX
on a text index that is created for a materialized view. You cannot alter the
text index to use a different refresh type.

Error 1556 "External environment failed to start and establish a connection

within the %1 second timeout"

Constant EXTENV_START_TIMED_OUT

SAP Sybase Error 3200

Number

SQL State WP017

SQL Code -1556L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The amount of time in seconds the server will wait for the external environ-
ment to start and establish a connection.

Probable Cause The External Environment took too long to start up and establish a connection
with the server. The problem may be due to the system being over stressed or
incorrectly configured.

Error 1557 "External environment cannot be started during database

startup"

Constant EXTENV_START_ON_STARTUP

SAP Sybase IQ Error Messages 497

Errors and Warnings

Error 1557 "External environment cannot be started during database

startup"

SAP Sybase Error 3201

Number

SQL State WP018

SQL Code -1557L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An external environment cannot be started while a database is starting up.
Wait for the database startup to complete before attempting to start an
external environment.

Error 1558 "Specified user '%1' is a role"

Constant CAN_NOT_DROP_ROLE

SAP Sybase Error Number 3202

SQL State 28000

SQL Code -1558L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the user being dropped.

Probable Cause You attempted to drop a role. Use DROP ROLE statement.

Error 1559 "Specified role '%1' is not a user extended as role"

Constant NOT_AN_EXTENDED_USER

SAP Sybase Error Number 3203

SQL State 28000

SQL Code -1559L

ODBC 2 State ERROR

498 SAP Sybase IQ

Errors and Warnings

Error 1559 "Specified role '%1' is not a user extended as role"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the role being dropped.

Probable Cause The role name provided is not a user extended as role. Use of FROM
USER clause is not allowed in such cases.

Error 1560 "Specified role '%1' is a user extended as role"

Constant AN_EXTENDED_USER

SAP Sybase Error Number 3204

SQL State 28000

SQL Code -1560L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the role being dropped.

Probable Cause Specified role is a user extended as role but FROM USER clause is not
specified in DROP ROLE command.

Error 1561 "Use of WITH DROP OBJECTS is not allowed with '%1'"

Constant WITH_DROP_OBJECTS_NOT_ALLOWED

SAP Sybase Error Number 3205

SQL State 28000

SQL Code -1561L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the role being dropped.

Probable Cause Use of WITH DROP OBJECTS is not allowed with user extended as
role.

SAP Sybase IQ Error Messages 499

Errors and Warnings

Error 1562 "The role '%1' was not dropped because it is granted to other
users or roles. Use the 'WITH REVOKE' option to drop it."

Constant CONTAINS_PRIV_GRANTS

SAP Sybase Error 3206

Number

SQL State 28000

SQL Code -1562L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the role being dropped.

Probable Cause The role being dropped has been granted to other users or roles with WITH
NO ADMIN OPTION or with WITH ADMIN OPTION. A role can be drop-
ped when either all of its grants are with WITH ADMIN ONLY OPTION or
WITH REVOKE option is specified in DROP ROLE command. Either revoke
all such grants or use WITH REVOKE option for DROP ROLE.

Error 1563 "Cannot drop a role that owns sequences in runtime

server"

Constant USER_OWNS_SEQUENCES

SAP Sybase Error Num- 3207

ber

SQL State 55W38

SQL Code -1563L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a role that owns procedures while using the
runtime server. This operation would result in dropping sequences.
The runtime server cannot drop sequences.

500 SAP Sybase IQ

Errors and Warnings

Error 1564 "Cannot drop a role that owns events in runtime server"

Constant USER_OWNS_EVENTS

SAP Sybase Error Number 3208

SQL State 55W39

SQL Code -1564L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a role that owns events while using the runtime
server. This operation would result in dropping events. The runtime
server cannot drop events.

Error 1565 "Cannot drop a role that owns web services in runtime server"

Constant USER_OWNS_WEB_SERVICES

SAP Sybase Error 3209

Number

SQL State 55W40

SQL Code -1565L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a role that owns web services while using the
runtime server. This operation would result in dropping web services.
The runtime server cannot drop web services.

Error 1566 "Cannot drop a role that owns external environment objects in
runtime server"

Constant USER_OWNS_EXTERNENVOBJECTS

SAP Sybase Error 3210

Number

SQL State 55W41

SAP Sybase IQ Error Messages 501

Errors and Warnings

Error 1566 "Cannot drop a role that owns external environment objects in
runtime server"

SQL Code -1566L

ODBC 2 State 42000

ODBC 3 State 42000

Severity Code 16 on page 2

Probable Cause You attempted to drop a role that owns external environment objects while
using the runtime server. This operation would result in dropping external
environment objects. The runtime server cannot drop external environ-
ment objects.

Error 1567 "External environment cannot be started, external process

terminated on start up"

Constant EXTENV_PID_NOT_FOUND

SAP Sybase Error 3211

Number

SQL State WP019

SQL Code -1567L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The request to start an external environment could not be completed due to
the fact that the external process terminated on start up. This problem is
usually due to a client configuration issue.

Error 1568 "Unable to generate a logical server ID."

Constant LS_MAX_ID_LIMIT_REACHED

SAP Sybase Error Number 2365

SQL State WQ019

SQL Code -1568L

ODBC 2 State ERROR

ODBC 3 State ERROR

502 SAP Sybase IQ

Errors and Warnings

Error 1568 "Unable to generate a logical server ID."

Severity Code 16 on page 2

Probable Cause Last generated logical server ID reached maximum limit. The data-
base catalog needs to be rebuilt.

Error 1569 "LDAP Server \"%1\" already exists"

Constant LDAPSERVER_ALREADY_EXISTS

SAP Sybase Error Number 3212

SQL State WW202

SQL Code -1569L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the LDAP Server.

Probable Cause An attempt was made to create an LDAP server that already exists in
the database.

Error 1570 "Attempt to allocate memory for LDAP server \"%1\"

failed."

Constant LDAPSERVER_ALLOC_FAILED

SAP Sybase Error Number 3213

SQL State WW203

SQL Code -1570L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the LDAP Server.

Probable Cause An attempt to allocate memory for an LDAP Server class object
failed.

SAP Sybase IQ Error Messages 503

Errors and Warnings

Messages 1571 through 1590

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1571 "The attempt to drop LDAP server \"%1\" failed, suspend
the server to drop it."

Constant INVALID_STATE_CHANGE

SAP Sybase Error Number 3214

SQL State WW204

SQL Code -1571L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the LDAP Server.

Probable Cause An attempt to drop an LDAP Server failed because it was in the
READY or ACTIVE state. Use WITH SUSPEND to change state
before dropping server.

Error 1572 "LDAP User Authentication feature is not supported in this

database"

Constant LDAPUA_NOT_SUPPORTED

SAP Sybase Error Num- 3215

ber

SQL State WW205

SQL Code -1572L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database is an older database and does not have catalog
support for LDAP User Authentication feature. To use this feature,
upgrade your database to the most recent version.

504 SAP Sybase IQ

Errors and Warnings

Error 1573 "Mirror server class is not supported for IQ databases"

Constant OMNI_NO_MIRROR_FOR_IQ

SAP Sybase Error Number 3216

SQL State WO029

SQL Code -1573L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to create a remote data access server of type mirror
while connected to an IQ database. The Mirror server class is not
supported for IQ databases.

Error 1574 "You must upgrade your database in order to use the mirror
server class"

Constant OMNI_MIRROR_NEEDS_UPGRADE

SAP Sybase Error 3217

Number

SQL State WO030

SQL Code -1574L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to create a remote data access server of type mirror while
connected to a database that was created with older software. You must
upgrade your database in order to make use of the mirror server class.

Error 1575 "Database upgrade not possible; the name or ID of new

IQ_SHARED_TEMP dbspace is already in use."

Constant IQ_SHTEMP_DBSPACE_CONFLICT

SAP Sybase Error 2364

Number

SQL State WQ020

SAP Sybase IQ Error Messages 505

Errors and Warnings

Error 1575 "Database upgrade not possible; the name or ID of new

IQ_SHARED_TEMP dbspace is already in use."

SQL Code -1575L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt to upgrade a database failed. Retry upgrade of the database
when no existing dbspace is using the name or ID of the
IQ_SHARED_TEMP dbspace.

Error 1576 "LDAP server \"%1\" is in use by login policy \"%2\"."

Constant LDAPSERVER_IN_USE

SAP Sybase Error Num- 3218

ber

SQL State WW206

SQL Code -1576L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the LDAP server.

Parameter 2 The name of the login policy.

Probable Cause The named login policy references the LDAP server. The login policy
must be changed to avoid referencing the LDAP server before the
LDAP server can be dropped. Or use DROP LDAP SERVER <server
name> WITH DROP ALL REFERENCES to remove any references in
login policies to the LDAP server.

Error 1577 "Invalid error raised by user-defined function: (%1) %2."

Constant EMSG_UDF_RAISED_INVALID_ERROR

SAP Sybase Error Number 3219

SQL State QFA67

SQL Code -1577L

506 SAP Sybase IQ

Errors and Warnings

Error 1577 "Invalid error raised by user-defined function: (%1) %2."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Invalid error code used by UDF.

Parameter 2 Error message provided by UDF to accompany UDF SQLCODE.

Probable Cause An error was raised by a user-defined function that is outside reserved
range.

Error 1578 "Table parameterized functions are not allowed across

server types."

Constant TPF_NOT_ALLOWED_ACROSS_SERVERS

SAP Sybase Error Number 3220

SQL State WO009

SQL Code -1578L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Table parameterized functions are not allowed across server types if a
query is not processed in full-passthrough mode.

Error 1579 "External procedures or functions are not allowed across

server types."

Constant PROC_NOT_ALLOWED_ACROSS_SERVERS

SAP Sybase Error Number 3221

SQL State WO031

SQL Code -1579L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 507

Errors and Warnings

Error 1579 "External procedures or functions are not allowed across

server types."

Probable Cause External procedure or function calls are not allowed across server
types if the query is not processed in full-passthrough mode.

Error 1580 "Failed to load the MobiLink client support libraries."

Constant COULD_NOT_LOAD_SYNC_LIBRARY

SAP Sybase Error Num- 3222

ber

SQL State WW207

SQL Code -1580L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 19 on page 2

Probable Cause To use the SYNCHRONIZE command, a MobiLink client must be in-
stalled on the same computer where the database server is running.

Error 1581 "Database name must be specified when connecting to a

cloud database server"

Constant NO_DEFAULT_DATABASE

SAP Sybase Error Number 3223

SQL State 08WA7

SQL Code -1581L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause When connecting to a cloud database server, a database name must be
specified by the connection string. Cloud database servers do not have
a default database.

508 SAP Sybase IQ

Errors and Warnings

Error 1582 "Server name can only be specified when connecting to a cloud
database server with NODETYPE=DIRECT"

Constant SERVER_NAME_NOT_ALLOWED

SAP Sybase Er- 3224

ror Number

SQL State 08WA8

SQL Code -1582L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause When connecting to a cloud database server, specifying a server name on the
connection string is only allowed for NODETYPE=DIRECT. When using other
NODETYPE values to connect to a cloud database server, specifying the server
name is not allowed. Typically, for connections to a cloud database server the
HOST connection parameter or HOST protocol option is used to specify the
address of one or more cloud database servers.

Error 1583 "Cannot upgrade the database. The database can be upgraded
only after starting the coordinator in single node mode."

Constant IQ_MPX_MUST_BE_SINGLE_NODE

SAP Sybase Error 3225

Number

SQL State WQ021

SQL Code -1583L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause In order to run ALTER DATABASE UPGRADE on the database, the
coordinator must be started in single node mode using the '-iqmpx_sn 1'
server startup option.

Error 1584 "Unable to load the dbrsakp shared object"

Constant RSA_LOAD_FAILED

SAP Sybase IQ Error Messages 509

Errors and Warnings

Error 1584 "Unable to load the dbrsakp shared object"

SAP Sybase Error Number 3226

SQL State 08WA9

SQL Code -1584L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause The server was unable to load the dbrsakp DLL on Windows plat-
forms or the libdbrsakp shared object on Unix platforms.

Error 1585 "Invalid tool name or admin user for generating security
token"

Constant INVALID_TOOL_NAME_OR_ADMIN_USER

SAP Sybase Error Number 3227

SQL State 08WB1

SQL Code -1585L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Probable Cause The tool name or admin user supplied is invalid for generating a
security token.

Error 1586 "Error modifying refresh type for text index \"%1\" on
materialized view \"%2\No message

Constant TEXT_INDEX_MV_ALTER_ERROR

SAP Sybase Error Number 3228

SQL State WT039

SQL Code -1586L

ODBC 2 State ERROR

ODBC 3 State ERROR

510 SAP Sybase IQ

Errors and Warnings

Error 1586 "Error modifying refresh type for text index \"%1\" on
materialized view \"%2\No message

SQL State 55W44

SQL Code -1589L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the certificate that could not be found

Probable Cause You misspelled the name of a certificate, or the certificate does not
exist.

Error 1590 "You cannot use a security token when making remote
connections"

Constant INVALID_USE_OF_SECURITY_TOKEN

SAP Sybase Error Number 3232

SQL State WO032

SQL Code -1590L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause A security token cannot be used to make remote data access connec-
tions

Messages 1591 through 1610

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1591 "Invalid use of BEFORE operator in text query."

Constant TEXT_INVALID_BEFORE

SAP Sybase Error Number 3233

512 SAP Sybase IQ

Errors and Warnings

Error 1591 "Invalid use of BEFORE operator in text query."

SQL State WT040

SQL Code -1591L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Probable Cause Only terms and prefixes are allowed as arguments to a BEFORE
operator.

Error 1592 "Text indexes on materialized views are not supported for
this database."

Constant TEXT_MV_UPGRADE_REQUIRED

SAP Sybase Error Number 3234

SQL State WT041

SQL Code -1592L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for text indexes on
materialized views. To use this feature, upgrade your database to the
most recent version.

Error 1593 "Unable to copy file %1 to destination %2"

Constant UNABLE_TO_COPY_DB_FILE_INTO_CLOUD

SAP Sybase Error Num- 3235

ber

SQL State 08WB2

SQL Code -1593L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

SAP Sybase IQ Error Messages 513

Errors and Warnings

Error 1593 "Unable to copy file %1 to destination %2"

Parameter 1 The file name of the file on the client computer

Parameter 2 The file name of the destination within the cloud

Probable Cause The client database file could not be copied to the requested cloud
destination.

Error 1594 "LDAP server definition of \"%1\" is incomplete. A search

URL, access distinguished name, password, and
authentication URL are required."

Constant LDAPSERVER_INCOMPLETE_DEF

SAP Sybase Error Num- 3236

ber

SQL State WW208

SQL Code -1594L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the LDAP server.

Probable Cause The named LDAP server is missing one or more of the values required to
search for a user's distinguished name or authenticate a user. Use AL-
TER LDAP SERVER <server name> to specify any missing values.

Error 1595 "Column '%1' not found in variable '%2'"

Constant COLUMN_NOT_FOUND_IN_VARIABLE

SAP Sybase Error Num- 3237

ber

SQL State 52006

SQL Code -1595L

ODBC 2 State S0002

ODBC 3 State 42S22

Severity Code 11 on page 2

514 SAP Sybase IQ

Errors and Warnings

Error 1595 "Column '%1' not found in variable '%2'"

Parameter 1 Name of the column that could not be found.

Probable Cause You tried to access an array element with an index outside the de-
clared size of the array. For an array of size N, valid array elements are
numbered 1 through N.

Error 1599 "Invalid use of collection type"

Constant INVALID_USE_OF_COLLECTION

SAP Sybase Error 3240

Number

SQL State WW210

SQL Code -1599L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

516 SAP Sybase IQ

Errors and Warnings

Error 1599 "Invalid use of collection type"

Probable Cause You tried to use an ARRAY or ROW type in an unsupported context. You
cannot store these values in tables or read them directly from client in-
terfaces such as ODBC, ESQL, and JDBC. You must extract the indi-
vidual values you are interested in.

Error 1600 "The bind to URL '%1' failed. The most recently reported
LDAP API error is: '%2'"

Constant LDAPUA_BINDFAIL

SAP Sybase Error Number 3241

SQL State WW211

SQL Code -1600L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The LDAP URL used with bind().

Parameter 2 The LDAP API error message.

Probable Cause The message is reported from the LDAP API client with context from
the LDAP User Authentication methods. An LDAP administrator or
Sybase Tech Support may use these low level messages to direct the
DBA how to resolve a problem.

Error 1601 "Password encryption failed. Error message '%1'."

Constant PWD_CIPHER_ERROR

SAP Sybase Error Number 3242

SQL State WW212

SQL Code -1601L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 16 on page 2

Parameter 1 The error message reported by block encrypter.

SAP Sybase IQ Error Messages 517

Errors and Warnings

Error 1601 "Password encryption failed. Error message '%1'."

Probable Cause Run-time block encrypter initialization failed.

Error 1602 "The specified distinguished name '%1' does not match the
search result '%2'."

Constant LDAPUA_DN_NOMAT

SAP Sybase Error Num- 3243

ber

SQL State WW213

SQL Code -1602L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The expected distinguished name that was specified in command.

Parameter 2 The result distinguished name returned by LDAP search.

Probable Cause VALIDATE LDAP SERVER command did a successful search to find
a user distinguished name, but the value differs from the expected
distinguished name specified in the command.

Error 1603 "The search using '%1' failed due to one or more invalid values
set."

Constant LDAPUA_SEARCHFAIL

SAP Sybase Error 3244

Number

SQL State WW214

SQL Code -1603L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The LDAP server name or search URL specifying the search.

518 SAP Sybase IQ

Errors and Warnings

Error 1603 "The search using '%1' failed due to one or more invalid values
set."

Probable Cause An LDAPUA search or validate failed returning LDAP_INVALID_CRE-

DENTIALS, LDAP_INSUFFICIENT_ACCESS, LDAP_INVA-
LID_DN_SYNTAX, LDAP_NO_SUCH_OBJECT, or LDAP_FIL-
TER_ERROR due to the invalid settings. Check the access account values
for the named LDAP server or search URL.

Error 1604 "Cannot use logical server policy clause more than once"

Constant LS_POLICY_USED_TWICE

SAP Sybase Error Number 3245

SQL State WQ022

SQL Code -1604L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause ls policy clause appeared more than once in a create/alter logical
server policy statement

Error 1605 "Table Parameterized Functions and V4 TableUDFs are not

supported for this database."

Constant TPF_UPGRADE_REQUIRED

SAP Sybase Error Number 3246

SQL State WP020

SQL Code -1605L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The current database does not have catalog support for table para-
meterized functions. To use this feature, upgrade your database to the
most recent version.

SAP Sybase IQ Error Messages 519

Errors and Warnings

Error 1606 "Multiple table parameters are not supported."

Constant ONLY_SINGLE_TABLE_PARM_SUPPORTED

SAP Sybase Error Number 3247

SQL State WP021

SQL Code -1606L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Table parameterized functions are limited to only having at most a
single table parameter.

Error 1607 "Outer references are not allowed for TPF input tables."

Constant TPF_OUTER_REFERENCES_NOT_ALLOWED

SAP Sybase Error Number 3249

SQL State WP022

SQL Code -1607L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause Outer references in the select list for a TPF input table are not allowed.

Error 1608 "Unable to delete file %1"

Constant UNABLE_TO_DELETE_FILE

SAP Sybase Error Number 3250

SQL State 08WB4

SQL Code -1608L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

520 SAP Sybase IQ

Errors and Warnings

Error 1608 "Unable to delete file %1"

Parameter 1 The file name of the file to be deleted

Probable Cause The request to delete a file failed

Error 1609 "File %1 already exists"

Constant FILE_ALREADY_EXISTS

SAP Sybase Error Number 3251

SQL State 08WB5

SQL Code -1609L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 The file name of the file that already exists

Probable Cause The request to create a file or directory failed because the file or
directory already exists

Error 1610 "Unable to create directory %1"

Constant UNABLE_TO_CREATE_DIRECTORY

SAP Sybase Error Number 3252

SQL State 08WB6

SQL Code -1610L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 The file name of the directory that could not be created

Probable Cause The request to create a directory failed

SAP Sybase IQ Error Messages 521

Errors and Warnings

Messages 1611 through 1630

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1611 "Unable to copy file %1"

Constant UNABLE_TO_COPY_FILE

SAP Sybase Error Number 3253

SQL State 08WB7

SQL Code -1611L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 The file name of the file to be copied

Probable Cause The request to copy a file failed

Error 1612 "Cannot ALTER LDAP SERVER '%1' while ldap server is in
active state."

Constant LDAPSERVER_IS_ACTIVE

SAP Sybase Error Number 3254

SQL State WW215

SAP Sybase Error Number 3257

SQL State WQ024

SQL Code -1615L

SAP Sybase IQ Error Messages 523

Errors and Warnings

Error 1615 "LS Policy '%1' cannot be dropped because this policy is
currently being used by a logical server"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 LS policy name.

Probable Cause A logical server policy cannot be dropped if a logical server is using
it.

Error 1616 "'%1' being used incorrectly in ls policy statement"

Constant LSP_USING_INCORRECT_ARGS

SAP Sybase Error Number 3258

SQL State WQ025

SQL Code -1616L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 LS policy option name.

Probable Cause A clause in a ls policy sql statement has been used incorrectly.

Error 1617 "The %1 remote data access class is no longer supported,

please use %2 instead"

Constant OMNI_JDBC_NO_LONGER_SUPPORTED

SAP Sybase Error Num- 3259

ber

SQL State WO033

SQL Code -1617L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

524 SAP Sybase IQ

Errors and Warnings

Error 1617 "The %1 remote data access class is no longer supported,

please use %2 instead"

Parameter 1 The JDBC based remote data access class.

Parameter 2 The preferred ODBC based remote data access class.

Probable Cause You attempted to use a JDBC based remote data access class which is
no longer supported. Please use the appropriate ODBC based class
instead.

Error 1618 "The %1 remote data access class has been deprecated,
please use %2 instead or change cis_option"

Constant OMNI_JDBC_DEPRECATED

SAP Sybase Error Num- 3260

ber

SQL State WO034

SQL Code -1618L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The JDBC based remote data access class.

Parameter 2 The preferred ODBC based remote data access class.

Probable Cause You attempted to use a JDBC based remote data access class which has
been deprecated. Please use the appropriate ODBC based class instead;
or change the cis_option setting to re-enable this feature.

Error 1619 "logical server '%1' cannot be used in a connect string"

Constant LS_NOT_ALLOWED

SAP Sybase Error Number 3261

SQL State WQ026

SQL Code -1619L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 525

Errors and Warnings

Error 1619 "logical server '%1' cannot be used in a connect string"

Severity Code 16 on page 2

Parameter 1 logical servername.

Probable Cause This logical server cannot be used as an argument to the connection
string parameter logicalserver

Error 1620 "The value specified is not within the required range %1 to
%2."

Constant LDAPUA_OPT_OUT_OF_RANGE

SAP Sybase Error Number 3262

SQL State WW217

SQL Code -1620L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The minimum value for this option.

Parameter 2 The maximum value for this option.

Probable Cause The specified value for an LDAP server option is too big or too small.

Error 1621 "LDAP server %1 may not accept anonymous binds."

Constant LDAPUA_ANONBINDERR

SAP Sybase Error Number 3263

SQL State WW218

SQL Code -1621L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The LDAP server name or search URL specifying the search.

526 SAP Sybase IQ

Errors and Warnings

Error 1621 "LDAP server %1 may not accept anonymous binds."

Probable Cause An LDAPUA search or validate failed returning LDAP_INAPPRO-

PRIATE_AUTH due to invalid settings for the target LDAP server.
Check the access account values for the named LDAP server or search
URL.

Error 1622 "Bind to LDAP server %1 without a password is not

allowed."

Constant LDAPUA_UTP

SAP Sybase Error Number 3264

SQL State WW219

SQL Code -1622L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The LDAP server name or search URL specifying the search.

Probable Cause An LDAPUA search or validate failed returning LDAP_UNWILL-

ING_TO_PERFORM due to invalid settings for the target LDAP
server. Check access account values for the named LDAP server or
search URL.

Error 1623 "The search on LDAP server %1 completed with no

matching results."

Constant LDAPUA_NO_SEARCH_RESULTS

SAP Sybase Error Num- 3265

ber

SQL State WW220

SQL Code -1623L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The LDAP server name or search URL specifying the search.

SAP Sybase IQ Error Messages 527

Errors and Warnings

Error 1623 "The search on LDAP server %1 completed with no

matching results."

Probable Cause An LDAPUA search or validate failed returning LDAP_NO_RE-

SULTS_RETURNED. This error is expected when the user does not
exist in the LDAP server.

Error 1624 "The length of the value specified is too long, it exceeds
the limit of %1 bytes."

Constant LDAPUA_OPT_TOO_LONG

SAP Sybase Error Number 3266

SQL State WW216

SQL Code -1624L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The maximum length of the value.

Probable Cause The specified value for an LDAP server option is too long. Specify a
shorter string.

Error 1625 "The UltraLite database deploy file is invalid (code: %1, file:
%2)"

Constant ULTRALITE_DEPLOY_FILE_INVALID

SAP Sybase Error 3267

Number

SQL State WU002

SQL Code -1625L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The diagnostic code.

Parameter 2 The associated filename, if applicable.

528 SAP Sybase IQ

Errors and Warnings

Error 1625 "The UltraLite database deploy file is invalid (code: %1, file:
%2)"

Probable Cause The UltraLite database deploy file is invalid. This can occur if the wrong
file is deployed, or if the file is damaged. Diagnostic code 1 indicates the
file is not a deploy file or has subsequently been corrupted. Diagnostic
code 2 indicates the file is not a valid size.

Error 1626 "The logical server policy for logical server '%1' does not
allow 'redirect=yes' in the connection string"

Constant LS_POLICY_DOES_NOT_ALLOW_REDIRECTION

SAP Sybase Error Number 3268

SQL State WQ027

SQL Code -1626L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 logical servername.

Probable Cause This logical server policy for this logical server does not allow redi-
rection"

Error 1627 "TLS ON cannot be used with URL %1"

Constant LDAPUA_TLS_WITH_LDAPS

SAP Sybase Error Num- 3269

ber

SQL State WW240

SQL Code -1627L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The LDAP URL that is using Secure LDAP.

SAP Sybase IQ Error Messages 529

Errors and Warnings

Error 1627 "TLS ON cannot be used with URL %1"

Probable Cause The LDAP server is specified with TLS ON and the specified LDAP
URL uses Secure LDAP, that is, 'ldaps' instead of 'ldap', which is not a
valid combination. Use either TLS ON or an 'ldaps' URL.

Error 1628 "logical server '%1' cannot be used as a default logical

server"

Constant LS_NOT_ALLOWED_AS_DEFAULT

SAP Sybase Error Number 3270

SQL State WQ028

SQL Code -1628L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 logical servername.

Probable Cause This logical server cannot be used as a default logical server

Error 1629 "Only one IDENTIFIED BY value may be specified."

Constant LDAPUA_TOO_MANY_IDENTBY

SAP Sybase Error Num- 3271

ber

SQL State WW241

SQL Code -1629L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The LDAP server is specified with more than one password or is speci-
fied with both IDENTIED BY and IDENTIFIED BY ENCRYPTED.
Set only one password.

530 SAP Sybase IQ

Errors and Warnings

Error 1630 "Server '%1' is not allowed to have different values for ls
policy option temp_data_in_shared_temp"

Constant LS_POLICY_OPTION_VALUE_DIFFERENT

SAP Sybase Error Num- 3272

ber

SQL State WQ029

SQL Code -1630L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 multiplex servername.

Probable Cause A server is not allowed to have different values for temp_da-
ta_in_shared_temp ls policy option

1631 - 1000150

Messages 1631 through 1650

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1631 "Use of table privilege '%1' is not supported on the current
database"

Constant TABPRIV_LOAD_TRUNCATE_UNSUPPORTED

SAP Sybase Error Num- 3273

ber

SQL State 0A007

SQL Code -1631L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Parameter 1 The table privilege, load or truncate.

SAP Sybase IQ Error Messages 531

Errors and Warnings

Error 1631 "Use of table privilege '%1' is not supported on the current
database"

Probable Cause The current database is an older database and does not have the capa-
bility to support table privileges load or truncate. You must upgrade your
database to use these table privileges.

Error 1632 "Dropping or altering arbiter \"%1\" requires a connection

to the partner."

Constant MIRROR_DROP_ARBITER_REQUIRES_PARTNER_CONN

SAP Sybase Error Number 3274

SQL State WW242

SQL Code -1632L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the arbiter server.

Probable Cause An attempt was made to drop or alter an arbiter that is not connected to
the partner server.

Error 1633 "Trace event '%1' is not valid"

Constant INVALID_TRACE_EVENT_NAME

SAP Sybase Error Number 3275

SQL State WE019

Constant TRACE_EVENT_IS_IN_USE

SAP Sybase Error Number 3278

SQL State WE022

SQL Code -1636L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 533

Errors and Warnings

Error 1636 "Trace event '%1' is referenced by one or more sessions.

Drop referencing sessions first."

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event name.

Probable Cause The specified trace event name is used and cannot be dropped before
dropping referencing sessions.

Error 1637 "Trace event session '%1' is active. Stop active session
before dropping the session."

Constant TRACE_EVENT_SESSION_IS_ACTIVE

SAP Sybase Error Number 3279

SQL State WE023

SQL Code -1637L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Probable Cause The specified trace event session is active. The session must be not be
active in order to be dropped.

Error 1638 "Too many arguments for trace event '%1'."

Constant TOO_MANY_PARAMETERS_FOR_TRACE_EVENT

SAP Sybase Error Number 3280

SQL State WE024

SQL Code -1638L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event name.

534 SAP Sybase IQ

Errors and Warnings

Error 1638 "Too many arguments for trace event '%1'."

Probable Cause Too many arguments were provided for the trace event specified.

Error 1639 "Database alter failed: %1"

Constant DATABASE_NOT_ALTERED

SAP Sybase Error Number 3281

SQL State 08WB8

SQL Code -1639L

ODBC 2 State 08004

ODBC 3 State 08004

Severity Code 14 on page 2

Parameter 1 Reason that the database was not altered.

Probable Cause Your attempt to alter a database failed.

Error 1640 "Too many active trace event sessions."

Constant TOO_MANY_ACTIVE_TRACE_SESSIONS

SAP Sybase Error Number 3282

SQL State WE025

SQL Code -1640L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Probable Cause Too many active trace sessions.

Error 1641 "Trace event session '%1' already active."

Constant TRACE_SESSION_ALREADY_ACTIVE

SAP Sybase Error Number 3283

SQL State WE026

SQL Code -1641L

SAP Sybase IQ Error Messages 535

Errors and Warnings

Constant TRACE_SESSION_ALREADY_STOPPED

SAP Sybase Error Number 3286

SQL State WE029

SQL Code -1644L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Probable Cause The specified trace event session is already stopped.

Error 1645 "Trace event session '%1' already has trace event '%2'."

Constant TRACE_SESSION_ALREADY_HAS_EVENT

SAP Sybase Error Number 3287

SQL State WE030

SQL Code -1645L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Parameter 2 The trace event name.

Probable Cause The specified trace event session already has the specified event.

Error 1646 "The specified target type '%1' is not valid"

Constant INVALID_TRACE_EVENT_TARGET_TYPE

SAP Sybase Error Number 3288

SAP Sybase IQ Error Messages 537

Errors and Warnings

Error 1646 "The specified target type '%1' is not valid"

SQL State WE031

SQL Code -1646L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event target type.

Probable Cause The specified trace event target type is not valid.

Error 1647 "Unknown option '%1' specified for target type '%2'."

Constant UNKNOWN_OPTION_FOR_TARGET_TYPE

SAP Sybase Error Number 3289

SQL State WE032

SQL Code -1647L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The option name.

Parameter 2 The trace event target type.

Probable Cause An unknown option name was specified for given target type.

Error 1648 "The option '%1' was not specified for target type '%2'."

Constant OPTION_FOR_TARGET_TYPE_NOT_SPECIFIED

SAP Sybase Error Number 3290

SQL State WE033

SQL Code -1648L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

538 SAP Sybase IQ

Errors and Warnings

Error 1648 "The option '%1' was not specified for target type '%2'."

Parameter 1 The option name.

Parameter 2 The trace event target type.

Probable Cause A required option for target type was not specified.

Error 1649 "Trace event session '%1' already has target type '%2'."

Constant TRACE_SESSION_ALREADY_HAS_TARGET_TYPE

SAP Sybase Error Number 3291

SQL State WE034

SQL Code -1649L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Parameter 2 The trace event target type.

Probable Cause The specified trace event session already has the specified target type.

Error 1650 "Trace event session '%1' does not have trace event '%2'."

Constant TRACE_SESSION_DOES_NOT_HAVE_TRACE_EVENT

SAP Sybase Error Num- 3292

ber

SQL State WE035

SQL Code -1650L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Parameter 2 The trace event name.

Probable Cause The trace event session does not the specified trace event.

SAP Sybase IQ Error Messages 539

Errors and Warnings

Messages 1651 through 1670

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1651 "Trace event session '%1' does not have trace event '%2'."

Constant TRACE_SESSION_DOES_NOT_HAVE_TARGET_TYPE

SAP Sybase Error Number 3293

SQL State WE036

SQL Code -1651L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Parameter 2 The trace event target type.

Probable Cause The trace event session does not the specified trace target type.

Error 1652 "Trace event session '%1' already exists."

Constant TRACE_SESSION_ALREADY_EXISTS

SAP Sybase Error Number 3294

SQL State WE037

SQL Code -1652L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace event session name.

Probable Cause A trace event session with that name already exists.

Error 1653 "RLV dbspace already exists. Cannot create more than one
RLV dbspace."

Constant RLV_DBSPACE_CREATION_NOT_ALLOWED

SAP Sybase IQ Error Messages 541

Errors and Warnings

Error 1655 "Invalid value for login policy option \"%1\No message

Severity Code 16 on page 2

Parameter 1 The name of login policy option.

Probable Cause The value supplied for login policy option is not within valid bounds.

Error 1656 "Database upgrade not possible; the name of a new

SYSTEM logical server is already in use."

Constant IQ_LOGICAL_SERVER_CONFLICT

SAP Sybase Error Number 3298

SQL State WQ032

SQL Code -1656L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt to upgrade a database failed. Retry upgrade of the database
when no existing logical server is using the name of the documented
system logical servers.

Error 1657 "Database upgrade not possible; Join Index in use."

Constant IQ_JOININDEX_PRESENT

SAP Sybase Error Number 3299

SQL State WQ033

SQL Code -1657L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt to upgrade a database failed. Retry upgrade of the data-
base when join indexes have been dropped from the database.

542 SAP Sybase IQ

Errors and Warnings

Error 1658 "To '%1' column '%2' Table '%3' must be partitioned by
'%4'"

Constant COLUMN_PARTITIONED_INCORRECTLY

SAP Sybase Error Number 3300

SQL State WW244

SQL Code -1658L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Partition type

Parameter 2 The column name

Parameter 3 The table name

Parameter 4 Partition type

Probable Cause The partitioning of this column must be consistent wit the table par-
titioning

Error 1659 "File or directory %1 not found"

Constant FILE_NOT_FOUND

SAP Sybase Error Number 3301

SQL State 08WB9

SQL Code -1659L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 The file or directory name that does not exist or fail to access

Probable Cause You attempted to perform an operation using a file or directory name
that does not exist or fail to access.

Error 1660 "Fail to compare %1 and %2"

Constant FILE_COMPARE_FAIL

SAP Sybase IQ Error Messages 543

Errors and Warnings

Error 1660 "Fail to compare %1 and %2"

SAP Sybase Error Number 3302

SQL State 08WC1

SQL Code -1660L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 The source file or directory name that fail to compare

Parameter 2 The target file or directory name that fail to compare

Probable Cause Fail to compare files or directories

Error 1661 "%1 is not a directory"

Constant NOT_A_DIRECTORY

SAP Sybase Error Number 3303

SQL State 08WC2

SQL Code -1661L

ODBC 2 State 08001

ODBC 3 State 08001

Severity Code 16 on page 2

Parameter 1 The path name that is not a directory

Probable Cause Fail to perform an operation using directory name

Error 1662 "%1 and %2 must not be the same"

Constant SAME_SOURCE_TARGET

SAP Sybase Error Number 3304

SQL State 08WC3

SQL Code -1662L

ODBC 2 State 08001

ODBC 3 State 08001

544 SAP Sybase IQ

Errors and Warnings

Error 1662 "%1 and %2 must not be the same"

Severity Code 16 on page 2

Parameter 1 The source file or directory name

Parameter 2 The target file or directory name

Probable Cause You attempted to perform an operation using the same source and
target file or directory

Error 1663 "Prevented removal of LDAP server because it is referenced by

Constant ONLY_LDAP_POLICY

SAP Sybase Error 3305

Number

SQL State WW245

SQL Code -1663L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the login policy.

Probable Cause The setting for server-wide login_mode option is LDAPUA so to avoid
locking out users from connecting, prevent the only login policy supporting
LDAPUA reference removal. Change login_mode before proceeding to
DROP LDAP SERVER <server name> WITH DROP ALL REFEREN-
CES.

Error 1664 "Prevented removal of LDAP server \"%1\" because it is the

only LDAP server and the value of login_mode is \"LDAPUA
\"."

Constant ONLY_LDAP_SERVER

SAP Sybase Error Num- 3306

ber

SQL State WW246

SQL Code -1664L

SAP Sybase IQ Error Messages 545

Errors and Warnings

Error 1664 "Prevented removal of LDAP server \"%1\" because it is the

only LDAP server and the value of login_mode is \"LDAPUA
\"."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the LDAP server.

Probable Cause The setting for server-wide login_mode option is LDAPUA so to avoid
locking out users from connecting, prevent the removal of the only
LDAP server. Change login_mode before proceeding to DROP LDAP
SERVER <server name>.

Error 1665 "Cannot change password because

change_password_dual_control process is in progress"

Constant CHANGE_PWD_DUAL_CONTROL_INPROGRESS

SAP Sybase Error Num- 3307

ber

SQL State 28W20

SQL Code -1665L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to change password while changing password by

change_password_dual_control option is in progress.

Error 1666 "Expression is not an array"

Constant NOT_AN_ARRAY

SAP Sybase Error Number 3308

SQL State 42X07

SQL Code -1666L

ODBC 2 State ERROR

ODBC 3 State ERROR

546 SAP Sybase IQ

Errors and Warnings

Error 1666 "Expression is not an array"

Severity Code 16 on page 2

Probable Cause You either tried to apply an ARRAY dereference (using double square
brackets) to an expression that does not evaluate to an array, or else
you tried to pass a non-ARRAY expression to UNNEST.

Error 1667 "The option '%1' cannot be set in user-defined logical

server policies."

Constant LSP_OPTION_OVERRIDE_NOT_ALLOWED

SAP Sybase Error Number 3309

SQL State WQ034

SQL Code -1667L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Error 1671 "The file '%1' is invalid when the disk sandbox feature is
enabled for database '%2'"

Constant DISKSANDBOX_INVALID_PATH

548 SAP Sybase IQ

Errors and Warnings

Error 1671 "The file '%1' is invalid when the disk sandbox feature is
enabled for database '%2'"

SAP Sybase Error Number 3313

SQL State 57W06

SQL Code -1671L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the invalid file.

Parameter 2 The name of the database that the disk sandbox feature is enabled for.

Probable Cause The file passed to the operation is invalid when the sandbox feature is
enabled.

Error 1672 "A disk sandbox error occurred for database '%1' when
determining the disk sandbox status for file '%2' "

Constant DISKSANDBOX_UNABLE_TO_DETERMINE

SAP Sybase Error Number 3314

SQL State 57W07

SQL Code -1672L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the database that could not determine the disk sandbox
status of the file.

Parameter 2 The name of the invalid file.

Probable Cause The file passed to the operation caused an error when determining the
disk sandbox status.

Error 1673 "A disk sandbox error occurred for database '%1' when
finding the full path for file '%1'"

Constant DISKSANDBOX_FULLPATH_ERROR

SAP Sybase IQ Error Messages 549

Errors and Warnings

Error 1673 "A disk sandbox error occurred for database '%1' when
finding the full path for file '%1'"

SAP Sybase Error Number 3315

SQL State 57W08

SQL Code -1673L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the database that could not find the full path of the file.

Parameter 2 The name of the invalid file.

Probable Cause There was an error in finding the full path of the file that was passed to
the operation.

Error 1674 "Error at offset '%1': unexpected token '%2'"

Constant PARSE_JSON_UNEXPECTED_TOKEN

SAP Sybase Error Number 3316

SQL State WX018

SQL Code -1674L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The offset where the error occurred.

Parameter 2 The unexpected token.

Probable Cause An unexpected token such as a comma, bracket, or brace was en-
countered.

Error 1675 "Error at offset '%1': unexpected trailing text"

Constant PARSE_JSON_UNEXPECTED_TEXT

SAP Sybase Error Number 3317

SQL State WX019

550 SAP Sybase IQ

Errors and Warnings

Probable Cause The expected token was missing in the JSON data.

Error 1678 "Error at offset '%1': expected JSON name/value pair"

Constant PARSE_JSON_EXPECTED_PAIR

SAP Sybase Error Number 3320

SQL State WX022

SQL Code -1678L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The offset where the error occurred.

Probable Cause A name/value pair was expected within the JSON object.

Error 1679 "Error at offset '%1': mismatched object or array

terminator"

Constant PARSE_JSON_MISMATCH_TERMINATOR

SAP Sybase Error Number 3321

SQL State WX023

SQL Code -1679L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The offset where the error occurred.

Probable Cause Encountered a mismatched terminator for a JSON object or array.

Error 1680 "Invalid variable or type"

Constant PARSE_JSON_INVALID_VARIABLE_TYPE

SAP Sybase Error Number 3322

SQL State WX024

552 SAP Sybase IQ

Errors and Warnings

Error 1680 "Invalid variable or type"

SQL Code -1680L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause The named variable is invalid or the wrong data type for the JSON
result.

Error 1681 "Procedure is currently being altered or dropped"

Constant PROCEDURE_IN_USE_DDL

SAP Sybase Error Number 3323

SQL State 42WF0

SQL Code -1681L

ODBC 2 State 40001

ODBC 3 State 40001

Severity Code 16 on page 2

Probable Cause You have attempted to use a procedure that is currently being altered
or dropped.

Error 1682 "The RLV dbspace '%1' cannot be made read only because it
contains RLV enabled tables"

Constant RLV_DBSPACE_CONTAINS_TABLES

SAP Sybase Error Num- 3324

ber

SQL State WQ038

SQL Code -1682L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the dbspace

SAP Sybase IQ Error Messages 553

Errors and Warnings

Error 1682 "The RLV dbspace '%1' cannot be made read only because it
contains RLV enabled tables"

Probable Cause You attempted to make the named RLV dbspace read only, but it con-
tains RLV enabled tables. You must drop or disable the tables before
making the dbspace read only.

Error 1683 "Cannot change the mirror server type from %1 to %2"

Constant CANNOT_CHANGE_MIRROR_SERVER_TYPE

SAP Sybase Error Num- 3325

ber

SQL State 42WF2

SQL Code -1683L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The original mirror server type

Parameter 2 The proposed new mirror server type

Probable Cause You attempted to use the CREATE OR REPLACE MIRROR SERVER
or ALTER MIRROR SERVER statement to change the mirror server
type, but the proposed change is not supported.

Error 1684 "Trace target option '%1' conflicts with already used option
'%2'."

Constant TARGET_OPTIONS_CONFLICT

SAP Sybase Error Number 3326

SQL State WE038

SQL Code -1684L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The trace target option name.

554 SAP Sybase IQ

Errors and Warnings

Error 1684 "Trace target option '%1' conflicts with already used option
'%2'."

Parameter 2 The trace target option name.

Probable Cause A trace target option conflict with another target option used.

Error 1685 "There was insufficient memory to complete the %1

operation"

Constant SFC_MEM_ERROR

SAP Sybase Error Number 3327

SQL State 08S01

SQL Code -1685L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 17 on page 2

Parameter 1 The name of the procedure that detected the error.

Probable Cause A call to a the specified procedure could not complete the operation
due to insufficient memory.

Error 1686 "Invalid parameter was used in the call to %1"

Constant SFC_INVALID_PARM

SAP Sybase Error Number 3328

SQL State 08S02

SQL Code -1686L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the procedure.

Probable Cause An invalid parameter value was passed to the specified procedure.

SAP Sybase IQ Error Messages 555

Errors and Warnings

Error 1687 "The secure feature key name '%2' is not valid in the call to
%1"

Constant SFC_INVALID_NAME

SAP Sybase Error Number 3329

SQL State 08S03

SQL Code -1687L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the procedure.

Parameter 2 The secure feature key name.

Probable Cause An invalid secure feature key name was passed to the specified pro-
cedure.

Error 1688 "An invalid authorization key was specified in the call to
%1"

Constant SFC_INVALID_KEY

SAP Sybase Error Number 3330

SQL State 08S04

SQL Code -1688L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the procedure.

Probable Cause An invalid secure feature key value was passed to the specified pro-
cedure.

Error 1689 "An invalid secure feature list '%2' was specified in the call
to %1"

Constant SFC_INVALID_FEAT

SAP Sybase Error Number 3331

556 SAP Sybase IQ

Errors and Warnings

Error 1689 "An invalid secure feature list '%2' was specified in the call
to %1"

SQL State 08S05

SQL Code -1689L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 15 on page 2

Parameter 1 The name of the procedure.

Parameter 2 The secure feature list.

Probable Cause An invalid list of secure features was passed to the specified proce-
dure.

Error 1690 "You are not authorized to assign the feature list '%2' to a
secure feature key using %1"

Constant SFC_NO_AUTH_FOR_FEAT

SAP Sybase Error Num- 3332

ber

SQL State 08S06

SQL Code -1690L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The name of the procedure.

Parameter 2 The secure feature list.

Probable Cause An attempt was made to define a secure feature key to use a secure
feature that the user is not authorized to use or assign.

SAP Sybase IQ Error Messages 557

Errors and Warnings

Messages 1691 through 1000002

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1691 "You are not authorized to change the secure feature key
named '%2' using %1"

Constant SFC_NO_AUTH_FOR_KEY

SAP Sybase Error Number 3333

SQL State 08S07

SQL Code -1691L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The name of the procedure.

Parameter 2 The secure feature key name.

Probable Cause The user is not authorized to change the named secure feature key.

Error 1692 "Call to %1 failed - the maximum number of secure feature

keys has already been created"

Constant SFC_HIT_MAX_LIMIT

SAP Sybase Error Number 3334

SAP Sybase IQ Error Messages 559

Errors and Warnings

Error 1695 "Call to %1 failed - the authorization key specified for the
secure feature key named '%2' is incorrect"

SAP Sybase Error Number 3337

SQL State 08S11

SQL Code -1695L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The name of the procedure.

Parameter 2 The secure feature key name.

Probable Cause The provided authorization key did not match the value stored for the
specified named key.

Error 1696 "Call to %1 failed - the key named '%2' is the last key with
the MANAGE_FEATURES and MANAGE_KEYS features"

Constant SFC_CANNOT_REMOVE_LAST

SAP Sybase Error Number 3338

SQL State 08S12

SQL Code -1696L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The name of the procedure.

Parameter 2 The secure feature key name.

Probable Cause The call attempted to remove the last secure feature key that would
enable both MANAGE_FEATURES and MANAGE_KEYS and this
is not allowed.

Error 1697 "Database upgrade not possible; LD Index in use."

Constant IQ_LDINDEX_PRESENT

SAP Sybase Error Number 3339

560 SAP Sybase IQ

Errors and Warnings

Error 1697 "Database upgrade not possible; LD Index in use."

SQL State WQ039

SQL Code -1697L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause An attempt to upgrade a database failed. Retry upgrade of the data-
base when LD indexes have been dropped from the database.

Error 1698 "change_password_dual_control is enabled for this user. Use

ALTER USER to change password."

Constant CHANGE_PWD_DUAL_CONTROL_ENABLED

SAP Sybase Error 3340

Number

SQL State 28W21

SQL Code -1698L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to change a password while the change_password_dual_con-

trol option is set for this user. When this option is set, you must use the
ALTER USER statement to change the dual password.

Error 1699 "Cannot convert database to multiplex. An RLV dbspace

exists."

Constant MPX_CONVERSION_NOT_ALLOWED_WITH_RLV_STORE

SAP Sybase Error Number 3341

SQL State WQ040

SQL Code -1699L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 561

Errors and Warnings

Error 1699 "Cannot convert database to multiplex. An RLV dbspace

exists."

Severity Code 16 on page 2

Probable Cause A simplex database with RLV dbspace cannot be converted to a mul-
tiplex database.

Error 1700 "TDS login requests with unencrypted passwords are not
permitted"

Constant UNENCRYPTED_TDS_LOGIN_REQUESTS_NOT_PERMITTED

SAP Sybase Error 3342

Number

SQL State 28W22

SQL Code -1700L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

Probable Cause You attempted to perform a TDS login without using RSA encryption for
the password. The current TDS login setting does not allow unencrypted
TDS login requests. Change the tdsl server option setting or connect using
an RSA encrypted password.

Error 1701 "TDS login requests with RSA encrypted passwords must also use
a nonce"

Constant RSA_ENCRYPTED_TDS_LOGIN_MUST_HAVE_NONCE

SAP Sybase Error 3343

Number

SQL State 28W23

SQL Code -1701L

ODBC 2 State 28000

ODBC 3 State 28000

Severity Code 16 on page 2

562 SAP Sybase IQ

Errors and Warnings

Error 1701 "TDS login requests with RSA encrypted passwords must also use
a nonce"

Probable Cause You attempted to perform a TDS login with a client that does not use a nonce
with the RSA encrypted password. The current TDS login setting does not
allow RSA encrypted TDS login requests without a nonce. Change the tdsl
server option setting or connect using a TDS client that supports a nonce with
the RSA encrypted password.

Error 1702 "Collection types not supported"

Constant COLLECTION_TYPES_NOT_SUPPORTED

SAP Sybase Error Num- 3344

ber

SQL State 0AW28

SQL Code -1702L

ODBC 2 State 37000

ODBC 3 State 42000

Severity Code 15 on page 2

Probable Cause The current database is an older database and does not have support for
row or array types. To use this feature, upgrade your database to the
most recent version.

Error 1703 "The user name specified must be the user name of the
current connection"

Constant CREATE_SCHEMA_USER_DOES_NOT_MATCH

SAP Sybase Error 3345

Number

SQL State 42WD5

SQL Code -1703L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause In the CREATE SCHEMA AUTHORIZATION clause, you specified a

user name other than the user name of the current connection.

SAP Sybase IQ Error Messages 563

Errors and Warnings

Error 1704 "Remote column %1 has been specified with the wrong
case"

Constant OMNI_RMT_COLUMN_WRONG_CASE

SAP Sybase Error Number 3346

SQL State WO035

SQL Code -1704L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 11 on page 2

Parameter 1 The complete name of the remote column.

Probable Cause The remote server requires that columns be specified in the correct
case.

Error 1705 "Illegal RLV Merge Type '%1'"

Constant RLV_ILLEGAL_MERGE_TYPE

SAP Sybase Error Number 3347

SQL State WQ041

SQL Code -1705L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 The illegal merge string

Probable Cause Legal RLV Merge Types: BLOCKING, NONBLOCKING

Error 1706 "The use of foreign keys in a RLV table is not supported"

Constant RLV_FOREIGNKEY_UNSUPPORTED

SAP Sybase Error Number 3348

SQL State WQ043

SQL Code -1706L

564 SAP Sybase IQ

Errors and Warnings

Error 1706 "The use of foreign keys in a RLV table is not supported"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Probable Cause You attempted to use a foriegn key within a RLV table which is
unsupported

Error 1707 "The datatype '%1' cannot be used with RLV enabled"

Constant RLV_UNSUPPORTED_DATATYPE

SAP Sybase Error Number 3349

SQL State WQ042

SQL Code -1707L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the unsupported datatype

Probable Cause You attempted to use an datatype that is not supported in combination
with RLV.

Error 1708 "The option '%1' cannot be used with RLV enabled"

Constant RLV_UNSUPPORTED_OPTION

SAP Sybase Error Number 3350

SQL State WQ044

SQL Code -1708L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 16 on page 2

Parameter 1 Name of the unsupported option

Probable Cause You attempted to use an option that is not supported in combination
with RLV.

SAP Sybase IQ Error Messages 565

Errors and Warnings

Error 1000000 "ESCAPES option must be OFF. %1"

Constant EMSG_INVALIDQUOTESESCAPES

SAP Sybase Error Number 20660

SQL State QDA00

SQL Code -1000000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Sybase IQ only supports 'LOAD TABLE' commands where the ES-
CAPES options must be OFF.

Error 1000002 "Cannot get the index id for %2 from the catalog. %1"

Constant EMSG_CAT_CANTGETINDEXID

SAP Sybase Error Number 20662

SQL State QDA02

SQL Code -1000002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 index id

Probable Cause This is an internal error. Join processing is not able to find an index in
the catalog. If this error occurs, it should be reported to Sybase.

Messages 1000003 through 1000036

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000003 "Cross-database joins are not supported. (%2 and %3) %1"

Constant EMSG_CAT_CROSSDBJOIN

566 SAP Sybase IQ

Errors and Warnings

Error 1000003 "Cross-database joins are not supported. (%2 and %3) %1"

SAP Sybase Error Number 20663

SQL State QDA03

SQL Code -1000003L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Fully qualified name of table specified in join.

Parameter 3 Fully qualified name of table specified in join.

Probable Cause Cannot join tables from different databases.

Error 1000004 "Index '%2' already exists in the catalog. %1"

Constant EMSG_CAT_DUPINDEXID

SAP Sybase Error Number 20664

SQL State QDA04

SQL Code -1000004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Name of index that already exists.

Probable Cause This is an internal error. Join processing is trying to create an index id
that already exists. If this error occurs, it should be reported to Sybase.

Error 1000006 "Only %2 NULL specifications on a column are permitted.

%1"

Constant EMSG_TOO_MANY_NULL_STRINGS

SAP Sybase Error Num- 20666

ber

SAP Sybase IQ Error Messages 567

Errors and Warnings

Error 1000006 "Only %2 NULL specifications on a column are permitted.

%1"

SQL State QDA06

SQL Code -1000006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 maximum NULL specifications permitted

Probable Cause A column specification in a LOAD statement can have a maximum

number of NULL clauses.

Error 1000008 "Unknown error. %1"

Constant EMSG_CAT_UNKNOWN

SAP Sybase Error Number 20668

SQL State QDA08

SQL Code -1000008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause An error condition was encountered for which there is no message. If
this error occurs, it should be reported to Sybase.

Error 1000009 "Cannot DISABLE index '%2'. It is open Read/Write and

may have updates pending. %1"

Constant EMSG_CAT_INDEXENABLERW

SAP Sybase Error Number 20669

SQL State QDA09

SQL Code -1000009L

568 SAP Sybase IQ

Errors and Warnings

Error 1000009 "Cannot DISABLE index '%2'. It is open Read/Write and

may have updates pending. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of the index user is attempting to disable.

Parameter 2 The index the user is attempting to disable.

Probable Cause This index cannot be DISABLED. It is open for write access and may
have updates pending. Wait until no other users are using the index.

Error 1000010 "Cannot DISABLE index '%2'. The index is in use. %1"

Constant EMSG_CAT_INDEXENABLESINDEX

SAP Sybase Error Number 20670

SQL State QDA10

SQL Code -1000010L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Name of the index user is attempting to disable.

Probable Cause This index cannot be DISABLED. It is in use. Wait until no other
users are using the index.

Error 1000011 "Transaction %2 attempted to access '%4' created by

transaction %3. %1"

Constant EMSG_CAT_FUTUREVERSION

SAP Sybase Error Number 20671

SQL State QDA11

SQL Code -1000011L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 569

Errors and Warnings

Error 1000011 "Transaction %2 attempted to access '%4' created by

transaction %3. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The current transaction ID.

Parameter 3 The transaction ID that created the object the user is attempting to
access.

Parameter 4 table name

Probable Cause Table Level Versioning doesn't allow access to versions newer than
your current transaction ID.

Error 1000012 "Index '%2' cannot be closed because it has %3 users. %1"

Constant EMSG_CAT_INDEXINUSE

SAP Sybase Error Number 20672

SQL State QDA12

SQL Code -1000012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Name of the index that is being closed.

Parameter 3 The number of users currently using the index.

Probable Cause This is an internal error. The index cannot be closed because it is in
use. If this error occurs, it should be reported to Sybase.

Error 1000014 "%2 MB is not sufficient for the load, update, or delete. %1"

Constant EMSG_INSUFFICIENT_LOAD_MEMORY

SAP Sybase Error 20674

Number

SQL State QDA14

570 SAP Sybase IQ

Errors and Warnings

Error 1000014 "%2 MB is not sufficient for the load, update, or delete. %1"

SQL Code -1000014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 user specified upper bound on megabytes of heap memory load/delete/up-

date can actually use

Probable Cause The user can control the amount of heap memory a load/delete/update
process (LOAD, INSERT VALUE, DELETE, SYNCHRONIZE, UPDATE)
can use via the Load_Memory_MB option. If this memory limit isn't suf-
ficient for the load/delete/update to run, then this exception is raised. To
proceed, the user must either turnoff the limit (i.e., set Load_Memory_MB
to zero) or increase the limit.

Error 1000018 "The object cannot be opened for DROP or ALTER. It is already
open. %1"

Constant EMSG_CAT_CANNOTOPENFORMETA

SAP Sybase Error 20678

Number

SQL State QDA18

SQL Code -1000018L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The object that you have requested to DROP or ALTER cannot be opened
for META access. Either the current connection or another connection has a
cursor open on the table you are trying to DROP or ALTER or on the table to
which the field or index you are trying open for META belongs. In order to
proceed, all cursors open on this object must be closed.

SAP Sybase IQ Error Messages 571

Errors and Warnings

Error 1000022 "Index '%2' has an invalid index type: %3. %1"

Constant EMSG_CAT_INDEXBADTYPE

SAP Sybase Error Number 20682

SQL State QDA22

SQL Code -1000022L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The index which has a bad type.

Parameter 3 The bad index type in question.

Probable Cause This is an internal error. The index is of a type that is unknown to
ASIQ. If this error occurs, it should be reported to Sybase.

Error 1000024 "For table pair %2, table '%3' has a datatype mismatch for
column %4. %1"

Constant EMSG_CAT_JINDEXDATATYPE

SAP Sybase Error Number 20684

SQL State QDA24

SQL Code -1000024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 table number

Parameter 4 column number

572 SAP Sybase IQ

Errors and Warnings

Error 1000024 "For table pair %2, table '%3' has a datatype mismatch for
column %4. %1"

Probable Cause Corresponding columns' in the table pairs must be of the same data-
type. (For example, INTEGER and INTEGER or CHAR and CHAR.)
Matching datatypes such as CHAR and VARCHAR or INT and
SMALLINT are not allowed.

Error 1000026 "The join virtual table for table '%2' has duplicate columns
in positions %3 and %4. %1"

Constant EMSG_CAT_JINDEXDUPFIELDS

SAP Sybase Error Number 20686

SQL State QDA26

SQL Code -1000026L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 column position

Parameter 4 column position

Probable Cause The join virtual table for table has duplicate columns. Perhaps the join
predicate is improperly specified.

Error 1000028 "For table pair %2, table '%3' has a length value mismatch
for column %4. %1"

Constant EMSG_CAT_JINDEXKEYSIZE

SAP Sybase Error Number 20688

SQL State QDA28

SQL Code -1000028L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 573

Errors and Warnings

Error 1000028 "For table pair %2, table '%3' has a length value mismatch
for column %4. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table pair

Parameter 3 table name

Parameter 4 column number

Probable Cause Corresponding columns in the table pair must be of the same length.

Error 1000029 "Cannot open the requested object for write in the current
transaction (%2). Another user has write access in
transaction %3. %1"

Constant EMSG_CAT_ONLY1WRITER

SAP Sybase Error Num- 20689

ber

SQL State QDA29

SQL Code -1000029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The transaction id of the hopeful writer.

Parameter 3 The transaction id of the user currently writing.

Probable Cause The ASIQ catalog allows only one transaction at a time to have write
access to an object. The id of the user that is currently writing to the
object can be found by running sp_iqtransaction and scanning the output
for the transaction id of the writer that currently has write access.

Warning 1000030 "\nMaster archive header information\n"

Constant EMSG__DB_HEADER_MSG1

SAP Sybase Error Number 20690

574 SAP Sybase IQ

Errors and Warnings

Warning 1000030 "\nMaster archive header information\n"

SQL State QDA30

SQL Code 1000030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000032 "The ultimate/top table is %1\n"

Constant EMSG_CAT_JINDEXLOADMSGLINKTABLE1

SAP Sybase Error Number 20692

SQL State 00A32

SQL Code 1000032L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 table name

Probable Cause This information message appears in the log when the CREATE JOIN
command is executed.

Warning 1000033 "Database: %1"

Constant EMSG_DB_HEADER_MSG2

SAP Sybase Error Number 20693

SQL State QDA33

SQL Code 1000033L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

SAP Sybase IQ Error Messages 575

Errors and Warnings

Warning 1000033 "Database: %1"

Parameter 1 Database

Probable Cause This message is displayed in context with other messages.

Warning 1000034 " Table Name Relationship"

Constant EMSG_CAT_JINDEXLOADMSGLINKTABLE3

SAP Sybase Error Number 20694

SQL State 00A34

SQL Code 1000034L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Probable Cause This information message appears in the log when the CREATE JOIN
command is executed.

Warning 1000036 "%1. %2 joined to '%3' %4"

Constant EMSG_CAT_JINDEXLOADMSGTABLE

SAP Sybase Error Number 20696

SQL State 00A36

SQL Code 1000036L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 argument 1 comment

Parameter 2 argument 2 comment

Parameter 3 argument 3 comment

Parameter 4 argument 4 comment

Probable Cause This information message appears in the log when the CREATE JOIN
command is executed.

576 SAP Sybase IQ

Errors and Warnings

Messages 1000037 through 1000056

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1000037 "------------------------------------------------------------------"

Constant EMSG_CAT_JINDEXLOADMSGTRAILER

SAP Sybase Error 20697

Number

SQL State 00A37

SQL Code 1000037L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Probable Cause This information message appears in the log when the CREATE JOIN
command is executed.

Warning 1000038 "Backup date: %1"

Constant EMSG_DB_HEADER_MSG3

SAP Sybase Error Number 20698

SQL State QDA38

SQL Code 1000038L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 backup date

Probable Cause This message displays the backup date.

Warning 1000039 "Backup created by: %1"

Constant EMSG_DB_HEADER_MSG4

SAP Sybase Error Number 20699

SAP Sybase IQ Error Messages 577

Errors and Warnings

Warning 1000039 "Backup created by: %1"

SQL State QDA39

SQL Code 1000039L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 user name

Probable Cause This message displays the user who created the backup.

Warning 1000040 "Comment: %1"

Constant EMSG_DB_HEADER_MSG5

SAP Sybase Error Number 20700

SQL State QDA40

SQL Code 1000040L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 comment

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000041 "Backup version: %1"

Constant EMSG_DB_HEADER_MSG6

SAP Sybase Error Number 20701

SQL State QDA41

SQL Code 1000041L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

578 SAP Sybase IQ

Errors and Warnings

Warning 1000041 "Backup version: %1"

Parameter 1 backup version

Probable Cause This message displays the backup version.

Warning 1000042 "Number of archive media in backup: %1"

Constant EMSG_DB_HEADER_MSG7

SAP Sybase Error Number 20702

SQL State QDA42

SQL Code 1000042L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 number of archive media in backup

Probable Cause This message displays how many media are in the backup.

Warning 1000043 "Number of files in backup: %1"

Constant EMSG_DB_HEADER_MSG8

SAP Sybase Error Number 20703

SQL State QDA43

SQL Code 1000043L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 number of files in backup

Probable Cause This message displays the number of files in the backup.

Error 1000044 "The join for table '%2' does not have enough columns
defined (%3). %1"

Constant EMSG_CAT_JINDEXNOFIELDS

SAP Sybase Error Number 20704

SAP Sybase IQ Error Messages 579

Errors and Warnings

Error 1000044 "The join for table '%2' does not have enough columns
defined (%3). %1"

SQL State QDA44

SQL Code -1000044L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Parameter 3 number of columns

Probable Cause Cannot define a join with zero columns. If this error occurs, it should
be reported to Sybase.

Error 1000045 "Index %2 does not exist. %1"

Constant EMSG_UTILITY_INDEXNOTFOUND

SAP Sybase Error Number 20705

SQL State QDA45

SQL Code -1000045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 index name given by the user

Probable Cause User has specified an index which does not exist in any table within
the current database.

Error 1000046 "No Field passed to PutMCIField. %1"

Constant EMSG_CAT_NOFIELDPUTMCI

SAP Sybase Error Number 20706

SQL State QDA46

580 SAP Sybase IQ

Errors and Warnings

Error 1000046 "No Field passed to PutMCIField. %1"

SQL Code -1000046L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause This error should not occur during normal operation and should be
reported to Sybase. See the iqmsg file for additional diagnostic in-
formation.

Error 1000047 "For table pair %2, table '%3' has a precision mismatch in
column %4. %1"

Constant EMSG_CAT_JINDEXPRECISION

SAP Sybase Error Number 20707

SQL State QDA47

SQL Code -1000047L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table pair

Parameter 3 table name

Parameter 4 column number

Probable Cause Corresponding columns in the join must have equal precision.

Error 1000048 "For table pair %2, table '%3' has a scale mismatch in
column %4. %1"

Constant EMSG_CAT_JINDEXSCALE

SAP Sybase Error Number 20708

SQL State QDA48

SAP Sybase IQ Error Messages 581

Errors and Warnings

Error 1000048 "For table pair %2, table '%3' has a scale mismatch in
column %4. %1"

SQL Code -1000048L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table pair

Parameter 3 table name

Parameter 4 column number

Probable Cause Corresponding columns in the join must have equal scale.

Error 1000049 "'%2' is being used in a self join. Self joins are not allowed.
%1"

Constant EMSG_CAT_JINDEXSELFJOIN

SAP Sybase Error Number 20709

SQL State QDA49

SQL Code -1000049L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause Self joins are not allowed.

Error 1000050 "Table '%2' is used in the join twice. %1"

Constant EMSG_CAT_JINDEXTABLETWICE

SAP Sybase Error Number 20710

SQL State QDA50

582 SAP Sybase IQ

Errors and Warnings

Error 1000050 "Table '%2' is used in the join twice. %1"

SQL Code -1000050L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause A table cannot be used twice in a join.

Error 1000051 "Cannot retrieve a row from the SYSIQJOINIXTABLE

system table. %1"

Constant EMSG_CAT_JIXTABLEFIND

SAP Sybase Error Number 20711

SQL State QDA51

SQL Code -1000051L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. Cannot retrieve a row from the SYSIQJOI-
NIXTABLE system table. If this error occurs, it should be reported to
Sybase.

Error 1000052 "Cannot delete a row from the SYSIQJOINIXTABLE system

table. %1"

Constant EMSG_CAT_JIXTABLEDELETE

SAP Sybase Error Number 20712

SQL State QDA52

SQL Code -1000052L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 583

Errors and Warnings

Error 1000052 "Cannot delete a row from the SYSIQJOINIXTABLE system

table. %1"

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. Cannot delete a row from the SYSIQJOI-
NIXTABLE system table. If this error occurs, it should be reported to
Sybase.

Error 1000053 "Cannot commit changes to the SYSIQJOINIXTABLE

system table. %1"

Constant EMSG_CAT_JIXTABLEFLUSH

SAP Sybase Error Number 20713

SQL State QDA53

SQL Code -1000053L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. Cannot commit changes to the SYSIQJOI-
NIXTABLE system table. If this error occurs, it should be reported to
Sybase.

Error 1000054 "Cannot open %2 in Meta (exclusive) mode. Object is

already open. %1"

Constant EMSG_CAT_METAACCESS

SAP Sybase Error Number 20714

SQL State QDA54

SQL Code -1000054L

ODBC 2 State ERROR

ODBC 3 State ERROR

584 SAP Sybase IQ

Errors and Warnings

Error 1000054 "Cannot open %2 in Meta (exclusive) mode. Object is

already open. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 object name

Probable Cause The object cannot be opened for exclusive access; it is already open.

Warning 1000055 "Warning: %1"

Constant EMSG_CLBK_WARNING

SAP Sybase Error Number 20715

SQL State 01A55

SQL Code 1000055L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Probable Cause This message appears in context with other messages.

Error 1000056 "Cannot convert from datatype '%2' to '%3' for column '%4'.
%1"

Constant EMSG_CAT_NOCONVERSIONPOSSIBLE

SAP Sybase Error Number 20716

SQL State QDA56

SQL Code -1000056L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 datatype

SAP Sybase IQ Error Messages 585

Errors and Warnings

Error 1000056 "Cannot convert from datatype '%2' to '%3' for column '%4'.
%1"

Parameter 3 datatype

Parameter 4 column name

Probable Cause Implicit conversion for this column is not possible.

Messages 1000057 through 1000078

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000057 "Column '%2' has an unknown datatype: '%3'. %1"

Constant EMSG_CAT_NODATATYPE

SAP Sybase Error Number 20717

SQL State QDA57

SQL Code -1000057L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column number

Parameter 3 the unknown datatype

Probable Cause The column is of a datatype that is unknown to ASIQ. This is an

internal error. If this error occurs, it should be reported to Sybase.

Warning 1000058 "Platform: %1"

Constant EMSG_DB_HEADER_MSG9

SAP Sybase Error Number 20718

SQL State QDA58

SQL Code 1000058L

ODBC 2 State ERROR

ODBC 3 State ERROR

586 SAP Sybase IQ

Errors and Warnings

Warning 1000058 "Platform: %1"

Severity Code 1 on page 2

Parameter 1 platform

Probable Cause This is an informational message reporting the platform type.

Error 1000060 "Column '%2', PRECISION (%3) cannot be greater than %4.
%1"

Constant EMSG_CAT_PRECISIONTOOBIG

SAP Sybase Error Number 20720

SQL State QDA60

SQL Code -1000060L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column number

Parameter 3 requested precision

Parameter 4 maximum allowed precision

Probable Cause The precision requested by the user is larger than what is allowed for
the datatype.

Error 1000061 "Column %2, PRECISION (%3) cannot be less than 0. %1"

Constant EMSG_CAT_PRECISIONTOOSMALL

SAP Sybase Error Number 20721

SQL State QDA61

SQL Code -1000061L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 587

Errors and Warnings

Error 1000061 "Column %2, PRECISION (%3) cannot be less than 0. %1"

Parameter 1 location of the exception

Parameter 2 column name

Parameter 3 column precision

Probable Cause The precision specified by the user is less than zero.

Error 1000062 "Cannot add column '%3' with 'not null' constraint on table
%2 with data. %1"

Constant EMSG_TABLEHASDATA

SAP Sybase Error Number 20722

SQL State QDC35

SQL Code -1000062L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Parameter 3 column name

Probable Cause The user tried to ALTER ADD a NOT NULL column to a table that
has data. The newly added column would violate the NOT NULL
constraint as it would have null data.

Error 1000063 "Cannot enforce the NOT NULL constraint. Column %2 has
NULL data. %1"

Constant EMSG_COLUMNHASNULLDATA

SAP Sybase Error Number 20723

SQL State QDC34

SQL Code -1000063L

ODBC 2 State ERROR

ODBC 3 State ERROR

588 SAP Sybase IQ

Errors and Warnings

Error 1000063 "Cannot enforce the NOT NULL constraint. Column %2 has
NULL data. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause The user tried ALTER MODIFY column NOT NULL on a column
that used to allow nulls and has null data. The user has to first delete
the null rows before altering the column to enforce the NOT NULL
constraint.

Error 1000064 "Column %2 can not be altered because it participates in

join %3. %1"

Constant EMSG_CAT_JOINFIELDINPREJOIN

SAP Sybase Error Number 20724

SQL State QDA64

SQL Code -1000064L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the error

Parameter 2 columns

Parameter 3 join

Probable Cause A column/field that participates in a join cannot be altered. Joins on

this field must be deleted before an ALTER can be performed.

Error 1000065 "Table %2 must be owned by the creator of the join. %1"

Constant EMSG_CAT_TABLEOWNERDIFF

SAP Sybase Error Number 20725

SQL State QDA65

SQL Code -1000065L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 589

Errors and Warnings

Error 1000065 "Table %2 must be owned by the creator of the join. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the error

Parameter 2 tablename

Probable Cause This error message is given during CREATE JOIN when one of the
tables specified is not owned by the owner of the join. Joins can only
be created from tables of the same owner.

Error 1000066 "ALTER on the column would interfere with the natural join
to table %2 in join %3. %1"

Constant EMSG_CAT_JOINFIELDNATMAT

SAP Sybase Error Number 20726

SQL State QDA66

SQL Code -1000066L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the error

Parameter 2 tablename

Parameter 3 join

Probable Cause This message is displayed when using the ALTER command or add-
ing columns to a table that participates in a join.

Error 1000067 "Table '%2' is not defined in the catalog. %1"

Constant EMSG_CAT_TABLENOTINCAT

SAP Sybase Error Number 20727

SQL State QDA67

SQL Code -1000067L

ODBC 2 State ERROR

590 SAP Sybase IQ

Errors and Warnings

Error 1000067 "Table '%2' is not defined in the catalog. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. The table does not exist in the catalog. If this
error occurs, it should be reported to Sybase.

Warning 1000069 " %1; %2 blocks; %3"

Constant EMSG_DB_HEADER_MSG10

SAP Sybase Error Number 20729

SQL State QDA69

SQL Code 1000069L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 argument 1 comment

Parameter 2 argument 2 comment

Parameter 3 argument 3 comment

Probable Cause This message is an informational message displayed in context with

other messages.

Warning 1000070 "File listing:"

Constant EMSG_DB_HEADER_MSG11

SAP Sybase Error Number 20730

SQL State QDA70

Warning 1000073 " start: %1; size: %2"

Constant EMSG_DB_HEADER_MSG21

SAP Sybase Error Number 20733

SQL State QDA73

SQL Code 1000073L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Probable Cause This message is displayed in context with other messages.

Warning 1000074 "Offset %1 Length %2, %3%4%5"

Constant EMSG_PREVIEWFILLER

SAP Sybase Error Number 20734

SQL State QDA74

SQL Code 1000074L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Parameter 5 Parameter 5 description

Probable Cause This message is displayed in context with other messages.

Warning 1000075 "%1, %2%3%4"

Constant EMSG_PREVIEWFILLER1

SAP Sybase IQ Error Messages 593

Errors and Warnings

Warning 1000075 "%1, %2%3%4"

SAP Sybase Error Number 20735

SQL State QDA75

SQL Code 1000075L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Probable Cause This message is displayed in context with other messages.

Warning 1000076 "%1, %2%3%4"

Constant EMSG_PREVIEWFILLER2

SAP Sybase Error Number 20736

SQL State QDA76

Messages 1000079 through 1000103

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000079 "IQ SIZE of '%2' for database '%3' is not valid. %1"

Constant EMSG_HDB_INVALIDDATABASESIZE

SAP Sybase Error Number 20739

SQL State QDA79

SQL Code -1000079L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 requested IQ SIZE

Parameter 3 database name

Probable Cause The maximum IQ SIZE is 128GB.

Error 1000082 "The insert must contain all of the table %2 columns
because it participates in one or more joins. %1"

Constant EMSG_INSRT_MUSTBE_FULLWIDTH

SAP Sybase Error Num- 20742

ber

SQL State QDA82

SQL Code -1000082L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

596 SAP Sybase IQ

Errors and Warnings

Error 1000082 "The insert must contain all of the table %2 columns
because it participates in one or more joins. %1"

Probable Cause If a table participates in a join, then the user cannot load data into that
table using a partial width insert.

Error 1000083 "The field array entry must be given a name. %1"

Constant EMSG_HDB_FIELDNONAME

SAP Sybase Error Number 20743

SQL State QDA83

SQL Code -1000083L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000084 "The %2th join field array entry for table '%3' must have a
name. %1"

Constant EMSG_HDB_FIELDNOJOINNAME

SAP Sybase Error Number 20744

SQL State QDA84

SQL Code -1000084L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 field array entry

Parameter 3 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

SAP Sybase IQ Error Messages 597

Errors and Warnings

Error 1000085 "The join field array for table '%2' must have at least one
entry. %1"

Constant EMSG_HDB_FIELDNOJOINNAMES

SAP Sybase Error Number 20745

SQL State QDA85

SQL Code -1000085L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This an internal error. If this error occurs, it should be reported to
Sybase.

Warning 1000086 "Length %1 %2%3%4"

Constant EMSG_PREVIEWFILLERA

SAP Sybase Error Number 20746

SQL State QDA86

SQL Code 1000086L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Probable Cause This is an informational message displayed in context with other

messages.

598 SAP Sybase IQ

Errors and Warnings

Warning 1000087 "Delimiter %1 %2%3%4"

Constant EMSG_PREVIEWFILLERCD

SAP Sybase Error Number 20747

SQL State QDA87

SQL Code 1000087L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 delimiter name

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000088 "Offset %1, Length %2, %3 nulls, %4%5%6 %7"

Constant EMSG_PREVIEWOFFSET

SAP Sybase Error Number 20748

SQL State QDA88

SQL Code 1000088L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 offset

Parameter 2 length

Parameter 3 nulls

Parameter 4 parameter 4 description

Parameter 5 parameter 5 description

SAP Sybase IQ Error Messages 599

Errors and Warnings

Warning 1000088 "Offset %1, Length %2, %3 nulls, %4%5%6 %7"

Parameter 6 parameter 6 description

Parameter 7 parameter 7 description

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000089 "Length %1, %2 nulls, %3%4%5 %6"

Constant EMSG_PREVIEWLENGTH

SAP Sybase Error Number 20749

SQL State QDA89

SQL Code 1000089L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 length

Parameter 2 nulls

Parameter 3 parameter 3 description

Parameter 4 parameter 4 description

Parameter 5 parameter 5 description

Parameter 6 parameter 6 description

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000090 "%1, %2 nulls, %3%4%5 %6"

Constant EMSG_PREVIEWPREFIX1

SAP Sybase Error Number 20750

SQL State QDA90

SQL Code 1000090L

ODBC 2 State ERROR

600 SAP Sybase IQ

Errors and Warnings

Warning 1000090 "%1, %2 nulls, %3%4%5 %6"

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 length

Parameter 2 nulls

Parameter 3 parameter 3 description

Parameter 4 parameter 4 description

Parameter 5 parameter 5 description

Parameter 6 parameter 6 description

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000091 "%1, %2 nulls, %3%4%5 %6"

Constant EMSG_PREVIEWPREFIX2

SAP Sybase Error Number 20751

SQL State QDA91

SQL Code 1000091L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 length

Parameter 2 nulls

Parameter 3 parameter 3 description

Parameter 4 parameter 4 description

Parameter 5 parameter 5 description

Parameter 6 parameter 6 description

Probable Cause This is an informational message displayed in context with other

messages.

SAP Sybase IQ Error Messages 601

Errors and Warnings

Error 1000092 "Table %2 must have a name for the join field array. %1"

Constant EMSG_HDB_TABLENOJOINNAME

SAP Sybase Error Number 20752

SQL State QDA92

SQL Code -1000092L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for %2

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Warning 1000093 "%1, %2 nulls, %3%4%5 %6"

Constant EMSG_PREVIEWPREFIX4

SAP Sybase Error Number 20753

SQL State QDA93

SQL Code 1000093L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Parameter 5 Parameter 5 description

Parameter 6 Parameter 6 description

Probable Cause This is an informational message displayed in context with other

messages.

602 SAP Sybase IQ

Errors and Warnings

Error 1000094 "Sufficient memory cannot be found for the LOAD. Increasing the
Load_Memory_MB or decreasing the BLOCK FACTOR or BLOCK
SIZE will allow the LOAD to proceed. %1"

Constant EMSG_BLOCK_FACTOR_SIZE_LOAD_MEMORY

SAP Sybase Er- 20754

ror Number

SQL State QDA94

SQL Code -1000094L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause When the user explicitly sets Load_Memory_MB, the LOAD process applies
various heuristics for load parameters in an attempt to find a combination such that
the memory required is not more than what the user specified. For a fixed width
LOAD, BLOCK FACTOR indicates the minimal number of rows that must be
read into memory for each read. The default BLOCK FACTOR is 10,000. De-
creasing the BLOCK FACTOR will make the LOAD's internal memory require-
ments smaller. For a variable length input LOAD, BLOCK SIZE represents the
size in bytes in which input data should be read. The default BLOCK SIZE is
500,000 bytes. Decreasing the BLOCK SIZE for a variable width input load will
reduce LOAD's memory requirements. Alternatively, the Load_Memory_MB
option setting could be raised.

Warning 1000096 "Delimiter %1 %2 nulls, %3%4%5 %6"

Constant EMSG_PREVIEWCD

SAP Sybase Error Number 20756

SQL State QDA96

SQL Code 1000096L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 delimiter

SAP Sybase IQ Error Messages 603

Errors and Warnings

Warning 1000096 "Delimiter %1 %2 nulls, %3%4%5 %6"

Parameter 2 nulls

Parameter 3 parameter 3 description

Parameter 4 parameter 4 description

Parameter 5 parameter 5 description

Parameter 6 parameter 6 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000097 "Parse Error in Command String at '%2'. %1"

Constant EMSG_PARSEERROR

SAP Sybase Error Number 20757

SQL State QDA97

SQL Code -1000097L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Start of the parse error

Probable Cause Consult the IQ reference manual for the DBCC grammar

Error 1000099 "The PAGE SIZE divided by the BLOCK SIZE must be equal
to 2, 4, 8, or 16. DATABASE: %2 PAGE SIZE: %3 BLOCK
SIZE: %4 %1"

Constant EMSG_HDB_INVALIDCHUNKSIZE

SAP Sybase Error Number 20759

SQL State QDA99

SQL Code -1000099L

ODBC 2 State ERROR

ODBC 3 State ERROR

604 SAP Sybase IQ

Errors and Warnings

Error 1000099 "The PAGE SIZE divided by the BLOCK SIZE must be equal
to 2, 4, 8, or 16. DATABASE: %2 PAGE SIZE: %3 BLOCK
SIZE: %4 %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 database name

Parameter 3 page size

Parameter 4 block size

Probable Cause (PAGE SIZE)/(BLOCK SIZE) must be one of 2, 4, 8, 16. Adjust the
PAGE SIZE or the BLOCK SIZE in the CREATE DATABASE state-
ment.

Error 1000100 "Cannot INSERT, LOAD, or UPDATE a join virtual table. %1"

Constant EMSG_SQL_NOINSERTJVT

SAP Sybase Error Number 20760

SQL State QDB00

SQL Code -1000100L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The user is not allowed to INSERT to or LOAD a join virtual table.
Instead you must INSERT to or LOAD the tables which participate in
the join and and execute the SYNCHRONIZE command.

Error 1000101 "%2 not supported by Sybase IQ. %1"

Constant EMSG_SQL_STMT_NOTSUPPORTED

SAP Sybase Error Number 20761

SQL State QDB01

SQL Code -1000101L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 605

Errors and Warnings

Error 1000101 "%2 not supported by Sybase IQ. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 sql statement type

Parameter 2 location of the exception

Probable Cause The statement in question is not supported by Sybase IQ.

Error 1000103 "Cannot find an index for field '%2'. Every field must have at least
one index. Current IndexCount = %3. %1"

Constant EMSG_CAT_FIELD_HAS_NOINDEX

SAP Sybase Error 20763

Number

SQL State QDB03

SQL Code -1000103L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Field name

Parameter 2 Number of indexes found for the named field.

Parameter 3 location of the exception

Probable Cause This error should not occur during normal operation. Every field in ASIQ
will have at least one index (the automatically generated FP index). This
error occurs, the operation should be retried. If the error persists, it should be
reported to Sybase. Extra information may have been output to the iqmsg
file.

Messages 1000104 through 1000129

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1000104 "in join virtual table '%1'%2"

Constant EMSG_DELETE_CBTNAMEJOIN

606 SAP Sybase IQ

Errors and Warnings

Warning 1000104 "in join virtual table '%1'%2"

SAP Sybase Error Number 20764

SQL State 01B04

SQL Code 1000104L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000105 "%1"

Constant EMSG_DELETE_CBTNAME1TABLE

SAP Sybase Error Number 20765

SQL State 01B05

SQL Code 1000105L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000106 "Local temporary table, %2, must be committed in order to

create an index. %1"

Constant EMSG_CAT_CANNOT_CREATEIDX_ONLTT

SAP Sybase Error Num- 20766

ber

SQL State QDB06

SAP Sybase IQ Error Messages 607

Errors and Warnings

Error 1000106 "Local temporary table, %2, must be committed in order to

create an index. %1"

SQL Code -1000106L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception.

Parameter 2 Tablename

Probable Cause To be able to create an index for a local temporary table, the table must be
in a committed state. If this message occurs, the user has tried to execute
a CREATE INDEX on a local temporary table that has had data inserted,
deleted, or updated that has not yet been committed.

Warning 1000107 "For table '%1' in join virtual table '%2', \n%3 left outer rows
with %4 columns will be moved (inserted/deleted).\n"

Constant EMSG_DELETE_CBTLOUTERROWSMOVED

SAP Sybase Error Number 20767

SQL State 01B07

SQL Code 1000107L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 tablename

Parameter 2 join virtual table

Parameter 3 number of rows moved

Parameter 4 number of columns

Probable Cause This is an informational message displayed in context with other

messages. The message displays the number of rows moved during an
insert to or delete from a join.

608 SAP Sybase IQ

Errors and Warnings

Warning 1000108 "The DELETE where clause yielded %1 rows, but table '%2'
has no data."

Constant EMSG_DELETE_TABLENODATA

SAP Sybase Error Number 20768

SQL State 01B08

SQL Code 1000108L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 number of rows

Parameter 2 tablename

Probable Cause This is an internal error. This warning should not occur during normal
use. If this error occurs, it should be reported to Sybase.

Error 1000110 "The wrong SIndex has been opened for a fast projection
index. %1"

Constant EMSG_CAT_WRONGSINDEX

SAP Sybase Error Num- 20770

ber

SQL State QDB10

SQL Code -1000110L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause This is an internal error and should not occur. Diagnostic information
has been output to the iqmsg file. If the error occurs, it should be re-
ported to Sybase. The operation that caused the error may be tried again.

Error 1000111 "The wrong FP Index has been opened for a field. %1"

Constant EMSG_CAT_WRONGFPOPENED

SAP Sybase IQ Error Messages 609

Errors and Warnings

Error 1000111 "The wrong FP Index has been opened for a field. %1"

SAP Sybase Error Num- 20771

ber

SQL State QDB11

SQL Code -1000111L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause This is an internal error and should not occur. Diagnostic information
has been output to the iqmsg file. If the error occurs, it should be reported
to Sybase. The operation that caused the error may be tried again.

Error 1000112 "The EBM on the field's columnDescriptor does not match
the column EBM on the FPIndex. %1"

Constant EMSG_CAT_EBMSDONTMATCH

SAP Sybase Error Num- 20772

ber

SQL State QDB12

SQL Code -1000112L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Error 1000113 "Field %2 does not have an FP index. %1"

Constant EMSG_CAT_FIELD_HAS_NOFPINDEX

SAP Sybase Error 20773

Number

610 SAP Sybase IQ

Errors and Warnings

Error 1000113 "Field %2 does not have an FP index. %1"

SQL State QDB13

SQL Code -1000113L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Field name.

Probable Cause This error should not occur during normal operation. Every field has an FP
index which is created automatically when the field is created. If the error
occurs, diagnostic information will be output to the iqmsg file and the oper-
ation that caused it may be tried again. If the problem persists, the server
should be shutdown and restarted. An occurrence of this error should be
reported to Sybase.

Error 1000114 "CMP index can only be created on two distinct columns having
identical datatypes. %1"

Constant EMSG_CMP_NOT_ON_TWOCOLUMNS

SAP Sybase Error 20774

Number

SQL State QDB14

SQL Code -1000114L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CMP index is an index that can be only created on two columns. You
cannot create a single column CMP index; nor can you create a CMP index
on three or more columns. Furthermore, when specifying two columns, the
two columns must have identical datatypes.

SAP Sybase IQ Error Messages 611

Errors and Warnings

Warning 1000117 "The data to be inserted into table '%2', column '%1' cannot
be converted to the datatype of the column. NULL will be
inserted if the column allows NULLs."

Constant EMSG_CANNOT_CONVERT_FOR_INSERT

SAP Sybase Error Num- 20777

ber

SQL State 00B17

SQL Code 1000117L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 The table that is being inserted to.

Parameter 2 The column that is being inserted to.

Probable Cause The database option CONVERSION_ERROR has been set to 'OFF' for
this INSERT. The data to be inserted to the named column cannot be
converted to the datatype of that column. If the column allows NULL,
then NULL will be inserted instead.

Warning 1000119 "The data to be inserted into table '%2', column `%1' from row
%3 of the select results cannot be converted to the datatype of
the destination column. NULL will be inserted if the column
allows NULLs."

Constant EMSG_CANNOT_CONVERT_FOR_INSERT_SELECT

SAP Sybase Error 20779

Number

SQL State 00B19

SQL Code 1000119L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 The table being inserted to.

Parameter 2 The column being inserted to.

612 SAP Sybase IQ

Errors and Warnings

Parameter 3 The row number in the SELECT results that contains the data that cannot
be converted.

Probable Cause The database option CONVERSION_ERROR has been set to 'OFF' for
this INSERT...SELECT. During INSERT...SELECT, the data to be inser-
ted to one of the columns cannot be converted to the datatype of that
column. If the column allows NULL, then NULL will be inserted instead.

Error 1000120 "Join %2 was not found in the catalog. %1"

Constant EMSG_DELETE_NOJOINTABLE

SAP Sybase Error Number 20780

SQL State QDB20

SQL Code -1000120L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000121 "binary data not supported on data longer than 32767 %2,
%1"

Constant EMSG_BINARYINPUTTOOLARGE

SAP Sybase Error Number 20781

SQL State QDB21

SQL Code -1000121L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 613

Errors and Warnings

Error 1000121 "binary data not supported on data longer than 32767 %2,
%1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 SA parse source code line

Probable Cause The user has input a binary string that is too wide

Warning 1000122 "The data to update table '%2', column `%1' cannot be
converted to the datatype of the destination column for update
number %3 to the table. NULL will be inserted if the column
allows NULLs."

Constant EMSG_CANNOT_CONVERT_FOR_UPDATE

SAP Sybase Error 20782

Number

SQL State 00B22

SQL Code 1000122L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 The table being updated.

Parameter 2 The column being updated.

Parameter 3 The n'th update to the table.

Probable Cause The database option CONVERSION_ERROR has been set to 'OFF' for this
UPDATE. During UPDATE, the data to update one of the columns cannot
be converted to the datatype of the column. The update number represents
the number of updates made to the table which is not necessarily the row
number of the table being updated. The column will be updated with NULL
if the column definition allows NULLs.

Error 1000123 "Index '%2' cannot be created. Multicolumn indexes must

be created using distinct columns. %1"

Constant EMSG_MCINDEX_NEEDS_DISTINCT_COLS

SAP Sybase Error Number 20783

614 SAP Sybase IQ

Errors and Warnings

Error 1000123 "Index '%2' cannot be created. Multicolumn indexes must

be created using distinct columns. %1"

SQL State QDB23

SQL Code -1000123L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The name of the index being created.

Parameter 2 Location of the exception.

Probable Cause Multicolumn indexes must be created using distinct columns. That is,
you cannot use the same column more than once when creating a
multicolumn index.

Error 1000124 "Function or Operator not supported on data longer than

%2 bytes. %1"

Constant EMSG_BINARYINPUTFIELDTOOLARGE

SAP Sybase Error Number 20784

SQL State QDB24

SQL Code -1000124L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 number of bytes

Probable Cause The user has entered a binary string that is too wide.

Error 1000126 "This database must be upgraded. %1"

Constant EMSG_VERSION_2OLD

SAP Sybase Error Number 20786

SQL State QDB26

SAP Sybase IQ Error Messages 615

Errors and Warnings

Error 1000126 "This database must be upgraded. %1"

SQL Code -1000126L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause This database must be upgraded with the ALTER DATABASE UP-
GRADE command in order to continue.

Error 1000127 "The LIMIT specified, '%2', is too large. %1"

Constant EMSG_SQL_LIMIT_INVALIDSIZE

SAP Sybase Error Num- 20787

ber

SQL State QDB27

SQL Code -1000127L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 The LIMIT that was entered.

Probable Cause The LIMIT entered is too large. The LIMIT entered on the command
line must be between 0 and 4294967295. However, this limitation is
only for the LIMIT clause in the sql command. See the ASIQ Refer-
ence Manual for the actual, valid LIMIT size.

Warning 1000129 "%1 row(s) deleted from index '%2' in %3 seconds."

Constant EMSG_DELETE_1INDEX_A

SAP Sybase Error Number 20789

SQL State QDB29

SQL Code 1000129L

ODBC 2 State OK

616 SAP Sybase IQ

Errors and Warnings

Warning 1000129 "%1 row(s) deleted from index '%2' in %3 seconds."

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Number of rows

Parameter 2 index name

Parameter 3 number of seconds to complete the operation

Probable Cause This is an informational message displayed after a delete.

Messages 1000130 through 1000150

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1000130 "%1 row(s) deleted from index '%2' on field '%3', %4
seconds."

Constant EMSG_DELETE_1INDEX

SAP Sybase Error Number 20790

SQL State 01B30

SQL Code 1000130L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Number of rows

Parameter 2 index name

Parameter 3 field name

Parameter 4 number of seconds to complete the operation

Probable Cause This is an informational message displayed after a delete.

Error 1000131 "The DELIMITED BY and LIMIT options are valid for WD
indexes only. %1"

Constant EMSG_OPTION_FOR_WDINDEX_ONLY

SAP Sybase Error Number 20791

SAP Sybase IQ Error Messages 617

Errors and Warnings

Error 1000131 "The DELIMITED BY and LIMIT options are valid for WD
indexes only. %1"

SQL State QDB31

SQL Code -1000131L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The DELIMITED BY and LIMIT options may be used only when
creating a WD (WORD) index.

Error 1000132 "In table '%2', the START ROW ID value (%3) must be greater
than %4. Data has already been inserted at this location. %1"

Constant EMSG_INSRT_BADSTARTRECID

SAP Sybase Error Num- 20792

ber

SQL State QDB32

SQL Code -1000132L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 requested START ROW ID value

Parameter 4 row id value

Probable Cause You have entered an incorrect START ROW ID and are trying to insert
into a column that already contains data. See the Administration and
Performance Guide's chapter Moving Data in and out of Databases. The
section on partial width inserts contains information regarding the
START ROW ID option.

618 SAP Sybase IQ

Errors and Warnings

Error 1000133 "During the LOAD into table '%2', the LOAD statement's
column count (%3) must be between 1 and %4. Check the
LOAD statement's 'load-specification'. %1"

Constant EMSG_INSRT_COLUMNCOUNT

SAP Sybase Error Num- 20793

ber

SQL State QDB33

SQL Code -1000133L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 number of columns attempting to insert to

Parameter 4 number of columns in the table.

Probable Cause The number of columns you are trying to insert to is not consistent with
the number of columns specified in the LOAD statement's 'load-spec-
ification'. You must specify by name each column you are attempting to
insert to via the LOAD statement.

Error 1000134 "Column '%2' is being inserted into twice by this INSERT
command. %1"

Constant EMSG_INSRT_DUPFIELD

SAP Sybase Error Number 20794

SQL State QDB34

SQL Code -1000134L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

SAP Sybase IQ Error Messages 619

Errors and Warnings

Error 1000134 "Column '%2' is being inserted into twice by this INSERT
command. %1"

Probable Cause The specified column was listed twice in the insert command.

Error 1000135 "Cannot open the existence list for table '%2'. %1"

Constant EMSG_INSRT_EXISTENCEBM

SAP Sybase Error Number 20795

SQL State QDB35

SQL Code -1000135L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000136 "A mismatch exists between the existence bitmaps in the
insert object. %1"

Constant EMSG_INSRT_EXISTENCEMISMATCH

SAP Sybase Error Number 20796

SQL State QDB36

SQL Code -1000136L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

620 SAP Sybase IQ

Errors and Warnings

Error 1000137 "While inserting, table '%2' already had a Complete

started. %1"

Constant EMSG_INSRT_HADDONE

SAP Sybase Error Number 20797

SQL State QDB37

SQL Code -1000137L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000138 "A data conversion error has occurred while loading record
%2. This error should be reported to Sybase. %1"

Constant EMSG_INSRT_CONVERTDATA

SAP Sybase Error 20798

Number

SQL State QDB38

SQL Code -1000138L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 The input record number when the error occurred.

Probable Cause A data conversion error occurred during an insert. The input datatype
cannot converted to the datatype of the data's destination field. This error
should be reported to Sybase. Diagnostic information has been output to
the iqmsg file.

SAP Sybase IQ Error Messages 621

Errors and Warnings

Error 1000139 "You cannot insert into table '%2' past the original end of
the table while there are %3 join virtual tables based on it.
%1"

Constant EMSG_INSRT_HASJOINPASTEND

SAP Sybase Error Number 20799

SQL State QDB39

SQL Code -1000139L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 number of join virtual tables

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000140 "You cannot change column '%2' because it is a 'link'

column. %1"

Constant EMSG_INSRT_HASLINK

SAP Sybase Error Number 20800

SQL State QDB40

SQL Code -1000140L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

622 SAP Sybase IQ

Errors and Warnings

Warning 1000142 "Insert into '%1', \n%2 Inners added, %3 Left Outers
converted to Inners, %4 Right Outers added."

Constant EMSG_INSRT_JOINTABLEDONE

SAP Sybase Error Number 20802

SQL State 01B42

SQL Code 1000142L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Join name

Parameter 2 number of inners added

Parameter 3 number of left outers converted to inners

Parameter 4 number of right outers added

Probable Cause This is an informational message displayed upon completion of an

insert to a join.

Error 1000143 "While inserting, table '%2' must be Complete(d) before it

can be (re)Prepare(d). %1"

Constant EMSG_INSRT_NODONE

SAP Sybase Error Number 20803

SQL State QDB43

SQL Code -1000143L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

SAP Sybase IQ Error Messages 623

SAP Sybase Error Number 20807

SQL State QDB47

SQL Code -1000147L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000148 "The table being inserted to does not have a name. %1"

Constant EMSG_INSRT_NOTABLENAME

SAP Sybase Error Number 20808

SAP Sybase IQ Error Messages 625

Errors and Warnings

Error 1000148 "The table being inserted to does not have a name. %1"

SQL State QDB48

SQL Code -1000148L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000149 "Unable to open table '%2' with Read/Write access for
insert. %1"

Constant EMSG_INSRT_NOTABLE

SAP Sybase Error Number 20809

SQL State QDB49

SQL Code -1000149L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause The table cannot be opened for write access. The insert cannot pro-
ceed. Another user has this table open with write access.

Error 1000150 "Cannot insert into the table. Column '%2' has no index.
%1"

Constant EMSG_INSRT_NOTNULLNOIDX

SAP Sybase Error Number 20810

SQL State QDB50

SQL Code -1000150L

626 SAP Sybase IQ

Errors and Warnings

Error 1000150 "Cannot insert into the table. Column '%2' has no index.
%1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

1000151 - 1001007

Messages 1000151 through 1000170

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000151 "NOT NULL column '%2' was not included in this insert.
Data is needed at row %3. %1"

Constant EMSG_INSRT_NOTNULLFIELDNOTINC

SAP Sybase Error Number 20811

SQL State QDB51

SQL Code -1000151L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Parameter 3 row number

Probable Cause Data must be provided for insertion into columns defined as "NOT
NULL".

SAP Sybase IQ Error Messages 627

Errors and Warnings

Error 1000152 "The NOT NULL column '%2' was not included in this
insert. %1"

Constant EMSG_INSRT_NOTNULLNOTINC

SAP Sybase Error Number 20812

SQL State QDB52

SQL Code -1000152L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause Data must be provided for insertion into columns defined as "NOT
NULL".

Error 1000153 "Table '%2', pass-x index count mismatch (%3/%4). %1"

Constant EMSG_INSRT_PXCOUNT

SAP Sybase Error Number 20813

SQL State QDB53

SQL Code -1000153L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 number used for comparison

Parameter 4 number used for comparison

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

628 SAP Sybase IQ

Errors and Warnings

Error 1000154 "While inserting into table '%2', the record number
recycled (%3). %1"

Constant EMSG_INSRT_RECNUMRECYCLED

SAP Sybase Error Number 20814

SQL State QDB54

SQL Code -1000154L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Parameter 3 record number

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000155 "The attempted insert length (%3) for column %2 is longer
than the maximum allowed (%4). %1"

Constant EMSG_INSRT_TOOLONG

SAP Sybase Error Number 20815

SQL State QDB55

SQL Code -1000155L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Parameter 3 requested insert length

Parameter 4 maximum insert length allowed.

SAP Sybase IQ Error Messages 629

Errors and Warnings

Error 1000155 "The attempted insert length (%3) for column %2 is longer
than the maximum allowed (%4). %1"

Probable Cause The attempted insert length is too long. The maximum length allowed
is 65535.

Error 1000156 "Tried to insert into too many (%2) LOW FAST indexes at
one time in table '%3'. %1"

Constant EMSG_INSRT_TOOMANYINDICES

SAP Sybase Error Number 20816

SQL State QDB56

SQL Code -1000156L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 requested number of indexes to insert to

Parameter 3 tablename

Probable Cause The maximum number allowed is 32727.

Error 1000157 "Columns for the index must be in ascending sort order.
%1"

Constant EMSG_ASCENDING_SORT_ONLY

SAP Sybase Error Number 20817

SQL State QDB57

SQL Code -1000157L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause It is required that ASC (ascending) sort order be used for the columns
in the indexes.

630 SAP Sybase IQ

Errors and Warnings

Error 1000158 "An Identity size mismatch has occurred. The current
transaction will rollback. %1"

Constant EMSG_CAT_IDSIZE_MISMATCH

SAP Sybase Error Num- 20818

ber

SQL State QDB58

SQL Code -1000158L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause IQ has encountered an Identity size mismatch. The current command
will be rolled back. If this error occurs, the operation that caused it may
be tried again. If the error occurs again, the server should be stopped and
restarted. If the problem persists, Sybase should be notified of the error.

Warning 1000159 "\nIn table '%1', the %2 width insert of %3 columns will
begin at record %4."

Constant EMSG_INSRT_STARTRECID

SAP Sybase Error Number 20819

SQL State 00B59

SQL Code 1000159L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 tablename

Parameter 2 partial/fixed

Parameter 3 number of columns

Parameter 4 row number

Probable Cause Informational message displayed during insert.

SAP Sybase IQ Error Messages 631

Errors and Warnings

Warning 1000160 "Option %1 has an invalid setting: %2."

Constant EMSG_INVALID_OPTION_SETTING

SAP Sybase Error Number 20820

SQL State 00B60

SQL Code 1000160L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Name of the option with the invalid setting.

Parameter 2 The current value of the option.

Probable Cause The named OPTION is set to an invalid value. See the documentation
for the valid values for the option.

Warning 1000161 "You have %1 and %2 available, respectively."

Constant EMSG_INSRT_MEMNEEDEDWARN

SAP Sybase Error Number 20821

SQL State 01B61

SQL Code 1000161L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 amount of memory

Parameter 2 amount of memory

Probable Cause Informational message displayed with other messages regarding

available memory.

Probable Cause Only UPDATE RESTRICT and DELETE RESTRICT supported

Error 1000165 "Only a single foreign key constraint can be created on the
same foreign key column(s) and same candidate key
column(s)."

Constant EMSG_SINGLE_FKEY_CONSTRAINT

SAP Sybase Error Number 20825

SQL State QNA34

SQL Code -1000165L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause For a given set of foreign key columns and candidate key columns,

Error 1000166 "Cannot specify IGNORE CONSTRAINT ALL or DATA

VALUE when option CONVERSION_ERROR is on. %1"

Constant EMSG_DATAVALUE_CONVERSION_ON

SAP Sybase Error Number 20826

SQL State QDB66

SQL Code -1000166L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

634 SAP Sybase IQ

Errors and Warnings

Error 1000166 "Cannot specify IGNORE CONSTRAINT ALL or DATA

VALUE when option CONVERSION_ERROR is on. %1"

Probable Cause When choosing to ignore DATA TYPE or ALL integrity constraint
violations on LOAD command, you must also have option CON-
VERSION_ERROR set to 'off'.

Error 1000167 "Cannot %3 table %2 because of RI concurrency conflict.

%1"

Constant EMSG_RI_CONCURRENCY_CONFLICT

SAP Sybase Error Num- 20827

ber

SQL State QDB67

SQL Code -1000167L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 name of table undergoing the given operation

Parameter 3 operation being performed on specified table

Probable Cause The named table cannot be modified in the manner specified because of
an RI concurrency conflict. Such a conflict arises under the following
conditions. delete/truncate/update candidate key at the same time its
corresponding foreign key is being loaded/inserted/updated

Error 1000168 "Cannot create %1 HG index because one already exists on

the given columns."

Constant EMSG_CANNOT_CREATE_HG

SAP Sybase Error Num- 20828

ber

SQL State QNA35

SQL Code -1000168L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 635

Errors and Warnings

Error 1000168 "Cannot create %1 HG index because one already exists on

the given columns."

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 type of HG index to be created (non-unique vs. unique)

Probable Cause Only a single HG index of a given type can be created on the same
column set. For example, you cannot have two unique HG indexes on
the same column set, but you are allowed to have a unique HG and a
non-unique HG index on the same set of columns.

Error 1000169 "Cannot create unique HG index because primary key or unique
constraint already exists on the given columns."

Constant EMSG_CANNOT_CREATE_UNIQUE_HG

SAP Sybase Error 20829

Number

SQL State QNA36

SQL Code -1000169L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause When you create a primary key or unique constraint, IQ automatically
creates a unique HG index as the mechanism for enforcing the 'uniqueness'
attribute of a primary key or unique constraint. Consequently, a user cannot
create another unique HG on the same columns on which the primary key or
unique constraint is defined.

Error 1000170 "Cannot create a duplicate '%1' index '%2'."

Constant EMSG_DUPLICATE_INDEX

SAP Sybase Error Number 20830

SQL State QNA37

SQL Code -1000170L

ODBC 2 State ERROR

636 SAP Sybase IQ

Errors and Warnings

Error 1000170 "Cannot create a duplicate '%1' index '%2'."

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 indextype

Parameter 2 indexname

Probable Cause Cannot create duplicate indexes of the same type on a set of columns.

Messages 1000171 through 1000192

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1000171 "Insert Pass IP2.2 started."

Constant EMSG_INSRT_SORTPASS22_STARTED

SAP Sybase Error Number 20831

SQL State 00B71

SQL Code 1000171L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Probable Cause Informational message.

Warning 1000172 "Insert Pass %1 (%2 of %3) started."

Constant EMSG_INSRT_SORTPASS234_STARTED

SAP Sybase Error Number 20832

SQL State 00B72

SQL Code 1000172L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 pass number

SAP Sybase IQ Error Messages 637

Errors and Warnings

Warning 1000172 "Insert Pass %1 (%2 of %3) started."

Parameter 2 pass number

Parameter 3 number

Probable Cause This is an informational message.

Error 1000173 "Index '%1' cannot be created. Multicolumn indexes must

be created using distinct columns."

Constant EMSG_NEED_DISTINCT_COLUMNS

SAP Sybase Error Number 20833

SQL State QNA38

SQL Code -1000173L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The name of the index being created.

Probable Cause Multicolumn indexes must be created using distinct columns. That is,
you cannot use the same column more than once when creating a
multicolumn index.

Warning 1000174 "\n\t%1 records were inserted into '%2'.\n"

Constant EMSG_INSRT_COMPLETE

SAP Sybase Error Number 20834

SQL State 01B74

SQL Code 1000174L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 number of insertions

Parameter 2 tablename

Probable Cause Informational message displayed after insert.

638 SAP Sybase IQ

Errors and Warnings

Warning 1000175 "%1 records were inserted into %2 join virtual tables (%3
sections)\n for '%4'.\n"

Constant EMSG_INSRT_COMPLETEJOINS

SAP Sybase Error Number 20835

SQL State 01B75

SQL Code 1000175L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 number of records

Parameter 2 number of join virtual tables

Parameter 3 number of join sorts

Parameter 4 join virtual table name

Probable Cause This is an informational message displayed at the end of insert.

Error 1000176 "Cannot perform foreign key create/alter operation

because one is already in progress. %1"

Constant EMSG_FK_INPROGRESS

SAP Sybase Error Number 20836

SQL State QDB76

SQL Code -1000176L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Probable Cause Concurrent foreign key create/alter operations are not supported. This
error means that there is such an operation already in progress. Con-
sequetly, this new operation will be denied.

SAP Sybase IQ Error Messages 639

Errors and Warnings

Warning 1000177 "Only the catalog entry for the '%1' index was created, no
data was available to populate the index."

Constant EMSG_APICREATEINDEXNODATA

SAP Sybase Error Number 20837

SQL State QDB77

SQL Code 1000177L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 The index name

Probable Cause This is an internal error. The new index was to be populated from
another, existing index but a source index could not be found. If this
error occurs, it should be reported to Sybase.

Error 1000178 "The DATA parameter must have a non-NULL value. %1"

Constant EMSG_APIDATAMUSTHAVEVALUE

SAP Sybase Error Number 20838

SQL State QDB78

SQL Code -1000178L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000179 "The column length (%2) must be [if variable sized,
between 0 and] %3. %1"

Constant EMSG_APISETACTUALFIELDLENGTH

SAP Sybase Error Number 20839

SQL State QDB79

640 SAP Sybase IQ

Errors and Warnings

Error 1000179 "The column length (%2) must be [if variable sized,
between 0 and] %3. %1"

SQL Code -1000179L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column length

Parameter 3 column length

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000180 "The maximum column length (%2) must be between 0 and
%3. %1"

Constant EMSG_APISETMAXFIELDLENGTH

SAP Sybase Error Number 20840

SQL State QDB80

SQL Code -1000180L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column length

Parameter 3 column length

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000181 "The maximum column length (%2) is less than the actual
length (%3). %1"

Constant EMSG_APIMAXACTUALFLEN

SAP Sybase Error Number 20841

SAP Sybase IQ Error Messages 641

Errors and Warnings

Error 1000181 "The maximum column length (%2) is less than the actual
length (%3). %1"

SQL State QDB81

SQL Code -1000181L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column length

Parameter 3 column length

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000182 "Table %2 cannot be opened because it is currently

involved in a foreign key create/alter operation. %1"

Constant EMSG_CANNOT_OPEN_FK_INPROGRESS

SAP Sybase Error Number 20842

SQL State QDB82

SQL Code -1000182L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 The name of the table being opened.

Probable Cause The named table cannot be opened for read or write access because it
is currently undergoing a create/alter foreign operation.

Error 1000183 "Attempt to insert data into column '%2' with a non-
insertable datatype (%3) ignored. %1"

Constant EMSG_APIINSERTDATATYPEIGNORED

SAP Sybase Error Number 20843

642 SAP Sybase IQ

Errors and Warnings

Error 1000183 "Attempt to insert data into column '%2' with a non-
insertable datatype (%3) ignored. %1"

SQL State QDB83

SQL Code -1000183L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for %2

Parameter 3 explanation for %3

Probable Cause This is an internal error. The datatype IQ is inserting to is unknown. If

this error occurs, it should be reported to Sybase.

Error 1000185 "Cannot drop table %1 because foreign keys still reference
it."

Constant EMSG_FKEY_STILL_EXISTS_TO_TABLE

SAP Sybase Error Number 20845

SQL State QNA39

SQL Code -1000185L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 name of the table

Probable Cause The named table cannot be dropped until all foreign keys referencing
it have first been dropped.

Error 1000186 "Cannot create foreign key constraint on a candidate key that is
also a foreign key."

Constant EMSG_CKEY_IS_ALSO_FKEY

SAP Sybase Error 20846

Number

SAP Sybase IQ Error Messages 643

Errors and Warnings

Error 1000186 "Cannot create foreign key constraint on a candidate key that is
also a foreign key."

SQL State QNA40

SQL Code -1000186L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause A candidate key cannot also be a foreign key. Here's an example illustrating
what is meant by this exception. (1) A [pk] <----- B [fk] [pk] <-- ADD THIS
ONE -- C[fk] (2) A [pk] <-- ADD THIS ONE -- B[fk] [pk] <------- C[fk] In
case (1), adding foreign key C[fk] is disallowed. In case (2), adding foreign
key B[fk] is disallowed.

Error 1000187 "Unable to implicitly convert column '%2' to datatype (%3)

from datatype (%4). %1"

Constant EMSG_SQL_IMPLICITCONVERSION

SAP Sybase Error 20847

Number

SQL State QCB87

SQL Code -1000187L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column converting

Parameter 3 datatype being converted to

Parameter 4 datatype being converted from

644 SAP Sybase IQ

Errors and Warnings

Error 1000187 "Unable to implicitly convert column '%2' to datatype (%3)

from datatype (%4). %1"

Probable Cause The attempted implicit conversion is not possible. The conversion must be
done explicitly. If implicit conversion is being attempted to or from a
NUMERIC and this error results, the datatype displayed in the error for
the NUMERIC will be SMALLINT, INT, or INT64 depending on the
precision of the NUMERIC. This is because NUMERICs are treated
internally as multiple precision signed integers.

Error 1000188 "Only ASCII, BCP and BINARY are supported LOAD
formats. %1"

Constant EMSG_LOAD_FORMAT_NOT_SUPPORTED

SAP Sybase Error Number 20848

SQL State QDB88

SQL Code -1000188L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The user specified a LOAD format that is not supported.

Error 1000189 "DDL statements cannot proceed while the %2 is in an out of

space condition. %1"

Constant EMSG_CAT_NODDL_WHILE_OUTOFSPACE

SAP Sybase Error 20849

Number

SQL State QDB89

SQL Code -1000189L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The store that is out of space.

SAP Sybase IQ Error Messages 645

Errors and Warnings

Error 1000189 "DDL statements cannot proceed while the %2 is in an out of

space condition. %1"

Parameter 2 Location of the exception.

Probable Cause The DDL statement cannot proceed until the named db store is no longer in an
out of space condtion. The out of space condition had been previously repor-
ted. The only course of action available is to stop and restart the server. The
database is in an out-of-space condition. Space needs to be added to the
database.

Error 1000190 "The index '%2' cannot be opened in the current

transaction (%3). %1"

Constant EMSG_CANNOTFINDINDEX

SAP Sybase Error Number 20850

SQL State QDB90

SQL Code -1000190L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the index.

Parameter 3 The current transaction.

Probable Cause The procedure cannot open the named index. It is likely that the index
was created by a transaction that began after the one that is trying to
open it. In order to proceed, COMMIT the current transaction and try
again.

Error 1000192 "The cursor for table '%2' has no data to fetch. %1"

Constant EMSG_JOIN_CURSORNOFETCH

SAP Sybase Error Number 20852

SQL State QDB92

SQL Code -1000192L

ODBC 2 State ERROR

646 SAP Sybase IQ

Errors and Warnings

Error 1000192 "The cursor for table '%2' has no data to fetch. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Messages 1000193 through 1000214

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000193 "The table '%2' is either not part of the join virtual table or
has had its data loaded through linked indices. %1"

Constant EMSG_JOIN_CURSORNOTUSED

SAP Sybase Error Number 20853

SQL State QDB93

SQL Code -1000193L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000194 "You must supply either a cursor count (%2) and a cursor
array, or neither. %1"

Constant EMSG_JOIN_CURSORS

SAP Sybase Error Number 20854

SQL State QDB94

SAP Sybase IQ Error Messages 647

Errors and Warnings

Error 1000194 "You must supply either a cursor count (%2) and a cursor
array, or neither. %1"

SQL Code -1000194L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 cursor count

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000195 "Load specification '%2' only valid for column(s) having
datatype '%3'. %1"

Constant EMSG_BINARYFILE

SAP Sybase Error Number 20855

SQL State QDB95

SQL Code -1000195L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 type of load specification

Parameter 3 datatype of column

Probable Cause The named load specification is only valid for columns that have the
given datatype.

Error 1000197 "Table '%2' has no columns in the cursor that don't already
have data, \nor the join field(s) are not part of the cursor.
%1"

Constant EMSG_JOIN_NOCOLUMNSTOINSERTINTO

SAP Sybase Error Number 20857

648 SAP Sybase IQ

Errors and Warnings

Error 1000197 "Table '%2' has no columns in the cursor that don't already
have data, \nor the join field(s) are not part of the cursor.
%1"

SQL State QDB97

SQL Code -1000197L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Warning 1000199 "Table '%1' has no data."

Constant EMSG_JOIN_NODATAINBASESRC

SAP Sybase Error Number 20859

SQL State 01B99

SQL Code 1000199L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 the name of the table that has no data %1

Probable Cause This is a warning that there is no data in a base table.

Error 1000200 "Table '%2' has no data with which to join the other tables.
%1"

Constant EMSG_JOIN_NODATAINSRC

SAP Sybase Error Number 20860

SQL State QDC00

SQL Code -1000200L

SAP Sybase IQ Error Messages 649

Errors and Warnings

Error 1000200 "Table '%2' has no data with which to join the other tables.
%1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause There is no data in a table which participates in a join.

Error 1000201 "JOIN cannot be created or updated because the thread's stack
space has been exceeded. %1"

Constant EMSG_CAT_NEAR_END_OF_STACK

SAP Sybase Error 20861

Number

SQL State QDC01

SQL Code -1000201L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Creation or update of this JOIN has exceeded the thread's stack space. Create
or update the JOIN after restarting the engine with a larger value for the -iqtss
startup parameter. See the ASIQ Reference Manual for information on setting
iqtss.

Error 1000202 "In join virtual table '%2', there is no table cursor at index
%3. %1"

Constant EMSG_JOIN_NOTABLECURSOR

SAP Sybase Error Number 20862

SQL State QDC02

SQL Code -1000202L

650 SAP Sybase IQ

Errors and Warnings

Error 1000202 "In join virtual table '%2', there is no table cursor at index
%3. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 jvt name

Parameter 3 index

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000203 "In join virtual table '%2', there is no tablename at index
%3. %1"

Constant EMSG_JOIN_NOTABLENAME

SAP Sybase Error Number 20863

SQL State QDC03

SQL Code -1000203L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Parameter 3 index

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000204 "Within the join, the portion for table '%2' already has data.
%1"

Constant EMSG_JOIN_TABLEHASDATA

SAP Sybase Error Number 20864

SQL State QDC04

SAP Sybase IQ Error Messages 651

Errors and Warnings

Error 1000204 "Within the join, the portion for table '%2' already has data.
%1"

SQL Code -1000204L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000205 "Within the join, the cursor for table '%2' yielded no data.
%1"

Constant EMSG_JOIN_TABLEHASNODATA

SAP Sybase Error Number 20865

SQL State QDC05

SQL Code -1000205L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000206 "Within the join, there remain no rows to insert into table
'%2' \nafter processing the INNER and OUTER rows. %1"

Constant EMSG_JOIN_TABLEHASNOROWS

SAP Sybase Error Number 20866

SQL State QDC06

SQL Code -1000206L

652 SAP Sybase IQ

Errors and Warnings

Error 1000206 "Within the join, there remain no rows to insert into table
'%2' \nafter processing the INNER and OUTER rows. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000207 "Within the join, the portion for table '%2' has no data.
\nINSERT INTO or LOAD this table first. %1"

Constant EMSG_JOIN_TABLENEEDSDATA

SAP Sybase Error Number 20867

SQL State QDC07

SQL Code -1000207L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 tablename

Probable Cause The named table must be populated with data.

Error 1000208 "Within the non-appending partial width insert into the join
virtual table '%2', \nthere must be at least one other column
besides the join field(s). %1"

Constant EMSG_JOIN_VINSERTNEEDSDATACOL

SAP Sybase Error Number 20868

SQL State QDC08

SQL Code -1000208L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 653

Errors and Warnings

Error 1000208 "Within the non-appending partial width insert into the join
virtual table '%2', \nthere must be at least one other column
besides the join field(s). %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000209 "Within the partial width insert into the join virtual table
'%2', \nrow %3 is no longer an inner join. %1"

Constant EMSG_JOIN_VINSERTNOTINNER

SAP Sybase Error Number 20869

SQL State QDC09

SQL Code -1000209L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Parameter 3 row number

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1000210 "For the partial width insert into the join virtual table '%2',
\nrow %3 is no longer a left outer. %1"

Constant EMSG_JOIN_VINSERTNOTLOUTER

SAP Sybase Error Number 20870

SQL State QDC10

SQL Code -1000210L

654 SAP Sybase IQ

Errors and Warnings

Error 1000210 "For the partial width insert into the join virtual table '%2',
\nrow %3 is no longer a left outer. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Parameter 3 row

Probable Cause This is an internal error. If this error occurs, then it should be reported
to Sybase.

Error 1000211 "For the partial width insert into the join virtual table '%2',
\nrow %3 is no longer a right outer. %1"

Constant EMSG_JOIN_VINSERTNOTROUTER

SAP Sybase Error Number 20871

SQL State QDC11

SQL Code -1000211L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Parameter 3 row

Probable Cause This is an internal error. If this error occurs, then it should be reported
to Sybase.

Error 1000212 "For the partial width insert into join virtual table '%2',
\nrow %3 is now a duplicate row (but was not before or
vice-versa). %1"

Constant EMSG_JOIN_VINSERTNOTT1TRUE

SAP Sybase Error Number 20872

SAP Sybase IQ Error Messages 655

Errors and Warnings

Error 1000212 "For the partial width insert into join virtual table '%2',
\nrow %3 is now a duplicate row (but was not before or
vice-versa). %1"

SQL State QDC12

SQL Code -1000212L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 join virtual table name

Parameter 3 row

Probable Cause This is an internal error. If this error occurs, then it should be reported
to Sybase.

Warning 1000213 No message

Constant EMSG_JOIN_WARNNOCURSORS_EMPTY_SLOT

SAP Sybase Error Number 20873

SQL State 01C13

SQL Code 1000213L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause No additional information available.

Error 1000214 "Duplicate records seen in table %2. The SYNCHRONIZE

operation will rollback. %1"

Constant EMSG_JOIN_DUPLICATE_ROWS

SAP Sybase Error Number 20874

SQL State QDC14

SQL Code -1000214L

656 SAP Sybase IQ

Errors and Warnings

Error 1000214 "Duplicate records seen in table %2. The SYNCHRONIZE

operation will rollback. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table containing duplicate records

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Messages 1000215 through 1000232

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000215 "An invalid filler option (e.g., filler()) was specified in the
load statement. %1"

Constant EMSG_INVALID_FILLER_OPTION

SAP Sybase Error Number 20875

SQL State QDC15

SQL Code -1000215L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause An invalid filler option was specified on the load statement.

Warning 1000216 No message

Constant EMSG_JOIN_EJP1ADD_EMPTY_SLOT

SAP Sybase Error Number 20876

SQL State 01C16

SQL Code 1000216L

SAP Sybase IQ Error Messages 657

Errors and Warnings

Warning 1000216 No message

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause No additional information available.

Warning 1000217 No message

Constant EMSG_JOIN_EJP1STARTRECID_EMPTY_SLOT

SAP Sybase Error Number 20877

SQL State 01C17

SQL Code 1000217L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause No additional information available.

Warning 1000218 "Join virtual table fetches (JP1%1) complete for '%2'."

Constant EMSG_JOIN_EJP12DONE

SAP Sybase Error Number 20878

SQL State 01C18

SQL Code 1000218L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Probable Cause This is an informational message displayed in context with other

messages.

658 SAP Sybase IQ

Errors and Warnings

Error 1000219 "The specified indextype does not exist in the given target.
%1"

Constant EMSG_DBCC_INDEXTYPE_NOT_FOUND

SAP Sybase Error Number 20879

SQL State QDC19

SQL Code -1000219L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The indextype the user requested to check with sp_iqcheckdb does
not exist in the given table or database.

Warning 1000220 " Left Rows: %1, Right Rows: %2, Ratio: %3 to %4\n"

Constant EMSG_JOIN_EJP12CNTS

SAP Sybase Error Number 20880

SQL State 01C20

SQL Code 1000220L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000221 " Right Rows Skipped: %1 (former left outers).\n"

Constant EMSG_JOIN_EJP12SKIPS

SAP Sybase IQ Error Messages 659

Errors and Warnings

Warning 1000221 " Right Rows Skipped: %1 (former left outers).\n"

SAP Sybase Error Number 20881

SQL State 01C21

SQL Code 1000221L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000222 "JP3&4"

Constant EMSG_JOIN_ESORT34

SAP Sybase Error Number 20882

SQL State QDC22

SQL Code -1000222L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000223 "Column name '%2' is invalid. The column name must
follow the format [OWNER.]TABLE.COLUMN. %1"

Constant EMSG_INVALID_COLUMN_NAME

SAP Sybase Error Number 20883

SQL State QDC23

SQL Code -1000223L

ODBC 2 State ERROR

ODBC 3 State ERROR

660 SAP Sybase IQ

Errors and Warnings

Error 1000223 "Column name '%2' is invalid. The column name must
follow the format [OWNER.]TABLE.COLUMN. %1"

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 The name of the column typed by the user.

Probable Cause The column name must follow the format [OWNER.]TABLE.COL-
UMN.

Warning 1000224 "Join record rejected: '%1', duplicate rows in 1st indexset.
\nRow# %2 & %3X, row %4 rejected."

Constant EMSG_CLBK_JOINIDXRECORDREJECTEDX

SAP Sybase Error Number 20884

SQL State 01C24

SQL Code 1000224L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Parameter 4 Parameter 4 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000225 "Cannot open table %2. The table has already been opened
by a cursor declared FOR UPDATE in transaction %3. %1"

Constant EMSG_CAT_CANNOT_OPEN_TABLE

SAP Sybase Error Number 20885

SQL State QDC25

SQL Code -1000225L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 661

Errors and Warnings

Error 1000225 "Cannot open table %2. The table has already been opened
by a cursor declared FOR UPDATE in transaction %3. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Tablename.

Parameter 3 The id of the transaction during which the cursor was opened.

Probable Cause A table opened by a CURSOR that has been declared FOR UPDATE
cannot be opened again by another operation.

Warning 1000226 "\n Inner Rows: %1, Left Outer Rows: %2, Right Outer
Rows: %3"

Constant EMSG_JOIN_EJP3CNT1

SAP Sybase Error Number 20886

SQL State 01C26

SQL Code 1000226L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000226 "The LOCATION string passed to the attached database

insert is invalid. %1"

Constant EMSG_INVALIDLOCATION

SAP Sybase Error Number 20996

SQL State QDC36

SQL Code -1000226L

662 SAP Sybase IQ

Errors and Warnings

Error 1000226 "The LOCATION string passed to the attached database

insert is invalid. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The user passed an invalid LOCATION string in an attached database
insert. Check the format of the string. It must be of the form "serv-
ername.dbname".

Warning 1000227 " Join Rows: %1, Left m2m Rows: %2, Right m2m Rows:
%3\n"

Constant EMSG_JOIN_EJP3CNT2

SAP Sybase Error Number 20887

SQL State 01C27

SQL Code 1000227L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000227 "Cannot load data with both BINARY and delimited
columns. %1"

Constant EMSG_LOADBINARYDELIMITED

SAP Sybase Error Number 20997

SQL State QDC37

SQL Code -1000227L

SAP Sybase IQ Error Messages 663

Errors and Warnings

Error 1000227 "Cannot load data with both BINARY and delimited
columns. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You cannot load data with both BINARY and delimited columns in
the same LOAD command.

Error 1000228 "JP4&5"

Constant EMSG_JOIN_ESORT45

SAP Sybase Error Number 20888

SQL State QDC28

SQL Code -1000228L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000229 "Only BINARY [WITH NULL BYTE] can be used as a column
specification when using UNLOAD FORMAT. %1"

Constant EMSG_CANTUSEINLOAD

SAP Sybase Error Num- 20998

ber

SQL State QDC38

SQL Code -1000229L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

664 SAP Sybase IQ

Errors and Warnings

Error 1000229 "Only BINARY [WITH NULL BYTE] can be used as a column
specification when using UNLOAD FORMAT. %1"

Probable Cause When using UNLOAD FORMAT, you cannot specify any column
specification other than BINARY. If need to load null values for a col-
umn using the BINARY column spec, you must specify the WITH
NULL BYTE option. You cannot use the [ROW] DELIMITED BY
options with UNLOAD FORMAT.

Warning 1000230 "\nInsert for '%1',\n completed in %2 seconds."

Constant EMSG_DELETE_INSERTDONE

SAP Sybase Error Number 20890

SQL State 01C30

SQL Code 1000230L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000230 "Columns that allow nulls must use the WITH NULL BYTE
option. %1"

Constant EMSG_MUSTUSENULLBYTE

SAP Sybase Error Number 20999

SQL State QDC39

SQL Code -1000230L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 665

Errors and Warnings

Error 1000230 "Columns that allow nulls must use the WITH NULL BYTE
option. %1"

Probable Cause The user must use the WITH NULL BYTE option for a BINARY
column spec for columns that allow nulls.

Error 1000232 "Partial input record skipped at EOF. %1"

Constant EMSG_PARTIAL_INPUT_ROW

SAP Sybase Error Number 20892

SQL State QDC32

SQL Code -1000232L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A partial input record was detected during a 'load' operation. This can
occur as a result of an OS/hardware error or simply because the input
data file was missing values for one or more columns in the table.

Messages 1000234 through 1000244

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1000234 "\nInsert into table '%1', %2 rows rejected (in all)."

Constant EMSG_CLBK_INSERTREJECTTOTAL

SAP Sybase Error Number 20894

SQL State 01C34

SQL Code 1000234L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 table name

666 SAP Sybase IQ

Errors and Warnings

Warning 1000234 "\nInsert into table '%1', %2 rows rejected (in all)."

Parameter 2 number of rows rejected.

Probable Cause This is an informational message displayed in context with other

messages. During the LOAD, some records were rejected.

Error 1000234 "The record size of the unloaded data: %2, does not match
the record size of the load: %3. %1"

Constant EMSG_RECSIZEWRONG

SAP Sybase Error Number 21000

SQL State QDC40

SQL Code -1000234L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 record size in the tape being read

Parameter 3 record size of the load command.

Probable Cause The record size of the unloaded data does not match the size of the
record described by the LOAD command.

Warning 1000235 "%3 Pass %1 completed in %2 seconds."

Constant EMSG_CLBK_INSERTPASSDONE

SAP Sybase Error Number 20895

SQL State 00C35

SQL Code 1000235L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

SAP Sybase IQ Error Messages 667

Errors and Warnings

Warning 1000235 "%3 Pass %1 completed in %2 seconds."

Parameter 3 Parameter 3 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000235 "The total number of columns of unloaded data: %2, does
not match the total number of columns in the load: %3. %1"

Constant EMSG_NUMCOLSWRONG

SAP Sybase Error Number 21001

SQL State QDC42

SQL Code -1000235L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 number of columns in the tape being read

Parameter 3 number of columns in the load command.

Probable Cause The total number of columns in the unloaded data does not match the
number of columns in the LOAD command.

Warning 1000236 "%4 for '%1' completed in %2 seconds. %3 rows %5."

Constant EMSG_CLBK_INSERTDONE

SAP Sybase Error Number 20896

SQL State 01C36

SQL Code 1000236L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 table name

Parameter 2 number of seconds

668 SAP Sybase IQ

Errors and Warnings

Warning 1000236 "%4 for '%1' completed in %2 seconds. %3 rows %5."

Parameter 3 number of rows inserted

Parameter 4 operation performed

Parameter 5 operation performed

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000236 "The total number of null columns in the unloaded data,
%2, does not match the total number of null columns in the
LOAD command, %3. %1"

Constant EMSG_NUMNULLCOLSWRONG

SAP Sybase Error Number 21002

SQL State QDC43

SQL Code -1000236L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 number of null columns in the tape being read

Parameter 3 number of null columns in the load command.

Probable Cause The total number of null columns in the unloaded data does not match
the number of null columns in the LOAD command.

Warning 1000237 "\t%1 Rows, %2 Seconds"

Constant EMSG_CLBK_INSERTNRECS

SAP Sybase Error Number 20897

SQL State 00C37

SQL Code 1000237L

ODBC 2 State OK

ODBC 3 State OK

SAP Sybase IQ Error Messages 669

Errors and Warnings

Warning 1000237 "\t%1 Rows, %2 Seconds"

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000237 "The total number of variable width columns in the

unloaded data, %2, does not match the total number of
variable width columns in the LOAD command, %3. %1"

Constant EMSG_NUMVARCOLSWRONG

SAP Sybase Error Number 21003

SQL State QDC44

SQL Code -1000237L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 number of variable width columns in the tape being read

Parameter 3 number of variable width columns in the load command.

Probable Cause The total number of variable width columns in the unloaded data does
not match the number of variable width columns in the LOAD com-
mand.

Warning 1000238 "\t%1 Rows, %2 Seconds, '%3'"

Constant EMSG_CLBK_INSERTNRECSINDEX

SAP Sybase Error Number 20898

SQL State 01C38

SQL Code 1000238L

ODBC 2 State OK

ODBC 3 State OK

670 SAP Sybase IQ

Errors and Warnings

Warning 1000238 "\t%1 Rows, %2 Seconds, '%3'"

Severity Code 10 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1000238 "The platform type of the unloaded data, %2, does not
match the platform type on the load, %3. %1"

Constant EMSG_PLATIDWRONG

SAP Sybase Error Num- 21009

ber

SQL State QDC45

SQL Code -1000238L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Platform ID in the tape being read

Parameter 3 Platform ID the load command command is executing in.

Probable Cause The Platform ID of unloaded data does not match the Platform ID of
load. The LOAD command detected that the platform on which the
UNLOAD was performed, is not the same platform on which the
LOAD is being attempted. Cross platform UNLOAD-LOAD cannot
be done.

Warning 1000239 "Inserting into table '%1',\ncolumn '%2'.\nInput record %3

was rejected."

Constant EMSG_CLBK_INSERTRECORDREJECTED

SAP Sybase Error Number 20899

SQL State 01C39

SAP Sybase IQ Error Messages 671

Errors and Warnings

Warning 1000239 "Inserting into table '%1',\ncolumn '%2'.\nInput record %3

was rejected."

SQL Code 1000239L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the table being inserted to.

Parameter 2 The column being inserted to.

Parameter 3 The data Being inserted to the column.

Probable Cause Some data cannot be inserted. Examine the data and column defini-
tion to determine why.

Error 1000239 "UNLOAD version number: %2, does not match the LOAD
version number: %3. %1"

Constant EMSG_VERSIONWRONG

SAP Sybase Error Number 21010

SQL State QDC46

SQL Code -1000239L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 version number of data in the tape being read

Parameter 3 version number of the load command.

Probable Cause The UNLOAD version number does not match the LOAD version
number. The version number of the data on the tape being read does
not match the version number of the LOAD command. The version
numbers must match before the data on the tape can be loaded.

672 SAP Sybase IQ

Errors and Warnings

Warning 1000240 "Inserting into table '%1',\nColumn '%2'.\nOn input record

%3, the value was rejected."

Constant EMSG_CLBK_INSERTVALUEREJECTED

SAP Sybase Error Number 20900

SQL State 01C40

SQL Code 1000240L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 The name of the table being inserted to.

Parameter 2 The column being inserted to.

Parameter 3 This is the nth record being inserted.

Probable Cause Some data was rejected on insert. Examine the input data and column
definition to determine why.

Error 1000240 "The total number of blocks of unloaded data: %2, does not
match the total number of blocks loaded: %3. %1"

Constant EMSG_BLOCKCOUNTWRONG

SAP Sybase Error Number 21011

SQL State QDC47

SQL Code -1000240L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 number of blocks on the tape being read

Parameter 3 number of blocks in the load command.

Probable Cause Total number of blocks of unloaded data on the tape does not match
the number of blocks of data that were just loaded.

SAP Sybase IQ Error Messages 673

Errors and Warnings

Warning 1000241 "The insert to the table will be single threaded."

Constant EMSG_CLBK_INSERT_SINGLE_THREADED

SAP Sybase Error Num- 20901

ber

SQL State QDC41

SQL Code 1000241L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Probable Cause There are not enough threads available to do a multithreaded insert or
load. The number of users doing parallel processing has limited the
number of threads available for your insert/load. The insert/load will
proceed, but will be done serially.

Warning 1000242 "Insert completed. Index '%1',\n in %2 seconds."

Constant EMSG_CLBK_INSERTINDEXDONE

SAP Sybase Error Number 20902

SQL State 01C42

SQL Code 1000242L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 index name

Parameter 2 number of seconds

Probable Cause This is an informational message that is displayed after an insert to an

index.

Error 1000242 "Total number of rows of unloaded data: %2, does not
match the total number of rows in the load: %3. %1"

Constant EMSG_ROWCOUNTWRONG

SAP Sybase Error Number 21012

674 SAP Sybase IQ

Errors and Warnings

Error 1000242 "Total number of rows of unloaded data: %2, does not
match the total number of rows in the load: %3. %1"

SQL State QDC48

SQL Code -1000242L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 number of rows on the tape being read

Parameter 3 number of rows in the load command.

Probable Cause The total number of rows of unloaded data on the tape does not match
the numbers of rows of data just loaded.

Warning 1000243 "\nInsert into join virtual table '%1' started.\n\t\t%2 tables
will be modified (in all)."

Constant EMSG_CLBK_INSERTJOINSTART

SAP Sybase Error Number 20903

SQL State 01C43

SQL Code 1000243L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 join virtual table name

Parameter 2 number of tables

Probable Cause This is an informational message.

Error 1000243 "The unload format number: %2, does not match the load
format number: %3. %1"

Constant EMSG_FORMATWRONG

SAP Sybase Error Number 21013

SAP Sybase IQ Error Messages 675

Errors and Warnings

Error 1000243 "The unload format number: %2, does not match the load
format number: %3. %1"

SQL State QDC49

SQL Code -1000243L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 format number of data in the tape being read.

Parameter 3 format number of the load command.

Probable Cause The unload format number does not match the load format number.
The data on the tape being read contains a format number. This num-
ber does not match the format number of the LOAD command. In
order to load the data, the numbers must match.

Warning 1000244 "\nInsert into join virtual table '%1' completed\n in %2

seconds.\n\t\t%3 tables modified (in all).\n"

Constant EMSG_CLBK_INSERTJOINDONE

SAP Sybase Error Number 20904

SQL State 01C44

SQL Code 1000244L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 join virtual table name

Parameter 2 number of seconds

Parameter 3 number of tables

Probable Cause This is an informational message.

676 SAP Sybase IQ

Errors and Warnings

Messages 1000244 through 1000261

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000244 "The BLOCK FACTOR of unloaded data: %2 does not

match the BLOCK FACTOR of the LOAD: %3. %1"

Constant EMSG_BLOCKFACTORWRONG

SAP Sybase Error Number 21014

SQL State QDC50

SQL Code -1000244L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Block Factor of data in the tape being read.

Parameter 3 Block Factor specified in the load command.

Probable Cause The BLOCK FACTOR used in the LOAD command must be the same
as the BLOCK FACTOR that was used in the LOAD command to
unload the data.

Warning 1000245 "Insert into join virtual table '%1' started.\n%2 rows will be
inserted (in all)."

Constant EMSG_CLBK_INSERTJOINTABLESTART

SAP Sybase Error Number 20905

SQL State 01C45

SQL Code 1000245L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 join virtual table name

SAP Sybase IQ Error Messages 677

Errors and Warnings

Warning 1000245 "Insert into join virtual table '%1' started.\n%2 rows will be
inserted (in all)."

Parameter 2 number of rows to be inserted

Probable Cause This is an informational message.

Error 1000245 "Tape / File already loaded. Block number %2 repeats. %1"

Constant EMSG_FILEALREADYLOADED

SAP Sybase Error Number 21015

SQL State QDC51

SQL Code -1000245L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 block number that was already loaded.

Probable Cause LOAD has encountered a block that has already been loaded. This
tape (or file) has already been loaded.

Warning 1000246 "%1 Rows, %2 Seconds"

Constant EMSG_CLBK_INSERTJOINNRECS

SAP Sybase Error Number 20906

SQL State 01C46

SQL Code 1000246L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 rows

Parameter 2 seconds

Probable Cause This is an informational message displayed in context with other

messages.

678 SAP Sybase IQ

Errors and Warnings

Error 1000246 "The number of rows loaded: %3, does not match the
number of rows unloaded: %2. %1"

Constant EMSG_ROWCOUNTMISMATCH

SAP Sybase Error Number 21016

SQL State QDC52

SQL Code -1000246L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Number of rows of data in all tapes that were read.

Parameter 3 Number of rows of data actually loaded by the load command.

Probable Cause The number of rows of data on all of the tapes that were loaded does
not match the number of rows of data that were unloaded by the
LOAD command.

Warning 1000247 "Insert into join virtual table '%1' completed in %2

seconds.\n%3 rows inserted (in all)."

Constant EMSG_CLBK_INSERTJOINTABLEDONE

SAP Sybase Error Number 20907

SQL State 01C47

SQL Code 1000247L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 join virtual table name

Parameter 2 number of seconds

Parameter 3 number of rows inserted

Probable Cause This is an informational message.

SAP Sybase IQ Error Messages 679

Errors and Warnings

Error 1000247 "The number of blocks loaded: %3, does not match the
number of blocks unloaded: %2. %1"

Constant EMSG_BLOCKCOUNTMISMATCH

SAP Sybase Error Number 21017

SQL State QDC54

SQL Code -1000247L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Number of blocks of data in all tapes that were read.

Parameter 3 Number of blocks of data actually loaded by the load command.

Probable Cause The number of blocks of data on all of the tapes that were loaded does
not match the number of blocks of data that were unloaded by the
LOAD command.

Warning 1000248 "\nJoin virtual table passes started for '%1'.\n"

Constant EMSG_CLBK_JOINIDXPASSESSTART

SAP Sybase Error Number 20908

SQL State 01C48

SQL Code 1000248L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 index name

Probable Cause This is an informational message.

Warning 1000249 "\nJoin Virtual Table Pass 1 started for '%1'.\n"

Constant EMSG_CLBK_JOINIDXPASS1START

SAP Sybase Error Number 20909

680 SAP Sybase IQ

Errors and Warnings

Warning 1000249 "\nJoin Virtual Table Pass 1 started for '%1'.\n"

SQL State 01C49

SQL Code 1000249L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 index name

Probable Cause This is an informational message.

Warning 1000250 "\nJoin virtual table Pass %1 completed for '%2', %3

seconds.\n\t\t%4 rows processed.\n"

Constant EMSG_CLBK_JOINIDXPASSCOMPLETE

SAP Sybase Error Number 20910

SQL State 01C50

SQL Code 1000250L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 pass

Parameter 2 index

Parameter 3 seconds

Parameter 4 rows

Probable Cause This is an informational message.

Warning 1000251 "\nJoin virtual table passes 1 and 2 complete for '%1' in %2
seconds.\n%3 rows processed.\n"

Constant EMSG_CLBK_JOINIDXPASS1AND2COMPLETE

SAP Sybase Error Number 20911

SQL State 01C51

SAP Sybase IQ Error Messages 681

Errors and Warnings

Warning 1000251 "\nJoin virtual table passes 1 and 2 complete for '%1' in %2
seconds.\n%3 rows processed.\n"

SQL Code 1000251L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 index name

Parameter 2 number of seconds

Parameter 3 number of rows processed

Probable Cause This is an informational message.

Error 1000253 "Cannot drop the constraint '%1'."

Constant EMSG_ALTER_DROP_CONSTRAINT

SAP Sybase Error Number 20913

SQL State QDC53

SQL Code -1000253L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Constraint name.

Probable Cause IQ is unable to drop the named constraint because the index associ-
ated with the constraint could not be found or opened.

Warning 1000254 "\t%1 Rows, JP%2, %3 Seconds"

Constant EMSG_CLBK_JOINIDXNRECS

SAP Sybase Error Number 20914

SQL State 01C54

SQL Code 1000254L

ODBC 2 State OK

682 SAP Sybase IQ

Errors and Warnings

Warning 1000254 "\t%1 Rows, JP%2, %3 Seconds"

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 rows

Parameter 2 explanation of %2

Parameter 3 seconds

Probable Cause This is an informational message displayed in the context of other

messages.

Warning 1000255 "Join Record Rejected: '%1', duplicate rows in 1st table.
\nRow# %2 & %3, row %4 rejected."

Constant EMSG_CLBK_JOINIDXRECORDREJECTED

SAP Sybase Error Number 20915

SQL State 01C55

SQL Code 1000255L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 rejected record

Parameter 2 duplicate row number

Parameter 3 duplicate row number

Parameter 4 rejected row

Probable Cause This is an informational message describing duplicate rows encoun-

tered.

Warning 1000256 "Join virtual table '%1'. \nTotal rows rejected: %2"

Constant EMSG_CLBK_JOINIDXREJECTEDTOTAL

SAP Sybase Error Number 20916

SQL State 01C56

SQL Code 1000256L

SAP Sybase IQ Error Messages 683

Errors and Warnings

Warning 1000256 "Join virtual table '%1'. \nTotal rows rejected: %2"

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 Join virtual table name

Parameter 2 number of records rejected

Probable Cause This is an informational message displayed in context with other

messages.

Warning 1000257 "Delete of %1 rows started for table: "

Constant EMSG_CLBK_DELETESTART

SAP Sybase Error Number 20917

SQL State 00C57

SQL Code 1000257L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 number of rows

Probable Cause This is an informational message foretelling the number of rows to be

deleted from a table.

Warning 1000258 "Portions of the insert/load will be single threaded."

Constant EMSG_CLBK_INSERT_SINGLE_THREADED1

SAP Sybase Error Num- 20918

ber

SQL State QDC58

SQL Code 1000258L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

684 SAP Sybase IQ

Errors and Warnings

Warning 1000258 "Portions of the insert/load will be single threaded."

Probable Cause The load will proceed, but portions of it will be done serially. This can be
caused by constraining the amount of memory available to the load with
the LOAD_MEMORY_MB option; executing a variable length load
without row delimiters; or executing a partial width, variable length
load.

Warning 1000259 "\nDelete of %1 rows completed for table: %2, %3

seconds."

Constant EMSG_CLBK_DELETEDONE

SAP Sybase Error Number 20919

SQL State 01C59

SQL Code 1000259L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 number of rows deleted

Parameter 2 table name

Parameter 3 number of seconds to do the delete

Probable Cause This is an informational message displayed at the end of a delete.

Error 1000260 "ALTER DBSPACE <dbspace-name> ADD <number> is not

supported. %1"

Constant EMSG_ALTER_ADD_NOTSUPPORTED

SAP Sybase Error Number 20920

SQL State QDC60

SQL Code -1000260L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 685

Errors and Warnings

Error 1000260 "ALTER DBSPACE <dbspace-name> ADD <number> is not

supported. %1"

Probable Cause For a Sybase IQ database, one can add space to a database only using
the CREATE DBSPACE command. The size of existing dbspaces
cannot be changed.

Error 1000261 "A Sybase IQ system dbspace, '%2', cannot be renamed.

%1"

Constant EMSG_ALTER_CANT_RENAME_DBSPACE

SAP Sybase Error Number 20921

SQL State QDC61

SQL Code -1000261L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause You cannot rename a dbspace in a Sybase IQ database.

Messages 1000262 through 1000281

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000262 "You cannot specify BLANK PADDING OFF for CREATE
DATABASE. %1"

Constant EMSG_BLANKPADDINGOFF

SAP Sybase Error Number 20922

SQL State QDC62

SQL Code -1000262L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

686 SAP Sybase IQ

Errors and Warnings

Error 1000262 "You cannot specify BLANK PADDING OFF for CREATE
DATABASE. %1"

Parameter 1 Location of the exception.

Probable Cause The BLANK PADDING OFF clause is not valid while creating a
Sybase IQ database.

Error 1000263 "Undo failure for row %2. Statement will rollback to
statement before the first insert..values. %1"

Constant EMSG_UNDO_UNDO_FAILED

SAP Sybase Error Num- 20973

ber

SQL State QDC63

SQL Code -1000263L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 row for which the 'undo' operation failed

Probable Cause There was a unrecoverable error encountered while attempting to undo
an 'insert' operation for the specified row. Consequently, the statement
now rolls back to the first insert..values statement that occurred since
the most recent commit, rollback, or non-insert..values command.

Error 1000264 "Ambiguous index name '%2'. Please specify owner. %1"

Constant EMSG_INDEXAMBIGUOUS

SAP Sybase Error Number 21077

SQL State QDB04

SQL Code -1000264L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

SAP Sybase IQ Error Messages 687

Errors and Warnings

Error 1000264 "Ambiguous index name '%2'. Please specify owner. %1"

Parameter 1 location of the exception

Parameter 2 Name of ambiguous index

Probable Cause The specified index name is shared by more than one owner. The
owner can be specified as OWNER.TABLE.INDEX

Error 1000265 "Index '%2' not found. %1"

Constant EMSG_INDEX_NOTFOUND

SAP Sybase Error Number 21078

SQL State QDB05

SQL Code -1000265L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of user specified index

Probable Cause The specified index could not be opened. Either the index does not
exists or the name format is incorrect The index name must follow the
format [OWNER.]TABLE.INDEX

Error 1000266 "Table '%2' not found. %1"

Constant EMSG_TABLE_NOTFOUND

SAP Sybase Error Number 21079

SQL State QDB09

SQL Code -1000266L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of user specified table

688 SAP Sybase IQ

Errors and Warnings

Error 1000266 "Table '%2' not found. %1"

Probable Cause The specified table could not be opened. Either the table does not
exists or the name format is incorrect The table name must follow the
format [OWNER.]TABLE

Error 1000267 "Cannot convert '%2' to an integer percent. %1"

Constant EMSG_RESOURCE_CONVERROR

SAP Sybase Error Number 21080

SQL State QDB07

SQL Code -1000267L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Percent specified for RESOURCES

Probable Cause The percent must be an integer value

Error 1000268 "The target '%2' overlaps an earlier target. %1"

Constant EMSG_TARGETS_OVERLAP

SAP Sybase Error Number 21081

SQL State QDB08

SQL Code -1000268L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of table or index

Probable Cause The user cannot specify an index or table multiple times. This also
applies to an index that was already included by specifying its table.

SAP Sybase IQ Error Messages 689

Errors and Warnings

Error 1000269 "DBCC: Multiple modes specified with a write mode. %1"

Constant EMSG_DBCC_MULTI_WRITE_MODES

SAP Sybase Error Number 21082

SQL State QDB59

SQL Code -1000269L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause The user can only specify one mode if a mode that updates the data-
base is present. Update modes are dbcc command REPAIR, server
switch -iqdrplks, database options Convert_HG_To_1242 and Con-
vert_Varchar_To_1242

Error 1000270 "DBCC: FP Recreate failed for index '%2'. %1"

Constant EMSG_DBCC_FP_RECREATE_FAILED

SAP Sybase Error Number 21083

SQL State QDB60

SQL Code -1000270L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of index

Probable Cause If an FP re-create fails, the command must rollback

Error 1000271 "Table '%2' is a temporary table, a view, or not an IQ table.

%1"

Constant EMSG_NOT_IQ_TABLE

SAP Sybase Error Number 21084

690 SAP Sybase IQ

Errors and Warnings

Error 1000271 "Table '%2' is a temporary table, a view, or not an IQ table.

%1"

SQL State QDB61

SQL Code -1000271L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of user specified table

Probable Cause The specified table was opened, but it was a non-IQ or temporary
table or a view. Only non-temporary IQ tables can be processed.

Error 1000272 "Invalid table name '%2'. %1"

Constant EMSG_INVALID_TABLE_NAME

SAP Sybase Error Number 21085

SQL State QDB63

SQL Code -1000272L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of user specified table

Probable Cause The table name must follow the format [OWNER.]TABLE

Error 1000273 "Invalid index name '%2'. %1"

Constant EMSG_INVALID_INDEX_NAME

SAP Sybase Error Number 21086

SQL State QDB64

SQL Code -1000273L

SAP Sybase IQ Error Messages 691

Errors and Warnings

Error 1000273 "Invalid index name '%2'. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Name of user specified index

Probable Cause The index name must follow the format [OWNER.]TABLE.INDEX

Error 1000274 "DBCC: Upgrade options can be used only with CHECK or
REPAIR mode. %1"

Constant EMSG_DBCC_UPGRADE_OPTIONS

SAP Sybase Error Number 21087

SQL State QDB65

SQL Code -1000274L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Probable Cause Upgrade options (such as Convert_HG_To_1242) can be used only

with CHECK or REPAIR. They cannot be used with ALLOCATION.

Error 1000275 "Cannot process object '%2' at the current transaction

level. %1"

Constant EMSG_FUTUREVERSION

SAP Sybase Error Number 21088

SQL State QDB68

SQL Code -1000275L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

692 SAP Sybase IQ

Errors and Warnings

Error 1000275 "Cannot process object '%2' at the current transaction

level. %1"

Parameter 1 Location of the exception.

Parameter 2 Name of the object that cannot be processed.

Probable Cause The requested object cannot be opened because it was created by a
future transaction. A COMMIT or ROLLBACK must be issued be-
fore the object can be opened

Error 1000276 "At least one mode and target must be specified. %1"

Constant EMSG_NOTHING_TO_DO

SAP Sybase Error Number 21094

SQL State QDB69

SQL Code -1000276L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Probable Cause DBCC has no default target or mode. The user must explicitly specify
both a mode and target.

Error 1000277 "\"dropleaks {database|dbspace dbspace-name}\" is the

only command allowed in drop leaks mode. %1"

Constant EMSG_DBCC_DROPLEAKS_COMMAND

SAP Sybase Error Number 21095

SQL State QDB70

SQL Code -1000277L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

SAP Sybase IQ Error Messages 693

Errors and Warnings

Error 1000277 "\"dropleaks {database|dbspace dbspace-name}\" is the

only command allowed in drop leaks mode. %1"

Probable Cause Modes are restricted to avoid long DBCC sessions during forced
recovery

Error 1000278 "\"resetclks\" must be run in single-node mode with

\"allocation database\". %1"

Constant EMSG_DBCC_RESETCLKS_COMMAND

SAP Sybase Error Number 21096

SQL State QDB71

SQL Code -1000278L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Probable Cause resetclks is restricted to allocation mode and single-node mode, and
requires checking entire DB

Error 1000279 "Column '%2' must be included in the insert. It is part of a

multicolumn index. %1"

Constant EMSG_INSRT_MISSING_COLUMN_ON_INSERT

SAP Sybase Error Number 21108

SQL State QDB99

SQL Code -1000279L

ODBC 2 State ERROR

Messages 1000282 through 1000303

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000282 "DBCC must be restricted to the MAIN or LOCAL store only.
%1"

Constant EMSG_DBCC_ONEMPXSTORE

SAP Sybase IQ Error Messages 695

Errors and Warnings

Error 1000282 "DBCC must be restricted to the MAIN or LOCAL store only.
%1"

SAP Sybase Error Number 21116

SQL State QDB72

SQL Code -1000282L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Probable Cause DBCC is restricted to either the main or the local store only. It may not
combine checking of tables in both main and local in the same dbcc
run.

Error 1000283 "Identity/Autoincrement Column value range exceeded for

column %2. %1"

Constant EMSG_IDENTITY_EXCEEDS_RANGE

SAP Sybase Error Num- 20030

ber

SQL State QDC65

SQL Code -1000283L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause Data overflow: An Identity/Autoincrement Column has reached its max-
imum value. To correct this create a new table in which the datatype of the
new Identity/Autoincrement Column is larger and copy this table into the
new table. Alternatively add a new Identity/Autoincrement Column to
the table with a larger datatype and delete the old one.

696 SAP Sybase IQ

Errors and Warnings

Error 1000284 "Identity/Autoincrement Column value for column %2

must be positive. %1"

Constant EMSG_IDENTITY_VALUE_MUST_BE_POSITIVE

SAP Sybase Error Number 20032

SQL State QDC66

SQL Code -1000284L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause All values in Identity/Autoincrement Columns must be positive. To

correct this, only use positive values when manually inserting into
Identity/Autoincrement Columns.

Error 1000285 "The value specified for the Identity/Autoincrement

Column %2 exceeds the range of its datatype. %1"

Constant EMSG_VALUE_TOO_LARGE

SAP Sybase Error Number 20034

SQL State QDC67

SQL Code -1000285L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause The value specified does not fit in the Identity/Autoincrement Col-
umn. To correct this, choose a smaller value

SAP Sybase IQ Error Messages 697

Errors and Warnings

Error 1000286 "Invalid table argument %2 to sp_iq_reset_identity, Table

has no Identity/Autoincrement Column. %1"

Constant EMSG_TABLE_HAS_NO_IDENTITY

SAP Sybase Error Number 20035

SQL State QDC68

SQL Code -1000286L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 name of table

Probable Cause Table's without Identity/Autoincrement Columns cannot be used in

calls to stored procedure sp_iq_reset_identity.

Error 1000287 "Invalid table argument %2 to sp_iq_reset_identity, Table

cannot be a JVT. %1"

Constant EMSG_NO_JVT_RESET_IDENTITY

SAP Sybase Error Number 20036

SQL State QDC69

SQL Code -1000287L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause Tables of type JVT are not allowed as arguments to the stored pro-
cedure sp_iq_reset_identity

Error 1000288 "Invalid table argument %2 for set option 'identity_insert',

Table cannot be a JVT. %1"

Constant EMSG_TABLE_CANNOT_BE_JVT

698 SAP Sybase IQ

Errors and Warnings

Error 1000288 "Invalid table argument %2 for set option 'identity_insert',

Table cannot be a JVT. %1"

SAP Sybase Error Number 20037

SQL State QDC70

SQL Code -1000288L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause Tables of type JVT are not allowed as a value for the set option
'identity_insert'

Error 1000289 "Invalid table argument %2 for set option 'identity_insert',

Table must be an IQ table. %1"

Constant EMSG_TABLE_MUST_BE_IQ_IDENTITY_INSERT

SAP Sybase Error Number 20038

SQL State QDC71

SQL Code -1000289L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause Only IQ tables are allowed as an argument value to the set option
'identity_insert'

Error 1000290 "Invalid table argument %2 for stored procedure

sp_iq_reset_identity, Table must be an IQ Table. %1"

Constant EMSG_TABLE_MUST_BE_IQ_RESET_IDENTITY

SAP Sybase Error Number 20039

SAP Sybase IQ Error Messages 699

Errors and Warnings

Error 1000290 "Invalid table argument %2 for stored procedure

sp_iq_reset_identity, Table must be an IQ Table. %1"

SQL State QDC72

SQL Code -1000290L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause Only IQ tables are allowed as a table argument to the stored procedure
sp_iq_reset_identity

Error 1000291 "You do not have insert permission on table %2. %1"

Constant EMSG_NO_PERM_IDENTITY_INSERT

SAP Sybase Error Number 20041

SQL State QDC73

SQL Code -1000291L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause You cannot set the option 'identity_insert' to a table for which you do
not have insert permission

Error 1000292 "Invalid use of set option 'identity insert'. Table %2 does
not have an Identity/Autoincrement Column. %1"

Constant EMSG_PARAM_TABLE_HAS_NO_IDENTITY

SAP Sybase Error Number 20474

SQL State QDC74

700 SAP Sybase IQ

Errors and Warnings

Error 1000292 "Invalid use of set option 'identity insert'. Table %2 does
not have an Identity/Autoincrement Column. %1"

SQL Code -1000292L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 table name

Probable Cause the set option 'identity insert' cannot be used on a table without an
Identity/Autoincrement Column.

Error 1000293 "Cannot insert or update Column %2: set option

'identity_insert' to the specific table name containing the
identity column to be modified. %1"

Constant EMSG_IDENTITY_INSERT_IS_OFF

SAP Sybase Error Number 20644

SQL State QDC75

SQL Code -1000293L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 column name

Probable Cause set option 'identity_insert' must be set to the specific table for which
you want to insert or update an Identity column. To turn it on use set
identity_insert <table_name>

Error 1000294 "Cannot set 'identity_insert', it is already on for a different

table. %1"

Constant EMSG_IDENTITY_INSERT_ON_FOR_OTHER

SAP Sybase Error Num- 20645

ber

SAP Sybase IQ Error Messages 701

Errors and Warnings

Error 1000294 "Cannot set 'identity_insert', it is already on for a different

table. %1"

SQL State QDC76

SQL Code -1000294L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Probable Cause the set option 'identity_insert' can only be set for one table at a time. To
set it for a different table, first turn it off using 'set identity_insert '' ' then
set it to the desired table.

Error 1000295 "Invalid table name %2 specified for option

'identity_insert'. %1"

Constant EMSG_INVALID_TAB_NAME

SAP Sybase Error Number 20646

SQL State QDC77

SQL Code -1000295L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 table name

Probable Cause The table associated with the table name specified for the 'identi-
ty_insert' option could not be found.

Error 1000296 " Invalid load specification for LOAD ... FORMAT BCP. %1"

Constant EMSG_INVALIDLOADSPECFORBCPLOAD

SAP Sybase Error Number 21124

SQL State QDC78

SQL Code -1000296L

702 SAP Sybase IQ

Errors and Warnings

Error 1000296 " Invalid load specification for LOAD ... FORMAT BCP. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Probable Cause The user specified a load specification that is not supported with
FORMAT BCP option.

Warning 1000297 "%1. Message logging stopped."

Constant EMSG_SQL_IQMSG_MANAGEMENT_ERROR

SAP Sybase Error 21149

Number

SQL State QCB17

SQL Code 1000297L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 Reason behind stopping of message logging. Can be either due to disk
error, or due to message log management error.

Probable Cause Message log management operation failed due to error in file renaming /
deletion / creation. Or log could not be written in the IQMSG file because
some DISK IO error occurred.

Warning 1000298 " Message logging resumed."

Constant EMSG_MESSAGE_LOGGING_RESUMED

SAP Sybase Error Number 21150

SQL State QCB18

SQL Code 1000298L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

SAP Sybase IQ Error Messages 703

Errors and Warnings

Probable Cause Table of TBLTYP_PARTITION type cannot be used.

Messages 1000304 through 1000325

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000304 " Cannot drop a partition key column. %1"

Constant EMSG_CAT_CANNOT_DROP_PARTITION_KEY

SAP Sybase Error Number 21157

SQL State QDC84

SQL Code -1000304L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Probable Cause Can not drop a partition key column.

Error 1000305 " Allocation failure. %1"

Constant EMSG_DBCC_ALLOCATION_FAILURE

SAP Sybase Error Number 21158

SAP Sybase IQ Error Messages 705

Errors and Warnings

Error 1000305 " Allocation failure. %1"

SQL State QDC85

SQL Code -1000305L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause DBCC allocation failure

Error 1000306 " Different DB space, cannot merge partition %2 into %3.
%1"

Constant EMSG_CAT_PARTITION_MERGE_ERROR

SAP Sybase Error Number 21164

SQL State QDC86

SQL Code -1000306L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 partition1

Parameter 3 partition2

Probable Cause Cannot merge Partition partition name 1 into Partition partition
name2 in different dbspaces

Error 1000307 " No data move is allowed, cannot split partition %2. %1"

Constant EMSG_CAT_PARTITION_SPLIT_ERROR

SAP Sybase Error Number 21165

SQL State QDC87

SQL Code -1000307L

706 SAP Sybase IQ

Errors and Warnings

Error 1000307 " No data move is allowed, cannot split partition %2. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 partition1

Probable Cause Cannot split Partition partition name 1 into Partition partition name2
and Partition name3 as the split requires to move data.

Error 1000308 " Boundary value for the partition %2 cannot be changed.
%1"

Constant EMSG_CAT_PARTITION_SPLIT_BOUNDARY_ERROR

SAP Sybase Error Number 21166

SQL State QDC88

SQL Code -1000308L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 partition name1

Probable Cause Cannot change boundary value for split Partition partition name 1 into
(partition-decl-1, partition-decl-2). Boundary value for partition-
decl-2 must be the same as partition name 1.

Error 1000309 " Not all partitions in each column are in same dbspace,
cannot unpartition %2. %1"

Constant EMSG_CAT_UNPARTITION_ERROR

SAP Sybase Error Number 21167

SQL State QDC89

SQL Code -1000309L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 707

Errors and Warnings

Error 1000309 " Not all partitions in each column are in same dbspace,
cannot unpartition %2. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 tablename

Probable Cause Cannot alter partitioned table to an unpartitioned table as not all
partitions in each column are in the same dbspace.

Error 1000310 " Cannot truncate table partition on a non-partitioned table

%2. %1"

Constant EMSG_TABLE_NOT_PARTITIONED

SAP Sybase Error Number 21168

SQL State QDC90

SQL Code -1000310L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 tablename

Probable Cause Cannot truncate table partition on a non-partitioned table.

Error 1000311 " '%2' is not an IQ DBSPACE. %1"

Constant EMSG_NO_SUCH_IQ_DBSPACE

SAP Sybase Error Number 21169

SQL State QDC91

SQL Code -1000311L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

708 SAP Sybase IQ

Errors and Warnings

Error 1000311 " '%2' is not an IQ DBSPACE. %1"

Parameter 1 location of exception

Parameter 2 supplied dbspace name

Probable Cause Specified dbspace does not exist or is a catalog dbspace.

Error 1000312 " ALTER INDEX MOVE can not move FP indexes.
Command failed for %2. Use ALTER TABLE MOVE
COLUMN instead. %1"

Constant EMSG_CANNOT_MOVE_FP_INDEX

SAP Sybase Error Number 21170

SQL State QDC92

SQL Code -1000312L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 Index name

Probable Cause ALTER INDEX MOVE command does not move FP indexes. Use
ALTER TABLE MOVE COLUMN instead.

Error 1000314 " All rows must be in the first partition. %1"

Constant EMSG_CAT_PARTITION_ERROR

SAP Sybase Error Number 21173

SQL State QDC94

SQL Code -1000314L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

SAP Sybase IQ Error Messages 709

Errors and Warnings

Error 1000314 " All rows must be in the first partition. %1"

Probable Cause Cannot alter unpartitioned table to a partitioned table as not all rows in
the first partition.

Error 1000315 " Cannot drop the last partition of a partitioned table. %1"

Constant EMSG_CAT_CANNOT_DROP_LAST_PARTITION_ERROR

SAP Sybase Error Number 21174

SQL State QDC95

SQL Code -1000315L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Probable Cause Cannot drop the last partition of a partitioned table.

Error 1000316 "The NoExec option is set. The current operation will be
rolled back. %1"

Constant EMSG_NOEXEC_OP_PROHIBITED

SAP Sybase Error Number 21175

SQL State QDC96

SQL Code -1000316L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Certain operations will not be allowed whenever the NoExec option is
set. They are: Alter table Split Partition & Alter Table Partition

Error 1000317 "The current operation is not allowed on RO partition. %1"

Constant EMSG_ROPARTITION_OP_PROHIBITED

710 SAP Sybase IQ

Errors and Warnings

Error 1000317 "The current operation is not allowed on RO partition. %1"

SAP Sybase Error Number 21181

SQL State QDC97

SQL Code -1000317L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Alter table drop/split/merge on a RO partition is not allowed.

Error 1000318 "Unexpected type encountered for column '%2'. %1"

Constant EMSG_UNEXPECTED_COLUMN_TYPE

SAP Sybase Error Number 21182

SQL State QDC98

SQL Code -1000318L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Exception Location

Parameter 2 Column Name

Probable Cause Parse tree contains an expected column type.

Error 1000319 "Server (%2) is no longer a Multiplex coordinator. %1"

Constant EMSG_MPX_NODE_NOT_COORDINATOR

SAP Sybase Error Number 21185

SQL State QDC99

SQL Code -1000319L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 711

Errors and Warnings

Error 1000319 "Server (%2) is no longer a Multiplex coordinator. %1"

Severity Code 14 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Probable Cause Specified server is no longer a Multiplex coordinator.

Error 1000320 "Table with table id %2 no longer exists. %1"

Constant EMSG_INVALID_TABLE_ID

SAP Sybase Error Number 21189

SQL State QDD00

SQL Code -1000320L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Table identifier

Probable Cause There is no table with the given table id. It would have been dropped.

Error 1000321 "dropleaks is not allowed in multiplex mode. %1"

Constant EMSG_DBCC_DROPLEAKS_NEED_SIMPLEX

SAP Sybase Error Number 22006

SQL State QDB85

SQL Code -1000321L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Probable Cause Dropleaks require server to be started in simplex configuration

712 SAP Sybase IQ

Errors and Warnings

Error 1000322 "Use CREATE DBSPACE USING FILE syntax for creating IQ
dbspaces. %1"

Constant EMSG_CREATE_DBSPACE_FILE_SYNTAX_NOT_USED

SAP Sybase Error Num- 22007

ber

SQL State QDB86

SQL Code -1000322L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause In Atomic IQ dbspaces can be created using the FILE Syntax for create
dbspace. Old pre-atomic syntax can be used to create catalog store
dbspaces only.

Error 1000324 "Maximum secondary node license limit reached. Cannot

add new secondary node. %1"

Constant EMSG_MPX_MAX_SECONDARY_LICENSE_EXCEEDED

SAP Sybase Error Number 21193

SQL State QDD03

SQL Code -1000324L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause New secondary node cannot be added since the license limit for add-
ing a new secondary node has been reached.

Error 1000325 "%2 node cannot be made a failover node. %1"

Constant EMSG_MPX_CANNOT_BE_FAILOVER

SAP Sybase Error Number 21194

SAP Sybase IQ Error Messages 713

Errors and Warnings

Error 1000325 "%2 node cannot be made a failover node. %1"

SQL State QDD04

SQL Code -1000325L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Could be either Excluded or Coordinator

Probable Cause An excluded or coordinator node cannot be made a failover node.

Messages 1000326 through 1001007

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1000326 "%2 of Coordinator node cannot be changed. %1"

Constant EMSG_MPX_COORD_ATTR_CANNOT_CHANGE

SAP Sybase Error Number 21195

SQL State QDD05

SQL Code -1000326L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Could be either ROLE or STATUS

Probable Cause ROLE or STATUS of Coordinator node cannot be changed.

Error 1000327 "Failover node cannot be Excluded. %1"

Constant EMSG_MPX_CANNOT_EXCLUDE_FAILOVER

SAP Sybase Error Number 21196

SQL State QDD06

714 SAP Sybase IQ

Errors and Warnings

Error 1000327 "Failover node cannot be Excluded. %1"

SQL Code -1000327L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A designated failover node cannot be Excluded.

Error 1000328 "%2 node cannot be dropped. %1"

Constant EMSG_MPX_CANNOT_BE_DROPPED

SAP Sybase Error Number 21197

SQL State QDD07

SQL Code -1000328L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Could be either COORDINATOR or FAILOVER

Probable Cause A Coordinator or a Failover node cannot be dropped from the mul-
tiplex configuration.

Error 1000329 "The move target %2 is already in the specified dbspace.

%1"

Constant EMSG_MOVE_TARGET_DBSPACE_UNCHANGED

SAP Sybase Error Number 21198

SQL State QDD02

SQL Code -1000329L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 715

Errors and Warnings

Error 1000329 "The move target %2 is already in the specified dbspace.

%1"

Severity Code 14 on page 2

Parameter 1 Target name to be moved.

Parameter 2 Location of the exception.

Probable Cause The move target for alter table or alter index is already in the specified
dbspace.

Error 1000330 "Default value %2 cannot be used as a LOAD default value.

%1"

Constant EMSG_INVALIDLOADDEFAULTVALUE

SAP Sybase Error Number 21199

SQL State QDD17

SQL Code -1000330L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 load default value

Probable Cause Specified default value cannot be used as a LOAD default value.

Error 1000331 "The requested FP style (%1) for %2 cannot be rebuilt. It

will be rebuilt as %3."

Constant EMSG_CANNOT_REBUILD_FP

SAP Sybase Error Number 21204

SQL State QDD19

SQL Code -1000331L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

716 SAP Sybase IQ

Errors and Warnings

Error 1000331 "The requested FP style (%1) for %2 cannot be rebuilt. It

will be rebuilt as %3."

Parameter 1 Requested FP style

Parameter 2 FP index

Parameter 3 Actual Rebuilt FP style

Probable Cause The requested FP style cannot be rebuilt. Increase main cache or set
FP_Lookup_Size_PPM to a higher percentage for 3-byte FP.

Error 1000332 "Odd length of binary data value detected on column %2 -

%1"

Constant EMSG_ODDNUMBER_NIBBLES

SAP Sybase Error Number 21206

SQL State QDD20

SQL Code -1000332L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the column where the error occurs

Probable Cause When loading hexadicimal data into BLOB, the total number of nib-
bles has to be an even number. If an odd number is detected, the load
engine will rollback. This restriction does not apply to binary and
varbinary data type.

Error 1000333 "DBCC IQ_SHARED_TEMP dbspace target not allowed

with other targets. %1"

Constant EMSG_DBCC_SHTEMP_MODE

SAP Sybase Error Number 22021

SQL State QDD22

SQL Code -1000333L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 717

Errors and Warnings

Error 1000333 "DBCC IQ_SHARED_TEMP dbspace target not allowed

with other targets. %1"

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Probable Cause When specifying the IQ_SHARED_TEMP dbspace as a DBCC

mode target, no other targets may be specified.

Error 1000334 "Unsupported DBCC dbspace target \"%2\". %1"

Constant EMSG_DBCC_UNSUPPORTED_DBSPACE

SAP Sybase Error Number 22022

SQL State QDD23

SQL Code -1000334L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 Location of the exception.

Parameter 2 Dbspace name.

Probable Cause DBCC Does not support checking modes on this dbspace target.

Error 1000335 "Cannot add writer when coordinator started with -

iqmpx_nowr %1"

Constant EMSG_SUMAVGOVERFLOW

SAP Sybase Error Number 20509

SQL State QFA00

SQL Code -1001000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001001 "DFE Typechecking error %1"

Constant EMSG_TCHECKERROR

SAP Sybase Error Number 20510

SQL State QFA01

SQL Code -1001001L

SAP Sybase Error Number 20513

SQL State QFA04

SQL Code -1001004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 721

Errors and Warnings

Error 1001004 "Data exception - substring error. %1"

Probable Cause No additional information available.

Error 1001005 "Data exception - string length error. %1"

Constant EMSG_STRINGLENERROR

SAP Sybase Error Number 20514

SQL State QFA05

SQL Code -1001005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001006 "Data exception - data type conversion is not possible. %1"

Constant EMSG_TYPECONVERSION

SAP Sybase Error Number 20515

SQL State QFA06

SQL Code -1001006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001007 "Data exception - operation resulted in division by zero.

%1"

Constant EMSG_DIVIDEBYZERO

SAP Sybase Error Number 20516

SQL State QFA07

722 SAP Sybase IQ

Errors and Warnings

Error 1001007 "Data exception - operation resulted in division by zero.

%1"

SQL Code -1001007L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

1001008 - 1006052

Messages 1001008 through 1001027

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1001008 "Data exception - invalid character data for cast. %1"

Constant EMSG_BADCASTVALUE

SAP Sybase Error Number 20517

SQL State QFA08

SQL Code -1001008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001009 "Data exception - string data, right truncation. %1"

Constant EMSG_TRUNCATEDSTRING

SAP Sybase Error Number 20518

SQL State QFA09

SAP Sybase IQ Error Messages 723

Error 1001011 "Data exception - argument must be DATE or DATETIME

%1"

Probable Cause No additional information available.

Error 1001012 "Internal state violation, please contact Sybase IQ support

%1"

Constant EMSG_INTERNALERROR

SAP Sybase Error Number 20521

SQL State QFA12

SQL Code -1001012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 18 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001013 "Invalid data type comparison %2, %1"

Constant EMSG_TYPECOMPAREERROR

SAP Sybase Error Number 20522

SQL State QFA13

SQL Code -1001013L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 SA parse source code line

Probable Cause No additional information available.

Error 1001014 "Data conversion failed %1"

Constant EMSG_DATACONVERSIONERROR

SAP Sybase IQ Error Messages 725

Errors and Warnings

Error 1001014 "Data conversion failed %1"

SAP Sybase Error Number 20523

SQL State QFA14

SQL Code -1001014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001015 "QUARTER, WEEK and MILLISECOND dateparts are not

currently supported %1"

Constant EMSG_DATEPARTNOTSUPPORTED

SAP Sybase Error Number 20524

SQL State QFA15

SQL Code -1001015L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001016 "Invalid datepart"

Constant EMSG_INVALIDDATEPARTTYPE

SAP Sybase Error Number 20525

SQL State QFA16

SQL Code -1001016L

ODBC 2 State ERROR

ODBC 3 State ERROR

726 SAP Sybase IQ

Errors and Warnings

Error 1001016 "Invalid datepart"

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1001017 "IQ Internal error in exception code. %1 "

Constant EMSG_PROGERRORINEXCEPTION

SAP Sybase Error Number 20526

SQL State QFA17

SQL Code -1001017L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 18 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001018 "INSERT ... VALUES ... accepts only constant expressions
as values %2, %1"

Constant EMSG_BADINSERTVALUES

SAP Sybase Error Number 20527

SQL State QFA18

SQL Code -1001018L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 SA parse source code line

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 727

Errors and Warnings

Error 1001019 "Function not supported on varchars longer than 32767

%2, %1"

Constant EMSG_FUNCNOTSUPONLVCHAR

SAP Sybase Error Number 20528

SQL State QFA19

SQL Code -1001019L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 SA parse source code line

Probable Cause No additional information available.

Error 1001020 "Incompatible data types %2, %1"

Constant EMSG_UNIONNOTCOMPATIBLE

SAP Sybase Error Number 20529

SQL State QFA20

SQL Code -1001020L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 SA parse source code line

Probable Cause No additional information available.

Error 1001021 "DFO State machine error %1"

Constant EMSG_DFOSTATE

SAP Sybase Error Number 20530

SQL State QFA21

728 SAP Sybase IQ

Error 1001023 "Query rejected because it exceeds resource:

Query_Temp_Space_Limit %1"

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001024 "Metadata for column %2 is internally inconsistent (%3):

database may be corrupted %1"

Constant EMSG_INCONSISTENT_INDEX_INFO

SAP Sybase Error Number 20533

SQL State QFA24

SQL Code -1001024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Parameter 3 what was apparently corrupted

Probable Cause No additional information available.

Error 1001025 "Function not currently supported. %2 %1"

Constant EMSG_DFFUNCNOTSUPPORTED

SAP Sybase Error Number 20534

SQL State QFA25

SQL Code -1001025L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The SA code line

730 SAP Sybase IQ

Errors and Warnings

Error 1001025 "Function not currently supported. %2 %1"

Probable Cause No additional information available.

Warning 1001026 "%1"

Constant EMSG_DF_ONEPLANLINE

SAP Sybase Error Number 20535

SQL State QFA26

SQL Code 1001026L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 prefix and detail string

Probable Cause No additional information available.

Error 1001027 "Query rejected because plan exceeds stack space %1"

Constant EMSG_QUERY_NEAR_END_OF_STACK

SAP Sybase Error Number 20536

SQL State QFA27

SQL Code -1001027L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 731

Errors and Warnings

Messages 1001028 through 1001047

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1001028 "Query rejected because it exceeds resource:

Query_Rows_Returned_Limit %1"

Constant EMSG_QUERY_EXCEEDS_ROW_LIMIT

SAP Sybase Error Number 20537

SQL State QFA28

SQL Code -1001028L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 17 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001029 "Index metadata for %2 is internally inconsistent:

database may be corrupted %1"

Constant EMSG_INCONSISTENT_COLUMN_INFO

SAP Sybase Error Number 20538

SQL State QFA29

SQL Code -1001029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause No additional information available.

732 SAP Sybase IQ

Errors and Warnings

Error 1001030 "Feature, %2, is not supported. %1"

Constant EMSG_NOTIMPLEMENTED_W_ARG

SAP Sybase Error Number 20539

SQL State QFA2A

SQL Code -1001030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 feature name

Parameter 2 SA parse source code line

Probable Cause No additional information available.

Error 1001031 "Non-aggregate select/having (%2) must appear in the

group by %1"

Constant EMSG_INVALIDGROUPINGEXPR

SAP Sybase Error Number 20540

SQL State QFA2B

SQL Code -1001031L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 name of illegal expression

Parameter 2 location of the exception

Probable Cause No additional information available.

Error 1001032 "Thread stack ran past the end of its allocated stack space
%1"

Constant EMSG_THREAD_PAST_END_OF_STACK

SAP Sybase Error Num- 20541

ber

SAP Sybase IQ Error Messages 733

Errors and Warnings

Error 1001032 "Thread stack ran past the end of its allocated stack space
%1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 variable name

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 735

Errors and Warnings

Error 1001037 "Text-style CONTAINS left-hand arg must be a character

type column from a base table. %1"

Constant EMSG_CONTAINS_LHS

SAP Sybase Error Number 20546

SQL State QFA33

SQL Code -1001037L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001038 "Text-style CONTAINS right-hand arglist must be string

constants each containing exactly one word. %1"

Constant EMSG_CONTAINS_RHS

SAP Sybase Error Number 20547

SQL State QFA34

SQL Code -1001038L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001039 "CONTAINS right-hand arglist too large. %1"

Constant EMSG_CONTAINS_RHS2LARGE

SAP Sybase Error Number 20548

SQL State QFA35

SQL Code -1001039L

736 SAP Sybase IQ

Errors and Warnings

Error 1001039 "CONTAINS right-hand arglist too large. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001040 "String contains a multi-byte character fragment. %1"

Constant EMSG_CHARFRAG

SAP Sybase Error Number 20549

SQL State QFA36

SQL Code -1001040L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001041 "Word-style CONTAINS left-hand arg must have a WD

index. %1"

Constant EMSG_CONTAINS_NOINDEX

SAP Sybase Error Number 20550

SAP Sybase Error Number 20553

SQL State QFA40

SQL Code -1001044L

738 SAP Sybase IQ

Errors and Warnings

Error 1001044 "Incompatible datatypes in ARGN. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1001045 "Invalid argument in Extract option: %2. %1"

Constant EMSG_BAD_EXTRACT_WARG

SAP Sybase Error Number 20554

SQL State QFA41

SQL Code -1001045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Invalid option

Probable Cause No additional information available.

Error 1001046 "Extract exceeds maximum supported row width of %2

(width %3). %1"

Constant EMSG_EXTRACT_TOO_WIDE_WARG

SAP Sybase Error Number 20555

SQL State QFA42

SQL Code -1001046L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 739

Errors and Warnings

Error 1001046 "Extract exceeds maximum supported row width of %2

(width %3). %1"

Parameter 2 maximum width supported

Parameter 3 current width

Probable Cause No additional information available.

Error 1001047 "%2. %1"

Constant EMSG_QUERY_GENERIC_WARG

SAP Sybase Error Number 20556

SQL State QFA43

SQL Code -1001047L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 error message

Probable Cause No additional information available.

Messages 1001048 through 1001067

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1001048 "To display a varbinary column > 32k you must set the
parameter Ase_Binary_Display to off. %1"

Constant EMSG_VARBIN_TOOBIG

SAP Sybase Error Number 20557

SQL State QFA44

SQL Code -1001048L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

740 SAP Sybase IQ

Errors and Warnings

Error 1001048 "To display a varbinary column > 32k you must set the
parameter Ase_Binary_Display to off. %1"

Parameter 1 location of the exception

Probable Cause cannot convert any varbinary > 32k to varchar.

Error 1001049 "Expression, \"%2\" changed datatypes between CURSOR

DESCRIBE and CURSOR OPEN from %3. The CURSOR
DESCRIBE needs to be rerun %1"

Constant EMSG_DATATYPE_CHANGE

SAP Sybase Error Number 20558

SQL State QFA45

SQL Code -1001049L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column number

Parameter 3 datatype info

Probable Cause Given a database's BLOCK SIZE and the number of blocks specified
by the user for the dbspace, the dbspace size (in bytes) would exceed
the OS's limit of bytes per file.

Error 1001050 "this row is too wide to extract. Reduce the row width to
less than %2 (iq page size) %1"

Constant EMSG_EXTRACT_ROW_TOO_WIDE

SAP Sybase Error Number 20559

SQL State QFA46

SQL Code -1001050L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 741

Errors and Warnings

Error 1001050 "this row is too wide to extract. Reduce the row width to
less than %2 (iq page size) %1"

Parameter 1 location of the exception

Parameter 2 this row width

Probable Cause An attempt was made to extract a row that is larger than this database's
pagesize.

Error 1001051 "Query returns %2 data > 2GB. Use %3 %1"

Constant EMSG_LOB_OVER_2G_W_ARG

SAP Sybase Error Number 21097

SQL State QFA47

SQL Code -1001051L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 long binary or long varchar data type

Parameter 2 function recommended

Parameter 3 SA parse source code line

Probable Cause No additional information available.

Error 1001052 "Parameter %2 must be long binary/varchar type. %3 %1"

Constant EMSG_ONLY_SUPPORT_LOB_W_ARG

SAP Sybase Error Number 21098

SQL State QFA48

SQL Code -1001052L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 lob argument name

742 SAP Sybase IQ

Errors and Warnings

Error 1001052 "Parameter %2 must be long binary/varchar type. %3 %1"

Parameter 2 recommended function name

Parameter 3 SA parse source code line

Probable Cause No additional information available.

Error 1001053 "Wrong number of parameters to function %2 %1"

Constant EMSG_WRONG_NUM_PARAMS_W_ARG

SAP Sybase Error Number 21099

SQL State QFA49

SQL Code -1001053L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 function name

Parameter 2 SA parse source code line

Probable Cause No additional information available.

Error 1001054 "You cannot specify long binary/varchar column in the

ORDER/GROUP by clause or in an aggregate function. %1"

Constant EMSG_LOB_NOT_ALLOWED_GROUP

SAP Sybase Error Number 21100

SQL State QFA50

SQL Code -1001054L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 743

Errors and Warnings

Warning 1001055 "An error occurred loading %1 column, %2, for %3, rowid
%4. "

Constant EMSG_LOB_LOAD_ERROR_WARN

SAP Sybase Error Number 21101

SQL State QFA51

SQL Code 1001055L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 long binary or long varchar data type

Parameter 2 FP index name

Parameter 3 secondary file name

Parameter 4 rowid

Probable Cause No additional information available.

Warning 1001056 "An error occurred extracting %1 column, %2, for %3. "

Constant EMSG_LOB_EXTRACT_ERROR_WARN

SAP Sybase Error Number 21102

SQL State QFA52

SQL Code 1001056L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 long binary or long varchar data type

Parameter 2 FP index name

Parameter 3 secondary file name

Probable Cause No additional information available.

744 SAP Sybase IQ

Errors and Warnings

Error 1001057 "You must use BFILE() to extract %2 column. %1"

Constant EMSG_LOB_EXTRACT_USE_BFILE

SAP Sybase Error Number 21103

SQL State QFA53

SQL Code -1001057L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 long binary or long varchar data type

Parameter 2 location of the exception

Probable Cause No additional information available.

Error 1001058 "The secondary file name, %2, is too long. %1"

Constant EMSG_LOB_SECONDARY_FILE_TOOLONG

SAP Sybase Error Number 21104

SQL State QFA54

SQL Code -1001058L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 14 on page 2

Parameter 1 secondary file name

Parameter 2 location of the exception

Probable Cause No additional information available.

Error 1001059 "IQ does not support ASE extended group by syntax (%2)
with join tables %1"

Constant EMSG_EXTGROUPINGWITHJOIN

SAP Sybase Error Number 21106

SQL State QFA2F

SAP Sybase IQ Error Messages 745

Errors and Warnings

Error 1001059 "IQ does not support ASE extended group by syntax (%2)
with join tables %1"

SQL Code -1001059L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 name of illegal expression

Parameter 2 location of the exception

Probable Cause No additional information available.

Error 1001060 "IQ does not support ASE extended group by columns
(%2) from view/derived table with distinct/group by/
aggregations %1"

Constant EMSG_EXTGROUPINGFROMVIEW

SAP Sybase Error Number 21107

SQL State QFA2G

SQL Code -1001060L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 name of illegal expression

Parameter 2 location of the exception

Probable Cause No additional information available.

Error 1001061 "extract error: incorrect \"%2\" size: valid sizes \"0 to %3\"
%1"

Constant EMSG_EXTRACT_ERROR

SAP Sybase Error Number 20560

SQL State QFA55

SQL Code -1001061L

746 SAP Sybase IQ

Errors and Warnings

Error 1001061 "extract error: incorrect \"%2\" size: valid sizes \"0 to %3\"
%1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 type of extract delimiter error

Parameter 3 max size

Probable Cause either a column delimeter or a row delimiter is of incorrect length

Error 1001062 "IQ does not support ASE extended group by syntax (%2)
with OLAP function %1"

Constant EMSG_EXTGROUPINGWITHOLAP

SAP Sybase Error Number 21120

SQL State QFA2H

SQL Code -1001062L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 name of illegal expression

Parameter 2 location of the exception

Probable Cause No additional information available.

Error 1001063 "Encrypt/Decrypt: Currently only AES algorithm is

supported."

Constant EMSG_ENCRYPT_ALGO_ERROR

SAP Sybase Error Number 20561

SQL State QFA56

SQL Code -1001063L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 747

Errors and Warnings

Error 1001063 "Encrypt/Decrypt: Currently only AES algorithm is

supported."

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause when the algorithm string is other than AES.

Error 1001064 "Decryption error: %2. %1"

Constant EMSG_DECRYPTION_ERROR

SAP Sybase Error Number 20562

SQL State QFA57

SQL Code -1001064L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 error message

Probable Cause An error occurred during decryption.

Error 1001065 "Encryption/Decryption for %2 datatype is not supported.

%1"

Constant EMSG_ENCRYPT_UNSUPPORTED_DATATYPE

SAP Sybase Error Number 20563

SQL State QFA58

SQL Code -1001065L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 datatype value which is not supported like float.

748 SAP Sybase IQ

Errors and Warnings

Error 1001065 "Encryption/Decryption for %2 datatype is not supported.

%1"

Probable Cause An error occurred during encryption/decryption.

Error 1001066 "Encrypt/Decrypt Error: %2. %1"

Constant EMSG_ENCRYPT_SIZE_ERROR

SAP Sybase Error Number 20564

SQL State QFA59

SQL Code -1001066L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 large input and key size not supported.

Probable Cause An error occurred during encryption/decryption.

Error 1001067 "Encrypt/Decrypt Error: %2. %1"

Constant EMSG_ENCRYPT_NULL_ERROR

SAP Sybase Error Number 20565

SQL State QFA60

SQL Code -1001067L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 key and algorithm string as null are not supported.

Probable Cause An error occurred during encryption/decryption.

SAP Sybase IQ Error Messages 749

Errors and Warnings

Messages 1001068 through 1002005

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1001068 "Datatype, %2 is not supported for this operation. %1"

Constant EMSG_UDF_PROGRAMMING_ERROR

SAP Sybase Error Number 20573

SQL State QFA65

SQL Code -1001072L

Error 1001100 "Load/insert/update/delete/RLV are not supported for 15.x char/

varchar/varbinary columns of width greater than 255 and LOB
datatypes. Please execute sp_iqrebuildindex first to convert the
index to IQ version 16. %1"

Constant EMSG_15_LVC_LOB_UPDATE_NOT_SUPPORTED

SAP Sybase Error 22150

Number

SQL State QSB92

SQL Code -1001100L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause When IQ 16.x engine attempts to load/insert/update data into a 15.x char/
varchar/varbinary greater than 255 or LOB FP index, this exception is thrown
to indicate that the operation is not allowed. It is required to run sp_iqrebuil-
dindex first so as to convert the index to IQ version 16.

Error 1001102 "RLV store merge already in progress for table %2. %1"

Constant EMSG_RV_MERGE_IN_PROGRESS

SAP Sybase Error Number 22038

SQL State QRA02

SQL Code -1001102L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The illegal merge string

Probable Cause There is already an RLV store merge in progress for this table. Only
one RLV merge is allowed at a time for an RLV table.

SAP Sybase IQ Error Messages 753

Errors and Warnings

Error 1001103 "Table %2 is not RLV enabled. %1"

Constant EMSG_RV_MERGE_NOT_RLV_ENABLED

SAP Sybase Error Num- 22039

ber

SQL State QRA03

SQL Code -1001103L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The table name

Probable Cause An RLV store merge was attempted on a table which was not RLV
enabled. Only tables which are RLV enabled may be merged.

Error 1001104 "Unable to perform merge, table %2 has too many fragments.
%1"

Constant EMSG_RV_MERGE_TOO_MANY_FRAGMENTS

SAP Sybase Error 22040

Number

SQL State QRA04

SQL Code -1001104L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause Long running transactions are keeping too many old fragments of the table
in memory. Table cannot be merged until the long running transactions
terminate.

Probable Cause BEGIN .. END PARALLEL IQ is not supported if any of the tables on
which (parallel) index is to be created is RLV enabled.

Error 1001108 "The option 'Revert_To_V15_Optimizer' is not supported

for queries involving RLV enabled tables"

Constant EMSG_RV_V15_CONFLICT

SAP Sybase Error Num- 22044

ber

SQL State QRA08

SQL Code -1001108L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Pre-Elan optimization is used with revert_to_v15_optimizer option,

query tree creation itself does not allow it if table is RLV enabled.

Error 1002000 "Unknown error: %1"

Constant EMSG_DATA_UNKNOWN

756 SAP Sybase IQ

Errors and Warnings

Error 1002000 "Unknown error: %1"

SAP Sybase Error Number 20502

SQL State QGA00

SQL Code -1002000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1002001 "Data has already been inserted into index %2 for row %3.
%1"

Constant EMSG_DATA_ALREADYINSERTED

SAP Sybase Error Number 20503

SQL State QGA01

SQL Code -1002001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1002002 " for IQ_ROWID row "

Constant EMSG_NOT_USED

SAP Sybase Error Number 20504

SQL State QGA02

SQL Code -1002002L

SAP Sybase IQ Error Messages 757

Errors and Warnings

Error 1002002 " for IQ_ROWID row "

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1002003 "Tried to insert a duplicate value into a unique index %2 on

row %3. %1"

Constant EMSG_DATA_DUPLICATEVALUE

SAP Sybase Error Number 20505

SQL State QGA03

SQL Code -1002003L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1002004 No message

Constant EMSG_DATA_DUPLICATEVALUE2_EMPTY_SLOT

SAP Sybase Error Number 20506

SQL State QGA04

SQL Code -1002004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

758 SAP Sybase IQ

Errors and Warnings

Error 1002005 "Tried to insert a null value into a non-null field %2 on row
%3. %1"

Constant EMSG_DATA_NONULLSALLOWED

SAP Sybase Error Number 20507

SQL State QGA05

SQL Code -1002005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Messages 1002006 through 1004004

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1002006 No message

Constant EMSG_DATA_NONULLSALLOWED2_EMPTY_SLOT

SAP Sybase Error Number 20508

SQL State QGA06

SQL Code -1002006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1003000 "Datatype %2, returned by Client Library, is not valid in

Sybase IQ. %1"

Constant EMSG_HQM_BAD_DATATYPE

SAP Sybase IQ Error Messages 759

Errors and Warnings

Error 1003000 "Datatype %2, returned by Client Library, is not valid in

Sybase IQ. %1"

SAP Sybase Error Num- 20172

ber

SQL State QHA00

SQL Code -1003000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 name of the CTLib datatype

Probable Cause Sybase IQ doesn't support a number of datatypes that ASE does (text or
image, for example). Refer to documentation for the respective prod-
ucts to see what datatypes are supported.

Error 1003001 "Cannot convert to Sybase IQ datatype: %2 from Client

Library datatype %3. %1"

Constant EMSG_HQM_CANT_CONVERT

SAP Sybase Error Number 20173

SQL State QHA01

SQL Code -1003001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 name of the IQ datatype

Parameter 3 name of the CTLib datatype

Probable Cause Error converting CSLIB datatype to IQ datatype.

760 SAP Sybase IQ

Errors and Warnings

Error 1003002 "CtLibrary Error: %2, Severity: %3, Origin: %4, Layer:
%5\nError Message: %6\nOS Error: %7, OS Message: %8.
%1"

Constant EMSG_HQM_CTLIB_ERROR

SAP Sybase Error Number 20174

SQL State QHA02

SQL Code -1003002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 CtLib error number

Parameter 3 CtLib severity number

Parameter 4 CtLib origin number

Parameter 5 CtLib layer number

Parameter 6 CtLib error message

Parameter 7 OS error number (optional)

Parameter 8 OS error message (optional)

Probable Cause General CTLIB/CSLIB error message. Refer to the CTLibrary/CSLi-

brary for error information.

Error 1003003 "Adaptive Server Error: %2, Severity: %3, State: %4, Line:
%5\nServer Name: %6, Procedure Name: %7\nError
Message: %8. %1"

Constant EMSG_HQM_SERVER_ERROR

SAP Sybase Error Number 20175

SQL State QHA03

SQL Code -1003003L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 761

Errors and Warnings

Error 1003003 "Adaptive Server Error: %2, Severity: %3, State: %4, Line:
%5\nServer Name: %6, Procedure Name: %7\nError
Message: %8. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Server error number

Parameter 3 Server severity number

Parameter 4 Server state number

Parameter 5 Server line number

Parameter 6 Server name (optional)

Parameter 7 Server stored procedure name (optional)

Parameter 8 Server error message

Probable Cause ASE error. Refer to the ASE error documentation for information
regarding the error.

Error 1003004 "COMPUTE values cannot be used in attached database

queries. %1"

Constant EMSG_HQM_NOCOMPUTES

SAP Sybase Error Number 20176

SQL State QHA04

SQL Code -1003004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Sybase IQ doesn't process COMPUTE clauses.

Error 1003005 "Connectivity libraries cannot be found (check your

dynamic library search path). Selects from attached
databases are not possible without these libraries. %1"

Constant EMSG_HQM_CTSTUB

762 SAP Sybase IQ

Errors and Warnings

Error 1003005 "Connectivity libraries cannot be found (check your

dynamic library search path). Selects from attached
databases are not possible without these libraries. %1"

SAP Sybase Error Number 20177

SQL State QHA05

SQL Code -1003005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Cannot process attached DB request without the connectivity libra-
ries. Check your dynamic library search path to make sure it is correct.

Error 1003006 "A call to ct_con_props failed trying to get the msglist from
the connection. %1"

Constant EMSG_HQM_GET_MSG

SAP Sybase Error 20178

Number

SQL State QHA06

SQL Code -1003006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause While trying to report an error condition, another error occurred trying to
retrieve the original error from the connection in order to report it to the
user. If this error occurs, retry the operation that caused it.

Error 1003007 "%2 functionality is not licensed on this server. %1"

Constant EMSG_NO_LICENSE

SAP Sybase Error Number 20179

SAP Sybase IQ Error Messages 763

Errors and Warnings

Error 1003007 "%2 functionality is not licensed on this server. %1"

SQL State QHA07

SQL Code -1003007L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Product or feature that is not licensed on the server.

Probable Cause The named feature is not licensed on the server.

Error 1003008 "Licensing error. Code = %2. %1"

Constant EMSG_CAT_LICENSE_ERROR

SAP Sybase Error Number 20180

SQL State QHA08

SQL Code -1003008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Error code returned from the license checking.

Probable Cause An error occurred while verifying the license. Refer to the documen-
tation for information about the Code reported in the error.

Error 1003009 "The specified target contains no indexes on which to

report. %1"

Constant EMSG_NOTHING_TO_REPORT

SAP Sybase Error Number 20181

SQL State QHA09

SQL Code -1003009L

764 SAP Sybase IQ

Errors and Warnings

Error 1003009 "The specified target contains no indexes on which to

report. %1"

Constant EMSG_HQM_EMPTY_SLOT8

SAP Sybase Error Number 20184

SQL State QHA12

SQL Code -1003012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1003013 No message

Constant EMSG_HQM_EMPTY_SLOT9

SAP Sybase Error Number 20185

SQL State QHA13

SQL Code -1003013L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1003014 No message

Constant EMSG_HQM_EMPTY_SLOT10

SAP Sybase Error Number 20186

SQL State QHA14

SQL Code -1003014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

766 SAP Sybase IQ

Errors and Warnings

Error 1004000 "The number of connections in the connection pool have

exceeded the upper limit"

Constant EMSG_INC_MAXCONNEXCEEDED

SAP Sybase Error Num- 20209

ber

SQL State QIA00

SQL Code -1004000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The number of connections in the connection pool have exceeded the
total number of connections allowed in the connection pool. No more
connections can be allocated.

Error 1004001 "Number of unused connections exceeded the maximum

number of unused connections in the connection pool"

Constant EMSG_INC_MAXUNUSEDEXCEEDED

SAP Sybase Error Number 20210

SQL State QIA01

SQL Code -1004001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The number of unused connections in the connection pool has ex-
ceeded the maximum number of unused connections in the connec-
tion pool.

Error 1004003 "Timeout period should be greater than or equal to the

heartbeat frequency"

Constant EMSG_INVALIDTIMEOUTPERIOD1

SAP Sybase Error Number 20212

SQL State QIA03

SAP Sybase IQ Error Messages 767

Errors and Warnings

Error 1004003 "Timeout period should be greater than or equal to the

heartbeat frequency"

SQL Code -1004003L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause All the timeout periods should be greater than or equal to the heartbeat
frequency.

Error 1004004 "No connection found for the server id %1 on the

coordinator"

Constant EMSG_CONNECTIONNOTFOUND

SAP Sybase Error Number 20215

SQL State QIA04

SQL Code -1004004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Parameter 1 description

Probable Cause A secondary node with the given server id does not exist on the
coordinator connection list

Messages 1004005 through 1005006

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1004005 "Timeout period should be multiple of the Heartbeat

Frequency"

Constant EMSG_INVALIDTIMEOUTPERIOD2

SAP Sybase Error Number 20216

SQL State QIA05

SQL Code -1004005L

768 SAP Sybase IQ

Errors and Warnings

Error 1004005 "Timeout period should be multiple of the Heartbeat

Frequency"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause All the timeout periods of INC(e.g.,AUTOEXCLUDE,LIVEN-

SAP Sybase Error Number 20220

SQL State QIA09

SQL Code -1004009L

Constant EMSG_INC_CONN_ERROR

SAP Sybase Error Num- 21223

ber

SQL State QIA12

SQL Code -1004012L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 771

Errors and Warnings

Error 1004012 "INC communication between coordinator and secondary

failed due to : %2 %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of exception

Parameter 2 Error message returned from target server

Probable Cause INC communication failed between coordinator and secondary nodes.
The error returned from target node is also displayed. This connection
is similar to a client connection.

Error 1004013 "Cannot drop multiplex server %2 as it holds freelist. %1"

Constant EMSG_MPX_CANNOT_DROP_HOLDS_FREELIST

SAP Sybase Error 21224

Number

SQL State QDD08

SQL Code -1004013L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception

Parameter 2 Multiplex Server Name

Probable Cause If a writer holds a freelist, it cannot be dropped. If the writer can be started,
start it. This is because a startup or a clean shutdown will clear the freelist. If
the writer cannot be restarted, restart the coordinator with -iqmpx_reclaim-
writerfreelist <server name> server switch to force the coordinator to reset
the writer freelist.

Error 1004014 "Trying to execute an unknown SQL type over the INC
connection"

Constant EMSG_INC_CONN_UNKNOWN_STMT

SAP Sybase Error Number 20225

SQL State QIA14

772 SAP Sybase IQ

Errors and Warnings

Error 1004014 "Trying to execute an unknown SQL type over the INC
connection"

SQL Code -1004014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The node is trying to execute an unknown SQL over the dblib con-
nections

Error 1004015 "Permission denied: Command not allowed on Multiplex

%2 servers. %1"

Constant EMSG_MPX_CMD_PERMISSION_LEVEL_DENIED

SAP Sybase Error Number 21225

SQL State QIA15

SQL Code -1004015L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception

Parameter 2 Role of current node

Probable Cause The command is not permitted on current multiplex node

Warning 1004060 "Warning: Heartbeat frequency should be less than or

equal to other timeout periods"

Constant EMSG_INVALIDHEARTBEATFREQUENCY1

SAP Sybase Error Number 20211

SQL State 01A60

SQL Code 1004060L

ODBC 2 State OK

ODBC 3 State OK

SAP Sybase IQ Error Messages 773

Errors and Warnings

Warning 1004060 "Warning: Heartbeat frequency should be less than or

equal to other timeout periods"

Severity Code 01 on page 2

Probable Cause The heartbeat frequency should always be less than or equal to other
timeout period. This is to make sure that the time lag between the
timeout occurring and the time when it is detected is minimal.

Warning 1004061 "Warning: All INC timeout periods should be multiple of

Heartbeat frequency"

Constant EMSG_INVALIDHEARTBEATFREQUENCY2

SAP Sybase Error Number 20213

SQL State QIA61

SQL Code 1004061L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 01 on page 2

Probable Cause All the timeout periods of INC(e.g.,AUTOEXCLUDE,LIVEN-

ESS,IDLE_CONNECTION) requires to be multiple of the Heartbeat
Frequency.

Error 1005000 "Bind parameters are not supported in data flow query
processing"

Constant EMSG_BINDPARAMETERS_UNSUPPORTED

SAP Sybase Error Number 20154

SAP Sybase Error Number 20157

SQL State QTA03

SQL Code -1005003L

SAP Sybase IQ Error Messages 775

Errors and Warnings

Error 1005003 "A maximum of one subquery predicate per conjunct is

supported in this release. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Messages 1005008 through 1005027

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1005008 "Sybase IQ does not support nested aggregations. %1"

Constant EMSG_UNSUPPORTEDNESTEDAGG

SAP Sybase Error Number 20162

SQL State QTA08

SAP Sybase Error Number 20165

778 SAP Sybase IQ

Errors and Warnings

Error 1005011 "There are two tables named '%2'. Please specify an alias
for one of them. %1"

SQL State QTA11

SQL Code -1005011L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name which is not unique

Probable Cause No additional information available.

Error 1005012 "The field '%2' specified in the query cannot be found, %1"

Constant EMSG_FIELDNOTDEFINED

SAP Sybase Error Number 20166

SQL State QTA12

SQL Code -1005012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1005013 "The FROM clause must have at least one table identifier
%1"

Constant EMSG_SEMANTIC_NO_TABLES_IN_FROM_CLAUSE

SAP Sybase Error Number 20167

SQL State QTA13

SQL Code -1005013L

SAP Sybase IQ Error Messages 779

Errors and Warnings

Error 1005013 "The FROM clause must have at least one table identifier
%1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1005014 "Non-space text found after ending quote character for an
enclosed field. %1"

Constant EMSG_NONSPACE_AFTER_QUOTE

SAP Sybase Error Number 20168

SQL State QTA14

SQL Code -1005014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Non-space text found after ending quote character for an enclosed
field.

Error 1005015 "The optimizer was unable to find a query plan that avoided
cartesian product joins larger than the
Max_Cartesian_Result setting %1"

Constant EMSG_CARTESION_RESULT_TOO_BIG

SAP Sybase Error Number 20169

SQL State QTA15

SQL Code -1005015L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

780 SAP Sybase IQ

Errors and Warnings

Error 1005015 "The optimizer was unable to find a query plan that avoided
cartesian product joins larger than the
Max_Cartesian_Result setting %1"

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1005016 "Aggregate functions are not allowed in a GROUP BY

clause %1"

Constant EMSG_ILLEGAL_SET_FUNCTION_USAGE

SAP Sybase Error Number 20170

SQL State QTA16

SQL Code -1005016L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1005017 "You cannot DELETE from a join virtual table. (%2) %1"

Constant EMSG_CANNOT_DELETE_FROM_JVT

SAP Sybase Error Number 20171

SQL State QTA17

SQL Code -1005017L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Tablename

Probable Cause If this message occurs, it means that the user has tried to DELETE
from a join virtual table. This is not permitted.

SAP Sybase IQ Error Messages 781

Errors and Warnings

Error 1005018 "Illegal ORDER BY item %2, %1"

Constant EMSG_BAD_ORDERBY_ITEM

SAP Sybase Error Number 20989

SQL State QTA18

SQL Code -1005018L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 argument

Probable Cause No additional information available.

Error 1005019 "The update FROM list must match the table-clause
exactly"

Constant EMSG_BAD_UPDATE_FROM_LIST

SAP Sybase Error Number 21060

SQL State QTA19

SQL Code -1005019L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1005020 "Only single-table updates are supported by Sybase IQ"

Constant EMSG_SINGLE_TABLE_UPDATE_ONLY

SAP Sybase Error Number 21062

SQL State QTA20

SQL Code -1005020L

SAP Sybase Error Number 21073

SQL State QTA23

SAP Sybase IQ Error Messages 783

Errors and Warnings

Error 1005023 "Unmatched number of select list items in union"

SQL Code -1005023L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Cube message here

Error 1005024 "Estimate number: %2 exceed the MAX_CUBE_RESULT of

GROUP BY CUBE or ROLLUP %1"

Constant EMSG_EXCEED_MAX_CUBE_RESULT

SAP Sybase Error Number 21074

SQL State QTA24

SQL Code -1005024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location

Parameter 2 the estimated total result of hash base cube

Probable Cause location of the exception the estimated total result of hash base cube
or rollup

Error 1005025 "Query rejected as too complex. After join simplifications

there were still %2 tables to be joined, which exceeds the
current setting of Max_Join_Enumeration. %1"

Constant EMSG_JOINS_TOO_COMPLEX

SAP Sybase Error Number 21089

SQL State QTA25

SQL Code -1005025L

ODBC 2 State ERROR

ODBC 3 State ERROR

784 SAP Sybase IQ

Errors and Warnings

Error 1005025 "Query rejected as too complex. After join simplifications

there were still %2 tables to be joined, which exceeds the
current setting of Max_Join_Enumeration. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the user name specified

Probable Cause The query will take too long to optimize, so it is being rejected

Error 1005026 "Update not supported on null supplying side of outer

join."

Constant EMSG_UPDATE_NOT_ALLOWED_NULL_OUTER

SAP Sybase Error Number 21090

SQL State QTA26

SQL Code -1005026L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1005027 "An error occurs during unistring conversion - %2. %1"

Constant EMSG_UNILIB_ERR

SAP Sybase Error Number 21091

SQL State QTA27

SQL Code -1005027L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the details of unilib error

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 785

Errors and Warnings

Messages 1005028 through 1006012

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1005028 "Syntax error - %2. %1"

Constant EMSG_SYNTAX_ERROR

SAP Sybase Error Number 21092

SQL State QTA28

SQL Code -1005028L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the details of syntax error

Probable Cause No additional information available.

Error 1005029 "You cannot SELECT from a join virtual table. (%2) %1"

Constant EMSG_CANNOT_SELECT_FROM_JVT

SAP Sybase Error Number 21143

SQL State QTA29

SQL Code -1005029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the details of the syntax error

Probable Cause No additional information available.

786 SAP Sybase IQ

Errors and Warnings

Error 1005030 "Query has an ambiguous table reference between prepare

and open cursor (%2). %1"

Constant EMSG_INCONSISTENT_TABLES

SAP Sybase Error Number 21145

SQL State QTA30

SQL Code -1005030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 table name

Probable Cause SA allows a base and temp table to both have the same table name. In
some places, such as when a temp table is created in a stored proce-
dure between the describe and open, IQ can find the base table in the
describe and the temp table in the open, giving inconsistent results.

Error 1005031 "Illegal PARTITION BY item %2, %1"

SAP Sybase Error Number 21220

SQL State QTA34

SQL Code -1005034L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available..

Error 1006000 "IQ Internal error. Please report this to Sybase IQ support.
%1"

Constant EMSG_PROGERROR

SAP Sybase Error Number 20238

SQL State QBA00

SQL Code -1006000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006001 "IQ Internal error. Please report this to Sybase IQ support.
%2 %1"

Constant EMSG_PROGERROR2

SAP Sybase Error Number 20239

SQL State QBA01

SQL Code -1006001L

SAP Sybase IQ Error Messages 789

Errors and Warnings

Error 1006001 "IQ Internal error. Please report this to Sybase IQ support.
%2 %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006002 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %1"

Constant EMSG_PROGERROR3

SAP Sybase Error Number 20240

SQL State QBA02

SQL Code -1006002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006003 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %1"

Constant EMSG_PROGERROR4

SAP Sybase Error Number 20241

SQL State QBA03

SQL Code -1006003L

ODBC 2 State ERROR

790 SAP Sybase IQ

Errors and Warnings

Error 1006003 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %1"

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Probable Cause No additional information available.

Error 1006004 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %1"

Constant EMSG_PROGERROR5

SAP Sybase Error Number 20242

SQL State QBA04

SQL Code -1006004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Probable Cause No additional information available.

Error 1006005 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %1"

Constant EMSG_PROGERROR6

SAP Sybase Error Number 20243

SAP Sybase IQ Error Messages 791

Errors and Warnings

Error 1006005 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %1"

SQL State QBA05

SQL Code -1006005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Parameter 6 explanation for arg %6 delete if no %6

Probable Cause No additional information available.

Error 1006006 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %7 %1"

Constant EMSG_PROGERROR7

SAP Sybase Error Number 20244

SQL State QBA06

SQL Code -1006006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

792 SAP Sybase IQ

Errors and Warnings

Error 1006006 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %7 %1"

Parameter 6 explanation for arg %6 delete if no %6

Parameter 7 explanation for arg %7 delete if no %7

Probable Cause No additional information available.

Error 1006007 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %7 %8 %1"

Constant EMSG_PROGERROR8

SAP Sybase Error Number 20245

SQL State QBA07

SQL Code -1006007L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Parameter 6 explanation for arg %6 delete if no %6

Parameter 7 explanation for arg %7 delete if no %7

Parameter 8 explanation for arg %8 delete if no %8

Probable Cause No additional information available.

Error 1006008 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %7 %8 %9 %1"

Constant EMSG_PROGERROR9

SAP Sybase Error Number 20246

SQL State QBA08

SAP Sybase IQ Error Messages 793

Errors and Warnings

Error 1006008 "IQ Internal error. Please report this to Sybase IQ support.
%2 %3 %4 %5 %6 %7 %8 %9 %1"

SQL Code -1006008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Parameter 6 explanation for arg %6 delete if no %6

Parameter 7 explanation for arg %7 delete if no %7

Parameter 8 explanation for arg %8 delete if no %8

Parameter 9 explanation for arg %9 delete if no %9

Probable Cause No additional information available.

Error 1006009 "Exception Stack Full %1"

Constant EMSG_ERRORSTACKFULL

SAP Sybase Error Number 20247

SQL State QBA09

SQL Code -1006009L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

794 SAP Sybase IQ

Errors and Warnings

Error 1006010 "No TRY Found %1"

Constant EMSG_ERRORNOTRYFOUND

SAP Sybase Error Number 20248

SQL State QBA10

SQL Code -1006010L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006011 "No Exception object found"

Constant EMSG_ERRORTHROWNOEXCEPT

SAP Sybase Error Number 20249

SQL State QBA11

SQL Code -1006011L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006012 "No Top Of Stack Set %1"

Constant EMSG_ERRORNOTOPOFSTACK

SAP Sybase Error Number 20250

SQL State QBA12

SQL Code -1006012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 795

Errors and Warnings

Error 1006012 "No Top Of Stack Set %1"

Parameter 1 location of the exception

Probable Cause No additional information available.

Messages 1006013 through 1006032

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006013 "Try Stack Corrupt %1"

Constant EMSG_ERRORTRYSTACKCORRUPT

SAP Sybase Error Number 20251

SQL State QBA13

SQL Code -1006013L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006014 "Object Not Found"

Constant EMSG_ERRORNOOBJECTFOUND

SAP Sybase Error Number 20252

SQL State QBA14

SQL Code -1006014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006015 "Invalid Object size on stack"

Constant EMSG_ERRORSTACKOBJSIZE

796 SAP Sybase IQ

Errors and Warnings

Error 1006015 "Invalid Object size on stack"

SAP Sybase Error Number 20253

SQL State QBA15

SQL Code -1006015L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006016 "hdb_sqlcode thrown: "

Constant EMSG_ERRORHDBSQLCODETHROWN

SAP Sybase Error Number 20254

SQL State QBA16

SQL Code -1006016L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006017 "Number of REGISTER()/UNREGISTER() calls do not

match"

Constant EMSG_ERRORREGUNREG

SAP Sybase Error Number 20255

SQL State QBA17

Error 1006021 "objects still registered on hos_ObjectStack when

~hos_ObjectStack() called"

Constant EMSG_ERRORSTILLREGISTERED

SAP Sybase Error Number 20259

SQL State QBA21

SQL Code -1006021L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006022 "* Aborting because AbortOnErrorNumber Matched *"

Constant EMSG_ERRORTHROW_ABORTONNUMBER

SAP Sybase Error Number 20260

SQL State QBA22

SQL Code -1006022L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006023 "*** Aborting because AbortOnErrorFile&Line Matched

***"

Constant EMSG_ERRORTHROW_ABORTONFILELINE

SAP Sybase Error Number 20261

SQL State QBA23

SQL Code -1006023L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 799

Errors and Warnings

Error 1006023 "*** Aborting because AbortOnErrorFile&Line Matched

***"

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006024 "Memory Corruption Found %1"

Constant EMSG_MEMORY_CORRUPTED

SAP Sybase Error Number 20262

SQL State QBA24

SQL Code -1006024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006025 "No Shared Memory Manager %1"

Constant EMSG_MEMORY_NOSHAREDMEMMGR

SAP Sybase Error Number 20263

SQL State QBA25

SQL Code -1006025L

Constant EMSG_MEMORY_BADTYPE

SAP Sybase Error Number 20266

SQL State QBA28

SQL Code -1006028L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 801

Errors and Warnings

Error 1006028 "Memory Type Invalid\nFound Object %2. Size %3 Type %4

\nAllocated from %5 : %6 %1"

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Parameter 6 explanation for arg %6 delete if no %6

Probable Cause No additional information available.

Error 1006029 "Memory Manager Leak Found\nCurrent Allocated

Memory %2 \nFound object %3 Size %4 Type %5
\nAllocated from %6 : %7 %1 "

Constant EMSG_MEMORY_LEAK

SAP Sybase Error Number 20267

SQL State QBA29

SQL Code -1006029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Parameter 6 explanation for arg %6 delete if no %6

Parameter 7 explanation for arg %7 delete if no %7

Probable Cause No additional information available.

802 SAP Sybase IQ

Errors and Warnings

Error 1006030 "Command line error. Invalid command line variable name
or value. %1"

Constant EMSG_CMDERROR

SAP Sybase Error Number 20268

SQL State QBA30

SQL Code -1006030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of failure

Probable Cause No additional information available.

Error 1006031 "Invalid SQL code %1"

Constant EMSG_INCORRECT_SQLCODE

SAP Sybase Error Number 20269

SQL State QBA31

SQL Code -1006031L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 invalid SQL code

Probable Cause No additional information available.

Warning 1006032 "\n=n*** File: %1\n\n"

Constant EMSG_MVION_INFO

SAP Sybase Error Number 20270

SQL State QBA32

SQL Code 1006032L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 803

Errors and Warnings

Warning 1006032 "\n=n*** File: %1\n\n"

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 file

Probable Cause No additional information available.

Messages 1006033 through 1006052

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1006033 "team id %1 : # threads = %2"

Constant EMSG_THREAD_TEAM_INFO

SAP Sybase Error Number 20271

SQL State QBA33

SQL Code 1006033L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 1 on page 2

Parameter 1 team id

Parameter 2 thread id

Probable Cause No additional information available.

Error 1006034 No message

Constant EMSG_MEMORY_LEAK6_EMPTY_SLOT

SAP Sybase Error Number 20272

SQL State QBA34

SQL Code -1006034L

Probable Cause No additional information available.

Error 1006038 No message

Constant EMSG_MEMORY_LEAKSHORTFORMHDR1_EMPTY_SLOT

SAP Sybase Error Number 20276

SQL State QBA38

SQL Code -1006038L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006039 No message

Constant EMSG_MEMORY_LEAKSHORTFORMHDR2_EMPTY_SLOT

SAP Sybase Error Number 20277

SQL State QBA39

SQL Code -1006039L

Constant EMSG_MEMORY_NOMEMORY

SAP Sybase Error Number 20280

SQL State QBA42

SQL Code -1006042L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 807

Errors and Warnings

Error 1006042 "All available virtual memory has been used; allocation
cancelled: [Extra info: %2] %1"

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006043 "No more event handlers %1"

Constant EMSG_MEMORY_NOMOREEVENTHANDLERS

SAP Sybase Error Number 20281

SQL State QBA43

SQL Code -1006043L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006044 "No more Mark Stack slots available %1"

Constant EMSG_MEMORY_NOMOREMARKSTACKSLOTS

SAP Sybase Error Number 20282

SQL State QBA44

SQL Code -1006044L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006045 "Not a Vector: delete[] was called on an object that is not a
vector %1"

Constant EMSG_MEMORY_NOTAVECTOR

808 SAP Sybase IQ

Errors and Warnings

Error 1006045 "Not a Vector: delete[] was called on an object that is not a
vector %1"

SAP Sybase Error Number 20283

SQL State QBA45

SQL Code -1006045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006046 "Is a Vector: delete was called on an object that is a vector;
use delete[] %1"

Constant EMSG_MEMORY_ISAVECTOR

SAP Sybase Error Number 20284

SQL State QBA46

SQL Code -1006046L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006047 "Error Memory Object errnum %2 %1"

Constant EMSG_MEMORY_DEFAULT

SAP Sybase Error Number 20285

SQL State QBA47

SQL Code -1006047L

ODBC 2 State ERROR

Error 1006051 "hos_memArena: could not get memory during

initialization %1"

Constant EMSG_MEMARENA_COULDNOTINIT

SAP Sybase Error Number 20289

SQL State QBA51

SQL Code -1006051L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006052 "hos_memArena: unknown error %1"

Constant EMSG_MEMARENA_DEFAULT

SAP Sybase Error Number 20290

SQL State QBA52

SQL Code -1006052L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 811

Errors and Warnings

Error 1006052 "hos_memArena: unknown error %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

1006053 - 1006255

Messages 1006053 through 1006072

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006053 "Vector index out of bounds %1"

Constant EMSG_VECTOR_OUTOFBOUNDS

SAP Sybase Error Number 20291

SQL State QBA53

SQL Code -1006053L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006054 "Error processing hos_vector_exception. _errnum: %2

%1"

Constant EMSG_VECTOR_DEFAULT

SAP Sybase Error Number 20292

SQL State QBA54

SQL Code -1006054L

ODBC 2 State ERROR

812 SAP Sybase IQ

Errors and Warnings

Error 1006054 "Error processing hos_vector_exception. _errnum: %2

%1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006059 "An I/O error has occurred on this object. File: %2 %1"

Constant EMSG_BIO_IOERRORSET

SAP Sybase Error Number 20297

SQL State QBA59

SQL Code -1006059L

814 SAP Sybase IQ

Errors and Warnings

Error 1006059 "An I/O error has occurred on this object. File: %2 %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006060 "Object not open for file %2 %1"

Constant EMSG_BIO_NOTOPEN

SAP Sybase Error Number 20298

SQL State QBA60

SQL Code -1006060L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006061 "Invalid Blocksize %2 %3 %1"

Constant EMSG_BIO_INVBLKSIZE

SAP Sybase Error Number 20299

SQL State QBA61

SQL Code -1006061L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 815

Errors and Warnings

Error 1006061 "Invalid Blocksize %2 %3 %1"

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006062 "OS error %2 reported on file %3. %1"

Constant EMSG_BIO_OSERROR

SAP Sybase Error Number 20300

SQL State QBA62

SQL Code -1006062L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The OS has returned Errno.

Parameter 3 The file on which the error occurred.

Probable Cause No additional information available.

Error 1006063 "Invalid block %2. File: %3 %1"

Constant EMSG_BIO_BADBLKNO

SAP Sybase Error Number 20301

SQL State QBA63

SQL Code -1006063L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

816 SAP Sybase IQ

Errors and Warnings

Error 1006063 "Invalid block %2. File: %3 %1"

Probable Cause No additional information available.

Error 1006064 No message

Constant EMSG_BIO_BLKNOTOOBIG_EMPTY_SLOT

SAP Sybase Error Number 20302

SQL State QBA64

SQL Code -1006064L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006065 No message

Constant EMSG_BIO_BLKNOTOOBIG2_EMPTY_SLOT

SAP Sybase Error Number 20303

SQL State QBA65

SQL Code -1006065L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006066 "Invalid number of blocks File: %2 %1"

Constant EMSG_BIO_BADNBLKS

SAP Sybase Error Number 20304

SQL State QBA66

SQL Code -1006066L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 817

Errors and Warnings

Error 1006066 "Invalid number of blocks File: %2 %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006067 "Filename does not exist. File: %2 %1"

Constant EMSG_BIO_NOSUCHOBJECT

SAP Sybase Error Number 20305

SQL State QBA67

SQL Code -1006067L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006068 No message

Constant EMSG_BIO_NOMESSAGE_EMPTY_SLOT

SAP Sybase Error Number 20306

SQL State QBA68

SQL Code -1006068L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

818 SAP Sybase IQ

Errors and Warnings

Error 1006069 "No more system record locks available %1"

Constant EMSG_BIO_NOMORELOCKS

SAP Sybase Error Number 20307

SQL State QBA69

SQL Code -1006069L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006070 "Attempt to use object after EOF on file %2 %1"

Constant EMSG_BIO_IOEOF

SAP Sybase Error Number 20308

SQL State QBA70

SQL Code -1006070L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006071 "Handle must be greater than 0 File: %2 %1"

Constant EMSG_BIO_INVHANDLE

SAP Sybase Error Number 20309

SQL State QBA71

SQL Code -1006071L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 819

Errors and Warnings

Error 1006071 "Handle must be greater than 0 File: %2 %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006072 "The file is/will be too big. File: %2 %1"

Constant EMSG_BIO_FILETOOBIG

SAP Sybase Error Number 20310

SQL State QBA72

SQL Code -1006072L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Messages 1006073 through 1006092

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006073 "Operation failed, user not owner. File: %2 %1"

Constant EMSG_BIO_NOTOWNER

SAP Sybase Error Number 20311

SQL State QBA73

SQL Code -1006073L

Error 1006076 "I/O Error on file %2 %1"

Constant EMSG_BIO_IOERROR

SAP Sybase Error Number 20314

SQL State QBA76

SQL Code -1006076L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006077 "No such device or address %2 %1"

Constant EMSG_BIO_NOSUCHDEVADDR

SAP Sybase Error Number 20315

SQL State QBA77

SQL Code -1006077L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006078 "Argument list to big %2 %1"

Constant EMSG_BIO_ARGTOBIG

SAP Sybase Error Number 20316

SQL State QBA78

SQL Code -1006078L

822 SAP Sybase IQ

Errors and Warnings

Error 1006078 "Argument list to big %2 %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006079 "Exec format error %2 %1"

Constant EMSG_BIO_EXECFORMAT

SAP Sybase Error Number 20317

SQL State QBA79

SQL Code -1006079L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006080 "Bad file handle passed to OS on file %2 %1"

Constant EMSG_BIO_BADFILEHANDLE

SAP Sybase Error Number 20318

SQL State QBA80

SQL Code -1006080L

Error 1006083 "No more memory %2 %1"

Constant EMSG_BIO_NOMOREMEMORY

SAP Sybase Error Number 20321

SQL State QBA83

SQL Code -1006083L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006084 "Operation failed on file due to file permissions. File: %2

%1"

Constant EMSG_BIO_PERMISSION

SAP Sybase Error Number 20322

SQL State QBA84

SQL Code -1006084L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006085 "Bad address %2 %1"

Constant EMSG_BIO_BADADDRESS

SAP Sybase Error Number 20323

SQL State QBA85

SAP Sybase IQ Error Messages 825

Errors and Warnings

Error 1006085 "Bad address %2 %1"

SQL Code -1006085L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006086 "File already exists. File: %2 %1"

Constant EMSG_BIO_FILEEXISTS

SAP Sybase Error Number 20324

SQL State QBA86

SQL Code -1006086L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006087 "%2 is not a directory %1"

Constant EMSG_BIO_NOTDIR

SAP Sybase Error Number 20325

SQL State QBA87

SQL Code -1006087L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

826 SAP Sybase IQ

Errors and Warnings

Error 1006087 "%2 is not a directory %1"

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006088 "%2 is a directory %1"

Constant EMSG_BIO_ISDIR

SAP Sybase Error Number 20326

SQL State QBA88

SQL Code -1006088L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006089 "Invalid Block I/O argument, maybe %2 is a directory, or it

exceeds maximum file size limit for the platform, or trying
to use Direct IO on unsupported OS %1"

Constant EMSG_BIO_INVARG

SAP Sybase Error Number 20327

SQL State QBA89

SQL Code -1006089L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

SAP Sybase IQ Error Messages 827

Errors and Warnings

Error 1006089 "Invalid Block I/O argument, maybe %2 is a directory, or it

exceeds maximum file size limit for the platform, or trying
to use Direct IO on unsupported OS %1"

Probable Cause No additional information available.

Error 1006090 No message

Constant EMSG_BIO_INVARG2_EMPTY_SLOT

SAP Sybase Error Number 20328

SQL State QBA90

SQL Code -1006090L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006091 "File table is full %2 %1"

Constant EMSG_BIO_FILETABLEFULL

SAP Sybase Error Number 20329

SQL State QBA91

SQL Code -1006091L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006092 "Too many files %2 %1"

Constant EMSG_BIO_TOMANYFILES

SAP Sybase Error Number 20330

828 SAP Sybase IQ

Errors and Warnings

Error 1006092 "Too many files %2 %1"

SQL State QBA92

SQL Code -1006092L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Messages 1006093 through 1006113

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006093 "File is too large. File: %2 %1"

Constant EMSG_BIO_FILETOLARGE

SAP Sybase Error Number 20331

SQL State QBA93

SQL Code -1006093L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006094 "Disk is or will be full on I/O to or allocation of file %2 %1"

Constant EMSG_BIO_DISKFULL

SAP Sybase Error Number 20332

SQL State QBA94

SAP Sybase IQ Error Messages 829

Errors and Warnings

Error 1006094 "Disk is or will be full on I/O to or allocation of file %2 %1"

SQL Code -1006094L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006095 "Read only filesystem on file %2 %1"

Constant EMSG_BIO_READONLYFS

SAP Sybase Error Number 20333

SQL State QBA95

SQL Code -1006095L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006096 "Backup device is busy %2 %1"

Constant EMSG_IO_DEVICEBUSY

SAP Sybase Error Number 20334

SQL State QBA96

SQL Code -1006096L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase Error Number 20337

SQL State QBA99

SAP Sybase IQ Error Messages 831

Errors and Warnings

Error 1006099 "Shared Bufman For "

SQL Code -1006099L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006100 "Shared Temp Bufman For "

Constant EMSG_BUFMAN_SHRTEMPBUFMANID

SAP Sybase Error Number 20338

SQL State QBB00

SQL Code -1006100L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006101 "Buffer too small %1"

Constant EMSG_CMPRS_BUFFTOOSMALL

SAP Sybase Error Number 20339

SQL State QBB01

SQL Code -1006101L

Error 1006106 "Invalid file path: %2 %1"

Constant EMSG_FN_BAD_PATH

SAP Sybase Error Number 20344

SQL State QBB06

SQL Code -1006106L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006107 "Invalid disk name: %2 %1"

Constant EMSG_FN_BAD_DISK

SAP Sybase Error Number 20345

SQL State QBB07

SQL Code -1006107L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006108 "Invalid directory name(s): %2 %1"

Constant EMSG_FN_BAD_DIRS

SAP Sybase Error Number 20346

SQL State QBB08

SQL Code -1006108L

834 SAP Sybase IQ

Errors and Warnings

Error 1006108 "Invalid directory name(s): %2 %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006109 "Invalid file name: %2 %1"

Constant EMSG_FN_BAD_NAME

SAP Sybase Error Number 20347

SQL State QBB09

SQL Code -1006109L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006110 "Invalid file extension : %2 %1"

Constant EMSG_FN_BAD_EXT

SAP Sybase Error Number 20348

SQL State QBB10

SQL Code -1006110L

Error 1006113 "Unknown error %1"

Constant EMSG_BITVEC_UNKNOWN

SAP Sybase Error Number 20351

SQL State QBB13

SQL Code -1006113L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Messages 1006114 through 1006134

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006114 "Operation on two hos_bitvec objects that are not the
same size %1"

Constant EMSG_BITVEC_SIZEERROR

SAP Sybase Error Number 20352

SQL State QBB14

SQL Code -1006114L

SAP Sybase Error Number 20355

SQL State QBB17

Constant EMSG_ATTN_OUTOFTIME

SAP Sybase Error Number 20358

SQL State QBB20

SQL Code -1006120L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 839

Errors and Warnings

Error 1006120 "The operation has been cancelled - Max_Query_Time

exceeded"

Probable Cause No additional information available.

Error 1006121 "Unknown error message"

Constant EMSG_SORT_UNKNOWN

SAP Sybase Error Number 20359

SQL State QBB21

SQL Code -1006121L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006123 "Attempt to add an invalid extent %1"

Constant EMSG_MVBIO_EXTENTSIZE

SAP Sybase Error Number 20361

SQL State QBB23

SQL Code -1006123L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006124 "Attempt to operate on object before being opened %1"

Constant EMSG_MVBIO_NOTOPEN

SAP Sybase Error Number 20362

SQL State QBB24

SQL Code -1006124L

840 SAP Sybase IQ

Errors and Warnings

Error 1006124 "Attempt to operate on object before being opened %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006125 "Bad block number %2 passed to object %1"

Constant EMSG_MVBIO_BADBLK

SAP Sybase Error Number 20363

SQL State QBB25

SQL Code -1006125L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) bad block number

Probable Cause No additional information available.

Error 1006126 "The File access and MVBIO access do not match %1"

Constant EMSG_MVBIO_BADACCESS

SAP Sybase Error Number 20364

SQL State QBB26

SQL Code -1006126L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 841

Errors and Warnings

Error 1006127 "The File is out of space. File: %2 %1"

Constant EMSG_MVBIO_DBFULL

SAP Sybase Error Number 20365

SQL State QBB27

SQL Code -1006127L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006128 "Invalid File Access argument. %1"

Constant EMSG_IO_BADACCESS

SAP Sybase Error Number 20366

SQL State QBB28

SQL Code -1006128L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006129 "An I/O error has occurred on this object."

Constant EMSG_IO_IOERRORSET

SAP Sybase Error Number 20367

SQL State QBB29

SQL Code -1006129L

ODBC 2 State ERROR

842 SAP Sybase IQ

Errors and Warnings

Error 1006129 "An I/O error has occurred on this object."

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006130 "Object not open for file %2 %1"

Constant EMSG_IO_NOTOPEN

SAP Sybase Error Number 20368

SQL State QBB30

SQL Code -1006130L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that could not be opened.

Probable Cause Unable to open file.

Error 1006131 "OS error reported on file: %2 . OS error: %3 %1"

Constant EMSG_IO_OSERROR

SAP Sybase Error Number 20369

SQL State QBB31

SQL Code -1006131L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that reports error

Parameter 3 system error IO operation reported (errno)

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 843

Errors and Warnings

Error 1006132 ". OS error: "

Constant EMSG_IO_OSERROR2_NOT_USED

SAP Sybase Error Number 20370

SQL State QBB32

SQL Code -1006132L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006133 "File does not exist. File: %2 %1"

Constant EMSG_IO_NOSUCHOBJECT

SAP Sybase Error Number 20371

SQL State QBB33

SQL Code -1006133L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that does not exist

Probable Cause No additional information available.

Error 1006134 "Invalid filename: %2. '::' is not allowed in the filename for
this statement. %1"

Constant EMSG_IO_INVALID_FILE

SAP Sybase Error Number 20372

SQL State QBB34

SQL Code -1006134L

ODBC 2 State ERROR

844 SAP Sybase IQ

Errors and Warnings

Error 1006134 "Invalid filename: %2. '::' is not allowed in the filename for
this statement. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 File or device name that is invalid.

Probable Cause A "::" (colon-colon) is not allowed in the filename by Sybase IQ for
the statement being executed."

Messages 1006135 through 1006154

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006135 "Attempt to use object after EOF on file %2 %1"

Constant EMSG_IO_IOEOF

SAP Sybase Error Number 20373

SQL State QBB35

SQL Code -1006135L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file we have read past EOF on

Probable Cause No additional information available.

Error 1006136 "The file is/will be too big "

Constant EMSG_IO_FILETOOBIG

SAP Sybase Error Number 20374

SQL State QBB36

SQL Code -1006136L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 845

Errors and Warnings

Error 1006136 "The file is/will be too big "

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006137 "Operation failed on file, user not owner. File: %2 %1"

Constant EMSG_IO_NOTOWNER

SAP Sybase Error Number 20375

SQL State QBB37

SQL Code -1006137L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that cannot be accessed

Probable Cause No additional information available.

Error 1006138 "No such process %2 %1"

Constant EMSG_IO_NOSUCHPROCESS

SAP Sybase Error Number 20376

SQL State QBB38

SAP Sybase Error Number 20379

SQL State QBB41

SQL Code -1006141L

SAP Sybase IQ Error Messages 847

Errors and Warnings

Error 1006141 "No such device or address %2 %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006142 "Argument list too big %2 %1"

Constant EMSG_IO_ARGTOBIG

SAP Sybase Error Number 20380

SQL State QBB42

SQL Code -1006142L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file the I/O operation failed on

Probable Cause No additional information available.

Error 1006143 "Exec format error %2 %1"

Constant EMSG_IO_EXECFORMAT

SAP Sybase Error Number 20381

SQL State QBB43

SQL Code -1006143L

Error 1006146 "No more processes %2 %1"

Constant EMSG_IO_NOMOREPROCESSES

SAP Sybase Error Number 20384

SQL State QBB46

SQL Code -1006146L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006147 "No more memory %2 %1 "

Constant EMSG_IO_NOMOREMEMORY

SAP Sybase Error Number 20385

SQL State QBB47

SQL Code -1006147L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006148 "Operation failed on file due to file permissions. File: %2

%1"

Constant EMSG_IO_PERMISSION

SAP Sybase Error Number 20386

SQL State QBB48

850 SAP Sybase IQ

Errors and Warnings

Error 1006148 "Operation failed on file due to file permissions. File: %2

%1"

SQL Code -1006148L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that the operation failed on.

Probable Cause No additional information available.

Error 1006149 "Bad address %2 %1"

Constant EMSG_IO_BADADDRESS

SAP Sybase Error Number 20387

SQL State QBB49

SQL Code -1006149L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006150 "File already exists. File: %2 %1"

Constant EMSG_IO_FILEEXISTS

SAP Sybase Error Number 20388

SQL State QBB50

SQL Code -1006150L

Error 1006153 "Invalid stream I/O argument, maybe %2 is a directory, or it

contains more than 2,147,483,647 bytes, %1"

Constant EMSG_IO_INVARG

SAP Sybase Error Number 20391

SQL State QBB53

SQL Code -1006153L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006154 "Perhaps the device (%2) is not in variable block mode?
%1"

Constant EMSG_IO_NOTVARBLOCKMODE

SAP Sybase Error Number 20392

SQL State QBB54

SQL Code -1006154L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 853

Errors and Warnings

Messages 1006155 through 1006174

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006155 "File table is full %2 %1"

Constant EMSG_IO_FILETABLEFULL

SAP Sybase Error Number 20393

SQL State QBB55

SQL Code -1006155L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006156 "Too many files %2 %1"

Constant EMSG_IO_TOMANYFILES

SAP Sybase Error Number 20394

SQL State QBB56

SQL Code -1006156L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006157 "File is too large. File: %2 %1"

Constant EMSG_IO_FILETOLARGE

854 SAP Sybase IQ

Errors and Warnings

Error 1006157 "File is too large. File: %2 %1"

SAP Sybase Error Number 20395

SQL State QBB57

SQL Code -1006157L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006158 "Disk is full on I/O to file %2 %1"

Constant EMSG_IO_DISKFULL

SAP Sybase Error Number 20396

SQL State QBB58

SQL Code -1006158L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that grew to fill the disk.

Probable Cause No additional information available.

Error 1006159 "Read only filesystem on file %2 %1"

Constant EMSG_IO_READONLYFS

SAP Sybase Error Number 20397

SQL State QBB59

SQL Code -1006159L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 855

Errors and Warnings

Error 1006159 "Read only filesystem on file %2 %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file invalid operation was tried on

Probable Cause No additional information available.

Error 1006160 "Bad tape blocksize %2 %1"

Constant EMSG_IO_BADBLOCKSIZE

SAP Sybase Error Number 20398

SQL State QBB60

SQL Code -1006160L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006161 "Operation Canceled %2 %1"

Constant EMSG_IO_OPCANCELED

SAP Sybase Error Number 20399

SQL State QBB61

SQL Code -1006161L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file that had an I/O operation cancelled

856 SAP Sybase IQ

Errors and Warnings

Error 1006161 "Operation Canceled %2 %1"

Probable Cause No additional information available.

Error 1006162 "Tape IO Error %2 %1 "

Constant EMSG_IO_TAPEIOERROR

SAP Sybase Error Number 20400

SQL State QBB62

SQL Code -1006162L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006163 "Operating system error : %2 %1"

Constant EMSG_LS_OSERROR

SAP Sybase Error Number 20401

SQL State QBB63

SQL Code -1006163L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006164 "The text in the DateString for Day is not a valid number.
Day: "

Severity Code 14 on page 2

858 SAP Sybase IQ

Errors and Warnings

Error 1006166 "The text in the DateString for Year is not a valid number.
Year: "

Probable Cause No additional information available.

Error 1006167 "DateTime is invalid (%2) %1"

Constant EMSG_DATE_INVALIDDATETIME

SAP Sybase Error Number 20405

SQL State QBB67

SQL Code -1006167L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006168 "Date is invalid (%2) %1"

Constant EMSG_DATE_INVALIDDATE

SAP Sybase Error Number 20406

SQL State QBB68

SQL Code -1006168L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006169 "Time is invalid (%2) %1"

Constant EMSG_DATE_INVALIDTIME

SAP Sybase IQ Error Messages 859

Errors and Warnings

Error 1006169 "Time is invalid (%2) %1"

SAP Sybase Error Number 20407

SQL State QBB69

SQL Code -1006169L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006170 "Date is invalid because of the year (%2) %1"

Constant EMSG_DATE_INVALIDYEAR

SAP Sybase Error Number 20408

SQL State QBB70

SQL Code -1006170L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006171 "Date is invalid because of the day of the year (%2) %1"

Constant EMSG_DATE_INVALIDJDAY

SAP Sybase Error Number 20409

SQL State QBB71

SQL Code -1006171L

ODBC 2 State ERROR

860 SAP Sybase IQ

Errors and Warnings

Error 1006171 "Date is invalid because of the day of the year (%2) %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006172 "Date is invalid because of the Month (%2) %1"

Constant EMSG_DATE_INVALIDMONTH

SAP Sybase Error Number 20410

SQL State QBB72

SQL Code -1006172L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006173 "Date is invalid because of the day the Month (%2) %1"

Constant EMSG_DATE_INVALIDMDAY

SAP Sybase Error Number 20411

SQL State QBB73

SQL Code -1006173L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

SAP Sybase IQ Error Messages 861

Errors and Warnings

Error 1006173 "Date is invalid because of the day the Month (%2) %1"

Probable Cause No additional information available.

Error 1006174 "Date is invalid (Year:%2 Month:%3 Day:%4) %1"

Constant EMSG_DATE_INVALIDYMD

SAP Sybase Error Number 20412

SQL State QBB74

SQL Code -1006174L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Probable Cause No additional information available.

Messages 1006175 through 1006194

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006175 "Time is invalid (Hour:%2 Minute:%3 Second:%4

MicroSecond:%5) %1"

Constant EMSG_DATE_INVALIDHMS

SAP Sybase Error Number 20413

SQL State QBB75

SQL Code -1006175L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

862 SAP Sybase IQ

Errors and Warnings

Error 1006175 "Time is invalid (Hour:%2 Minute:%3 Second:%4

MicroSecond:%5) %1"

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Parameter 4 explanation for arg %4 delete if no %4

Parameter 5 explanation for arg %5 delete if no %5

Probable Cause No additional information available.

Error 1006176 No message

Constant EMSG_DATE_INVALIDDAYS_EMPTY_SLOT

SAP Sybase Error Number 20414

SQL State QBB76

SQL Code -1006176L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006177 "Time is invalid because of the MicroSeconds (%2) %1"

Constant EMSG_DATE_INVALIDUSECONDS

SAP Sybase Error Number 20415

SQL State QBB77

SQL Code -1006177L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

SAP Sybase IQ Error Messages 863

Errors and Warnings

Error 1006177 "Time is invalid because of the MicroSeconds (%2) %1"

Probable Cause No additional information available.

Error 1006178 "DateTime is invalid because of the MicroSeconds from

1/1/0000 (%2) %1"

Constant EMSG_DATE_INVALIDUSECONDSBOE

SAP Sybase Error Number 20416

SQL State QBB78

SQL Code -1006178L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006179 "Cannot allocate space for CS context %1 "

Constant EMSG_DATE_INVALIDCSCONTEXTALLOC

SAP Sybase Error Number 20417

SQL State QBB79

SQL Code -1006179L

SAP Sybase Error Number 20420

SQL State QBB82

SQL Code -1006182L

SAP Sybase Error Number 20423

SQL State QBB85

866 SAP Sybase IQ

Error 1006187 "OS error was found on a lock (mutex,condvar,etc) Call:

error = %2 %1"

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006188 "USEAGE error was found on a lock (mutex,condvar,etc)

Call %1"

Constant EMSG_LOCK_USEERROR

SAP Sybase Error Number 20426

SQL State QBB88

SQL Code -1006188L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006189 "The condition variable was killed %1"

Constant EMSG_LOCK_KILLED

SAP Sybase Error Number 20427

SQL State QBB89

SQL Code -1006189L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006190 "The semaphore variable was canceled %1"

Constant EMSG_SEMA_KILLED

868 SAP Sybase IQ

Errors and Warnings

Error 1006190 "The semaphore variable was canceled %1"

SAP Sybase Error Number 20428

SQL State QBB90

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006193 "Unknown error was found on Thread Call %1"

Constant EMSG_THREAD_DEFAULT

SAP Sybase Error Number 20431

SQL State QBB93

SQL Code -1006193L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006194 "Could not get a thread %1"

Constant EMSG_THREAD_COULDNT_GET_THREAD

SAP Sybase Error Number 20432

SQL State QBB94

SQL Code -1006194L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

870 SAP Sybase IQ

Errors and Warnings

Messages 1006195 through 1006214

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006195 "OS error was found on hos_threadman Call: error = %2

%1"

Constant EMSG_THREADMAN_OSERROR

SAP Sybase Error Number 20433

SQL State QBB95

SQL Code -1006195L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006196 "hos_threadman: the environment variable

HOS_NUM_OF_CPUS does not exist %1"

Constant EMSG_THREADMAN_NOENVVAR

SAP Sybase Error Number 20434

SQL State QBB96

SQL Code -1006196L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 871

Errors and Warnings

Error 1006197 "Unknown error was found during hos_threadman

Constructor %1"

Constant EMSG_THREADMAN_CSTRFAILED

SAP Sybase Error Number 20435

SQL State QBB97

SQL Code -1006197L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006198 "Unknown error was found during hos_threadman

Destructor %1"

Constant EMSG_THREADMAN_DSTRFAILED

SAP Sybase Error Number 20436

SQL State QBB98

SQL Code -1006198L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006199 "Unknown error was found on hos_threadman Call %1"

Constant EMSG_THREADMAN_DEFAULT

SAP Sybase Error Number 20437

SQL State QBB99

SQL Code -1006199L

872 SAP Sybase IQ

SAP Sybase IQ Error Messages 873

Errors and Warnings

Error 1006202 "Syntax error in conversion of string to DATETIME value."

SAP Sybase Error Number 20440

SQL State QBC02

SQL Code -1006202L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006203 "Syntax error in conversion of string to DATE value."

Constant EMSG_INVALID_DATESYNTAX

SAP Sybase Error Number 20441

SQL State QBC03

SQL Code -1006203L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006204 "Syntax error in conversion of string to TIME value."

Constant EMSG_INVALID_TIMESYNTAX

SAP Sybase Error Number 20442

SQL State QBC04

SQL Code -1006204L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

874 SAP Sybase IQ

Errors and Warnings

Errors and Warnings

Error 1006207 "ACCESS exception: OS error %1"

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006208 "CONSTRAINT exception: OS error %2 %1"

Constant EMSG_CONSTRAINT_OSERROR

SAP Sybase Error Number 20446

SQL State QBC08

SQL Code -1006208L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 error number

Probable Cause No additional information available.

Error 1006209 "The exception handler's memory manager could not get
memory during initialization"

Constant EMSG_EXMEM_COULDNOTINIT

SAP Sybase Error Number 20447

SQL State QBC09

SQL Code -1006209L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006210 "The exception handler's memory manager has run out of
memory"

Constant EMSG_EXMEM_OUTOFMEM

876 SAP Sybase IQ

Errors and Warnings

Error 1006210 "The exception handler's memory manager has run out of
memory"

SAP Sybase Error Number 20448

SQL State QBC10

SQL Code -1006210L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006211 "Not all memory was returned to the exception handler's
memory manager"

Constant EMSG_EXMEM_MEMLEAK

SAP Sybase Error Number 20449

SQL State QBC11

SQL Code -1006211L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006212 "The exception handler's memory manager has been

corrupted"

Constant EMSG_EXMEM_MEMCORRUPT

SAP Sybase Error Number 20450

SQL State QBC12

SQL Code -1006212L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 877

Errors and Warnings

Error 1006212 "The exception handler's memory manager has been

corrupted"

Probable Cause No additional information available.

Error 1006213 "Unable to use shared memory because "

Constant EMSG_SHRMEM_BECAUSE

SAP Sybase Error Number 20451

SQL State QBC13

SQL Code -1006213L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006214 "the semaphore for shared memory did not exist"

Constant EMSG_SHRMEM_NO_SUCH_SEMAPHORE

SAP Sybase Error Number 20452

SQL State QBC14

SQL Code -1006214L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Messages 1006215 through 1006234

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006215 "the semaphore for shared memory was deleted"

Constant EMSG_SHRMEM_SEMAPHORE_DELETED

SAP Sybase Error Number 20453

878 SAP Sybase IQ

Errors and Warnings

Error 1006215 "the semaphore for shared memory was deleted"

SQL State QBC15

SQL Code -1006215L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006216 "of insufficient system semaphore resources"

Constant EMSG_SHRMEM_INSUF_SEM_RESOURCES

SAP Sybase Error Number 20454

SQL State QBC16

SQL Code -1006216L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006217 "the system limit on the number of processes allowed to

request semaphore undos would be exceeded"

Constant EMSG_SHRMEM_SEM_UNDOS_ENOSPC

SAP Sybase Error Number 20455

SQL State QBC17

SQL Code -1006217L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 879

Errors and Warnings

Error 1006218 "the system limit on the number of semaphore undo

requests allowed per process (semume) would be
exceeded"

Constant EMSG_SHRMEM_SEM_UNDOS_EINVAL

SAP Sybase Error Number 20456

SQL State QBC18

SQL Code -1006218L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006219 "the creation of a new semaphore would exceed the

system limit on either the maximum number of
semaphores allowed or the maximum number of
semaphore identifiers allowed"

Constant EMSG_SHRMEM_SEMGET_CREATE_ENOSPC

SAP Sybase Error Number 20457

SQL State QBC19

SQL Code -1006219L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006220 "of insufficient system shared memory resources"

Constant EMSG_SHRMEM_INSUF_SHM_RESOURCES

SAP Sybase Error Number 20458

SQL State QBC20

SQL Code -1006220L

ODBC 2 State ERROR

880 SAP Sybase IQ

Errors and Warnings

Error 1006220 "of insufficient system shared memory resources"

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006221 "the creation of a new shared memory segment would

exceed the system limit on the maximum number of shared
segments allowed"

Constant EMSG_SHRMEM_SHMGET_CREATE_ENOSPC

SAP Sybase Error Number 20459

SQL State QBC21

SQL Code -1006221L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006222 "the requested shared memory segment size is less than
the system-imposed minimum (shmmin) or greater than the
system-imposed maximum (shmmax)"

Constant EMSG_SHRMEM_SHMGET_CREATE_EINVAL

SAP Sybase Error Number 20460

SQL State QBC22

Probable Cause No additional information available.

Error 1006226 "you have no permission to access the shared memory

semaphore"

Constant EMSG_SHRMEM_SEM_NO_ACCESS

SAP Sybase Error Number 20464

SQL State QBC26

SQL Code -1006226L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006227 "you have no permission to access the shared memory

segment"

Constant EMSG_SHRMEM_SHM_NO_ACCESS

SAP Sybase Error Number 20465

SQL State QBC27

SQL Code -1006227L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006228 "the attach failed because the shared memory segment
was created by a process with significantly different
settings (e.g. max threads)"

Constant EMSG_SHRMEM_SHM_ATTACH_FAILED

Errors and Warnings

Error 1006230 "lock request was interrupted"

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006231 "ACCESS exception: OS error %2: %3 %1"

Constant EMSG_ACCESS_OSERROR2

SAP Sybase Error Number 20469

SQL State QBC31

SQL Code -1006231L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 error number

Parameter 3 working directory

Probable Cause No additional information available.

Error 1006232 "Unknown ParamSet error %1"

Constant EMSG_PARAM_UNKNOWN

SAP Sybase Error Number 20470

SQL State QBC32

SQL Code -1006232L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 885

Errors and Warnings

Error 1006233 "CONSTRAINT exception: OS error %2: pathname len is

%3, your buffer size is %4. Pathname is %5 %1"

Constant EMSG_CONSTRAINT_OSERROR2

SAP Sybase Error Number 20471

SQL State QBC33

SQL Code -1006233L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 error number

Parameter 3 pathname length

Parameter 4 buffer size

Parameter 5 pathname

Probable Cause No additional information available.

Error 1006234 "The IQ SET command has no option named '%2' %1"

Constant EMSG_PARAM_UNKNOWNPARAM

SAP Sybase Error Number 20472

SQL State QBC34

SQL Code -1006234L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

886 SAP Sybase IQ

Errors and Warnings

Messages 1006235 through 1006255

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006235 "The IQ SET SERVERDEFAULT command requires the

SA_ROLE %1"

Constant EMSG_PARAM_SERVER_ONLY_SA

SAP Sybase Error Number 20473

SQL State QBC35

SQL Code -1006235L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1006237 "The IQ SET option, '%2', can not be set server-wide %1"

Constant EMSG_PARAM_NOT_SET_SERV2

SAP Sybase Error Number 20475

SQL State QBC37

SAP Sybase Error Number 20478

888 SAP Sybase IQ

Errors and Warnings

Error 1006240 "The value, %2, is not valid for the SQL Anywhere option,
'%3' %1"

SQL State QBC40

SQL Code -1006240L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006241 "The value, %2, is not valid for the integer option, '%3' %1"

Constant EMSG_PARAM_BADPARAMVALUEINT

SAP Sybase Error Number 20479

SQL State QBC41

SQL Code -1006241L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006242 "The value, %2, is not valid for the unsigned integer option,
'%3' %1"

Constant EMSG_PARAM_BADPARAMVALUEUINT

SAP Sybase Error Number 20480

SAP Sybase IQ Error Messages 889

Errors and Warnings

Error 1006242 "The value, %2, is not valid for the unsigned integer option,
'%3' %1"

SQL State QBC42

SQL Code -1006242L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006243 "The value, %2, is not valid for the boolean option, '%3' %1"

Constant EMSG_PARAM_BADPARAMVALUEBOOL

SAP Sybase Error Number 20481

SQL State QBC43

SQL Code -1006243L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006244 "The value, %2, is not valid for the unsigned 64bit integer
option, '%3' %1"

Constant EMSG_PARAM_BADPARAMVALUEUINT64

SAP Sybase Error Number 20482

890 SAP Sybase IQ

Errors and Warnings

Error 1006244 "The value, %2, is not valid for the unsigned 64bit integer
option, '%3' %1"

SQL State QBC44

SQL Code -1006244L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006245 "The value, %2, is not valid for the string option, '%3' %1"

Constant EMSG_PARAM_BADPARAMVALUESTRING

SAP Sybase Error Number 20483

SQL State QBC45

SQL Code -1006245L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Parameter 3 explanation for arg %3 delete if no %3

Probable Cause No additional information available.

Error 1006246 No message

Constant EMSG_PARAM_UNKNOWNDATATYPE_EMPTY_SLOT

SAP Sybase Error Number 20484

SQL State QBC46

SAP Sybase IQ Error Messages 891

TEMPSHMEMMB, greater than system limit (max 4GB)"

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006252 "Requested shared memory size, SHMEMMB or

TEMPSHMEMMB, too small (min 1MB)"

Constant EMSG_SHAREDSEG_SHMEMMB_TOO_SMALL

SAP Sybase Error Number 20490

SQL State QBC52

SQL Code -1006252L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006253 "Requested shared memory size, SYSTEMSHMMAX,

greater than system limit"

Constant EMSG_SHAREDSEG_SYSTEMSHMMAX_TOO_BIG

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1006256 "Invalid arithmetic construction %2 %1"

Constant EMSG_NUMERIC_CONSTRUCTOR

SAP Sybase Error Number 20494

SQL State QBC56

SQL Code -1006256L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006257 "Invalid arithmetic conversion %2 %1"

Constant EMSG_NUMERIC_CONVERSION

SAP Sybase Error Number 20495

SQL State QBC57

SQL Code -1006257L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006258 "Invalid arithmetic operation %2 %1"

Constant EMSG_NUMERIC_OPERATOR

896 SAP Sybase IQ

Errors and Warnings

Error 1006258 "Invalid arithmetic operation %2 %1"

SAP Sybase Error Number 20496

SQL State QBC58

SQL Code -1006258L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006259 "Invalid arithmetic function arguments %2 %1"

Constant EMSG_NUMERIC_FUNCTION

SAP Sybase Error Number 20497

SQL State QBC59

SQL Code -1006259L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause No additional information available.

Error 1006260 " Could not open file: "

Constant EMSG_FILEINFO_OPENERR

SAP Sybase Error Number 20498

SQL State QBC60

SQL Code -1006260L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 897

Errors and Warnings

Error 1006260 " Could not open file: "

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006261 "\n\n*** File: %s\n\n"

Constant EMSG_FILENAME

SAP Sybase Error Number 20499

SQL State QBC61

SQL Code -1006261L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006262 " This new operator should never be called "

Constant EMSG_SHOULDNOTCALLNEW

SAP Sybase Error Number 20500

SQL State QBC62

SQL Code -1006262L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006263 " This delete operator should never be called "

Constant EMSG_SHOULDNOTCALLDELETE

SAP Sybase Error Number 20501

SQL State QBC63

898 SAP Sybase IQ

Errors and Warnings

Error 1006263 " This delete operator should never be called "

SQL Code -1006263L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1006264 "Invalid Blocksize %2 less than the Device Sectorsize %3

%4 %1"

Constant EMSG_BIO_INVBLKSZFORDEV

SAP Sybase Error Number 21072

SQL State QBC64

SQL Code -1006264L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 %2 Invalid block size

Parameter 3 %3 Device Sector Size

Parameter 4 %4 Name of Raw device

Probable Cause No additional information available.

Error 1006265 "Invalid Filename: %2. %1"

Constant EMSG_IO_INVALID_FILENAME

SAP Sybase Error Number 21093

SQL State QBC65

SQL Code -1006265L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 899

Errors and Warnings

Error 1006265 "Invalid Filename: %2. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 %2 Invalid filename

Probable Cause A bad filename (perhaps zero-length) was specified.

Error 1006266 "Found bad sector on raw device: %1"

Constant EMSG_RAWIO_BAD_SECTOR

SAP Sybase Error Number 21105

SQL State QBC66

SQL Code -1006266L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A bad sector was detected on the given raw device.

Error 1006267 "%2 blocks is greater than the partition size of %3 blocks
%1"

Constant EMSG_BIO_RESIZETOOBIG

SAP Sybase Error Number 21119

SQL State QBC67

SQL Code -1006267L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 user specified size

Parameter 3 partition size

900 SAP Sybase IQ

Errors and Warnings

Error 1006267 "%2 blocks is greater than the partition size of %3 blocks
%1"

Probable Cause No additional information available.

Error 1006268 "The current operation has been cancelled:

Max_Temp_Space_Per_Connection exceeded"

Constant EMSG_ATTN_MAXTEMPSPACE

SAP Sybase Error Number 21151

SQL State QBC68

SQL Code -1006268L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause User has exhausted maximum temp dbspace limit for this connection

Error 1006269 "No SYSAM License Available"

Constant EMSG_NO_SYSAMLICENSE

SAP Sybase Error Number 21161

SQL State QBC69

SQL Code -1006269L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause SYSAM license for the product is either not available or not config-
ured.

Error 1006270 "SYSAM Failure while doing: %1"

Constant EMSG_SYLAPI_FAILURE

SAP Sybase Error Number 21162

SQL State QBC70

SAP Sybase IQ Error Messages 901

Errors and Warnings

Error 1006270 "SYSAM Failure while doing: %1"

SQL Code -1006270L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Parameter 1 description

Probable Cause SYSAM internal failure.

Error 1006271 "IQ_CORE License has expired"

Constant EMSG_IQCORE_EXPIRED

SAP Sybase Error Number 21163

SQL State QBC71

SQL Code -1006271L

ODBC 2 State ERROR

ODBC 3 State ERROR

Error 1008000 "Users are not allowed to create an FP index. FP indexes

are created automatically when the table is created."

Constant EMSG_IQ_NOCREATEFP

SAP Sybase Error Number 20596

SQL State QNA00

SQL Code -1008000L

SAP Sybase IQ Error Messages 903

Errors and Warnings

Error 1008000 "Users are not allowed to create an FP index. FP indexes

are created automatically when the table is created."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Users are not able to create Fast Projection indexes on columns. They
are created automatically when the table is created.

Messages 1008001 through 1008024

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1008001 "The user cannot create indexes on a join virtual table."

Constant EMSG_IQ_NOCREATEINDEXJVT

SAP Sybase Error Number 20621

SQL State QNA01

SQL Code -1008001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Users cannot create indexes on a join virtual table. They are auto-
matically created.

Error 1008004 "Cannot DROP index '%1'."

Constant EMSG_IQ_NODROPIQINDEX

SAP Sybase Error Number 20673

SQL State QNA04

SQL Code -1008004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

904 SAP Sybase IQ

Errors and Warnings

Error 1008004 "Cannot DROP index '%1'."

Parameter 1 Name of the index the user is attempting to drop.

Probable Cause Users cannot drop internally created indexes except by dropping the
table or alter-dropping the table. Fast Projection indexes are internally
created indexes.

Error 1008005 "Cannot ALTER join virtual table '%1'."

Constant EMSG_IQ_NOALTERJVT

SAP Sybase Error Number 20675

SQL State QNA05

SQL Code -1008005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 The join virtual table the user is attempting to alter.

Probable Cause The user cannot alter a join virtual table.

Error 1008006 "You cannot specify a DEFAULT value for a column."

Constant EMSG_IQ_INVALIDDEFAULT

SAP Sybase Error Number 20676

SQL State QNA06

SQL Code -1008006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The user cannot specify a DEFAULT value for a column during
CREATE TABLE or ALTER TABLE ADD COLUMN.

Error 1008007 "The ALTER TABLE option '%2' is not supported by Sybase
IQ. %1"

Constant EMSG_IQ_NOSUPPORT

SAP Sybase IQ Error Messages 905

Errors and Warnings

Error 1008007 "The ALTER TABLE option '%2' is not supported by Sybase
IQ. %1"

SAP Sybase Error Number 20677

SQL State QNA07

SQL Code -1008007L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 The ALTER TABLE option the user is attempting to use.

Probable Cause The user entered an option that is not supported by Sybase IQ but is
supported by ASA (like REPLICATION ON).

Error 1008008 "You cannot TRUNCATE a join virtual table."

Constant EMSG_IQ_NOTRUNCATEJVT

SAP Sybase Error Number 20679

SQL State QNA08

SQL Code -1008008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The user is not allowed to TRUNCATE a join virtual table.

Error 1008009 "This statement is not supported by Sybase IQ."

Constant EMSG_IQ_STMTNOTSUPPORTED

SAP Sybase Error Number 20680

SQL State QNA09

SQL Code -1008009L

ODBC 2 State ERROR

906 SAP Sybase IQ

Errors and Warnings

Error 1008009 "This statement is not supported by Sybase IQ."

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The statement entered is supported by Adaptive Server Anywhere,

but not by Sybase IQ.

Error 1008010 "A request was made to delete the primary key constraint,
but the primary key cannot be found."

Constant EMSG_IQ_NOPRIMARYKEY

SAP Sybase Error Number 20681

SQL State QNA10

SQL Code -1008010L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The user wanted to delete the primary key constraint on the table but
the primary key could not be found.

Error 1008012 "This unique index/constraint must be ENFORCED."

Constant EMSG_IQ_NEEDENFORCED

SAP Sybase Error Number 20990

SQL State QNA12

SQL Code -1008012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This unique index/constraint must be ENFORCED (The UNEN-

FORCED keyword not allowed for this index/constraint).

SAP Sybase IQ Error Messages 907

Errors and Warnings

Error 1008013 "This multi-column unique index/constraint must be

UNENFORCED."

Constant EMSG_IQ_NEEDUNENFORCED

SAP Sybase Error Number 20991

SQL State QNA13

SQL Code -1008013L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This multi-column unique index/constraint must be UNENFORCED

(The UNENFORCED keyword is required for this index/constraint).

Error 1008014 "This foreign key must be UNENFORCED."

Constant EMSG_IQ_FKEYNOSUPP

SAP Sybase Error Number 20992

SQL State QNA14

SQL Code -1008014L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This foreign key must be UNENFORCED (The UNENFORCED

keyword is required for this foreign key).

Error 1008015 "This check constraint must be ENFORCED."

Constant EMSG_IQ_CHCKENFORCED

SAP Sybase Error Number 20993

SQL State QNA15

SQL Code -1008015L

ODBC 2 State ERROR

ODBC 3 State ERROR

908 SAP Sybase IQ

Errors and Warnings

Error 1008015 "This check constraint must be ENFORCED."

Severity Code 14 on page 2

Probable Cause The keyword UNENFORCED is not supported.

Error 1008016 "Cannot ALTER DELETE a column that has a unique or

primary key constraint."

Constant EMSG_IQ_CONSTRAINTONCOL

SAP Sybase Error Number 20994

SQL State QNA16

SQL Code -1008016L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Cannot ALTER DELETE a column that has a unique or primary key
constraint. This is a duplicate of an SA error code.

Error 1008017 "Cannot ALTER DELETE a column that has multi-column

index."

Constant EMSG_IQ_MULTICOLONINDEX

SAP Sybase Error Number 20995

SQL State QNA17

SQL Code -1008017L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Cannot ALTER DELETE a column that has multi-column index. This
is a duplicate of an SA error code.

Error 1008019 "Multiplex is currently inactive."

Constant EMSG_IQMPX_INACTIVE

SAP Sybase Error Number 21041

SAP Sybase IQ Error Messages 909

Errors and Warnings

Error 1008019 "Multiplex is currently inactive."

SQL State QNA19

SQL Code -1008019L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The user has either requested a multiplex function or has asked for
multiplex status.

Error 1008020 "Multiplex command or request is unimplemented."

Constant EMSG_IQMPX_NOTIMPL

SAP Sybase Error Number 21042

SQL State QNA20

SQL Code -1008020L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The user has requested an unimplemented multiplex feature. This
would typically be a status request which doesn't exist.

Error 1008021 "The SYSIQFILE table is not configured for this server to run in a
multiplex."

Constant EMSG_IQMPX_BADCONFIG

SAP Sybase Error 21043

Number

SQL State QNA21

SQL Code -1008021L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

910 SAP Sybase IQ

Errors and Warnings

Error 1008021 "The SYSIQFILE table is not configured for this server to run in a
multiplex."

Probable Cause SYSIQFILE identifies all files which make up the given stores that the IQ
server requires (main, temp, and message). For multiplex, each entry in
SYSIQFILE must be associated with a particular multiplex server before
that server can access the particular file. This message indicates that some
these rows are missing for the active server.

Error 1008022 "Bad commit identity block. The server may be out of
synchronization. %1"

Constant EMSG_IQMPX_BADCMID

SAP Sybase Error Number 21044

SQL State QNA22

SQL Code -1008022L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Multiplex servers cannot start this database. Start the coordinator in
single server mode.

Error 1008023 "Cannot start multiplex secondary server while the

coordinator is in single server mode"

Constant EMSG_IQMPX_SPXDB

SAP Sybase Error Number 21045

SQL State QNA23

SQL Code -1008023L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Restart the secondary server after the coordinator has restarted in
normal mode.

SAP Sybase IQ Error Messages 911

Errors and Warnings

Error 1008024 "Multiplex coordinator must start as server@host: %2, on

file: %3; to start with different settings, you must use the
override switch. %1"

Constant EMSG_IQMPX_TWOWRITERS

SAP Sybase Error Number 21046

SQL State QNA24

SQL Code -1008024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 server@host names for coordinator

Parameter 3 catalog db filename for coordinator

Probable Cause Only the configured coordinator can start the database. Start with the
override switch (-iqmpx_ov 1) to bypass this check.

Messages 1008025 through 1009019

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1008025 "Multiplex secondary server cannot continue while the

coordinator is in single server mode. %1"

Constant EMSG_IQMPX_SPXONLY

SAP Sybase Error Number 21047

SQL State QNA25

SQL Code -1008025L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

912 SAP Sybase IQ

Errors and Warnings

Error 1008025 "Multiplex secondary server cannot continue while the

coordinator is in single server mode. %1"

Probable Cause Resynchronize and restart the secondary server after the coordinator
has restarted in normal mode.

Error 1008026 "Multiplex secondary server out of synchronization with

the coordinator. %1"

Constant EMSG_IQMPX_CATSYNC

SAP Sybase Error Number 21048

SQL State QNA26

SQL Code -1008026L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The secondary server's IQ catalog cannot be brought up to date with
the coordinator's IQ catalog. This server must be synchronized.

Error 1008027 "Multiplex secondary node shutting down due to a file added
to the IQ_SYSTEM_MAIN dbspace.\nThis node must be
synchronized and restarted. %1"

Constant EMSG_IQMPX_SEGCOUNT

SAP Sybase Error Num- 21057

ber

SQL State QNA28

SQL Code -1008027L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 913

Errors and Warnings

Error 1008027 "Multiplex secondary node shutting down due to a file added
to the IQ_SYSTEM_MAIN dbspace.\nThis node must be
synchronized and restarted. %1"

Probable Cause The user has added a dbspace file to IQ_SYSTEM_MAIN on the co-
ordinator. This causes secondary nodes to shut down. All secondary
nodes must be synchronized and restarted after this operation.

Error 1008029 "Cannot create foreign key to an unenforced primary key

or unenforced unique constraint."

Constant EMSG_NOFKEY_TO_UNENFORCED

SAP Sybase Error Number 21059

SQL State QNA29

SQL Code -1008029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Existing unenforced primary keys or unique constraints cannot be

used to create an referential integrity relationship to a foreign table.

Error 1008030 "Only IQ index types can be created on IQ tables within a

Parallel IQ block."

Constant EMSG_SQL_PLBEGINONLYCI

SAP Sybase Error 21064

Number

SQL State QNA30

SQL Code -1008030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Parallel IQ Begin/End blocks allow users to create multiple indexes si-
multaneously. At this time, only Create Index statements for HG, HNG,
LF, LD, DATE, TIME, WD, and CMP index types on IQ tables are allowed
within Parallel IQ Begin and End statements.

914 SAP Sybase IQ

Errors and Warnings

Error 1008031 "Cannot do Create Index commands on global or local

temporary tables or catalog server tables in a Parallel IQ
block."

Constant EMSG_SQL_NOTEMPINPLB

SAP Sybase Error Number 21065

SQL State QNA31

SQL Code -1008031L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause Cannot do Create Index commands on global or local temporary

tables in a Parallel IQ block.

Error 1008032 "Foreign keys disallowed on Identity/Autoincrement Columns

when set option identity_enforce_uniqueness is on"

Constant EMSG_FOREIGN_KEY_DISALLOWED

SAP Sybase Error 20026

Number

SQL State QNA41

SQL Code -1008032L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause An Identity/Autoincrement Column cannot be a foreign key when the set
option identity_enforce_uniqueness is on. Either turn the option off, or
chose a different column for the foreign key.

Error 1008033 "Identity/Autoincrement Column %2 has Invalid datatype:

scale must be 0. %1"

Constant EMSG_NON_ZERO_SCALE

SAP Sybase Error Number 20027

SQL State QNA42

SAP Sybase IQ Error Messages 915

Errors and Warnings

Error 1008033 "Identity/Autoincrement Column %2 has Invalid datatype:

scale must be 0. %1"

SQL Code -1008033L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause Identity/Autoincrement Columns defined as datatype numeric must

have scale 0

Error 1008035 "Invalid datatype for Identity/Autoincrement Column %2.

%1"

Constant EMSG_INVALID_DATATYPE

SAP Sybase Error Number 20029

SQL State QNA44

SQL Code -1008035L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause The datatype used is not supported by Identity/Autoincrement col-

umn. Valid datatypes are bigint, unsigned bigint, integer, unsigned
integer, smallint, tinyint, numeric scale 0 and decimal scale 0

Error 1008036 "Table %2 already has an Identity/Autoincrement Column.

%1 "

Constant EMSG_ALREADY_HAS_IDENTITY_COLUMN

SAP Sybase Error Number 20642

SQL State QNA45

916 SAP Sybase IQ

Errors and Warnings

Error 1008036 "Table %2 already has an Identity/Autoincrement Column.

%1 "

SQL Code -1008036L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Table name

Probable Cause An Identity/Autoincrement Column cannot be added to this table

because it already has one.

Error 1008037 "Cannot drop %1 %2: set option 'identity_insert' must be

off. "

Constant EMSG_IDENTITY_INSERT_IS_ON

SAP Sybase Error Number 20643

SQL State QNA46

SQL Code -1008037L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 string literal 'Table' or 'Column'

Parameter 2 column name

Probable Cause option 'identity insert' must not be set to any table name to drop an
Identity Column. To turn it off use 'set identity_insert '' '

Error 1008038 "create schema command not allowed on an active

multiplex server. "

Constant EMSG_NOSCHEMACMD_MULTIPLEX

SAP Sybase Error Number 21123

SQL State QNA47

SQL Code -1008038L

SAP Sybase IQ Error Messages 917

Errors and Warnings

Error 1008038 "create schema command not allowed on an active

multiplex server. "

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause the create schema command is not allowed on an active multiplex
server

Error 1008039 "Permission denied: The current multiplex server is not a

writer server"

Constant EMSG_MPX_GLOBAL_CMD_PERMISSION_DENIED

SAP Sybase Error Number 22005

SQL State QNA48

SQL Code -1008039L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The global command is not permitted on current multiplex node

Error 1009000 "Bit %2 is unexpectedly on in bitmap. If the error persists,

you may have a damaged index; please run sp_iqcheckdb.
%1"

Constant EMSG_BM_BITON

SAP Sybase Error Number 20021

SQL State QSA00

SQL Code -1009000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Bit that is on.

918 SAP Sybase IQ

Errors and Warnings

Error 1009000 "Bit %2 is unexpectedly on in bitmap. If the error persists,

you may have a damaged index; please run sp_iqcheckdb.
%1"

Probable Cause This is either an internal calling error (some component called bitmap
SET with a duplicate bit), a corrupt bitmap (and dbcc needs be run), or
a bitmap operator that has gone awry and mis-computed a result.

Error 1009001 "Bit %2 is unexpectedly off in bitmap. If the error persists,

you may have a damaged index; please run sp_iqcheckdb.
%1"

Constant EMSG_BM_BITOFF

SAP Sybase Error Number 20022

SQL State QSA01

SQL Code -1009001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Bit that is off.

Probable Cause This is either an internal calling error (some component called bitmap
CLEAR with a duplicate bit), a corrupt bitmap (and dbcc needs be
run), or a bitmap operator that has gone awry and mis-computed a
result.

Warning 1009002 " Index %2: Starting Insert Pass 2. %1"

Constant EMSG_HG_STARTING_PASS2

SAP Sybase Error Number 20023

SQL State 00002

SQL Code 1009002L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

SAP Sybase IQ Error Messages 919

Errors and Warnings

Warning 1009002 " Index %2: Starting Insert Pass 2. %1"

Parameter 1 location of the exception

Parameter 2 Index name

Probable Cause No additional information available.

Warning 1009003 " Index %1: Thread %2 Inserting %3 Recs, %4 Secs."

Constant EMSG_HG_INSERTED

SAP Sybase Error Number 20024

SQL State 00003

SQL Code 1009003L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 Index name

Parameter 2 Thread index

Parameter 3 Number of records

Parameter 4 Time

Probable Cause No additional information available.

Error 1009004 "Statistics context = %2 %3\n %1"

Constant EMSG_STATS_CONTEXT

SAP Sybase Error Number 20025

SQL State QSA04

SQL Code -1009004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 majContext

920 SAP Sybase IQ

Errors and Warnings

Error 1009004 "Statistics context = %2 %3\n %1"

Parameter 3 minContext

Probable Cause No additional information available.

Error 1009012 "Cannot create %2 index on a column having a datatype

%3. %1"

Constant EMSG_ERROR_INDEX_NOTALLOWED

SAP Sybase Error Number 20033

SQL State QSA12

SQL Code -1009012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the index type (e.g., LF, HG)

Parameter 3 textual name of the column's datatype

Probable Cause A named index type index cannot be created on named datatype

Error 1009019 "An internal server component, a bitmap, was given invalid
input. %1"

Constant EMSG_BM_BADINPUT

SAP Sybase Error Number 20040

SQL State QSA19

SQL Code -1009019L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 921

Errors and Warnings

Error 1009019 "An internal server component, a bitmap, was given invalid
input. %1"

Probable Cause Some non-bitmap component has called a bitmap with an illegal
argument. This is an internal programming error and not the (direct)
result of customer error.

Messages 1009021 through 1009040

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009021 "This server must first be started in Multiplex single-node

mode (-iqmpx_sn 1) %1"

Constant EMSG_DATABASE_MPX_BADTLVFORMAT_START_SINGLE

SAP Sybase Error Number 20042

SQL State QSA21

SQL Code -1009021L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The tlv log has an incorrect format

Error 1009022 "Cannot create a WD index on a column narrower than 3

bytes. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_CW2SMALL

SAP Sybase Error Number 20043

SQL State QSA22

SQL Code -1009022L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

922 SAP Sybase IQ

Errors and Warnings

Error 1009022 "Cannot create a WD index on a column narrower than 3

bytes. %1"

Probable Cause No additional information available.

Error 1009023 "Cannot create a WD index on a column wider than 32767

bytes. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_CW2LARGE

SAP Sybase Error Number 20044

SQL State QSA23

SQL Code -1009023L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009024 "Cannot create a WD index with a max permitted word size
less than 1 byte. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_WL2SMALL

SAP Sybase Error Number 20045

SQL State QSA24

SQL Code -1009024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009025 "Cannot create a WD index with a max permitted word size
greater than 255 bytes. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_WL2LARGE

SAP Sybase IQ Error Messages 923

Errors and Warnings

Error 1009025 "Cannot create a WD index with a max permitted word size
greater than 255 bytes. %1"

SAP Sybase Error Number 20046

SQL State QSA25

SQL Code -1009025L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009026 "Cannot create a WD index with a separator string this

long. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_SS2LARGE

SAP Sybase Error Number 20047

SQL State QSA26

SQL Code -1009026L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009027 "Cannot create a WD index with a separator string

containing a character fragment. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_SSFRAG

SAP Sybase Error Number 20048

SQL State QSA27

SQL Code -1009027L

ODBC 2 State ERROR

924 SAP Sybase IQ

Errors and Warnings

Error 1009027 "Cannot create a WD index with a separator string

containing a character fragment. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009028 "Cannot create a WD index with more than 256 separators.
%1"

Constant EMSG_ERROR_WD_NOTALLOWED_NS2LARGE

SAP Sybase Error Number 20049

SQL State QSA28

SQL Code -1009028L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009029 "Words exceeding the maximum permitted word length not
supported. %1"

Constant EMSG_ERROR_WD_TRUNCWORD_NOT_SUPPORTED

SAP Sybase Error Number 20050

SQL State QSA29

SQL Code -1009029L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 925

Errors and Warnings

Error 1009030 "Cannot create a WD index with the database IQ pagesize

less than 4KB. %1"

Constant EMSG_ERROR_WD_NOTALLOWED_PS2SMALL

SAP Sybase Error Number 20051

SQL State QSA30

SQL Code -1009030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009031 "%2: All buffer cache pages are in use, ask your DBA to
increase the size of the buffer cache. %1"

Constant EMSG_BUFMAN_ALLSLOTSLOCKED

SAP Sybase Error Number 20052

SQL State QSA31

SQL Code -1009031L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Probable Cause No additional information available.

Error 1009032 "%2: Bio ptr must be non-null; buffer={%3} page={%4}.

%1"

Constant EMSG_BUFMAN_BADBIOP

SAP Sybase Error Number 20053

SQL State QSA32

926 SAP Sybase IQ

Errors and Warnings

Error 1009032 "%2: Bio ptr must be non-null; buffer={%3} page={%4}.

%1"

SQL Code -1009032L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009033 "%2: Blocksize must be a multiple of sizeof(hos_mrdtype

& hos_uint) and > 0; buffer={%3} page={%4}. %1"

Constant EMSG_BUFMAN_BADBLOCKSIZE

SAP Sybase Error Number 20054

SQL State QSA33

SQL Code -1009033L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009034 "%2: The number of blocks must be > 0; buffer={%3}

page={%4}. %1"

Constant EMSG_BUFMAN_BADNUMOFBLKS

SAP Sybase IQ Error Messages 927

Errors and Warnings

Error 1009034 "%2: The number of blocks must be > 0; buffer={%3}

page={%4}. %1"

SAP Sybase Error Number 20055

SQL State QSA34

SQL Code -1009034L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009035 "%2: The logical or physical block number must be > 0;
buffer={%3} page={%4}. %1"

Constant EMSG_BUFMAN_BADBLOCKNUMBER

SAP Sybase Error Number 20056

SQL State QSA35

SQL Code -1009035L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

928 SAP Sybase IQ

Errors and Warnings

Error 1009035 "%2: The logical or physical block number must be > 0;
buffer={%3} page={%4}. %1"

Probable Cause Typically, production builds will abort here if trying to Find() a page
that does not exist (non-existent pages have a 0 pbn in the blockmap
entry).

Error 1009036 "%2: Invalid compression type; buffer={%3} page={%4}.

%1"

Constant EMSG_BUFMAN_BADCTYPE

SAP Sybase Error Number 20057

SQL State QSA36

SQL Code -1009036L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009037 "%2: Buffer was not locked when it should have been;
buffer={%3} page={%4}. %1"

Constant EMSG_BUFMAN_MUSTBEACTIVEBUF

SAP Sybase Error Number 20058

SQL State QSA37

SQL Code -1009037L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

SAP Sybase IQ Error Messages 929

Errors and Warnings

Error 1009037 "%2: Buffer was not locked when it should have been;
buffer={%3} page={%4}. %1"

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009038 "%2: Tried to write to a readonly database; buffer={%3}

page={%4}. %1"

Constant EMSG_BUFMAN_MUSTHAVERWACCESS

SAP Sybase Error Number 20059

SQL State QSA38

SQL Code -1009038L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009039 "%2: An error was detected on a database page. You may have
a damaged index. For additional information, please check
your IQ message file or run sp_iqcheckdb. %1"

Constant EMSG_BUFMAN_INCORRECT_DISKBLOCKHEADER

SAP Sybase Error Num- 20060

ber

SQL State QSA39

SQL Code -1009039L

ODBC 2 State ERROR

930 SAP Sybase IQ

Errors and Warnings

Error 1009039 "%2: An error was detected on a database page. You may have
a damaged index. For additional information, please check
your IQ message file or run sp_iqcheckdb. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Probable Cause When we read a page from the database, we detected that its header was
either corrupt or that the header did not correspond to the page we thought
we were reading. This is normally a fatal error; the database itself is likely
to be corrupt.

Error 1009040 "%2: Memory & disk block number mismatch; buffer={%3}
page={%4}. %1"

Constant EMSG_BUFMAN_BIO_MISMATCH_BLOCK

SAP Sybase Error Number 20061

SQL State QSA40

SQL Code -1009040L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 931

Errors and Warnings

Messages 1009041 through 1009060

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009041 "%2: Memory & disk block type mismatch; buffer={%3}
page={%4}. %1"

Constant EMSG_BUFMAN_BIO_MISMATCH_BTYPE

SAP Sybase Error Number 20062

SQL State QSA41

SQL Code -1009041L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009042 "%2: Attempted to write a page that was not dirty;
buffer={%3} page={%4}. %1"

Constant EMSG_BUFMAN_BIO_NOTDIRTY

SAP Sybase Error Number 20063

SQL State QSA42

SQL Code -1009042L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

932 SAP Sybase IQ

Errors and Warnings

Error 1009042 "%2: Attempted to write a page that was not dirty;
buffer={%3} page={%4}. %1"

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009043 "%2: Memory & disk number of blocks mismatch. %1"

Constant EMSG_BUFMAN_BIO_MISMATCH_NBLKS

SAP Sybase Error Number 20064

SQL State QSA43

SQL Code -1009043L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Probable Cause No additional information available.

Error 1009044 "An IO error was encountered while reading a database

page in %2 DBSpace. %1"

Constant EMSG_BUFMAN_BIO_READ_ERROR

SAP Sybase Error Number 20065

SQL State QSA44

SQL Code -1009044L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) dbspace name

SAP Sybase IQ Error Messages 933

Errors and Warnings

Error 1009044 "An IO error was encountered while reading a database

page in %2 DBSpace. %1"

Probable Cause No additional information available.

Error 1009045 "Bitmap failed internal checks. You may have a damaged
index. Please check your IQ message file for additional
information. %1"

Constant EMSG_BM_VERIFY

SAP Sybase Error Number 20066

SQL State QSA45

SQL Code -1009045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Probable Cause No additional information available.

Error 1009046 "%2: An error was detected on a database page. You may
have a damaged index. For additional information, please
check your IQ message file or run sp_iqcheckdb. %1"

Constant EMSG_BUFMAN_DECOMPRESSION_ERROR

SAP Sybase Error Number 20067

SQL State QSA46

SQL Code -1009046L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Probable Cause No additional information available.

934 SAP Sybase IQ

Errors and Warnings

Error 1009047 "%2: Blockmap info error; bmp={%3}. %1"

Constant EMSG_BUFMAN_BLOCKMAP_INFO_ERROR

SAP Sybase Error Number 20068

SQL State QSA47

SQL Code -1009047L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the blockmap

Probable Cause No additional information available.

Error 1009048 "%2: Tried to destroy a userlocked buffer; buffer={%3}

page={%4}. %1"

Constant EMSG_BUFMAN_LOCK_DURINGDESTROY

SAP Sybase Error Number 20069

SQL State QSA48

SAP Sybase Error Number 20072

SQL State QSA51

SQL Code -1009051L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009052 "Internal error. Index %2 does not yet support the
requested operation. %1"

Constant EMSG_INDEX_OPERATION_NOT_IMPLEMENTED

SAP Sybase Error Number 20073

SQL State QSA52

SQL Code -1009052L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 name of the index

Probable Cause An operation, for example SUM, was forwarded to an index, for
example HG, that does not directly implement the operation. Nor-
mally, this should not be possible, but can be forced by setting com-
mand options.

Error 1009053 "%2: s_dbmvbio WriteCheck failed; buffer={%3}

page={%4}. %1"

Constant EMSG_BUFMAN_BIO_WRITECHECK

SAP Sybase IQ Error Messages 937

Errors and Warnings

Error 1009053 "%2: s_dbmvbio WriteCheck failed; buffer={%3}

page={%4}. %1"

SAP Sybase Error Number 20074

SQL State QSA53

SQL Code -1009053L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the sbuf involved, if any.

Parameter 4 4) Information about the disk block header involved, if any.

Probable Cause No additional information available.

Error 1009054 "Command prohibited on a multiplex coordinator, %1"

Constant EMSG_NOCMD_MPX_WRITE

SAP Sybase Error Number 20075

SQL State QSA54

SQL Code -1009054L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause Command not allowed on a multiplex coordinator

Error 1009055 "Command prohibited on a multiplex query server, %1"

Constant EMSG_NOCMD_MPX_QUERY

SAP Sybase Error Number 20076

SQL State QSA55

938 SAP Sybase IQ

Errors and Warnings

Error 1009055 "Command prohibited on a multiplex query server, %1"

SQL Code -1009055L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Command not allowed on a multiplex query server

Error 1009056 "Command prohibited on a multiplex server, %1"

Constant EMSG_NOCMD_MPX_SERVER

SAP Sybase Error Number 20077

SQL State QSA56

SQL Code -1009056L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Command not allowed on a multiplex server

Error 1009057 "Cannot make all dbspaces readonly while there are active
or uncheckpointed readwrite transactions, %1"

Constant EMSG_CANNOT_ALTER_TOALLRO

SAP Sybase Error Number 20078

SQL State QSA57

SQL Code -1009057L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 939

Errors and Warnings

Error 1009057 "Cannot make all dbspaces readonly while there are active
or uncheckpointed readwrite transactions, %1"

Probable Cause Cannot make the last rw dbspace ro while there is rw activity.

Error 1009058 "There are no dbspaces open in readwrite mode for this
RW operation, %1"

Constant EMSG_NO_RWDBSPACE

SAP Sybase Error Number 20079

SQL State QSA58

SQL Code -1009058L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009059 "Alter dbspace relocate requires at least one other

readwrite dbspace (%2). %1"

Constant EMSG_SDBEXT_NEEDRWFORRR

SAP Sybase Error Number 20080

SQL State QSA59

SQL Code -1009059L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause Cannot alter the only readwrite dbspace to relocate mode.

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009064 "Cannot create or add file %2 for dbspace %3 until new readwrite
space is added to dbspace %4 to hold the new freelist. %1"

Constant EMSG_SDBEXT_NO_FREELIST_SPACE

SAP Sybase Error 20085

Number

SQL State QSA64

SQL Code -1009064L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 pathname of file being created

Parameter 3 name of dbspace for which file is being created

Parameter 4 name of IQ_SYSTEM_MAIN dbspace

942 SAP Sybase IQ

Errors and Warnings

Error 1009064 "Cannot create or add file %2 for dbspace %3 until new readwrite
space is added to dbspace %4 to hold the new freelist. %1"

Probable Cause When creating a new dbspace in the IQ MAIN STORE, or creating a new file
for a dbspace other than IQ_SYSTEM_MAIN in the IQ MAIN STORE, there
must if sufficient freelist space available to describe the physical blocks we
are adding to the database. If this is not the case, the above error occurs. (The
space for the freelist can only be allocated in readwrite IQ_SYSTEM_MAIN
files.) The corrective action is to first add a new file to the IQ_SYS-
TEM_MAIN dbspace so that new freelist space becomes available.

Error 1009065 "Operation '%2' not allowed in forced recovery. %1"

Constant EMSG_DBSPACE_NOT_IN_FORCEDRECOVERY

SAP Sybase Error Number 20086

SQL State QSA65

SQL Code -1009065L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Dbspace name

Probable Cause Certain operations are not permitted in forced recovery

Error 1009066 "Cannot execute '%2' yet since previous alter command is
not yet propagated through the multiplex. Try again. %1"

Constant EMSG_CMD_NOT_REPLAYED

SAP Sybase Error Number 20087

SQL State QSA66

SQL Code -1009066L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 943

Errors and Warnings

Error 1009066 "Cannot execute '%2' yet since previous alter command is
not yet propagated through the multiplex. Try again. %1"

Parameter 2 Dbspace name

Probable Cause The command cannot be executed since the previous alter/create
command has not propagated through multiplex yet.

Error 1009067 "%1"

Constant EMSG_RFU_QSA67

SAP Sybase Error Number 20088

SQL State QSA67

SQL Code -1009067L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009068 "Tried to insert a duplicate entry. %1"

Constant EMSG_HASHTB_DUPENTRY

SAP Sybase Error Number 20089

SQL State QSA68

SQL Code -1009068L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009069 "Could not find key in hashtable"

Constant EMSG_HASHTB_KEYNOTFOUND

944 SAP Sybase IQ

Errors and Warnings

Error 1009069 "Could not find key in hashtable"

SAP Sybase Error Number 20090

SQL State QSA69

SQL Code -1009069L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1009070 "Hashtable is full"

Constant EMSG_HASHTB_FULL

SAP Sybase Error Number 20091

SQL State QSA70

SQL Code -1009070L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1009071 "Hash input key descriptor has zero fields (%2, %3). %1"

Constant EMSG_PHASH_NOKEY

SAP Sybase Error Number 20092

SQL State QSA71

SQL Code -1009071L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

SAP Sybase IQ Error Messages 945

Errors and Warnings

Error 1009071 "Hash input key descriptor has zero fields (%2, %3). %1"

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009072 "Insufficient buffers for hash. (%2, %3). %1"

Constant EMSG_PHASH_MAXBUFFERS

SAP Sybase Error Number 20093

SQL State QSA72

SQL Code -1009072L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause Specifically, the number of estimated buffers given to the hash object
exceeds the size of the buffer cache.

Error 1009073 "Hash function can't handle this datatype (%2, %3). %1"

Constant EMSG_PHASH_HASHDT

SAP Sybase Error Number 20094

SQL State QSA73

SQL Code -1009073L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

946 SAP Sybase IQ

Errors and Warnings

Error 1009073 "Hash function can't handle this datatype (%2, %3). %1"

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009074 "Key length in hash equality function is zero (%2, %3). %1
"

Constant EMSG_PHASH_EQUALKEYLEN

SAP Sybase Error Number 20095

SQL State QSA74

SQL Code -1009074L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009075 "Buffer mapper init incorrect (%2, %3). %1"

Constant EMSG_PHASH_BUFMAPINIT

SAP Sybase Error Number 20096

SQL State QSA75

SQL Code -1009075L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 947

Errors and Warnings

Error 1009075 "Buffer mapper init incorrect (%2, %3). %1"

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009076 "Internal hash error; buffer was previously created: %2

(%3, %4). %1"

Constant EMSG_PHASH_BUFDOUBLECREATE

SAP Sybase Error Number 20097

SQL State QSA76

SQL Code -1009076L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) Buffer Number.

Parameter 3 3) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 4 4) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009077 "Internal hash error; next data entry should be valid (%2,
%3). %1"

Constant EMSG_PHASH_INVALID_NEXTENTRY

SAP Sybase Error Number 20098

SQL State QSA77

948 SAP Sybase IQ

Errors and Warnings

Error 1009077 "Internal hash error; next data entry should be valid (%2,
%3). %1"

SQL Code -1009077L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009078 "Internal hash error; buffer not pinned (%2, %3). %1"

Constant EMSG_PHASH_NOT_PINNED

SAP Sybase Error Number 20099

SQL State QSA78

SQL Code -1009078L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009079 "Internal hash error; too many buffers left in use: %2 (%3,
%4). %1"

Constant EMSG_PHASH_INUSE_HIGH

SAP Sybase IQ Error Messages 949

Errors and Warnings

Error 1009079 "Internal hash error; too many buffers left in use: %2 (%3,
%4). %1"

SAP Sybase Error Number 20100

SQL State QSA79

SQL Code -1009079L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) Number of buffers.

Parameter 3 3) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 4 4) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009080 "Key doesn't fit on a single database page: %2 (%3, %4).
%1"

Constant EMSG_PHASH_KEY_TOO_LARGE

SAP Sybase Error Number 20101

SQL State QSA80

SQL Code -1009080L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) Key size.

Parameter 3 3) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

950 SAP Sybase IQ

Errors and Warnings

Error 1009080 "Key doesn't fit on a single database page: %2 (%3, %4).
%1"

Parameter 4 4) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009081 "Data doesn't fit on a single database page: %2 (%3, %4).
%1"

Constant EMSG_PHASH_DATA_TOO_LARGE

SAP Sybase Error Number 20102

SQL State QSA81

SQL Code -1009081L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) Data size.

Parameter 3 3) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 4 4) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Messages 1009082 through 1009101

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009082 "Hash object has no data to retrieve, only keys (%2, %3).
%1"

Constant EMSG_PHASH_NO_DATA

SAP Sybase Error Number 20103

SQL State QSA82

SAP Sybase IQ Error Messages 951

Errors and Warnings

Error 1009082 "Hash object has no data to retrieve, only keys (%2, %3).
%1"

SQL Code -1009082L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) major context (hos_StatsObj::SubStatementId, usually dfo num-

ber)

Parameter 3 3) minor context (s_phash::StatMinorContext, see s_phash.h for

enum)

Probable Cause No additional information available.

Error 1009083 "DBSpace '%2' must be OFFLINE for ALTER PATH. %1"

Constant EMSG_ALTER_PATH_REQUIRES_OFFLINE_DBSPACE

SAP Sybase Error Number 20104

SQL State QSA83

SQL Code -1009083L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause No additional information available.

Error 1009084 "Error opening DBSPACE '%2'. %1"

Constant EMSG_DBSPACE_OPEN_ERROR

SAP Sybase Error Number 20105

SQL State QSA84

SQL Code -1009084L

952 SAP Sybase IQ

Errors and Warnings

Error 1009084 "Error opening DBSPACE '%2'. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause No additional information available.

Error 1009085 "DBFILE '%2' is not valid. The catalog DBSpaceID is

incorrect. DBSpaceID found: %3 DBSpaceID expected:
%4. This segment cannot be used. %1"

Constant EMSG_BAD_CAT_DBSPACEID

SAP Sybase Error Number 20106

SQL State QSA85

SQL Code -1009085L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 file path

Parameter 3 dbspace_id found

Parameter 4 dbspace_id expected

Probable Cause No additional information available.

Error 1009086 "Error opening DBFILE '%2'. %1"

Constant EMSG_DBFILE_OPEN_ERROR

SAP Sybase Error Number 20107

SQL State QSA86

SQL Code -1009086L

SAP Sybase IQ Error Messages 953

Errors and Warnings

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Key value.

Probable Cause No additional information available.

Error 1009090 "Page size selected is too small for this datatype. %1"

Constant EMSG_BT_LARGERPAGE

SAP Sybase Error Number 20111

SQL State QSA90

SQL Code -1009090L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Parameter 1 description

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 955

Errors and Warnings

Error 1009091 "Attempt to create a B-Tree with RecordSize+KeySize too

large. %1"

Constant EMSG_BT_SIZEERROR

SAP Sybase Error Number 20112

SQL State QSA91

SQL Code -1009091L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009092 "Must provide a key comparison routine on object

creation. %1"

Constant EMSG_BT_NOKEYCOMPARE

SAP Sybase Error Number 20113

SQL State QSA92

SQL Code -1009092L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009093 "The maximum key size must be between 1 and 5300. Key
size: %2 %1"

Constant EMSG_BT_MAXKEYSIZEWRONG

SAP Sybase Error Number 20114

SQL State QSA93

SQL Code -1009093L

956 SAP Sybase IQ

Error 1009095 "MESSAGE LOG and ROW LOG cannot be the same on-
disk file. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The MESSAGE LOG and ROW LOG files cannot be the same on-
disk files.

Error 1009096 "%3 integrity constraint limit (%2) exceeded. %1"

Constant EMSG_SVIOLATION_IGNORE_LIMIT_EXCEEDED

SAP Sybase Error Number 20117

SQL State QSA96

SQL Code -1009096L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 user specified integrity constraint limit

Parameter 3 type of integrity constraint violation specified by the user

Probable Cause The number of integrity constraint violations for the given type has
been exceeded during the LOAD. The LOAD will rollback.

Error 1009097 "Cumulative total (%2) for all integrity constraint violations
exceeded. %1"

Constant EMSG_SVIOLATION_ALL_LIMIT_EXCEEDED

SAP Sybase Error Number 20118

SQL State QSA97

SQL Code -1009097L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

958 SAP Sybase IQ

Errors and Warnings

Error 1009097 "Cumulative total (%2) for all integrity constraint violations
exceeded. %1"

Parameter 1 location of exception

Parameter 2 maximum number of constraint violations to ignore

Probable Cause The total number of NULL, UNIQUE, DATA VALUE, and FOR-
EIGN KEY integrity constraint violations has exceeded the user
specified limit.

Error 1009098 "Invalid MESSAGE LOG or ROW LOG filename. %1"

Constant EMSG_SVIOLATION_INVALID_FILENAME

SAP Sybase Error Number 20119

SQL State QSA98

SQL Code -1009098L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Probable Cause A bad filename (perhaps zero-length) was specified for either the
MESSAGE LOG or ROW LOG files on the LOAD statement.

Error 1009099 "%1"

Constant EMSG_RFU_QSA99

SAP Sybase Error Number 20120

SQL State QSA99

SQL Code -1009099L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 959

Errors and Warnings

Error 1009100 "Database segment '%2' is not valid. It is of type '%3'. Type
BTYPE_DBEXT was expected. This segment cannot be
used. %1"

Constant EMSG_SDBEXT_BAD_BTYPE

SAP Sybase Error Num- 20121

ber

SQL State QSB00

SQL Code -1009100L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the segment.

Parameter 3 Internal segment type found.

Probable Cause The segment type written to the segment header was found not to be of
the expected type. You will need to restore your database from backup.

Error 1009101 "Database segment '%2' is not valid. PhysicalNBlocks

Found: %3 PhysicalNBlocks Expected: 1. This segment
cannot be used. %1"

Constant EMSG_SDBEXT_BAD_NUMPHYSBLOCKS

SAP Sybase Error Number 20122

SQL State QSB01

SQL Code -1009101L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the segment.

Parameter 3 Number of Physical Blocks found.

960 SAP Sybase IQ

Errors and Warnings

Error 1009101 "Database segment '%2' is not valid. PhysicalNBlocks

Found: %3 PhysicalNBlocks Expected: 1. This segment
cannot be used. %1"

Probable Cause The number of physical blocks read from the segment header is in-
correct. You will need to restore your database from backup.

Messages 1009102 through 1009121

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009102 "Incorrect HG Index Version (%2): Index must be dropped

by previous version of Sybase IQ and recreated. %1"

Constant EMSG_ERROR_VERSION

SAP Sybase Error Number 20123

SQL State QSB02

SQL Code -1009102L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Incorrect version of index.

Probable Cause No additional information available.

Error 1009103 "Number of unique values exceeded for index. %2 %3 %1"

Constant EMSG_ERROR_KVTMAX

SAP Sybase Error Number 20124

SQL State QSB03

SQL Code -1009103L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 961

Errors and Warnings

Error 1009103 "Number of unique values exceeded for index. %2 %3 %1"

Parameter 1 location of the exception

Parameter 2 Index.

Parameter 3 Number of values.

Probable Cause No additional information available.

Error 1009104 "Bad args, both values must be >= 1 (%2 %3). %1"

Constant EMSG_VDO_BADARGS

SAP Sybase Error Number 20125

SQL State QSB04

SQL Code -1009104L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Value 1

Parameter 3 Value 2

Probable Cause No additional information available.

Error 1009105 "Could not find block: %2. %1"

Constant EMSG_VDO_BLKNOTFOUND

SAP Sybase Error Number 20126

SQL State QSB05

SQL Code -1009105L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Block Number

962 SAP Sybase IQ

Errors and Warnings

Error 1009105 "Could not find block: %2. %1"

Probable Cause No additional information available.

Error 1009106 "DBFILE '%2' is not valid. The catalog file id is incorrect.
FileID found: %3 FileID expected: %4. This segment cannot
be used. %1"

Constant EMSG_SDBEXT_BAD_CATFILEID

SAP Sybase Error Num- 20127

ber

SQL State QSB06

SQL Code -1009106L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Segment name.

Parameter 3 FileID found on the disk segment header.

Parameter 4 FileID expected to be found on the disk segment header.

Probable Cause The FileID information stored on the disk segment's header is not
correct. The disk segment cannot be used.

Error 1009107 "Duplicate entry for block: %2, record %3. %1"

Constant EMSG_VDO_DUPENTRY

SAP Sybase Error Number 20128

SQL State QSB07

SQL Code -1009107L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 963

Errors and Warnings

Error 1009107 "Duplicate entry for block: %2, record %3. %1"

Parameter 2 Block with duplication entry.

Parameter 3 Duplicate entry.

Probable Cause No additional information available.

Error 1009108 "Database segment '%2' is not valid. Startblock found in the
header: %3 Startblock expected: %4. This segment cannot
be used. %1"

Constant EMSG_SDBEXT_BAD_STARTBLOCK

SAP Sybase Error Num- 20129

ber

SQL State QSB08

SQL Code -1009108L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the segment.

Parameter 3 Starting block found in the disk header.

Parameter 4 Starting block expected.

Probable Cause The start block of the disk segment that was found in the disk segment
header is not the same as what was expected. The disk segment cannot
be used.

Error 1009109 "Key size %2 is more than the maximum %3. %1"

Constant EMSG_VDO_KEYTOOBIG

SAP Sybase Error Number 20130

SQL State QSB09

SQL Code -1009109L

ODBC 2 State ERROR

ODBC 3 State ERROR

964 SAP Sybase IQ

Errors and Warnings

Error 1009109 "Key size %2 is more than the maximum %3. %1"

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Key size.

Parameter 3 Max key size.

Probable Cause No additional information available.

Error 1009110 "%1"

Constant EMSG_RFU_QSB10

SAP Sybase Error Number 20131

SQL State QSB10

SQL Code -1009110L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009111 "Could not find record %2 within block %3. %1"

Constant EMSG_VDO_RECNOTFOUND

SAP Sybase Error Number 20132

SQL State QSB11

SQL Code -1009111L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Record that could not be found.

Parameter 3 Block being searched.

SAP Sybase IQ Error Messages 965

Errors and Warnings

Error 1009111 "Could not find record %2 within block %3. %1"

Probable Cause No additional information available.

Error 1009112 "%1"

Constant EMSG_RFU_QSB12

SAP Sybase Error Number 20133

SQL State QSB12

SQL Code -1009112L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009113 "Secondary error noted. Semi-Join not ready %2. %1"

Constant EMSG_SECONDARY_ERR

SAP Sybase Error Number 20134

SQL State QSB13

SQL Code -1009113L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 more information about join node for which semi-join is not ready.

Probable Cause No additional information available.

Error 1009114 "Tried to put too many records %2 into block %3. %1"

Constant EMSG_VDO_TOOMANYRECS

SAP Sybase Error Number 20135

966 SAP Sybase IQ

Errors and Warnings

Error 1009114 "Tried to put too many records %2 into block %3. %1"

SQL State QSB14

SQL Code -1009114L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 Number of records.

Parameter 3 Block being inserted into.

Probable Cause No additional information available.

Error 1009115 "Database segment '%2' is not valid. %3 imaginary freelist

blocks were found, but %4 imaginary freelist blocks were
expected. This segment cannot be used. %1"

Constant EMSG_SDBEXT_DIF_NIBLOCKS

SAP Sybase Error 20136

Number

SQL State QSB15

SQL Code -1009115L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the segment.

Parameter 3 Number of imaginary freelist blocks recorded in the segment header.

Parameter 4 Number of freelist blocks that were expected to be recorded in the header.

Probable Cause When a database segment is opened, the segment header is read and the
number of freelist blocks read from the header is compared with the number
of freelist blocks that are expected to be read from the segment header. If the
numbers do not match, the segment cannot be used and the database must be
restored from backup.

SAP Sybase IQ Error Messages 967

Errors and Warnings

Error 1009116 "Wrong new() was called. %1"

Constant EMSG_VDO_WRONGNEW

SAP Sybase Error Number 20137

SQL State QSB16

SQL Code -1009116L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009117 "Update can not do different sized values yet. New size =
%2, old size = %3. %1"

Constant EMSG_VDO_UPDATESIZE

SAP Sybase Error Number 20138

SQL State QSB17

SQL Code -1009117L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 New size.

Parameter 3 Old size.

Probable Cause No additional information available.

Error 1009118 "Database segment '%2' is not valid. %3 freelist blocks were
found, but %4 freelist blocks were expected. This segment cannot
be used. %1"

Constant EMSG_SDBEXT_DIF_NFLBLOCKS

968 SAP Sybase IQ

Errors and Warnings

Error 1009118 "Database segment '%2' is not valid. %3 freelist blocks were
found, but %4 freelist blocks were expected. This segment cannot
be used. %1"

SAP Sybase Error 20139

Number

SQL State QSB18

SQL Code -1009118L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the segment.

Parameter 3 Number of freelist blocks recorded in the segment header.

Parameter 4 Number of freelist blocks that were expected to be recorded in the header.

Probable Cause When a database segment is opened, the segment header is read and the
number of freelist blocks read from the header is compared with the number of
freelist blocks that are expected to be read from the segment header. If the
numbers do not match, the segment cannot be used and the database must be
restored from backup.

Error 1009119 "Record size too large for database page size. %1"

Constant EMSG_SORT_INVALIDRECSIZE

SAP Sybase Error Number 20140

SQL State QSB19

SQL Code -1009119L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 969

Errors and Warnings

Warning 1009120 " %1 Sort: Sorted #%2, %3 Recs, %4 Secs"

Constant EMSG_SORT_INFOSORTED

SAP Sybase Error Number 20141

SQL State QSB20

SQL Code 1009120L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 What is being sorted.

Parameter 2 Which particular run of the sort.

Parameter 3 How many records were sorted.

Parameter 4 How long the sort took.

Probable Cause No additional information available.

Warning 1009121 " %1 Sort: Saved #%2, %3 Recs, %4 Secs"

Constant EMSG_SORT_INFOSAVED

SAP Sybase Error Number 20142

SQL State QSB21

SQL Code 1009121L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 What is being sorted.

Parameter 2 Which particular run of the sort.

Parameter 3 How many records were sorted.

Parameter 4 How long the sort took.

Probable Cause No additional information available.

970 SAP Sybase IQ

Errors and Warnings

Messages 1009122 through 1009142

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1009122 " %1 Sort: Merged %2 runs, %3 Secs, %4 runs remaining"

Constant EMSG_SORT_INFOMERGED

SAP Sybase Error Number 20143

SQL State QSB22

SQL Code 1009122L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 What is being sorted.

Parameter 2 How many merged.

Parameter 3 Time taken.

Parameter 4 How many runs still requiring to be merged.

Probable Cause No additional information available.

Error 1009123 "Database Segment %2 is not valid. Missing DBSignature.

This Segment can not be used. %1"

Constant EMSG_SDBEXT_BAD_DBSIGNATURE

SAP Sybase Error Number 20144

SQL State QSB23

SQL Code -1009123L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

SAP Sybase IQ Error Messages 971

Errors and Warnings

Error 1009123 "Database Segment %2 is not valid. Missing DBSignature.

This Segment can not be used. %1"

Probable Cause No additional information available.

Error 1009124 "Database Segment %2, blocksize %3 does not match

catalog blocksize of %4. This Segment can not be used.
%1"

Constant EMSG_SDBEXT_DIF_BLOCKSIZE

SAP Sybase Error Number 20145

SQL State QSB24

SQL Code -1009124L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Parameter 3 Block size.

Parameter 4 Catalog Block size.

Probable Cause No additional information available.

Error 1009125 "Database Segment %2, maxcompression %3 does not

match catalog maxcompression of %4. This Segment can
not be used. %1"

Constant EMSG_SDBEXT_DIF_MAXCOMPRESSION

SAP Sybase Error Number 20146

SQL State QSB25

SQL Code -1009125L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

972 SAP Sybase IQ

Errors and Warnings

Error 1009125 "Database Segment %2, maxcompression %3 does not

match catalog maxcompression of %4. This Segment can
not be used. %1"

Parameter 2 Database segment.

Parameter 3 Max compression

Parameter 4 Catalog max compression.

Probable Cause No additional information available.

Error 1009126 "Database Segment %2, createtime does not match

catalog. This Segment can not be used. %1"

Constant EMSG_SDBEXT_DIF_CREATETIME

SAP Sybase Error Number 20147

SQL State QSB26

SQL Code -1009126L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause No additional information available.

Error 1009127 "Database Segment %2, %3 size does not match catalog
size of %4. This Segment can not be used. %1"

Constant EMSG_SDBEXT_DIF_NBLOCKS

SAP Sybase Error Number 20148

SQL State QSB27

SQL Code -1009127L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 973

Errors and Warnings

Error 1009127 "Database Segment %2, %3 size does not match catalog
size of %4. This Segment can not be used. %1"

Parameter 1 location of the exception

Parameter 2 Database segment.

Parameter 3 Size of segment.

Parameter 4 Catalog size of segment.

Probable Cause No additional information available.

Error 1009128 "The IQ_SYSTEM_TEMP dbspace does not have dbfiles

for this server. %1"

Constant EMSG_SDBEXT_NOFREELIST

SAP Sybase Error Number 20149

SQL State QSB28

SQL Code -1009128L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1009129 "Database Segment %2, secondary server can not find a
valid header. This segment can not be used. %1"

Constant EMSG_SDBEXT_QSERVER_FAIL

SAP Sybase Error Number 20150

SQL State QSB29

SQL Code -1009129L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

974 SAP Sybase IQ

Errors and Warnings

Error 1009129 "Database Segment %2, secondary server can not find a
valid header. This segment can not be used. %1"

Parameter 2 Database segment.

Probable Cause No additional information available.

Error 1009130 "Database %2, does not have a segment for catalogfileid
%3. %1"

Constant EMSG_SDBEXT_MISSING_CATALOGFILEID

SAP Sybase Error Number 20151

SQL State QSB30

SQL Code -1009130L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Database segment.

Parameter 2 Max compression

Parameter 3 Catalog max compression.

Probable Cause No additional information available.

Warning 1009131 "You have run out of %1 dbspace in database %2. In

another session, please issue a CREATE DBSPACE ... %3
command and add a dbspace of at least %4 MB."

Constant EMSG_IQSTORE_OUTOFDISK_HEADER

SAP Sybase Error Number 20152

SQL State QSB31

SQL Code 1009131L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 string IQ STORE or IQ TEMPORARY STORE

SAP Sybase IQ Error Messages 975

Errors and Warnings

Warning 1009131 "You have run out of %1 dbspace in database %2. In

another session, please issue a CREATE DBSPACE ... %3
command and add a dbspace of at least %4 MB."

Parameter 2 database name

Parameter 3 string IQ STORE or IQ TEMPORARY STORE

Parameter 4 the minimum number of megabytes to add

Probable Cause You have run out of DBSPACE in the named database. In order to
continue, you must add another DBSPACE to the database unless
space becomes available from another connection.

Warning 1009132 "The DBA has added %1 %2 dbspaces to database %3.

Sybase IQ (TM) is no longer waiting for more dbspace."

Constant EMSG_IQSTORE_OUTOFDISK_TRAILER

SAP Sybase Error Number 20153

SQL State QSB32

SQL Code 1009132L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation for arg %2 delete if no %1

Parameter 2 explanation for arg %3 delete if no %2

Parameter 3 explanation for %3

Probable Cause No additional information available.

Error 1009133 "You have run out of space during the CHECKPOINT
operation. %1"

Constant EMSG_IQSTORE_OUTOFSPACE_CHECKPOINT

SAP Sybase Error Num- 20982

ber

SQL State QSB33

SQL Code -1009133L

976 SAP Sybase IQ

Errors and Warnings

Error 1009133 "You have run out of space during the CHECKPOINT
operation. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The checkpoint operation in progress needs to allocate blocks so that it
can construct and save required checkpoint information. When space is
exhausted during a checkpoint operation, it is not possible to add more
space via a CREATE DBSPACE command. Consequently, the check-
point operation will fail.

Error 1009134 "Insufficient buffers for '%2'. %1"

Constant EMSG_SORT_MINBUFSAVAIL

SAP Sybase Error Number 21023

SQL State QSB34

SQL Code -1009134L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 clientType

Probable Cause No additional information available.

Error 1009135 "Cannot perform requested command as there is a

CREATE DBSPACE command in progress. %1"

Constant EMSG_IQSTORE_INCREATEDBSPACE

SAP Sybase Error Number 21034

SQL State QSB36

SQL Code -1009135L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 977

Errors and Warnings

Error 1009135 "Cannot perform requested command as there is a

CREATE DBSPACE command in progress. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CREATE DBSPACE or a DROP DBSPACE command was issued

when there was already a DROP DBSPACE command in progress.

Error 1009136 "Cannot perform requested command as there is a DROP

DBSPACE command in progress. %1"

Constant EMSG_IQSTORE_INDROPDBSPACE

SAP Sybase Error Number 21035

SQL State QSB37

SQL Code -1009136L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CREATE DBSPACE or a DROP DBSPACE command was issued

when there was already an ALTER DBSPACE command in progress.

Error 1009137 "Cannot perform DDL command now on table %2 as a DDL

command is already in progress on that table. %1"

Constant EMSG_DDLINPROGRESS

SAP Sybase Error Number 21036

SQL State QDC55

SQL Code -1009137L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Parameter 1 description

978 SAP Sybase IQ

Errors and Warnings

Error 1009137 "Cannot perform DDL command now on table %2 as a DDL

command is already in progress on that table. %1"

Parameter 2 location of the exception

Probable Cause There is already a DDL command in progress at the moment on the
table specified and you must wait until it is finished before starting
another DDL command on that table.

Error 1009139 "Cannot perform requested command as there is a

CHECKPOINT command in progress. %1"

Constant EMSG_IQSTORE_INCHECKPOINT

SAP Sybase Error Number 21038

SQL State QSB38

SQL Code -1009139L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CREATE DBSPACE or a DROP DBSPACE command was issued

when there was already a CHECKPOINT command in progress.

Error 1009140 "Cannot restore dbspace '%2' to raw partition '%3' because
its size is smaller than the size of the original raw partition
(%4 vs. %5 blocks). %1"

Constant EMSG_RESTORE_RAW_PARTITION_SIZE_MISMATCH

SAP Sybase Error Num- 21039

ber

SQL State QCA49

SQL Code -1009140L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 979

Errors and Warnings

Error 1009140 "Cannot restore dbspace '%2' to raw partition '%3' because
its size is smaller than the size of the original raw partition
(%4 vs. %5 blocks). %1"

Parameter 2 name of the IQ dbspace being restored

Parameter 3 raw partition to which the IQ dbspace is being restored

Parameter 4 size of the new raw partition

Parameter 5 size of the old raw partition

Probable Cause This error means that the user is attempting to restore an IQ dbspace on a
raw partition that is not the same size as the original raw partition on
which the IQ dbspace existed at the time of the backup. The user must
resize the raw partition and then retry the restore operation.

Error 1009141 "Table '%2' cannot be found in the IQ store. %1"

Constant EMSG_SQL_IQTABLENOTFOUND

SAP Sybase Error Number 21061

SQL State QCA51

SQL Code -1009141L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 table name

Probable Cause The stored procedure sp_iqtablesize cannot find the table. This stored
procedure is for IQ tables only. It cannot be run against system tables
or ASA tables.

Warning 1009142 " %1 SortMerge0: %2 records, PhaseI=%3 Secs, %4 runs

total, %5 pgs=%6 M, runlen=%7, %8 est. phases"

Constant EMSG_SORT_INFOMERGED0

SAP Sybase Error Number 21067

SQL State QSB39

SQL Code 1009142L

980 SAP Sybase IQ

Errors and Warnings

Warning 1009142 " %1 SortMerge0: %2 records, PhaseI=%3 Secs, %4 runs

total, %5 pgs=%6 M, runlen=%7, %8 est. phases"

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 What is being sorted.

Parameter 2 How many records are being sorted.

Parameter 3 Time taken in Phase I.

Parameter 4 How many runs to be merged.

Parameter 5 How many pages of data to be sorted.

Parameter 6 How many Mbytes of data to be sorted.

Parameter 7 Average number of pages in a run.

Parameter 8 Estimated number of merge phases.

Probable Cause This information is provided after the Phase I radix sorting is com-
plete and the Phase II merge-sorting is about to begin. Each run
consists of a sequence of pages that have been radix sorted in Phase I.
These runs are merged together in Phase II to finish the sort.

Messages 1009143 through 1009162

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1009143 " %1 SortMergePass: Merged %2 runs, %3 Secs, %4 runs

remaining, %5 reads = %6 M, runlen=%7, phase %8, %9 M
on disk"

Constant EMSG_SORT_INFOMERGED1

SAP Sybase Error Num- 21068

ber

SQL State QSB40

SQL Code 1009143L

ODBC 2 State OK

ODBC 3 State OK

SAP Sybase IQ Error Messages 981

Errors and Warnings

Warning 1009143 " %1 SortMergePass: Merged %2 runs, %3 Secs, %4 runs

remaining, %5 reads = %6 M, runlen=%7, phase %8, %9 M
on disk"

Severity Code 1 on page 2

Parameter 1 What is being sorted.

Parameter 2 How many runs were merged in this merge pass..

Parameter 3 Time taken in this merge pass.

Parameter 4 How many runs still to be merged.

Parameter 5 How many page reads done in this pass.

Parameter 6 How many Mbytes of data read in this pass.

Parameter 7 Average length of runs in pages, this pass.

Parameter 8 Fractional phase number reached.

Parameter 9 How many Mbytes of data physically read in this pass.

Probable Cause This information is provided after each merge pass. One merge pass
merges a certain number of runs, using one pinned buffer page per run
plus one pinned buffer for the output run. Note that there can be several
passes in a merge phase. One merge phase reads all the sort data and
produces a new set of runs that provide input to the next phase.

Warning 1009144 " %1 SortMergeDone: Ave mem %2 M, %3 Secs, %4

passes, %5 reads, %6 M data= %7 pgs, %8 phases, %9 M
on disk"

Constant EMSG_SORT_INFOMERGED2

SAP Sybase Error Number 21069

SQL State QSB41

SQL Code 1009144L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 What is being sorted.

982 SAP Sybase IQ

Errors and Warnings

Warning 1009144 " %1 SortMergeDone: Ave mem %2 M, %3 Secs, %4

passes, %5 reads, %6 M data= %7 pgs, %8 phases, %9 M
on disk"

Parameter 2 Time-average number of pinned page buffers used by Phase II of the

sort.

Parameter 3 Time taken for Phase II of the sort.

Parameter 4 Total number of passes in Phase II.

Parameter 5 Total number of page reads in Phase II.

Parameter 6 Total Mbytes of data sorted.

Parameter 7 Total number of pages of data sorted.

Parameter 8 Number of merge phases in the merge sort of Phase II.

Parameter 9 Total Mbytes of physical reads in Phase II.

Probable Cause This information is provided at the end of Phase II to summarize the
resource usage of the whole merge sort. The last pass of the sort is
separately reported on by an EMSG_SORT_INFOMERGED1 mes-
sage.

Error 1009145 "Data exception - data type conversion is not possible. %2,
%1"

Constant EMSG_TYPECONVERSION_W_ARG

SAP Sybase Error Number 21070

SQL State QFA2E

SQL Code -1009145L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Exception line number

Parameter 2 SA parse source code line

Probable Cause No additional information available.

SAP Sybase IQ Error Messages 983

Errors and Warnings

Error 1009146 "Cannot perform requested command as there is a DBCC

command in progress. %1"

Constant EMSG_IQSTORE_INDBCC

SAP Sybase Error Number 21071

SQL State QSB42

SQL Code -1009146L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CHECKPOINT command was issued when there was already a
DBCC command in progress.

Warning 1009147 "Space has become available in the %1 store of database

%2. Sybase IQ (TM) is no longer waiting for more
dbspace."

Constant EMSG_IQSTORE_OUTOFDISK_SPACEAVAILABLE

SAP Sybase Error Number 20188

SQL State QSB43

SQL Code 1009147L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 string IQ STORE or IQ TEMPORARY STORE

Parameter 2 Database Name

Probable Cause No additional information available.

Error 1009148 "Cannot use -iqfrec to start a multiplex secondary server.

%1"

Constant EMSG_IQSTORE_NOFREC

SAP Sybase Error Number 21049

984 SAP Sybase IQ

Errors and Warnings

Error 1009148 "Cannot use -iqfrec to start a multiplex secondary server.

%1"

SQL State QSB44

SQL Code -1009148L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A sp_iqcheckdb procedure call was issued on an IQ multiplex sec-

ondary server, or it was started in drop-leaks or forced recovery mode.
These operations are only allowed on the coordinator

Error 1009149 "%2 Internal Inconsistency: %1 (%3,%4,%5)"

Constant EMSG_INDEXCONTAINER_CORRUPT

SAP Sybase Error Number 20189

SQL State QSB45

SQL Code -1009149L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Container type

Parameter 3 Internal Error Code

Parameter 4 Internal Error Info 1

Parameter 5 Internal Error Info 2

Probable Cause A corrupt index container was found. DBCC cannot repair the con-
tainer. The database object using the container must be re-created.

Error 1009150 "Cannot delete/truncate CK %2 because of RI violation - FK

has non-nulls. %1"

Parameter 4 row id that violated RI

Probable Cause No additional information available. Cannot insert/update FK if there

does not exist same value in associated CK any associated foreign key
which has any all non-null data.

Error 1009153 "Cannot remove row %3 from CK %2 during LOAD cleanup

because of RI violation. %1"

Constant EMSG_RI_VIOLATION_LOADCLEANUP

SAP Sybase Error Number 20193

SQL State QSB49

SQL Code -1009153L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 index name for CK

Parameter 3 row id that violated RI

SAP Sybase IQ Error Messages 987

Errors and Warnings

Error 1009153 "Cannot remove row %3 from CK %2 during LOAD cleanup

because of RI violation. %1"

Probable Cause No additional information available. If removing self-referential CK

during LOAD cleanup phase and there exists a FK of removed value,
we roll back the whole operation.

Error 1009154 "Cannot alter dbspace when a backup is in progress"

Constant EMSG_IQSTORE_CANNOT_ALTERDBSPACE

SAP Sybase Error Number 21118

SQL State QSB50

SQL Code -1009154L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause An alter dbspace operation was attempted while a backup was run-
ning. The alter dbspace operation cannot proceed since it may modify
internal database structures that are being backed up.

Error 1009155 "Cannot perform requested command as there is an

ALTER DBSPACE command in progress. %1"

Constant EMSG_IQSTORE_INALTERDBSPACE

SAP Sybase Error Number 22000

SQL State QSB55

SQL Code -1009155L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CREATE DBSPACE or a DROP DBSPACE command was issued

when there was already an ALTER DBSPACE command in progress.

988 SAP Sybase IQ

Errors and Warnings

Error 1009156 "Drop disallowed for dbspace %2. One or more of the file(s)
are in use by the database. %1"

Constant EMSG_SDBEXT_DROPSEGMENTINUSE

SAP Sybase Error Number 20194

SQL State QSB51

SQL Code -1009156L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause A segment must contain no user data and no database structures to
drop

Error 1009157 "There is insufficient reserve space to add %3 blocks to

segment %2. Only %4 blocks or less may be added. %1"

Constant EMSG_SDBEXT_SEGMENTNORESERVE

SAP Sybase Error Number 20195

SQL State QSB52

SQL Code -1009157L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Parameter 3 Number of blocks user attempted to add

Parameter 4 Maximum blocks that may be added

Probable Cause Since a segment must use a contiguous range of block numbers, it can
only be resized larger when the blocks following it are not in use by
the next segment.

SAP Sybase IQ Error Messages 989

Errors and Warnings

Error 1009158 "Cannot resize segment %2 since the truncated region is

in use. %1"

Constant EMSG_SDBEXT_RESIZESEGMENTINUSE

SAP Sybase Error Number 20196

SQL State QSB53

SQL Code -1009158L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause A segment can only be resized smaller when no blocks in the trun-
cated are in use.

Error 1009159 "The status specified for segment %2 is unchanged. %1"

Constant EMSG_SDBEXT_SEGMENTSAMERWMODE

SAP Sybase Error Number 20197

SQL State QSB54

SQL Code -1009159L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause The "alter dbspace status" syntax requires the new status to be dif-
ferent than the original status.

Error 1009160 "There must be at least one readwrite dbspace (%2). %1"

Constant EMSG_SDBEXT_MUST_HAVE_RW

SAP Sybase Error Number 20198

990 SAP Sybase IQ

Errors and Warnings

Error 1009160 "There must be at least one readwrite dbspace (%2). %1"

SQL State QSB56

SQL Code -1009160L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause There must at least one readwrite segment

Error 1009161 "Cannot resize segment %2 since it is readonly. %1"

Constant EMSG_SDBEXT_RO_RESIZE

SAP Sybase Error Number 20199

SQL State QSB57

SQL Code -1009161L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause A readonly segment cannot be resized

Error 1009162 "Insufficient space to relocate structures on %2. %1"

Constant EMSG_SDBEXT_NO_RELOCATE_SPACE

SAP Sybase Error Number 20200

SQL State QSB58

SQL Code -1009162L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 991

Errors and Warnings

Error 1009162 "Insufficient space to relocate structures on %2. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Probable Cause Database structures may need to be relocated in order to drop a seg-
ment or make it readonly. This space must be available on other
segments.

1009163 - 1013038

Messages 1009163 through 1009182

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009163 "Segment %2 cannot be smaller than %3 blocks. %1"

Constant EMSG_SDBEXT_SEGMENTTOOSMALL

SAP Sybase Error Number 20201

SQL State QSB59

SQL Code -1009163L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Database segment.

Parameter 3 Minimum size in blocks

Probable Cause Database structures may need to be relocated in order to drop a seg-
ment or make it readonly. This space must be available on other
segments.

Error 1009164 "You cannot drop the last dbspace. %1"

Constant EMSG_DATABASE_LASTDBSPACE

992 SAP Sybase IQ

Errors and Warnings

Error 1009164 "You cannot drop the last dbspace. %1"

SAP Sybase Error Number 20202

SQL State QSB60

SQL Code -1009164L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You can drop the last dbspace only if it is a temp dbspace

Error 1009165 "Cannot perform requested command as the SYSIQFILE

table is locked by another transaction. %1"

Constant EMSG_IQSTORE_INREADSYSFILE

SAP Sybase Error Number 20203

SQL State QSB61

SQL Code -1009165L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A CREATE DBSPACE, ALTER DPSACE or DROP DBSPACE

command was issued when there was another command or stored
procedure accessing the system table SYSIQFILE.

Error 1009166 "%3 %4 is in use by dropped dbspace %2 on a secondary server.

The drop dbspace command has not yet propagated through the
multiplex. %1"

Constant EMSG_SDBEXT_IN_USE_BY_QUERY_SERVER

SAP Sybase Error 20204

Number

SQL State QSB62

SAP Sybase IQ Error Messages 993

Errors and Warnings

Error 1009166 "%3 %4 is in use by dropped dbspace %2 on a secondary server.

The drop dbspace command has not yet propagated through the
multiplex. %1"

SQL Code -1009166L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 DBSpace name

Parameter 3 Description of field in use (i.e. File, Name, File ID)

Parameter 4 Value of field in use

Probable Cause Fields for dropped dbspaces cannot be re-used until the drop dbspace com-
mands have propagated through the multiplex

Error 1009167 "dbspace %2 failed to open since it's definition conflicts with
dbspace %3. Secondary server may need to be synchronized.
%1"

Constant EMSG_SDBEXT_DBSPACE_BLOCK_RANGE

SAP Sybase Error 20207

Number

SQL State QSB63

SQL Code -1009167L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Name of DBSpace that was already open

Parameter 3 Name of DBSpace that failed to open

Probable Cause The server has an invalid dbspace configuration. New dbspaces may fail to
open or the server may fail to start until this is corrected.

994 SAP Sybase IQ

Errors and Warnings

Error 1009168 "The WORD SKIP limit (%2) has been exceeded. %1"

Constant EMSG_SVIOLATION_WORDSKIP_LIMIT_EXCEEDED

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause No additional information available..

Error 1009172 "%2 is in use by another sp_iqemptyfile or ALTER DBSPACE

command. %1"

Constant EMSG_DBSPACE_FILE_IN_USE_BY_ALTER_OR_EMPTY

SAP Sybase Error 20226

Number

SQL State QSB68

SQL Code -1009172L

996 SAP Sybase IQ

Errors and Warnings

Error 1009172 "%2 is in use by another sp_iqemptyfile or ALTER DBSPACE

command. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Name of the FILE or DBSPACE locked.

Probable Cause sp_iqemptyfile or ALTER DBSPACE commands disallow status change

for the FILE(s) or DBSPACE. No other ALTER DBSPACE or sp_iqemp-
tyfile command can run on those FILE(s) or DBSPACE.

Error 1009173 "Operation not permitted on an OFFLINE DBSpace %2.

%1"

Constant EMSG_OFFLINE_DBSPACE_ILLEGAL_ACCESS

SAP Sybase Error Number 20227

SQL State QSB69

SQL Code -1009173L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause No additional information available..

Error 1009174 "Operation not yet supported. Sort metadata sources have
incompatible record descriptors. %1"

Constant EMSG_SORT_METADATADESC_MISMATCH

SAP Sybase Error Number 20228

SQL State QSB70

SQL Code -1009174L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 997

Errors and Warnings

Error 1009174 "Operation not yet supported. Sort metadata sources have
incompatible record descriptors. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available..

Error 1009175 "Database segment '%2' is not valid. Reserve Blocks found
in the header: %3 Reserve Blocks expected: %4. This
segment cannot be used. %1"

Constant EMSG_SDBEXT_BAD_RESERVE

SAP Sybase Error Num- 20229

ber

SQL State QSB71

SQL Code -1009175L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the segment.

Parameter 3 Reserve blocks found in the disk header.

Parameter 4 Reserve blocks expected.

Probable Cause The start block of the disk segment that was found in the disk segment
header is not the same as what was expected. The disk segment cannot
be used. You will need to restore your database from backup.

Error 1009176 "Create temporary dbspace not allowed. %1"

Constant EMSG_DBSPACE_TEMP_NOT_ALLOWED

SAP Sybase Error Num- 20230

ber

SQL State QSB72

998 SAP Sybase IQ

Errors and Warnings

Error 1009176 "Create temporary dbspace not allowed. %1"

SQL Code -1009176L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Additional dbspaces may not be created in temp store. Temp space
may only be added to IQ_SYSTEM_TEMP.

Error 1009177 "%2 is already %3. %1"

Constant EMSG_DBSPACE_ATTRIB_UNCHANGED

SAP Sybase Error Number 20231

SQL State QSB73

SQL Code -1009177L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Parameter 3 READONLY, READWRITE, ONLINE, OFFLINE

Probable Cause The dbspace being altered already had the requested attributes

Error 1009178 "Operation not allowed on dbspaces that contain multiple

files. %1"

Constant EMSG_DBSPACE_NOT_FOR_MULTI_DBSPACE

SAP Sybase Error Num- 20232

ber

SQL State QSB74

SQL Code -1009178L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 999

Errors and Warnings

Error 1009178 "Operation not allowed on dbspaces that contain multiple

files. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The specified operation cannot be applied to a file the contains mul-
tiple files

Error 1009179 "The last file in a dbspace may only be removed by DROP
DBSPACE. %1"

Constant EMSG_DBSPACE_CANT_DROP_LAST_FILE

SAP Sybase Error 20233

Number

SQL State QSB75

SQL Code -1009179L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A dbspace must contain at least one file. The last file can only be removed by
dropping the dbspace that contains it.

Error 1009180 "%2 is not allowed on system dbspace %3. %1"

Constant EMSG_DBSPACE_NOT_ALLOWED_SYSTEM

SAP Sybase Error Number 20234

SQL State QSB76

SQL Code -1009180L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

1000 SAP Sybase IQ

Errors and Warnings

Error 1009180 "%2 is not allowed on system dbspace %3. %1"

Parameter 2 disallowed command

Parameter 3 dbspace name

Probable Cause The requested DDL operation is not allowed on system dbspaces

Error 1009181 "Multiple FILE clauses are not allowed for this command.
%1"

Constant EMSG_DBSPACE_SINGLE_FILE_CLAUSE

SAP Sybase Error Number 20235

SQL State QSB77

SQL Code -1009181L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Some alter dbspace commands do not allow multiple files to be
specified

Error 1009182 "DBFile name %2 is already in use. %1"

Constant EMSG_DBSPACE_DBFILE_NAME_IN_USE

SAP Sybase Error Number 20236

SQL State QSB78

SQL Code -1009182L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 logical filename

Probable Cause logical filenames must be unique for dbfiles

SAP Sybase IQ Error Messages 1001

Errors and Warnings

Messages 1009183 through 1009417

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009183 "A readwrite dbspace may not be placed offline. %1"

Constant EMSG_DBSPACE_NO_OFFLINE_RW_DBSPACE

SAP Sybase Error Number 20237

SQL State QSB79

SQL Code -1009183L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A dbspace must be readonly before it can be placed offline

Error 1009184 "Operation not permitted on a READONLY DBSpace. %1"

Constant EMSG_READONLY_DBSPACE_ILLEGAL_ACCESS

SAP Sybase Error Number 21190

SQL State QSB80

SQL Code -1009184L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available..

Error 1009185 "An IO error was encountered while writing a database

page in %2 DBSpace. %1. File is readonly."

Constant EMSG_READONLY_FILE_ILLEGAL_ACCESS

SAP Sybase Error Number 21191

1002 SAP Sybase IQ

Errors and Warnings

Error 1009185 "An IO error was encountered while writing a database

page in %2 DBSpace. %1. File is readonly."

SQL State QSB81

SQL Code -1009185L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause No additional information available..

Error 1009186 "Global Request for freelist failed. %1"

Constant EMSG_GLOBAL_FL_REQUEST_FAILED

SAP Sybase Error Number 21200

SQL State QSB82

SQL Code -1009186L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Global reqest for freelist failed.

Error 1009187 "Textindex External Error: Error Code: %2: Error Message:
%3. %1"

Constant EMSG_EXTLIB_ERROR

SAP Sybase Error Number 21205

SQL State QSB83

SQL Code -1009187L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1003

Errors and Warnings

Error 1009187 "Textindex External Error: Error Code: %2: Error Message:
%3. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Error code set by the external library

Parameter 2 Error message from the external library

Parameter 3 location of the exception

Probable Cause Error from external prefilter or term breaker library.

Error 1009188 "Create shared temporary dbspace not allowed. %1"

Constant EMSG_DBSPACE_SHARED_TEMP_NOT_ALLOWED

SAP Sybase Error 22019

Number

SQL State QDD1A

SQL Code -1009188L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Additional dbspaces may not be created in shared temp store. Shared Temp
space may only be added to IQ_SHARED_TEMP.

Error 1009189 "Text document exceeds maximum number of terms.

Support up to 4294967295 terms per document. %1"

Constant EMSG_MAXTERM_ERROR

SAP Sybase Error Number 21210

SQL State QSB84

SQL Code -1009189L

ODBC 2 State ERROR

ODBC 3 State ERROR

1004 SAP Sybase IQ

Errors and Warnings

Error 1009189 "Text document exceeds maximum number of terms.

Support up to 4294967295 terms per document. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Error from external prefilter or term breaker library.

Error 1009190 "Incorrect %3 Index Version (%2): Index must be dropped

and recreated. %1"

Constant EMSG_TEXTVERSION_ERROR

SAP Sybase Error Number 21211

SQL State QSB85

SQL Code -1009190L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Incorrect version of index.

Parameter 3 index type.

Probable Cause Error from text index.

Error 1009191 "The FORCE READWRITE clause is not allowed on this

dbspace. It can be specified for the dbspace
IQ_SHARED_TEMP only. %1"

Constant EMSG_DBSPACE_FORCE_READWRITE_NOT_ALLOWED

SAP Sybase Error Number 22025

SQL State QSB86

SQL Code -1009191L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 1005

Errors and Warnings

Error 1009191 "The FORCE READWRITE clause is not allowed on this

dbspace. It can be specified for the dbspace
IQ_SHARED_TEMP only. %1"

Parameter 1 location of the exception

Probable Cause The FORCE READWRITE clause can be used with

IQ_SHARED_TEMP only.

Error 1009192 "File may not be accessible from one or more multiplex servers.
Use sp_iqmpxfilestatus for further diagnosis. %1"

Constant EMSG_DBSPACE_GLOBAL_FILE_STATUS_INVALID

SAP Sybase Error 22026

Number

SQL State QSB87

SQL Code -1009192L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The file must be accessible from all multiplex servers (except those that are
excluded) before its mode can be changed to READWRITE. The global file
status maintained at the coordinator indicates that file may not be accessible
from one or more multiplex servers. Use sp_iqmpxfilestatus for further
diagnosis.

Error 1009193 "Insufficient space to accommodate Freelist blocks. Please

use a file with at least %2 MB space and turn that file
READWRITE. %1"

Constant EMSG_DBSPACE_INSUFFICIENT_SPACE_FOR_RW

SAP Sybase Error Num- 22027

ber

SQL State QSB88

SQL Code -1009193L

ODBC 2 State ERROR

1006 SAP Sybase IQ

Errors and Warnings

Error 1009193 "Insufficient space to accommodate Freelist blocks. Please

use a file with at least %2 MB space and turn that file
READWRITE. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Size of the file needed

Probable Cause There is no READWRITE file in IQ_SHARED_TEMP dbspace at this

point in time. While trying to turn the first file READWRITE, the file
needs to have enough space to accommodate freelist blocks for all the
existing files.

Error 1009194 "Please drop the rest of the files in this dbspace before trying to
drop this file. \nThis was the first file to be made READWRITE and
can only be dropped if it is the last remaining file. %1"

Constant EMSG_DBSPACE_LAST_FILE_DROPPED

SAP Sybase Error 22028

Number

SQL State QSB89

SQL Code -1009194L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause This was the first file to be made READWRITE in IQ_SHARED_TEMP
dbspace This file should be the last file in IQ_SHARED_TEMP to be drop-
ped. Please drop rest of the files before trying to drop this file.

Error 1009195 "Cannot open file %2, alter file ReadWrite operation failed.
%1"

Constant EMSG_SDBEXT_SHTEMP_RW_NOT_ALLOWED

SAP Sybase Error Num- 22030

ber

SAP Sybase IQ Error Messages 1007

Errors and Warnings

Error 1009195 "Cannot open file %2, alter file ReadWrite operation failed.
%1"

SQL State QSB90

SQL Code -1009195L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 logical filename

Probable Cause Secondary node cannot make a file in IQ_SHARED_TEMP dbspace

READWRITE if it is not accessible.

Error 1009196 "%2: Cannot convert blockmap; bmp={%3}. %1"

Constant EMSG_BLOCKMAP_CONVERSION_FAILED

SAP Sybase Error Number 22033

SQL State QSB91

SQL Code -1009196L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 1) location of the exception

Parameter 2 2) The particular buffer cache throwing the exception.

Parameter 3 3) Information about the blockmap

Probable Cause Blockmap conversion failed. Blockmap remains unconverted and in

read only mode.

Error 1009412 "The INSERT ... LOCATION statement must use a SELECT
statement. %1"

Constant EMSG_SQL_INS_LOC_SEL

SAP Sybase Error Number 21050

1008 SAP Sybase IQ

Errors and Warnings

Error 1009412 "The INSERT ... LOCATION statement must use a SELECT
statement. %1"

SQL State QCB10

SQL Code -1009412L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The INSERT ... LOCATION statement must use a SELECT state-
ment. No other SQL statement is supported here.

Error 1009413 "Secondary server cannot maintain catalog sync. %1"

Constant EMSG_CAT_MPX_REPLAY_FAIL

SAP Sybase Error Number 21051

SQL State QCB11

SQL Code -1009413L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause An error has occurred while applying catalog updates from the co-
ordinator. The secondary server must be restarted or synchronized.

Error 1009414 "Secondary server cannot recover catalog during post-

synchronization. %1"

Constant EMSG_CAT_MPX_POSTSYNC_FAIL

SAP Sybase Error Number 21052

SQL State QCB12

SQL Code -1009414L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1009

Errors and Warnings

Error 1009414 "Secondary server cannot recover catalog during post-

synchronization. %1"

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause An error has occurred while reconstituting catalog entries for the IQ
Local store. Manual repair is required.

Error 1009415 "CREATE TABLE cannot use IN clause for IQ Local store.
%1"

Constant EMSG_CAT_MPX_NO_LOCAL_INCLAUSE

SAP Sybase Error Num- 21053

ber

SQL State QCB13

SQL Code -1009415L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You may not specify the IN clause to create tables in IQ Local store.
Without an IN clause, the secondary server create tables in Local store
by default.

Error 1009416 "Option '%2' not allowed on a partitioned table. %1"

Constant EMSG_UNSUPPORTED_PARTITIONED_TABLE_LOAD_OP-
TION

SAP Sybase Error Number 21054

SQL State QCB14

SQL Code -1009416L

ODBC 2 State ERROR

ODBC 3 State ERROR

1010 SAP Sybase IQ

Errors and Warnings

Error 1009416 "Option '%2' not allowed on a partitioned table. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 option name

Probable Cause Certain 'load table' options are not supported on a partitioned table.

Error 1009417 "Updating partition key column on a partitioned table is

not allowed. %1"

Constant EMSG_CANNOT_UPDATE_PARTITION_COLUMN

SAP Sybase Error Number 21055

SQL State QCB15

SQL Code -1009417L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A partition key column cannot be updated.

Messages 1009418 through 1010015

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1009418 "Operation not allowed - partition key column %2 not

specified. %1"

Constant EMSG_PARTITIONING_COLUMN_OMITTED

SAP Sybase Error Number 21056

SQL State QCB16

SQL Code -1009418L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 1011

Errors and Warnings

Error 1009418 "Operation not allowed - partition key column %2 not

specified. %1"

Parameter 1 location of the exception

Parameter 2 column name

Probable Cause A partial width insert on a partitioned table is not permitted when at
least one of the table's partition key columns is omitted.

Error 1009419 "The width of one or more columns are too large to fit into
database's page."

Constant EMSG_PAGESIZE_TOO_SMALL_FOR_QCP

SAP Sybase Error Number 21159

SQL State QCB19

SQL Code -1009419L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The LOAD Engine cannot fit a column into the page.

Error 1009420 "Value of row's partition-key columns do not fit into any of
the table's partitions."

Constant EMSG_VALUE_DOES_NOT_FIT

SAP Sybase Error Number 21160

SQL State QCB20

SQL Code -1009420L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The value for the partition key columns for a specific row do not fit
within any of the table's partitions.

1012 SAP Sybase IQ

Errors and Warnings

Error 1010000 "The file '%2' already exists. %1"

Constant EMSG_DATABASE_FILEALREADYEXISTS

SAP Sybase Error Number 20014

SQL State QXA00

SQL Code -1010000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause The named dbspace already exists (and it is a raw partition). To pro-
ceed, you must first remove it by hand.

Error 1010001 "Cannot use raw partition for dbspace file '%2'. %1"

Constant EMSG_DATABASE_FILEISRAW

SAP Sybase Error Number 20015

SQL State QXA01

SQL Code -1010001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Probable Cause The named dbspace cannot exist on a raw partition.

Error 1010002 "File format mismatch; database %2; Sybase IQ: %3. %1"

Constant EMSG_DATABASE_FILEFORMAT

SAP Sybase Error Number 20016

SQL State QXA02

SAP Sybase IQ Error Messages 1013

Errors and Warnings

Error 1010002 "File format mismatch; database %2; Sybase IQ: %3. %1"

SQL Code -1010002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file format of database as found in SYSIQINFO

Parameter 3 file format as known by IQ DLL

Probable Cause The file format of the database doesn't match the file format as ex-
pected by the IQ DLL. The IQ DLL and the database each have a
format version. They must match.

Error 1010003 "Catalog format mismatch: database %2; Sybase IQ: %3.
%1"

Constant EMSG_DATABASE_CATALOGFORMAT

SAP Sybase Error Number 20017

SQL State QXA03

SQL Code -1010003L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 catalog format of database as found in SYSIQINFO

Parameter 3 catalog format as known by IQ DLL

Probable Cause The catalog format of the database doesn't match the catalog format as
expected by the IQ DLL. The IQ DLL and the ASA catalog each have
a format version. They must match.

Error 1010004 "Stored procedure format mismatch: database %2; Sybase

IQ: %3. %1"

Constant EMSG_DATABASE_SPFORMAT

1014 SAP Sybase IQ

Errors and Warnings

Error 1010004 "Stored procedure format mismatch: database %2; Sybase

IQ: %3. %1"

SAP Sybase Error Number 20018

SQL State QXA04

SQL Code -1010004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 stored procedure of database as found in SYSIQINFO

Parameter 3 stored procedure format as known by IQ DLL

Probable Cause The stored procedure format of the database doesn't match the stored
procedure format as expected by the IQ DLL. The IQ DLL and the
database each contain a stored procedure format version. They must
match.

Error 1010005 "File format date mismatch: database %2; Sybase IQ: %3.
%1"

Constant EMSG_DATABASE_TIMESTAMP

SAP Sybase Error Number 20019

SQL State QXA05

SQL Code -1010005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file format date of database as found in SYSIQINFO

Parameter 3 file format as known by IQ DLL

Probable Cause The file format date of the database doesn't match the file format date
as expected by the IQ DLL.

SAP Sybase IQ Error Messages 1015

Errors and Warnings

Error 1010006 "Maximum blocks for dbspace '%2' is %3 blocks. %4

blocks were specified. (Database blocksize is %5.) %1"

Constant EMSG_DATABASE_BLOCKRANGE

SAP Sybase Error Number 20020

SQL State QXA06

SQL Code -1010006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace name

Parameter 3 maximum number of blocks for a dbspace given the database's

blocksize

Parameter 4 maximum blocks the user specified

Parameter 5 The blocksize of the database.

Probable Cause Given a database's BLOCK SIZE and the number of blocks specified
by the user for the dbspace, the dbspace size (in bytes) would exceed
the OS's limit of bytes per file.

Error 1010007 "The number of blocks (%3) for dbspace '%2' must be less
than or equal to the number of blocks in the raw partition
(%4). %1"

Constant EMSG_DATABASE_INVALIDNBLOCKS

SAP Sybase Error Number 20980

SQL State QXA07

SQL Code -1010007L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

1016 SAP Sybase IQ

Errors and Warnings

Error 1010007 "The number of blocks (%3) for dbspace '%2' must be less
than or equal to the number of blocks in the raw partition
(%4). %1"

Parameter 2 dbspace name

Parameter 3 user's number of blocks in dbspace

Parameter 4 number of blocks in raw partition

Probable Cause When creating a dbspace on a raw partition, if the user specifies the
dbspace's size, then it must exactly match the size of the raw partition.

Error 1010008 "For an IQ PAGE SIZE of %2, the dbspace '%3' must have at
least %4 MB. %1"

Constant EMSG_DATABASE_DBNBLOCKS

SAP Sybase Error Number 20981

SQL State QXA08

SQL Code -1010008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 page size

Parameter 3 dbspace name

Parameter 4 required minimum size in mega-bytes

Probable Cause The named dbspace must have the stated minimum size in megabytes.

Error 1010009 "Improper use of cursor - programmer error %1"

Constant EMSG_CURSOR_PROG_ERROR

SAP Sybase Error Number 21005

SQL State QXA09

SQL Code -1010009L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1017

Errors and Warnings

Error 1010009 "Improper use of cursor - programmer error %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The programmer has misused the internal cursor class(es)

Error 1010010 "An invalid attribute flag was passed to the cursor"

Constant EMSG_CURSOR_INVALID_ATTRIBUTE

SAP Sybase Error Number 21006

SQL State QXA10

SQL Code -1010010L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause A state violation was detected in the cursor

Error 1010011 "Not enough server threads available for this query."

Constant EMSG_CURSOR_NO_THREADS

SAP Sybase Error Number 21007

SQL State QXA11

SQL Code -1010011L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No thread could be allocated to allow this query to be executed

Error 1010012 "The cursor is in an invalid state %1"

Constant EMSG_CURSOR_INVALID_STATE

SAP Sybase Error Number 21008

1018 SAP Sybase IQ

Errors and Warnings

Error 1010012 "The cursor is in an invalid state %1"

SQL State QXA12

SQL Code -1010012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A state violation was detected in the cursor

Warning 1010013 "IQ cannot support the %1 connections requested by the

server.\nRestart the server with -gm %2 on the command
line."

Constant EMSG_CONN_INFO

SAP Sybase Error Number 21024

SQL State 00A13

SQL Code 1010013L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 the number of connections

Parameter 2 the number of supported connections

Probable Cause Inform the DBA about the number of connection

Error 1010013 "Raw partition %2 is already in use. %1"

Constant EMSG_RAW_PARTITION_INUSE

SAP Sybase Error Number 21025

SQL State QXA13

SQL Code -1010013L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1019

Errors and Warnings

Error 1010013 "Raw partition %2 is already in use. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 name of the raw partition

Probable Cause User attempted to create dbspace on a raw partition which is currently
in use by the database.

Warning 1010014 "Default cache size is used for command %1."

Constant EMSG_DEFAULTCACHESIZEUSED

SAP Sybase Error Number 21058

SQL State QXA14

SQL Code 1010014L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 command type

Probable Cause warning is issued for the command that uses the default cache size

Error 1010015 "The MAIN store is out of space. Space must be added to
the MAIN store first. %1"

Constant EMSG_DATABASE_MSNOSPACE

SAP Sybase Error Number 21075

SQL State QXA15

SQL Code -1010015L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

1020 SAP Sybase IQ

Errors and Warnings

Error 1010015 "The MAIN store is out of space. Space must be added to
the MAIN store first. %1"

Probable Cause The MAIN store is out of space. Space must be added to the MAIN
store before space can be added to any other store.

Messages 1010016 through 1010037

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1010016 "The TEMPORARY store is out of space. Space must be

added to the TEMPORARY store first. %1"

Constant EMSG_DATABASE_TSNOSPACE

SAP Sybase Error Number 21076

SQL State QXA16

SQL Code -1010016L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The TEMPORARY store is out of space. Space must be added to the
TEMPORARY store before space can be added to any other store.

Error 1010017 "You cannot create tables on a secondary server without a

readwrite local IQ Store. %1"

Constant EMSG_DATABASE_MPX_NOLOCAL

SAP Sybase Error Number 21111

SQL State QXA17

SQL Code -1010017L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

SAP Sybase IQ Error Messages 1021

Errors and Warnings

Error 1010017 "You cannot create tables on a secondary server without a

readwrite local IQ Store. %1"

Probable Cause MPX secondary servers can only create IQ objects in a local store.

Error 1010019 "Cannot modify object %2 on dbspace %3. %1"

Constant EMSG_DATABASE_MPX_NOROMAIN

SAP Sybase Error Number 21113

SQL State QXA19

SQL Code -1010019L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 object name

Parameter 3 dbspace name

Probable Cause A generic error indicating error in modifying an object.

Error 1010020 "Backup not allowed on secondary servers. %1"

Constant EMSG_DATABASE_MPX_NOLOCALFORBU

SAP Sybase Error Number 21114

SQL State QXA20

SQL Code -1010020L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The backup command is not allowed to be executed on a secondary

server. Execute the command on the coordinator.

1022 SAP Sybase IQ

Errors and Warnings

Error 1010021 "Foreign key constraint on a local table cannot reference a

shared table. %1"

Constant EMSG_DATABASE_MPX_NOXKEYS

SAP Sybase Error Number 21115

SQL State QXA21

SQL Code -1010021L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Cannot combine main and local tables in a foreign key relationship.

Error 1010022 "Cannot modify main store from a multiplex query server.
%1"

Constant EMSG_DATABASE_MPX_NOMAINRWACCESS

SAP Sybase Error Number 21117

SQL State QXA22

SQL Code -1010022L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The general error when a query server tries to modify the shared main
store. There are other more detailed messages for specific cases.

Error 1010023 "Cursor is not updatable: %2. %1"

Constant EMSG_CURSOR_NOT_UPDATABLE

SAP Sybase Error Number 21121

SQL State QXA23

SQL Code -1010023L

SAP Sybase IQ Error Messages 1023

Errors and Warnings

Error 1010023 "Cursor is not updatable: %2. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of exception.

Parameter 2 Reason why the cursor is not updatable.

Probable Cause Cursor is not updatable: there are join/group by/distinct/set, union,
olap function, or no updatable columns.

Error 1010024 "Column '%2' is not updatable. %1"

Constant EMSG_COLUMN_NOT_UPDATABLE

SAP Sybase Error Number 21122

SQL State QXA24

SQL Code -1010024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of exception.

Parameter 2 Column name.

Probable Cause Column is not updatable if it is long binary/varchar, rowid, (var)bi-

nary when ASE_Binary_Display is ON, referenced by other expres-
sions in the select list, identity column, or not in FOR UPDATE of
list.

Error 1010025 "Cannot restore to multiplex secondary server. %1"

Constant EMSG_DATABASE_MPX_NOLOCALFORRESTORE

SAP Sybase Error Number 21125

SQL State QXA25

SQL Code -1010025L

ODBC 2 State ERROR

1024 SAP Sybase IQ

Errors and Warnings

Error 1010025 "Cannot restore to multiplex secondary server. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Multiplex secondary server cannot be restored. Only the coordinator
can be restored.

Error 1010026 "Only a server in single_node mode can become a

coordinator %1"

Constant EMSG_DATABASE_MPX_CANTBECOMEWRITER

SAP Sybase Error Number 21126

SQL State QXA26

SQL Code -1010026L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Must be in simplex mode to convert to coordinator mode.

Error 1010027 "Only a server in coordinator mode can become a

single_node server %1"

Constant EMSG_DATABASE_MPX_CANTBECOMESPX

SAP Sybase Error Number 21127

SQL State QXA27

Constant EMSG_DATABASE_MPX_QUERY_NOWRITE

SAP Sybase Error Number 21131

SQL State QXA31

SQL Code -1010031L

1026 SAP Sybase IQ

Errors and Warnings

Error 1010031 "Cannot modify object %2 on dbspace %3. A query server

may not modify objects in the main IQ store. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 object name

Parameter 3 dbspace name

Probable Cause A query server may not modify objects in the main store.

Error 1010032 "Bad Database Identity block. %1"

Constant EMSG_DATABASE_MPX_BADDBID

SAP Sybase Error Number 21132

SQL State QXA32

SQL Code -1010032L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The secondary server has too many or too few shared main dbspaces
defined.

Error 1010033 "This secondary server was not shut down cleanly before
synchronize. Must start with -iqfrec %1"

Constant EMSG_DATABASE_MPX_READERNOTSHUTDOWNCLEAN-
LY

SAP Sybase Error Number 21133

SQL State QXA33

SQL Code -1010033L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1027

Errors and Warnings

Error 1010033 "This secondary server was not shut down cleanly before
synchronize. Must start with -iqfrec %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Must start with iqfrec to rebuild freelist.

Error 1010034 "Modifications of the iq main store not allowed in readonly

mode. %1"

Constant EMSG_DATABASE_MPX_NOWRITEIFREADONLY

SAP Sybase Error Number 21134

SQL State QXA34

SQL Code -1010034L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The mpx mode does not match the restore type.

Error 1010035 "The transaction log does not match the mpx mode of this
server. %1"

Constant EMSG_DATABASE_MPX_LOGDBMODEMISMATCH

SAP Sybase Error Number 21135

SQL State QXA35

SQL Code -1010035L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The mpx mode does not match the transaction log.

1028 SAP Sybase IQ

Errors and Warnings

Error 1010036 "MPX: invalid file_id. Single_node or coordinator using a

local or bad fileID. %1"

Constant EMSG_DATABASE_MPX_BADFILEID

SAP Sybase Error Number 21136

SQL State QXA36

SQL Code -1010036L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The fileid is not valid for this mpx mode.

Error 1010037 "MPX: invalid local file_id. Secondary server using a bad
local fileID. %1"

Constant EMSG_DATABASE_MPX_BADLOCALFILEID

SAP Sybase Error Number 21137

SQL State QXA37

SQL Code -1010037L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The local fileid is not valid for this mpx mode.

Messages 1010038 through 1010057

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1010038 "MPX: Local stores are not supported. %1"

Constant EMSG_DATABASE_MPX_NOLOCALFILEID

SAP Sybase Error Number 21138

SAP Sybase IQ Error Messages 1029

Errors and Warnings

Error 1010038 "MPX: Local stores are not supported. %1"

SQL State QXA38

SQL Code -1010038L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The local fileid is not valid for this mpx mode.

Error 1010039 "MPX: Inconsistent Transaction Manager Data. %1"

Constant EMSG_DATABASE_MPX_TXNMGRCHECK

SAP Sybase Error Number 21139

SQL State QXA39

SQL Code -1010039L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause The local fileid is not valid for this mpx mode.

Error 1010040 "Cannot restore to multiplex secondary server without a

local store. %1"

Constant EMSG_DATABASE_UNDEFINEDUTILITYCMD

SAP Sybase Error Number 21140

SQL State QXA40

SQL Code -1010040L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

1030 SAP Sybase IQ

Errors and Warnings

Error 1010040 "Cannot restore to multiplex secondary server without a

local store. %1"

Parameter 1 Location of the exception.

Probable Cause A secondary server must have local store dbspaces defined in order to
do a restore.

Error 1010041 "Inconsistent data during OpenDatabase. %1"

Constant EMSG_DATABASE_OPENDBCHECK

SAP Sybase Error Number 21141

SQL State QXA41

SQL Code -1010041L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Open database check failure.

Error 1010042 "\"drop leaks\" is not allowed without executing post-sync

secondary server replay. %1"

Constant EMSG_DBCC_DROPLEAKS_NEED_LOCAL_REPLAY

SAP Sybase Error Number 21142

SQL State QDB73

SQL Code -1010042L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Disallow DBCC to drop leaked blocks on a MPX secondary server
without executing post-sync local TLV replay.

SAP Sybase IQ Error Messages 1031

Errors and Warnings

Error 1010043 "dbspace %2 is currently not open. %1"

Constant EMSG_DATABASE_DBSPACE_NOT_OPENED

SAP Sybase Error Number 21144

SQL State QXA42

SQL Code -1010043L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Name of dbpace

Parameter 2 Location of the exception.

Probable Cause The specifed dbspace exists but is not currently open.

Error 1010044 "Plan not available."

Constant EMSG_QPTCACHE_NOPLAN

SAP Sybase Error 21146

Number

SQL State QXA43

SQL Code -1010044L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause "User request for the plan and there is no plan in the cache to be returned.
cases when this error will be returned :1. User makes a connection and
executes select graphical_plan() or select html_plan(). 2. When the the
SQL function graphical_plan and html_plan is used to get the plan for an
IQ query for which IQ does not generate plan. "

Error 1010045 "Plan not available. Plan type is not supported for Sybase
IQ queries."

Constant EMSG_QPTCACHE_INVALID_PLANTYPE

SAP Sybase Error Number 21147

1032 SAP Sybase IQ

Errors and Warnings

Error 1010045 "Plan not available. Plan type is not supported for Sybase
IQ queries."

SQL State QXA44

SQL Code -1010045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause "IQ supports only graphical_plan and html_plan SQL functions.
Other SA plan functions (plan, explanation etc.) are not supported for
Sybase IQ."

Error 1010046 "Plan not available. The database option

QUERY_PLAN_TEXT_ACCESS is off."

Constant EMSG_QPTCACHE_ACCESS_NOT_ALLOWED

SAP Sybase Error Num- 21148

ber

SQL State QXA45

SQL Code -1010046L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause "The plan can be accessed on the client by the user only when DBA sets
option QUERY_PLAN_TEXT_ACCESS to ON for the user."

Error 1010047 "%1 is not designated as failover server"

Constant EMSG_IQMPX_NOT_FAILOVER

SAP Sybase Error Number 21176

SQL State QXA46

SQL Code -1010047L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 1033

Errors and Warnings

Error 1010047 "%1 is not designated as failover server"

Severity Code 14 on page 2

Parameter 1 server name

Probable Cause Failover process is started on a server which is not designated as

failover server

Error 1010048 "iqmpx_failover and iqmpx_sn switches cannot be

enabled simultaneously"

Constant EMSG_IQMPX_CANNOT_MIX_FAILOVER_SN

SAP Sybase Error Number 21177

SQL State QXA47

SQL Code -1010048L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause While starting an IQ server, both iqmpx_failover and iqmpx_sn com-
mand line server switches are ON.

Error 1010049 "Transaction log recovery not allowed during failover. Please
restart the server without the failover switch, do a clean
shutdown, restart failover"

Constant EMSG_IQMPX_NO_RECOVERY_IN_FAILOVER

SAP Sybase Error 21178

Number

SQL State QXA48

SQL Code -1010049L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

1034 SAP Sybase IQ

Errors and Warnings

Error 1010049 "Transaction log recovery not allowed during failover. Please
restart the server without the failover switch, do a clean
shutdown, restart failover"

Probable Cause The failover process should be started only after clean shutdown of the
server. If recovery process is initiated during failover then the server was not
shut down cleanly and failover should be restarted after the server is restar-
ted and shut down without the failover switch.

Error 1010050 "Recovery required to complete the last failover process.

Please restart the server with failover switch"

Constant EMSG_IQMPX_START_IN_FAILOVER

SAP Sybase Error 21179

Number

SQL State QXA49

SQL Code -1010050L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause A previous failover attempt did not finish cleanly. The failover changes
must be recovered and to do that restart the server with failover switch.

Error 1010051 "Failover node catalog is not in sync with TLV log. Please restart
server without failover switch, run BEGIN TRANSACTION, do a
clean shutdown, then restart failover "

Constant EMSG_IQMPX_FAILOVER_CAT_OUT_OF_SYNC

SAP Sybase Error 21180

Number

SQL State QXA50

SQL Code -1010051L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 1035

Errors and Warnings

Error 1010051 "Failover node catalog is not in sync with TLV log. Please restart
server without failover switch, run BEGIN TRANSACTION, do a
clean shutdown, then restart failover "

Probable Cause The failover process can be started only if the failover node's catalog is up to
date with the TLV log. To fix this, restart the server without the failover
switch, run BEGIN TRANSACTION, do a clean shutdown, then restart the
server with the failover switch.

Error 1010052 "Only one dbspace file may be added at a time for multiplex
servers"

Constant EMSG_IQMPX_ALTERADD_MULTIPLE_FILES

SAP Sybase Error Number 21183

SQL State QXA51

SQL Code -1010052L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause When using ALTER DBSPACE to add a file to a multiplex server, only
one file may be added at a time. Specifying a list of files to add is not
supported.

Error 1010053 "DBSPACE command extended syntax not permitted"

Constant EMSG_DBSPACE_EXTENDED_SYNTAX

SAP Sybase Error Number 21184

SQL State QXA52

SQL Code -1010053L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause When using ALTER DBSPACE command, extended syntax is not
allowed on a user connection

1036 SAP Sybase IQ

Errors and Warnings

Error 1010054 "Server option '-iqmpx_ov' only valid when used with '-
iqmpx_sn' or '-iqmpx_failover'. %1"

Constant EMSG_MPX_OV_INVALID_USE

SAP Sybase Error Number 21186

SQL State QXA53

SQL Code -1010054L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Server option '-iqmpx_ov' is permitted on an Multiplex coordinator

node or in combination with either '-iqmpx_sn' or '-iqmpx_failover' on
any other Multiplex node type.

Error 1010055 "iqmpx_reclaimwriterfreelist server switch can not be

used in Simplex or Secondary nodes"

Constant EMSG_MPX_SWITCH_INVALID_FOR_SPX_OR_SECON-
DARY

SAP Sybase Error Number 21187

SQL State QXA54

SQL Code -1010055L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause iqmpx_reclaimwriterfreelist server switch can only be used on a Co-

ordinator node.

Error 1010056 "Recovery switch '-iqfrec' is allowed on a multiplex server

only in single-node operating mode. %1"

Constant EMSG_MPX_FREC_INVALID_USE

SAP Sybase Error Number 21188

SAP Sybase IQ Error Messages 1037

Errors and Warnings

Error 1010056 "Recovery switch '-iqfrec' is allowed on a multiplex server

only in single-node operating mode. %1"

SQL State QXA55

SQL Code -1010056L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Recovery switch '-iqfrec' is allowed on a multiplex server only in

single-node operating mode.

Error 1010057 "'%2' command is not allowed on temp store files, when
server started with -iqnotemp switch. %1"

Constant EMSG_ILLEGAL_ALTER_DBSPACE_NOTEMP

SAP Sybase Error Number 21201

SQL State QXA56

SQL Code -1010057L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 alter dbspace command type string

Probable Cause When the server is running with -iqnotemp switch, certain alter
dbspace operations are not allowed. For e.g. alter dbspace add file.

Messages 1010058 through 1012002

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1010058 "Unable to perform forced recovery when database is in

read only mode. %1"

Constant EMSG_FREC_IN_READ_ONLY

1038 SAP Sybase IQ

Errors and Warnings

Error 1010058 "Unable to perform forced recovery when database is in

read only mode. %1"

SAP Sybase Error Number 21202

SQL State QXA57

SQL Code -1010058L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Recovery switch '-iqfrec' is allowed on read/write databases only

Error "Unable to open the multiplex database. The database can only be
1010059 opened by starting the Coordinator server using single node mode
switch '-iqmpx_sn 1'. %1"

Constant EMSG_MPX_OPEN_OLDDB_NEED_SINGLE

SAP Sybase 22023

Error Num-
ber

SQL State QXA58

SQL Code -1010059L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable An older version of multiplex database can only be opened bystarting the server in
Cause single node mode. If you get this error after upgrading the database when the server
was started using '-iqro 1', then the database still needs to be opened by starting the
coordinator server in single node mode but without '-iqro 1'. This is because the
internal IQ on-disk structures could not be upgraded earlier. To complete the up-
grade, open the database by starting the coordinator server using single node mode
switch '-iqmpx_sn 1', but without '-iqro 1'. After a clean shutdown, the database can
then be started normally.

SAP Sybase IQ Error Messages 1039

Errors and Warnings

Error 1010060 "Server option -iqmpx_nowr only allowed when there are
no writers in multiplex %1"

Constant EMSG_MPX_NOWR_INVALID_USE

SAP Sybase Error Number 21212

SQL State QXA60

SQL Code -1010060L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause Please restart coordinator without -iqmpx_nowr switch to add a writ-
er

Error 1010061 "Server switch -iqmpx_nowr only allowed on coordinator

node %1"

Constant EMSG_MPX_NOWR_INVALID_USE_NOTCNODE

SAP Sybase Error Number 21213

SQL State QXA61

SQL Code -1010061L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause Please restart the server without -iqmpx_nowr switch

Error 1010062 "Unable to open the database. Start the coordinator server first,
without server option -iqro, to complete the Database Upgrade.
%1"

Constant EMSG_MPX_START_COORD_FIRST

SAP Sybase Error 22029

Number

1040 SAP Sybase IQ

Errors and Warnings

Error 1010062 "Unable to open the database. Start the coordinator server first,
without server option -iqro, to complete the Database Upgrade.
%1"

SQL State QXA62

SQL Code -1010062L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause As IQ store was opened in RO mode when you upgraded the database, some
of its internal meta-data information could not be upgraded to new format.
Please start the coordinator server first, without server option -iqro, to
complete the IQ side upgrade and continue.

Error 1011000 "Vertical Projection Cursor state error %1"

Constant EMSG_CURSORSTATEERROR

SAP Sybase Error Number 20000

SQL State QVA00

SQL Code -1011000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1011001 "Cannot find index for a given dfe %1"

Constant EMSG_INDEXNOTFOUND

SAP Sybase Error Number 20001

SQL State QVA01

SQL Code -1011001L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1041

Errors and Warnings

Error 1011001 "Cannot find index for a given dfe %1"

ODBC 3 State ERROR

Severity Code 18 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1011002 "The number of existing indexes exceeds the current

maximum number of indexes. %1"

Constant EMSG_EXCEEDEDMAXINDEXES

SAP Sybase Error Number 20002

SQL State QVA02

SQL Code -1011002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1011003 "Vertical Projection Cursor does not support AD-HOC

joins. %1"

Constant EMSG_ADHOCJOINREQUIRED

SAP Sybase Error Number 20003

SQL State QVA03

SQL Code -1011003L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

1042 SAP Sybase IQ

Errors and Warnings

Error 1011004 "Cannot drop primary key or unique constraint because a

foreign key still references it."

Constant EMSG_FKEY_STILL_EXISTS_TO_CKEY

SAP Sybase Error Num- 20004

ber

SQL State QNA27

SQL Code -1011004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause A primary key or unique constraint involved in a referential integrity

relationship cannot be dropped until its corresponding foreign key is
first dropped.

Error 1011006 "the pattern argument in a like predicate must have string
datatype."

Constant EMSG_INVALIDDATATYPE

SAP Sybase Error Number 20006

SQL State QVA06

SQL Code -1011006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1011007 "the escape argument in a like predicate must be a one

byte character."

Constant EMSG_INVALIDESCAPE

SAP Sybase Error Number 20007

SQL State QVA07

SQL Code -1011007L

SAP Sybase IQ Error Messages 1043

Errors and Warnings

SAP Sybase IQ Error Messages 1045

Errors and Warnings

Error 1012000 "You cannot do a partial restore for database '%2' because
it has been updated (%3) since its last backup (%4). %1"

Constant EMSG_RESTORE_MORE_RECENT_UPDATETIME

SAP Sybase Error Number 20923

SQL State QUA00

SQL Code -1012000L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 database

Parameter 3 last update

Parameter 4 last backup

Probable Cause No additional information available.

Error 1012001 "There is already a backup or selective restore in progress.

%1"

Constant EMSG_BACKUP_MULTIPLE_IN_PROGRESS

SAP Sybase Error Number 20924

SQL State QUA01

SQL Code -1012001L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012002 "Unable to write to archive. ('%2') %1"

Constant EMSG_BACKUP_DEVICE_WRITEERROR

1046 SAP Sybase IQ

Errors and Warnings

Error 1012002 "Unable to write to archive. ('%2') %1"

SAP Sybase Error Number 20925

SQL State QUA02

SQL Code -1012002L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for %2

Probable Cause No additional information available.

Messages 1012003 through 1012022

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1012003 "You must do a full backup before doing an incremental

backup. %1"

Constant EMSG_BACKUP_NEED_FULL_FIRST

SAP Sybase Error Number 20926

SQL State QUA03

SQL Code -1012003L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012004 "You cannot do incremental backups with this release. %1"

Constant EMSG_BACKUP_INC_NOT_IMPLEMENTED

SAP Sybase Error Number 20927

SAP Sybase IQ Error Messages 1047

Errors and Warnings

Error 1012004 "You cannot do incremental backups with this release. %1"

SQL State QUA04

SQL Code -1012004L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012005 "Server is reporting no files in the database. %1"

Constant EMSG_BACKUP_SA_NUMFILES_ZERO

SAP Sybase Error Number 20928

SQL State QUA05

SQL Code -1012005L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012006 "Server reports '%2' files in IQ store, IQ reports '%3'. %1"

Constant EMSG_BACKUP_SA_IQ_NUMFILES_DISAGREE

SAP Sybase Error Number 20929

SQL State QUA06

SQL Code -1012006L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

1048 SAP Sybase IQ

Errors and Warnings

Error 1012006 "Server reports '%2' files in IQ store, IQ reports '%3'. %1"

Parameter 2 explanation for %2

Parameter 3 explanation for %3

Probable Cause No additional information available.

Error 1012007 "IQ unable to find all files to back up. %1"

Constant EMSG_BACKUP_NO_FILES

SAP Sybase Error Number 20930

SQL State QUA07

SQL Code -1012007L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012008 "Database has changed since last restore. %1"

Constant EMSG_RESTORE_DBCHANGED

SAP Sybase Error Number 20931

SQL State QUA08

SQL Code -1012008L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012009 "This restore cannot immediately follow the previous

restore. %1"

Constant EMSG_RESTORE_BAD_PREVRESTORE

SAP Sybase IQ Error Messages 1049

Errors and Warnings

Error 1012009 "This restore cannot immediately follow the previous

restore. %1"

SAP Sybase Error Number 20932

SQL State QUA09

SQL Code -1012009L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012010 "Unable to read from archive ('%2'). %1"

Constant EMSG_RESTORE_READ_IOERROR

SAP Sybase Error Number 20933

SQL State QUA10

SQL Code -1012010L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for %2

Probable Cause No additional information available.

Error 1012011 "Header of block to be restored appears to be corrupted.

%1"

Constant EMSG_RESTORE_BAD_BLOCK_HEADER

SAP Sybase Error Number 20934

SQL State QUA11

SQL Code -1012011L

1050 SAP Sybase IQ

Errors and Warnings

Error 1012011 "Header of block to be restored appears to be corrupted.

%1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012012 "Media data appears corrupted (bad checksum). %1"

Constant EMSG_RESTORE_BAD_CRC

SAP Sybase Error Number 20935

SQL State QUA12

SQL Code -1012012L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012013 "Media meta data appears corrupted (boundary record).

%1"

Constant EMSG_RESTORE_BAD_BOUNDARY_RECORD

SAP Sybase Error Number 20936

SQL State QUA13

SQL Code -1012013L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 1051

Errors and Warnings

Error 1012013 "Media meta data appears corrupted (boundary record).

%1"

Parameter 1 location of the exception

Parameter 2 explanation for %2

Parameter 3 explanation for %3

Probable Cause No additional information available.

Error 1012017 "An I/O write error has occurred on '%2'. The restore query
has failed. %1"

Constant EMSG_RESTORE_WRITE_IOERROR

SAP Sybase Error Number 20940

SQL State QUA17

SQL Code -1012017L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for %2

Probable Cause No additional information available.

Error 1012018 "An I/O read error has occurred on '%2'. The backup query
has failed. %1"

Constant EMSG_BACKUP_READ_IOERROR

SAP Sybase IQ Error Messages 1053

Errors and Warnings

Error 1012018 "An I/O read error has occurred on '%2'. The backup query
has failed. %1"

SAP Sybase Error Number 20941

SQL State QUA18

SQL Code -1012018L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for %2

Probable Cause No additional information available.

Error 1012019 ".db or .log file does not exist. Incremental restore not
possible. %1"

Constant EMSG_RESTORE_SADB_FILE_DOES_NOT_EXIST

SAP Sybase Error Number 20942

SQL State QUA19

SQL Code -1012019L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012020 "Wrong IQ backup tape or file. %1"

Constant EMSG_RESTORE_WRONG_ARCHIVE

SAP Sybase Error Number 20943

SQL State QUA20

SQL Code -1012020L

Messages 1012023 through 1012042

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1012023 "Not an IQ backup tape or file. %1"

Constant EMSG_RESTORE_NOT_IQ_ARCHIVE

SAP Sybase Error Number 20946

SQL State QUA23

SQL Code -1012023L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012024 "Ran out of threads. Start up server with more threads.
%1"

Constant EMSG_RESTORE_OUT_OF_THREADS

SAP Sybase Error Number 20947

SQL State QUA24

SQL Code -1012024L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012025 ".db or .log file exists. Full restore will not be done. %1"

Constant EMSG_RESTORE_SADB_FILE_EXISTS

SAP Sybase Error Number 20948

1056 SAP Sybase IQ

Errors and Warnings

Error 1012025 ".db or .log file exists. Full restore will not be done. %1"

SQL State QUA25

SQL Code -1012025L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Warning 1012026 "Number of IQ blocks backed up: %1"

Constant EMSG_BACKUP_BLOCK_COUNT

SAP Sybase Error Number 20949

SQL State QUA26

SQL Code 1012026L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 number of blocks

Probable Cause No additional information available.

Warning 1012027 "Total number of IQ blocks backed Up: %1\n at %2\n\tIQ

Blocksize %3\n\tbackup Blocksize %4\n\tblocking factor
%5\n\tbuffer size %6"

Constant EMSG_BACKUP_STATS

SAP Sybase Error Number 20950

SQL State QUA27

SQL Code 1012027L

ODBC 2 State OK

ODBC 3 State OK

SAP Sybase IQ Error Messages 1057

Errors and Warnings

Warning 1012027 "Total number of IQ blocks backed Up: %1\n at %2\n\tIQ

Blocksize %3\n\tbackup Blocksize %4\n\tblocking factor
%5\n\tbuffer size %6"

Severity Code 1 on page 2

Parameter 1 number of blocks

Parameter 2 time of backup

Parameter 3 IQ Blocksize

Parameter 4 Backup BlockSize

Parameter 5 Blocking Factor

Parameter 6 BufferSize

Probable Cause No additional information available.

Warning 1012028 "Total number of IQ blocks to be backed up: %1"

Constant EMSG_TOTAL_BACKUP_BLOCK_COUNT

SAP Sybase Error Number 20951

SQL State QUA28

SQL Code 1012028L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 number of blocks

Probable Cause No additional information available.

Error 1012029 "Incremental backups disabled, perhaps due to forced

recovery. To enable,\n do a full backup"

Constant EMSG_BACKUP_INCS_DISABLED

SAP Sybase Error Number 20952

SQL State QUA29

SQL Code -1012029L

ODBC 2 State ERROR

1058 SAP Sybase IQ

Errors and Warnings

Error 1012029 "Incremental backups disabled, perhaps due to forced

recovery. To enable,\n do a full backup"

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1012030 "for long binary/varchar Column '%2', database page size
of (%3) must be greater than %4. %1"

Constant EMSG_CAT_PAGESIZETOOSMALL

SAP Sybase Error Number 20953

SQL State QUA30

SQL Code -1012030L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column number

Parameter 3 requested page size

Parameter 4 minimum allowed page size

Probable Cause The database page size requested by the user for a long binary column
is too small.

Error 1012031 "A readonly dbspace does not match this backup. Found:
AlterID %2 startBlock %3 numBlocks %4 fileID %5 %1"

Constant EMSG_RESTORE_BAD_RO_FILE

SAP Sybase Error Number 20954

SQL State QUA31

SQL Code -1012031L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 1059

Errors and Warnings

Error 1012031 "A readonly dbspace does not match this backup. Found:
AlterID %2 startBlock %3 numBlocks %4 fileID %5 %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 alterID found in the RO dbspace header

Parameter 3 startBlock found in the RO dbspace header

Parameter 4 number of blocks found in the RO dbspace header

Parameter 5 fileID found in the RO dbspace header

Probable Cause There is a readonly dbspace that does not match the RO dbspaces that
existed at the time of the backup.

Error 1012032 "You may either do selective backup of readonly dbspaces

or readonly dbfiles with backup type 'full' alone, or do an
all-inclusive backup"

Constant EMSG_BACKUP_RO_WITH_FULL_ALONE

SAP Sybase Error Number 20955

SQL State QUA32

SQL Code -1012032L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1012033 "IQ store dbfile %2 must be either readonly or belong to an

RO dbspace. %1"

Constant EMSG_BACKUP_RO_ILLEGAL

SAP Sybase Error Number 20956

SQL State QUA33

SQL Code -1012033L

ODBC 2 State ERROR

ODBC 3 State ERROR

1060 SAP Sybase IQ

Errors and Warnings

Error 1012033 "IQ store dbfile %2 must be either readonly or belong to an

RO dbspace. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbfile to backup

Probable Cause Dbfile or the dbspace specified in RO selective backup found to be

Error 1012034 "IQ store dbspace or dbfile %2 is unavailable. Backup will

not be done. %1"

Constant EMSG_BACKUP_DBSPACE_OFFLINE

SAP Sybase Error Number 20957

SQL State QUA34

SQL Code -1012034L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbspace to backup

Probable Cause dbspace to backup must be online, both in catalog and dynamically

Error 1012035 "You may either do selective restore of readonly dbspaces

or readonly dbfiles from a 'full' backup archive, or restore
from an all-inclusive backup."

Constant EMSG_RESTORE_RO_WITH_FULL_ALONE

SAP Sybase Error Num- 20958

ber

SQL State QUA35

SQL Code -1012035L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 1061

Errors and Warnings

Error 1012035 "You may either do selective restore of readonly dbspaces

or readonly dbfiles from a 'full' backup archive, or restore
from an all-inclusive backup."

Severity Code 14 on page 2

Probable Cause No additional information available.

Error 1012036 "IQ unable to find any file to restore. %1"

Constant EMSG_RESTORE_NO_FILES

SAP Sybase Error Number 20959

SQL State QUA36

SQL Code -1012036L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Error 1012037 "IQ store dbfile %2 exists. Restore will not be done. %1"

Constant EMSG_RESTORE_IQDB_FILE_EXISTS

SAP Sybase Error Num- 20960

ber

SQL State QUA37

SQL Code -1012037L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 dbfile to restore

Probable Cause File must not exist when restoring from a full backup, unless restore is
RO selective or restoring from virtual backup, or the file was created
after the dependent backup when restoring from inc backup.

1062 SAP Sybase IQ

Errors and Warnings

Error 1012038 "IQ store dbfile %2 does not exist. Restore will not be done.
%1"

Constant EMSG_RESTORE_IQDB_FILE_DOES_NOT_EXIST

SAP Sybase Error 20961

Number

SQL Code -1012041L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Warning 1012042 "(%1) Please mount archive media on '%2'."

Constant EMSG_RESTORE_MOUNT_NONMASTERMEDIA

SAP Sybase Error Number 20965

SQL State 01A42

1064 SAP Sybase IQ

Errors and Warnings

Warning 1012042 "(%1) Please mount archive media on '%2'."

SQL Code 1012042L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Probable Cause No additional information available.

Messages 1012043 through 1013016

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Warning 1012043 "(%1) Please mount IQ MASTER archive media for

database '%2' on '%3'."

Constant EMSG_RESTORE_MOUNT_MASTERMEDIA

SAP Sybase Error Number 20966

SQL State 01A43

SQL Code 1012043L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause No additional information available.

Warning 1012044 "(%1) Please mount Backup Server archive media for
database '%2' on '%3'."

Constant EMSG_RESTORE_MOUNT_BACKUPSERVERMEDIA

SAP Sybase Error Number 20967

SAP Sybase IQ Error Messages 1065

Errors and Warnings

Warning 1012044 "(%1) Please mount Backup Server archive media for
database '%2' on '%3'."

SQL State 01A44

SQL Code 1012044L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause No additional information available.

Warning 1012045 "(%1) Please mount archive media on '%2'."

Constant EMSG_BACKUP_MOUNT_NONMASTERMEDIA

SAP Sybase Error Number 20968

SQL State 01A45

SQL Code 1012045L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Probable Cause No additional information available.

Warning 1012046 "(%1) Please mount archive media on '%2'. It will be the IQ
MASTER archive for database '%3'."

Constant EMSG_BACKUP_MOUNT_MASTERMEDIA

SAP Sybase Error Number 20969

SQL State 01A46

1066 SAP Sybase IQ

Errors and Warnings

Warning 1012046 "(%1) Please mount archive media on '%2'. It will be the IQ
MASTER archive for database '%3'."

SQL Code 1012046L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause No additional information available.

Warning 1012047 "(%1) Please mount archive media on '%2'. It will be the
Backup Server archive for database '%3'."

Constant EMSG_BACKUP_MOUNT_BACKUPSERVERMEDIA

SAP Sybase Error Number 20970

SQL State 01A47

SQL Code 1012047L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause No additional information available.

Warning 1012048 "(%1) Archive media mounted on '%2'."

Constant EMSG_BACKUP_ARCHIVEMEDIA_MOUNTED

SAP Sybase Error Number 20971

SQL State 01U48

SAP Sybase IQ Error Messages 1067

Errors and Warnings

Warning 1012048 "(%1) Archive media mounted on '%2'."

SQL Code 1012048L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Probable Cause No additional information available.

Warning 1012049 "(%1) Done with archive media on '%2'."

Constant EMSG_BACKUP_ARCHIVEMEDIA_CLOSED

SAP Sybase Error Number 20972

SQL State 01U49

SQL Code 1012049L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 explanation of %1

Parameter 2 explanation of %2

Probable Cause No additional information available.

Error 1012050 "Bad opcode detected during restore. Expected opcode is

'%2', but '%3' was seen. %1"

Constant EMSG_HEADER_BADOPCODE

SAP Sybase Error Number 20974

SQL State QUA50

SQL Code -1012050L

ODBC 2 State ERROR

ODBC 3 State ERROR

1068 SAP Sybase IQ

Errors and Warnings

Error 1012050 "Bad opcode detected during restore. Expected opcode is

'%2', but '%3' was seen. %1"

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause This is an internal error. If this error occurs it should be reported to
Sybase.

Error 1012051 "An invalid database segment number (%2, %3) has been
detected. %1"

Constant EMSG_HEADER_BAD_SEGMENTNUMBER

SAP Sybase Error Number 20975

SQL State QUA51

SQL Code -1012051L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1012052 "Programming error: looking for hole '%2', but only have
'%3'. %1"

Constant EMSG_HEADER_HOLE_ERROR

SAP Sybase Error Number 20976

SQL State QUA52

SQL Code -1012052L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1069

Errors and Warnings

Error 1012052 "Programming error: looking for hole '%2', but only have
'%3'. %1"

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause This is an internal error. If this error occurs it should be reported to
Sybase.

Error 1012053 "Fatal internal error: looking for segment containing hole
{%2,%3}, but none was found. %1"

Constant EMSG_HEADER_HOLE_LOOKUP_ERROR

SAP Sybase Error Number 20977

SQL State QUA53

SQL Code -1012053L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation of %2

Parameter 3 explanation of %3

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1012054 "Fatal internal error: looking for segment containing block
'%2', but none was found. %1"

Constant EMSG_BACKUP_SEGMENT_NUMBER_ERROR

SAP Sybase Error Number 20978

SQL State QUA54

SQL Code -1012054L

1070 SAP Sybase IQ

Errors and Warnings

Error 1012054 "Fatal internal error: looking for segment containing block
'%2', but none was found. %1"

ODBC 2 State ERRORi

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 explanation of %2

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1012055 "RESTORE VERIFY has found errors with the archive. %1"

Constant EMSG_RESTORE_VERIFY_FAILED_WITH_ERRORS

SAP Sybase Error Number 21207

SQL State QUA55

SQL Code -1012055L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The verification of the provided archive has failed. Please check the
server log for details of errors which were thrown during the verifi-
cation process.

Warning 1012056 "Total number of IQ blocks verified: %1/%2 ( %3%% )"

Constant EMSG_RESTORE_VERIFY_PROGRESS

SAP Sybase Error Number 21208

SQL State QUA56

SQL Code 1012056L

ODBC 2 State OK

ODBC 3 State OK

SAP Sybase IQ Error Messages 1071

Errors and Warnings

Warning 1012056 "Total number of IQ blocks verified: %1/%2 ( %3%% )"

Severity Code 1 on page 2

Parameter 1 Parameter 1 description

Parameter 2 Parameter 2 description

Parameter 3 Parameter 3 description

Probable Cause This is an informational message displayed in context with other

messages.

Error 1012057 "Command specified for virtual backup failed. %1"

Constant EMSG_BACKUP_VIRTUAL_CMD_FAILED

SAP Sybase Error Number 21209

SQL State QUA57

SQL Code -1012057L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause No additional information available.

Warning 1013000 "*** BlockSize: %2, Block size: Record size: %1"

Constant EMSG_ISQL_RECORDBLOCKING

SAP Sybase Error Number 20570

SQL State 00A00

SQL Code 1013000L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 record size

Parameter 2 block size

1072 SAP Sybase IQ

Errors and Warnings

Warning 1013000 "*** BlockSize: %2, Block size: Record size: %1"

Probable Cause No additional information available.

Warning 1013001 "*** Record size: variable, Block size: %1"

Constant EMSG_ISQL_RECORDBLOCKSIZE

SAP Sybase Error Number 20571

SQL State 00A01

SQL Code 1013001L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 block size

Probable Cause No additional information available.

Warning 1013015 "Row Delimiter: %1"

Constant EMSG_ISQL_PREVIEWROWD

SAP Sybase Error Number 20585

SQL State 00A15

SQL Code 1013015L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 row delimiter

Probable Cause This is the ROW DELIMITER used for the LOAD.

Error 1013015 "Multi-column indexes that are non unique or of more than
5300 bytes in total width are not supported. %1"

Constant EMSG_SQL_MULTICOLWIDTH

SAP Sybase Error Num- 20584

ber

SAP Sybase IQ Error Messages 1073

Errors and Warnings

Error 1013015 "Multi-column indexes that are non unique or of more than
5300 bytes in total width are not supported. %1"

SQL State QCA15

SQL Code -1013015L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Multicolumn indexes that are non unique or of more than 1024 bytes in
total width are not supported. The total width is obtained by summing
the individual widths of the various columns involved in the multicol-
umn index.

Error 1013016 "FILLER"

Constant EMSG_ISQL_FILLERNAME

SAP Sybase Error Number 20586

SQL State QCA16

SQL Code -1013016L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause No additional information available.

Messages 1013017 through 1013038

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1013017 "An internal error occurred while calling a method on a

db_sql_*_identifier. Object does not have an IIndex
Handle. %1"

Constant EMSG_SQL_NOINDEX

SAP Sybase Error Number 20587

1074 SAP Sybase IQ

Errors and Warnings

Error 1013017 "An internal error occurred while calling a method on a

db_sql_*_identifier. Object does not have an IIndex
Handle. %1"

SQL State QCA17

SQL Code -1013017L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This error should not occur during normal operation. It is an internal
error. If this error occurs, it should be reported to Sybase.

Error 1013018 "An internal error occurred while calling a method on

db_sql_*_identifier. Object does not have an IColumn
Handle. %1"

Constant EMSG_SQL_NOCOLUMN

SAP Sybase Error Number 20588

SQL State QCA18

SQL Code -1013018L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This error should not occur during normal operation. It is an internal
error. If this error occurs, it should be reported to Sybase.

Error 1013019 "CHECK constraint has unsupported component %2. %1"

Constant EMSG_SQL_IQ_UNSUPPORTED_CONSTRAINT

SAP Sybase Error Number 20589

SQL State QCA19

SQL Code -1013019L

SAP Sybase IQ Error Messages 1075

Errors and Warnings

Error 1013019 "CHECK constraint has unsupported component %2. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 details of the constraint

Probable Cause the CHECK constraints contains either a subquery, a aggregate func-
tion, a user defined function, or other components that are not sup-
ported by IQ. CHECK constraints are not supported by Sybase IQ.

Error 1013020 "User defined default values are not supported. %1"

Constant EMSG_SQL_NODEFAULT

SAP Sybase Error Number 20590

SQL State QCA20

SQL Code -1013020L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause User defined default values are not supported by Sybase IQ.

Error 1013021 "Multi-column indexes of the specified type are not

supported. %1"

Constant EMSG_SQL_NOCLUSTEREDINDEX

SAP Sybase Error Number 20591

SQL State QCA21

SQL Code -1013021L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

1076 SAP Sybase IQ

Errors and Warnings

Error 1013021 "Multi-column indexes of the specified type are not

supported. %1"

Parameter 1 location of the exception

Probable Cause Multi-column indexes of the user specified type are not supported by
Sybase IQ.

Error 1013022 "Cannot create a duplicate '%2' index '%3'. %1"

Constant EMSG_SQL_INDEXFOUND

SAP Sybase Error Number 20592

SQL State QCA22

SQL Code -1013022L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 indextype

Parameter 3 indexname

Probable Cause Cannot create duplicate indexes of the same type on a set of columns.

Error 1013023 "Cannot create a unique '%2' index. %1"

Constant EMSG_SQL_INDEXNOUNIQUE

SAP Sybase Error Number 20593

SQL State QCA23

SQL Code -1013023L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

SAP Sybase IQ Error Messages 1077

Errors and Warnings

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 # of bytes.

Parameter 3 maximum number of bytes allowed.

Probable Cause The number of bytes you are trying to load into a column from an
input file has exceeded the maximum number of bytes allowed.

Error 1013028 "An invalid size (too large) was specified for a LOAD
option. %1"

Constant EMSG_SQL_INVALIDSIZE

SAP Sybase Error Number 20598

SQL State QCA28

SQL Code -1013028L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause A size too large was specified for a LOAD option. Check the options
specified for the LOAD statement.

Error 1013029 "The INSERT...LOCATION statement must have a SELECT

statement. %1"

Constant EMSG_SQL_INS_LOC_SELECT

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1013033 "An error occurred while calling a method on

db_sql_*_identifier. Object does not have an IJoinIndex
handle. %1"

Constant EMSG_SQL_NOJOININDEX

SAP Sybase Error Number 20603

SQL State QCA33

SQL Code -1013033L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal error. If this error occurs, it should be reported to
Sybase.

Error 1013034 "Cannot create an index with no columns. %1"

Constant EMSG_SQL_INDEXNOFIELDS

SAP Sybase Error Number 20604

SQL State QCA34

SQL Code -1013034L

ODBC 2 State ERROR

ODBC 3 State ERROR

SAP Sybase IQ Error Messages 1081

Errors and Warnings

Error 1013034 "Cannot create an index with no columns. %1"

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You cannot create an index with no columns.

Error 1013035 "The number of insert VALUES does not match the column
list. %1"

Constant EMSG_SQL_INSERTNOVALUE

SAP Sybase Error Number 20605

SQL State QCA35

SQL Code -1013035L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The number of columns in the INSERT does not match the number of
of VALUES provided.

Error 1013036 "The keyword 'FILLER' is not valid in this context. %1"

Constant EMSG_SQL_NOFILLER

SAP Sybase Error Number 20606

SQL State QCA36

SQL Code -1013036L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You cannot use the 'FILLER' keyword here. No column can be of type
'FILLER' for a VALUES insert.

1082 SAP Sybase IQ

Errors and Warnings

Error 1013037 "The datatype of column '%2' is not valid. %1"

Constant EMSG_SQL_DATATYPENOTVALIDFOROP

SAP Sybase Error Number 20607

SQL State QCA37

SQL Code -1013037L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column

Probable Cause The named column has an invalid datatype. If subsequent examina-
tion of the column definition reveals a datatype that is valid, then this
error should be reported to Sybase.

Error 1013038 "The number of columns given does not match. %1"

Constant EMSG_SQL_INSERTNUMBERFIELDS

SAP Sybase Error Number 20608

SQL State QCA38

SQL Code -1013038L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The number of columns to be inserted does not match the number of
columns in the insert. If this error persists, it should be reported to
Sybase.

1013039 - 1013131

SAP Sybase IQ Error Messages 1083

Errors and Warnings

Messages 1013039 through 1013060

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1013039 "An internal error occurred while constructing a

db_sql_*_identifier. The IColumn handle does not belong
to the ITable. %1"

Constant EMSG_SQL_COLUMNMISMATCH

SAP Sybase Error Number 20609

SQL State QCA39

SQL Code -1013039L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This error should not occur during normal operation. It is an internal
error. If this error occurs, it should be reported to Sybase.

Error 1013040 "Column '%2' in the INSERT list has no matching column in
the SELECT list. %1"

Constant EMSG_SQL_INSERTNOMATCHILIST

SAP Sybase Error Number 20610

SQL State QCA40

SQL Code -1013040L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column

Probable Cause The named column in the INSERT list does not have a matching
column in the SELECT list.

1084 SAP Sybase IQ

Errors and Warnings

Error 1013041 "Column '%2' in the SELECT list has no matching column
in the INSERT list. %1"

Constant EMSG_SQL_INSERTNOMATCHCLIST

SAP Sybase Error Number 20611

SQL State QCA41

SQL Code -1013041L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column

Probable Cause The named column in the SELECT list does not have a matching
column in the INSERT list.

Error 1013042 "An internal error occurred while constructing a

db_sql_*_identifier. The IIndex handle does not belong to
the ITable. %1"

Constant EMSG_SQL_INDEXMISMATCH

SAP Sybase Error Number 20612

SQL State QCA42

SQL Code -1013042L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This error should not occur during normal operation. It is an internal
error. If this error occurs it should be reported to Sybase.

Error 1013043 "Unable to convert column '%2' to the requested datatype

(%3) from datatype (%4). %1"

Constant EMSG_SQL_INVALIDCONVERSION

SAP Sybase IQ Error Messages 1085

Errors and Warnings

Error 1013043 "Unable to convert column '%2' to the requested datatype

(%3) from datatype (%4). %1"

SAP Sybase Error Number 20613

SQL State QCA43

SQL Code -1013043L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column

Parameter 3 requested datatype

Parameter 4 current datatype

Probable Cause This column cannot be converted to the requested datatype.

Error 1013044 "An internal error occurred. An invalid table type was
encountered. %1"

Constant EMSG_SQL_INVALID_TBL_TYPE

SAP Sybase Error Number 20614

SQL State QCA44

SQL Code -1013044L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This is an internal programming error. The table type was not cor-
rectly set to BASE, VIEW, JVT, TMP, LOCAL TMP for its context. If
this error occurs it should be reported to Sybase.

Error 1013045 "An invalid file name ('%2') was specified for a LOAD
TABLE. The file name has zero length. %1"

Constant EMSG_SQL_INVALIDFILENAME

1086 SAP Sybase IQ

Errors and Warnings

Error 1013045 "An invalid file name ('%2') was specified for a LOAD
TABLE. The file name has zero length. %1"

SAP Sybase Error Number 20615

SQL State QCA45

SQL Code -1013045L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 file name

Probable Cause A file name of zero length was specified for LOAD TABLE.

Error 1013046 "An internal error occurred. An invalid index type was
encountered. %1"

Constant EMSG_SQL_INVALIDINDEXTYPE

SAP Sybase Error Number 20616

SQL State QCA46

SQL Code -1013046L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause This error should not occur during normal operation. It is an internal
error and should be reported to Sybase.

Error 1013047 "Cannot alter index '%2'. Only indexes in base tables or
global temporary tables can be altered. %1"

Constant EMSG_SQL_CANNOT_ALTER_INDEX

SAP Sybase Error Number 20617

SQL State QCA47

SAP Sybase IQ Error Messages 1087

Errors and Warnings

Error 1013047 "Cannot alter index '%2'. Only indexes in base tables or
global temporary tables can be altered. %1"

SQL Code -1013047L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Indexname.

Probable Cause Only indexes in base tables and global temporary tables listed in
SYS.SYSINDEX can be altered.

Warning 1013048 "Warning: Partial input record (%1 bytes) skipped at EOF
(O/S %2). %3 rows read."

Constant EMSG_SQL_INSERTPARTIALRECORD

SAP Sybase Error Number 20618

SQL State 01A48

SQL Code 1013048L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 number of bytes at end of file that were skipped

Parameter 2 operating system error

Parameter 3 number of rows read from the input file

Probable Cause An incomplete input record was found at the end of the flat file. If the
operating system error returned is not zero, you may need to take
action as dictated by the error and try the LOAD again.

Warning 1013049 "******* Possible Tape/File Error *******\n\n Bytes Read: %1,
O/S errno: %2\n %3 rows read. Input suspended."

Constant EMSG_SQL_INSERTTAPEERROR

SAP Sybase Error Number 20619

1088 SAP Sybase IQ

Errors and Warnings

Warning 1013049 "******* Possible Tape/File Error *******\n\n Bytes Read: %1,
O/S errno: %2\n %3 rows read. Input suspended."

SQL State 01A49

SQL Code 1013049L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

Parameter 1 number of bytes read

Parameter 2 operating system error number

Parameter 3 number of rows read

Probable Cause Take action as dictated by the operating system error and retry the
operation.

Error 1013050 "The Temp_Extract_Name1 option is set. The current

operation will be rolled back. %1"

Constant EMSG_SQL_OP_PROHIBITED

SAP Sybase Error 20620

Number

SQL State QCA50

SQL Code -1013050L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Probable Cause Certain operations will not be allowed whenever the Temp_Ex-
tract_Name1 option is set. They are: INSERT...VALUES, LOAD, DE-
LETE, and INSERT...LOCATION if the table being inserted, loaded or
deleted from is the top table in a join. INSERT...SELECT. For example,
'insert t1 select * from t2'.

Error 1013052 "The BLOCK FACTOR for LOAD cannot be zero. %1"

Constant EMSG_SQL_BLOCKFACTOR_IS_ZERO

SAP Sybase IQ Error Messages 1089

Errors and Warnings

Error 1013052 "The BLOCK FACTOR for LOAD cannot be zero. %1"

SAP Sybase Error Number 20622

SQL State QCA52

SQL Code -1013052L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The BLOCK FACTOR for LOAD cannot be zero.

Error 1013054 "Delimiter '%2' must be 1 to %3 characters in length. %1"

Constant EMSG_SQL_INVALIDDELIMITERSIZE

SAP Sybase Error Number 20624

SQL State QCA54

SQL Code -1013054L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 delimiter

Parameter 3 maximum allowable length of column delimiter or row terminator

Probable Cause The row or column delimiter in a LOAD statement must be 1-4 char-
acters.

Error 1013055 "ON_ERROR = 'CONTINUE' is valid only for a full-width

INSERT. %1"

Constant EMSG_SQL_INVALIDCONTINUE

SAP Sybase Error Number 20625

SQL State QCA55

1090 SAP Sybase IQ

Errors and Warnings

Error 1013055 "ON_ERROR = 'CONTINUE' is valid only for a full-width

INSERT. %1"

SQL Code -1013055L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause ON_ERROR = 'CONTINUE' is valid only for a full width insert.

Error 1013056 "FILLER width must be greater than zero. %1"

Constant EMSG_SQL_INVALIDFILLERWIDTH

SAP Sybase Error Number 20626

SQL State QCA56

SQL Code -1013056L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause FILLER width must be greater than zero.

Error 1013057 "ASCII input column width must be greater than zero. %1"

Constant EMSG_SQL_INVALIDASCIIWIDTH

SAP Sybase Error Number 20627

SQL State QCA57

SQL Code -1013057L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

SAP Sybase IQ Error Messages 1091

Errors and Warnings

Error 1013057 "ASCII input column width must be greater than zero. %1"

Probable Cause ASCII input column width must be greater than zero.

Error 1013058 "The row delimiter must be distinct from all column
delimiters. %1"

Constant EMSG_SQL_IDENTICALDELIMITERANDROWTERMINA-
TOR

SAP Sybase Error Number 20628

SQL State QCA58

SQL Code -1013058L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The row delimiter cannot be the same as any column delimiter.

Error 1013059 "The BLOCK SIZE option is not valid for a fixed-width input
insert. %1"

Constant EMSG_SQL_INVALIDBLOCKSIZEOPTION

SAP Sybase Error Number 20629

SQL State QCA59

SQL Code -1013059L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You cannot specify BLOCK SIZE for a fixed-width input insert.

Error 1013060 "The BLOCK FACTOR option is not valid for a variable
width input insert. %1"

Constant EMSG_SQL_INVALIDBLOCKFACTOROPTION

1092 SAP Sybase IQ

Errors and Warnings

Error 1013060 "The BLOCK FACTOR option is not valid for a variable
width input insert. %1"

SAP Sybase Error Number 20630

SQL State QCA60

SQL Code -1013060L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause You cannot specify BLOCK FACTOR for a variable width input
insert.

Probable Cause No data was found during a scan of an input file during insert.

1094 SAP Sybase IQ

Errors and Warnings

Error 1013064 "Row delimiter not seen during scan of input file. At least
one of the input rows is missing a terminator. %1"

Constant EMSG_SQL_ROWTERMINATORNOTSEEN

SAP Sybase Error Number 20634

SQL State QCA64

SQL Code -1013064L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A row delimiter has been omitted from an input file.

Error 1013065 "Row delimiter '%2' and column delimiter '%3' cannot be
substrings of each other. %1"

Constant EMSG_SQL_CANTBESUBSTRING

SAP Sybase Error Number 20635

SQL State QCA65

SQL Code -1013065L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the row delimiter

Parameter 3 the column delimiter

Probable Cause Row and column delimiters cannot be substrings of each other.

Error 1013066 "The %2 load option can be specified only once. %1"

Constant EMSG_SQL_MULTIPLE_LOAD_OPTION

SAP Sybase Error Number 20636

SAP Sybase IQ Error Messages 1095

Errors and Warnings

Error 1013066 "The %2 load option can be specified only once. %1"

SQL State QCA66

SQL Code -1013066L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 name of the load option

Probable Cause The named load option can be specified only once per LOAD state-
ment.

Error 1013067 "Option CONVERSION ERROR must be OFF when

IGNORE CONSTRAINT DATA VALUE or ALL is specified.
%1"

Constant EMSG_SQL_DATAVALUE_CVTERROR

SAP Sybase Error Number 20637

SQL State QCA67

SQL Code -1013067L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause When IGNORE CONSTRAINT DATA VALUE or ALL is given on a

load statement, the database option CONVERSION ERROR must be
off.

Error 1013068 "Constraint '%2' violated: Invalid value for column '%3' in
table '%4'. %1"

Constant EMSG_SQL_COLUMN_CHECK_CONSTRAINT_VIOLATED

SAP Sybase Error Number 20638

SQL State QCA68

1096 SAP Sybase IQ

Errors and Warnings

Error 1013068 "Constraint '%2' violated: Invalid value for column '%3' in
table '%4'. %1"

SQL Code -1013068L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 constraint name

Parameter 3 column name for which the violation occurred

Parameter 4 table name

Probable Cause The Data being inserted or updated is invalid due to a column check
constraint violation.

Error 1013070 "Cannot specify check constraints off and ignore all, ignore
check, log all or log check during load. %1"

Constant EMSG_SQL_IQ_LOAD_CONFLICT

SAP Sybase Error Number 20640

SQL State QCA70

SQL Code -1013070L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause when check constraints off is specified during load ignore all, ignore
check, log all, log check are not available.

Error 1013071 "Constraint '%2' violated: Invalid value in table '%3'. %1"

Constant EMSG_SQL_TABLE_CHECK_CONSTRAINT_VIOLATED

SAP Sybase Error Number 20641

SQL State QCA71

SAP Sybase IQ Error Messages 1097

Errors and Warnings

Error 1013071 "Constraint '%2' violated: Invalid value in table '%3'. %1"

SQL Code -1013071L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 constraint name

Parameter 3 table name on which the table check violation occurred

Probable Cause The Data being inserted or updated is invalid due to a table check
constraint violation.

Error 1013077 "ROW DELIMITED BY is valid only when all columns are
delimited or ASCII fixed-width. %1"

Constant EMSG_SQL_INVALIDUSEOFROWTERMINATOR

SAP Sybase Error Number 20647

SQL State QCA77

SQL Code -1013077L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause ROW DELIMITED BY is valid only when all columns are delimited
or ASCII fixed-width. You cannot use a row delimiter with PREFIX
or BINARY columns.

Error 1013078 "Insert Pass 1 CPU utilization"

Constant EMSG_FFINSERT_1

SAP Sybase Error Number 20648

SQL State QCA78

SQL Code -1013078L

SAP Sybase Error Number 20651

SAP Sybase IQ Error Messages 1099

Errors and Warnings

Error 1013081 "Insert Pass 2 CPU utilization"

SQL State QCA81

SQL Code -1013081L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This is displayed as part of an informational message during insert.

Error 1013082 "Insert Pass 2 user (%)"

Constant EMSG_FFINSERT_2U

SAP Sybase Error Number 20652

SQL State QCA82

SQL Code -1013082L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This is displayed as part of an informational message during insert.

Error 1013083 "Insert Pass 2 system (%)"

Constant EMSG_FFINSERT_2S

SAP Sybase Error Number 20653

SQL State QCA83

Errors and Warnings

Error 1013089 "Insert Total system (%)"

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause This is displayed as part of an informational message during insert.

Error 1013090 "Single or double quote mark cannot be the first character
of column delimiter or row terminator with QUOTES option
ON. %1"

Constant EMSG_INVALID_COLUMN_DELIM

SAP Sybase Error Number 20979

SQL State QCA90

SQL Code -1013090L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Cannot use single or double quote mark for column/row delimiter
with QUOTES option ON.

Error 1013091 "Column pairs %2=%3 could not be matched. %1"

Constant EMSG_SQL_COLUMNPAIRSNOTFOUND

SAP Sybase Error Number 20983

SQL State QCA91

SQL Code -1013091L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 column name

Parameter 3 column name

SAP Sybase IQ Error Messages 1103

Errors and Warnings

Error 1013091 "Column pairs %2=%3 could not be matched. %1"

Probable Cause The columns specified in CREATE JOIN could not be matched in the
tables specified.

Error 1013092 "The MONITOR for this database, connection and buffer
cache already exists. %1"

Constant EMSG_SQL_MONITOREXISTS

SAP Sybase Error Number 20984

SQL State QCA92

SQL Code -1013092L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause A monitor has already been started for this database, connection and
buffer cache.

Warning 1013093 "Insert started: %1\n"

Constant EMSG_SQL_INSERTSTARTED

SAP Sybase Error Number 20985

SQL State 00A93

SQL Code 1013093L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 1 on page 2

Parameter 1 The table being inserted to.

Probable Cause This is an informational message displayed during insert.

Error 1013096 "Index %2 could not be created. The datatype does not
support an index of %3. %1"

Constant EMSG_SQL_INDEXTYPEUNSUPPORTED

1104 SAP Sybase IQ

Errors and Warnings

Error 1013096 "Index %2 could not be created. The datatype does not
support an index of %3. %1"

SAP Sybase Error Number 20988

SQL State QCA96

SQL Code -1013096L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 indexname

Parameter 3 indextype

Probable Cause You cannot create an index of the type specified for the column's
datatype.

Error 1013100 "The ON keyword cannot be used in a NATURAL join. %1"

Constant EMSG_SQL_JOININVALIDONWITHNATURAL

SAP Sybase Error Number 21020

SQL State QCB00

SQL Code -1013100L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The ON keyword cannot be used in a NATURAL join.

Error 1013102 "User name '%2' does not exist. %1"

Constant EMSG_SQL_FINDUSERBYNAME

SAP Sybase Error Number 21022

SQL State QCB02

SAP Sybase IQ Error Messages 1105

Errors and Warnings

Error 1013102 "User name '%2' does not exist. %1"

SQL Code -1013102L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 the user name specified

Probable Cause The specified user does not exist.

Error 1013103 "%2 not implemented %1"

Constant EMSG_SQL_IQMSG_NOT_YET_IMPLEMENTED_IN_ATOM-
IC

SAP Sybase Error Number 22001

SQL State QCC00

SQL Code -1013103L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 Name of the feature

Probable Cause This feature has not been implemented

Error 1013104 "This operation is not allowed on the dbspace

IQ_SYSTEM_TEMP. %1"

Constant EMSG_DBSPACE_ILLEGAL_TEMP_OP

SAP Sybase Error Number 22012

SQL State QDD13

SQL Code -1013104L

ODBC 2 State ERROR

1106 SAP Sybase IQ

Errors and Warnings

Error 1013104 "This operation is not allowed on the dbspace

IQ_SYSTEM_TEMP. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Illegal op for iq_system_temp

Error 1013105 "Use ALTER DBSPACE ALTER FILE for this operation. %1"

Constant EMSG_DBSPACE_USE_ALTER_FILE

SAP Sybase Error Number 22013

SQL State QDD14

SQL Code -1013105L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Must use alter dbspace alter file

Error 1013106 "logical file %2 not part of dbspace %3. %1"

Constant EMSG_NON_EXISTENT_LOGICAL_FILENAME

SAP Sybase Error Number 22004

SQL State QDC59

SQL Code -1013106L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 logical filename that is to be altered

Parameter 3 dbspace named in sql command

SAP Sybase IQ Error Messages 1107

Errors and Warnings

Error 1013106 "logical file %2 not part of dbspace %3. %1"

Probable Cause this logical filename is not part of this dbspace

Error 1013107 "MPX: server %2 is not part of the Multiplex configuration.

%1"

Constant EMSG_MPX_BADSERVER_NAME

SAP Sybase Error Number 22008

SQL State QDD09

SQL Code -1013107L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 Server name

Probable Cause This is a multiplex and this server is not part of it.

Error 1013108 "MPX: startup failure message: server '%2' was started on
an incorrect host '%3': this server was created with this
connection string '%4'. %1"

Constant EMSG_MPX_START_WRONG_HOST

SAP Sybase Error Num- 22009

ber

SQL State QDD10

SQL Code -1013108L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 server name

Parameter 3 host server was started on

1108 SAP Sybase IQ

Errors and Warnings

Error 1013108 "MPX: startup failure message: server '%2' was started on
an incorrect host '%3': this server was created with this
connection string '%4'. %1"

Parameter 4 this server connection information

Probable Cause This server cannot be started on this host

Error 1013109 "MPX: coordinator has been started with an incorrect

catalog. %1"

Constant EMSG_MPX_INCORRECT_CATALOG

SAP Sybase Error Number 22010

SQL State QDD11

SQL Code -1013109L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause The coordinator has been started with an incorrect catalog

Warning "IQ had insufficient memory to create the buffer cache with the size
1013110 specified with the Main_Cache_Memory_MB or
Temp_Cache_Memory_MB options. Instead, the cache will be
created using the default size."

Constant EMSG_IQSTORE_OUTOFMEM_ONOPENDB

SAP Sybase Error 21033

Number

SQL State QSB35

SQL Code 1013110L

ODBC 2 State OK

ODBC 3 State OK

Severity Code 10 on page 2

SAP Sybase IQ Error Messages 1109

Errors and Warnings

Probable Cause If we catch an OUTOFMEMORY exception when creating the MAIN or the
TEMP buffer cache, we report this warning of our failure and retry to create the
cache with the default settings (and NOT the settings in the hos_paramset). This
will allow the DBA to re-open a database even if the Main_Cache_Memo-
ry_MB or Temp_Cache_Memory_MB options are set so high as to otherwise
prevent the re-opening of the database. (QTS 183253.)

Error 1013110 "MPX: server %2 has been started with an incorrect

catalog path (expected path: %3). %1"

Constant EMSG_MPX_INCORRECT_CATALOG_PATH

SAP Sybase Error Number 22011

SQL State QDD12

SQL Code -1013110L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 server name

Parameter 3 expected catalog path

Probable Cause The coordinator has been started with the incorrect catalog

Error 1013111 "MPX: This operation is not supported on a MPX

secondary node. %1"

Constant EMSG_MPX_DBSPACE_ILLEGAL_ON_SN

SAP Sybase Error Number 22014

SQL State QDD15

SQL Code -1013111L

ODBC 2 State ERROR

1110 SAP Sybase IQ

Errors and Warnings

Error 1013111 "MPX: This operation is not supported on a MPX

secondary node. %1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Not supported on a mpx secondary node

Messages 1013112 through 1013131

Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full
description of the message.

Error 1013112 "MPX: Striping parameters for IQ_SYSTEM_TEMP are

global and may only be altered on the coordinator node.
%1"

Constant EMSG_MPX_DBSPACE_STRIPING_ILLEGAL_ON_SN

SAP Sybase Error Number 22015

SQL State QDD116

SQL Code -1013112L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Change striping for IQ_SYSTEM_TEMP on coordinator only.

Error 1013113 "The multiplex server '%2' is not included in the multiplex.
%1"

Constant EMSG_MPX_SERVER_NOT_INCLUDED

SAP Sybase Error Number 22016

SQL State QNA49

SQL Code -1013113L

ODBC 2 State ERROR

SAP Sybase IQ Error Messages 1111

Errors and Warnings

Error 1013113 "The multiplex server '%2' is not included in the multiplex.
%1"

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Exception Location

Parameter 2 server name

Probable Cause This multiplex server has been excluded

Error 1013114 "To start a Secondary node in single-node mode (-iqmpx_sn 1) the
override switch (-iqmpx_ov 1) should be used %1"

Constant EMSG_MPX_SECONDARY_NEED_OV_START_SINGLE

SAP Sybase Error 22017

Number

SQL State QNA50

SQL Code -1013114L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Probable Cause Secondary servers are not allowed to start with -iqmpx_sn 1. As the use of -
iqmpx_sn 1 makes the server the owner of the IQ database it should not be used
unless coordinator restore and failover operations have failed. If it becomes
necessary to re-establish ownership of the database by a secondary server you
can start the secondary server with -iqmpx_sn 1 only with override (-iqmpx_ov
1)

Error 1013115 "IQ Internal multiplex error. Please report this to Sybase IQ
support. %1"

Constant EMSG_MPX_FATAL_PROGERROR

SAP Sybase Error Number 22018

SQL State QDD18

SQL Code -1013115L

1112 SAP Sybase IQ

Errors and Warnings

Error 1013115 "IQ Internal multiplex error. Please report this to Sybase IQ
support. %1"

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Probable Cause A fatal programming error encountered, server will be aborted.

Error 1013116 "The operation has been cancelled -

Mpx_Work_Unit_Timeout exceeded. %2 %1"

Constant EMSG_MPX_WU_TIMEOUT

SAP Sybase Error Number 22020

SQL State QDD21

SQL Code -1013116L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 explanation for arg %2 delete if no %2

Probable Cause The elapsed time to complete a distributed work unit exceed the
timeout value.

Error 1013117 "Worker rejected query fragment - %2. %1"

Constant EMSG_WORKER_REJECTED_QUERY_FRAGMENT

SAP Sybase Error Number 22024

SQL State QDD24

SQL Code -1013117L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

SAP Sybase IQ Error Messages 1113

Errors and Warnings

Error 1013117 "Worker rejected query fragment - %2. %1"

Parameter 1 location of exception

Parameter 2 reason for rejecting the fragment.

Probable Cause Worker node could not execute a remote procedure call.

Error 1013118 "Login denied to logical server '%2', Either the server is not
part of the logical server or does not match the node type
or login redirection is disabled. %1"

Constant EMSG_LOGIN_REDIRECTION_ERROR

SAP Sybase Error Number 22031

SQL State QXA63

SQL Code -1013118L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

Parameter 2 logical server id

Probable Cause This connection attempt failed because the logical server did not
match the connection criteria

Error 1013119 "To redirect to the COORDINATOR logical server the

connection parameter nodetype should be a 'writer'. %1"

Constant EMSG_NODETYPE_MUST_BE_WRITER

SAP Sybase Error Number 22032

SQL State QXA64

SQL Code -1013119L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 23 on page 2

Parameter 1 location of the exception

1114 SAP Sybase IQ

Errors and Warnings

Error 1013119 "To redirect to the COORDINATOR logical server the

connection parameter nodetype should be a 'writer'. %1"

Probable Cause The connection paramenter logicalserver = coordinator must ask for a
writer node

Error 1013120 "Worker unable to send remote procedure call to leader. -

%2. %1"

Constant EMSG_WORKER_RPC_FAILURE

SAP Sybase Error Number 22035

SQL State QDD28

SQL Code -1013120L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of exception

Parameter 2 reason for rejecting the fragment.

Probable Cause The worker node is trying to send a message to the leader node but the
leader is no longer available.

Error 1013121 "Cannot truncate partition '%2' of table '%3' - table

partitioned incorrectly. %1"

Constant EMSG_CANNOT_TRUNCATE_PARTITION

SAP Sybase Error Number 22151

SQL State QDD29

SQL Code -1013121L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 Location of the exception.

Parameter 2 partition name.

Parameter 3 table name.

SAP Sybase IQ Error Messages 1115

Errors and Warnings

Error 1013121 "Cannot truncate partition '%2' of table '%3' - table

partitioned incorrectly. %1"

Constant EMSG_RLV_FREELIST_CORRUPT

SAP Sybase Error Number 22158

SQL State QRLV1B

SQL Code -1013128L

1118 SAP Sybase IQ

Errors and Warnings

Error 1013128 "The RLV freelist is corrupted."

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause The RLV freelist is corrupted.

Error 1013129 "RLV Store has run out of memory"

Constant EMSG_RLV_HEAP_MEMORY_EXHAUSTED

SAP Sybase Error Number 22159

SQL State QRLV1C

SQL Code -1013129L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Probable Cause RLV store has exceeded the configured memory limit.

Error 1013130 "All IQ large memory has been used, allocation canceled
[size: %2] %1"

Constant EMSG_LMA_OUTOFMEMORY

SAP Sybase Error Number 22160

SQL State QBC75

SQL Code -1013130L

ODBC 2 State ERROR

ODBC 3 State ERROR

Severity Code 14 on page 2

Parameter 1 location of the exception

Parameter 2 The size of unable to allocate memory

Probable Cause iqlm large memory manager reprot error

SAP Sybase IQ Error Messages 1119

Errors and Warnings

Error 1013131 "Cannot unpartition a non-empty hash or hash-range

partitioned table %2 %1"

Constant EMSG_TABLE_CONTAINS_DATA_CANNOT_UNPARTI-
TION_HASH_PARTITION

SAP Sybase Error Number 22161

SQL State QDD35

SQL Code -1013131L

ODBC 2 State ERROR

ODBC 3 State ERROR

Error Type Message Possible Cause

Code
2699 Error char, WCHAR, and TCHAR You have attempted to use parame-
string parameters cannot be ters to one statement that are not all
mixed char strings, WCHAR strings or
TCHAR strings. String parameters
(other than INTO and USING pa-
rameters) for one statement must all
be the same type of string. Note that
literal strings are treated as char
strings.
2701 Error FOR UPDATE or FOR READ You specified the FOR UPDATE or
ONLY clause must be specified FOR READ ONLY clause on a DE-
on PREPARE (not on DE- CLARE CURSOR statement. The
CLARE CURSOR) FOR UPDATE or FOR READ ON-
LY clause must be specified on the
PREPARE statement and not the DE-
CLARE CURSOR statement. For
compatibility with previous versions
(but with reduced performance), the
sqlpp -m HISTORICAL option can
be used to allow the FOR UPDATE
or FOR READ ONLY clause on the
DECLARE CURSOR statement.

SAP Sybase IQ Error Messages 1129

SQL Preprocessor Errors

1130 SAP Sybase IQ

Error Messages Explained SAP BOBJ XI4.0
100% (2)
Error Messages Explained SAP BOBJ XI4.0
517 pages
Esb Err Msgs
No ratings yet
Esb Err Msgs
186 pages
Iq Query
0% (2)
Iq Query
172 pages
Error Messages
0% (1)
Error Messages
478 pages
Manuales de IQ
No ratings yet
Manuales de IQ
626 pages
Xi31 Sp3 Error Messages en
No ratings yet
Xi31 Sp3 Error Messages en
552 pages
IQ 16.0 SAP Sybase IQ Error Messages Sybase Inc
No ratings yet
IQ 16.0 SAP Sybase IQ Error Messages Sybase Inc
1,138 pages
Error Messages Version 5x PDF
No ratings yet
Error Messages Version 5x PDF
742 pages
Sap IQTroubleshooting
No ratings yet
Sap IQTroubleshooting
125 pages
Sybase IQ: Troubleshooting and Error Messages Guide
No ratings yet
Sybase IQ: Troubleshooting and Error Messages Guide
512 pages
Abap Error
No ratings yet
Abap Error
125 pages
Print Brush Java Project
50% (2)
Print Brush Java Project
40 pages
Data Miner 2 Api Guide PDF
No ratings yet
Data Miner 2 Api Guide PDF
58 pages
Sybase IQ: Installation and Configuration Guide
No ratings yet
Sybase IQ: Installation and Configuration Guide
158 pages
JJ
No ratings yet
JJ
153 pages
PC 811 TroubleshootingGuide
0% (1)
PC 811 TroubleshootingGuide
654 pages
Sap Error Code
No ratings yet
Sap Error Code
5 pages
Dump
No ratings yet
Dump
147 pages
Introduction To SAP Sybase IQ
No ratings yet
Introduction To SAP Sybase IQ
42 pages
Dump Analysis
33% (3)
Dump Analysis
218 pages
Short Dump
100% (1)
Short Dump
85 pages
An Introduction To GCC - Brian Gough PDF
No ratings yet
An Introduction To GCC - Brian Gough PDF
124 pages
Db2 SQL Errors
100% (1)
Db2 SQL Errors
574 pages
Understanding Warning and Error Messages Quick Steps
No ratings yet
Understanding Warning and Error Messages Quick Steps
3 pages
Mastering ArduinoJson
0% (1)
Mastering ArduinoJson
49 pages
Informatics Practices Class 12
No ratings yet
Informatics Practices Class 12
225 pages
Srdytft
No ratings yet
Srdytft
61 pages
Srdy 00
No ratings yet
Srdy 00
61 pages
CS - 8TH Bridge Course
No ratings yet
CS - 8TH Bridge Course
4 pages
ST22 2
No ratings yet
ST22 2
130 pages
Functional Specification Workbrain and SAP Interface Error Management
0% (1)
Functional Specification Workbrain and SAP Interface Error Management
22 pages
Error To Warning
No ratings yet
Error To Warning
2 pages
Build A Restful App With Spring MVC and Angularjs
No ratings yet
Build A Restful App With Spring MVC and Angularjs
161 pages
ABAP Basics (2nd Edition)
No ratings yet
ABAP Basics (2nd Edition)
4 pages
SAP Mobile Platform 2.3
No ratings yet
SAP Mobile Platform 2.3
782 pages
Contract Search
No ratings yet
Contract Search
183 pages
PL7 Reference Manual
No ratings yet
PL7 Reference Manual
462 pages
LCX Validation Error
No ratings yet
LCX Validation Error
174 pages
Java
No ratings yet
Java
27 pages
Sybase IQ 16.0 Installation
No ratings yet
Sybase IQ 16.0 Installation
64 pages
Designing and Building Parallel Programs
No ratings yet
Designing and Building Parallel Programs
371 pages
Advanced Topics in Types and Programming Languages 1st Edition Benjamin C. Pierce Download
No ratings yet
Advanced Topics in Types and Programming Languages 1st Edition Benjamin C. Pierce Download
64 pages
C# Notes
No ratings yet
C# Notes
488 pages
DBMS Viva Questions: 1. What Is Database?
100% (1)
DBMS Viva Questions: 1. What Is Database?
9 pages
List Manipulation in Turbo Prolog: V.Cotelea
No ratings yet
List Manipulation in Turbo Prolog: V.Cotelea
14 pages
Short Dump MESSAGE - TYPE - X - Delete Project
No ratings yet
Short Dump MESSAGE - TYPE - X - Delete Project
29 pages
Core Java - Unit 1 2 3
No ratings yet
Core Java - Unit 1 2 3
21 pages
Message Type X
No ratings yet
Message Type X
125 pages
ECMA-262 6th Edition June 2015
No ratings yet
ECMA-262 6th Edition June 2015
566 pages
Dumpr
No ratings yet
Dumpr
59 pages
Messae Type X
No ratings yet
Messae Type X
169 pages
GH
No ratings yet
GH
18 pages
NN Tool Example
No ratings yet
NN Tool Example
3 pages
ARRAYS
No ratings yet
ARRAYS
69 pages
Assignment 013 ComprogCS201
No ratings yet
Assignment 013 ComprogCS201
6 pages
Ug912 Vivado Properties
No ratings yet
Ug912 Vivado Properties
341 pages
Error
No ratings yet
Error
126 pages
1 s2.0 S0045790623000320 Main
No ratings yet
1 s2.0 S0045790623000320 Main
15 pages
Sample Internship Report
No ratings yet
Sample Internship Report
27 pages
Topic - Class Based Views
No ratings yet
Topic - Class Based Views
4 pages
DSA Project v1
No ratings yet
DSA Project v1
3 pages
CV. Mohammad Vicky Agassi 2024
No ratings yet
CV. Mohammad Vicky Agassi 2024
3 pages
Open Ended Lab 7 C++
No ratings yet
Open Ended Lab 7 C++
4 pages
Unit 1 Programming Assignment 1 of 1 Fall 2024
No ratings yet
Unit 1 Programming Assignment 1 of 1 Fall 2024
4 pages
Internet Applications Final Part
No ratings yet
Internet Applications Final Part
50 pages
Error
No ratings yet
Error
13 pages
Delta Extractors CO Poor Performance
No ratings yet
Delta Extractors CO Poor Performance
4 pages
Error Abap
No ratings yet
Error Abap
103 pages
The Blue Ribbon Country Cookbook
From Everand
The Blue Ribbon Country Cookbook
Diane Roupe
5/5 (4)
The Corpse That Talked
From Everand
The Corpse That Talked
Richard Telfair
No ratings yet
A Reader's Greek New Testament: Third Edition
From Everand
A Reader's Greek New Testament: Third Edition
Richard J. Goodrich
4/5 (37)
Wind Follower
From Everand
Wind Follower
Carole McDonnell
4.5/5 (7)
The Stephen Crane Megapack: 94 Classic Works by the Author of The Red Badge of Courage
From Everand
The Stephen Crane Megapack: 94 Classic Works by the Author of The Red Badge of Courage
Stephen Crane
3.5/5 (1234)
NCV, Dad's Bible: The Father's Plan
From Everand
NCV, Dad's Bible: The Father's Plan
Robert Wolgemuth
2/5 (1)
Anasazi Exile: A Science Fiction Novel
From Everand
Anasazi Exile: A Science Fiction Novel
Eric G. Swedin
No ratings yet
The Sandy Steele Mystery MEGAPACK®: 6 Young Adult Novels (Complete Series)
From Everand
The Sandy Steele Mystery MEGAPACK®: 6 Young Adult Novels (Complete Series)
Roger Barlow
No ratings yet
NKJV, Beautiful Word Bible, eBook: 500 Full-Color Illustrated Verses
From Everand
NKJV, Beautiful Word Bible, eBook: 500 Full-Color Illustrated Verses
Zondervan
5/5 (3)
An Accidental Jewel: Wisconsin's Turtle-Flambeau Flowage
From Everand
An Accidental Jewel: Wisconsin's Turtle-Flambeau Flowage
Michael Hittle
No ratings yet
A Discourse Analysis of 1 Peter
From Everand
A Discourse Analysis of 1 Peter
Ervin Ray Starwalt
No ratings yet
KJV, Beautiful Word Bible, eBook: 500 Full-Color Illustrated Verses
From Everand
KJV, Beautiful Word Bible, eBook: 500 Full-Color Illustrated Verses
Zondervan
5/5 (2)
Pocketbook Writer: Confessions of a Commercial Hack
From Everand
Pocketbook Writer: Confessions of a Commercial Hack
Charles Nuetzel
No ratings yet
Get Closer: A Journal For Encountering God
From Everand
Get Closer: A Journal For Encountering God
Van Moody
No ratings yet
The E.F. Benson MEGAPACK ®: 36 Classic Horror Stories
From Everand
The E.F. Benson MEGAPACK ®: 36 Classic Horror Stories
E. F. Benson
4/5 (2)
Get Closer: A Devotional For Encountering God
From Everand
Get Closer: A Devotional For Encountering God
Van Moody
No ratings yet
The Mary E. Wilkins Freeman Megapack: 59 Classic Stories
From Everand
The Mary E. Wilkins Freeman Megapack: 59 Classic Stories
Mary E Wilkins Freeman
5/5 (1)
The Jacques Futrelle Megapack: 47 Tales of The Thinking Machine and Others
From Everand
The Jacques Futrelle Megapack: 47 Tales of The Thinking Machine and Others
Jacques Futrelle
No ratings yet
The Katherine Mansfield MEGAPACK ®: 101 Classic Works
From Everand
The Katherine Mansfield MEGAPACK ®: 101 Classic Works
Katherine Mansfield
No ratings yet
The Arthur Conan Doyle MEGAPACK ®: 65 Stories Beyond Sherlock Holmes!
From Everand
The Arthur Conan Doyle MEGAPACK ®: 65 Stories Beyond Sherlock Holmes!
Arthur Conan Doyle
5/5 (1)
The Maxim Gorky MEGAPACK®: 61 Classic Novels and Stories
From Everand
The Maxim Gorky MEGAPACK®: 61 Classic Novels and Stories
Maxim Gorky
No ratings yet
The First Science Fiction Novel MEGAPACK®: 6 Great Science Fiction Novels
From Everand
The First Science Fiction Novel MEGAPACK®: 6 Great Science Fiction Novels
John Gregory Betancourt
No ratings yet