Number
|
Severity
|
Text and Explanation
|
21
|
10
|
WARNING - Fatal Error %ld occurred at %S_DATE. Please note the error and time, and contact a user with System Administrator (SA) authorization.
Explanation: This is an informational message. Unless otherwise specified,
no action is required. Contact your System Administrator about any
warning issued in the message.
|
101
|
15
|
Line %d: SQL syntax error.
Explanation: Command failed. Check syntax and semantics.
|
102
|
15
|
Incorrect syntax near `%.*s'.
Explanation: Refer to the writeup for Error 102.
|
103
|
15
|
The %S_MSG that starts with `%.*s' is too long. Maximum length is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
104
|
15
|
Order-by items must appear in the select-list if the statement contains set operators.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
105
|
15
|
Unclosed quote before the character string `%.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
106
|
16
|
Too many table names in the query. The maximum allowable is %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
107
|
15
|
The column prefix `%.*s' does not match with a table name or alias name used in the query. Either the table is not specified in the FROM clause or it has a correlation name which must be used instead.
Explanation: Refer to the writeup for Error 107.
|
108
|
15
|
The order-by position number `%ld' is out of range of the number of items in the select-list.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
109
|
15
|
There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
110
|
15
|
There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
111
|
15
|
%s must be the first command in a query batch.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
112
|
15
|
Variables are not allowed in %s statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
113
|
15
|
Missing end comment mark '*/'.
Explanation: Command failed. Check syntax and semantics.
|
114
|
15
|
`%.*s' is not a recognized DUMP DATABASE/TRANSACTION truncation option.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
115
|
15
|
The offset `%d' given in a CONTROLROW command does not correspond to the beginning of a statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
116
|
15
|
The symbol `*' can only be used for a subquery select list when the subquery is introduced with EXISTS or NOT EXISTS.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
117
|
15
|
The %S_MSG name `%.*s' contains more than the maximum number of prefixes. The maximum is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
118
|
15
|
`%s' option name length plus value string length must total less than %d characters.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
119
|
15
|
Must pass parameter number %d and subsequent parameters as `@name = value'. Once the form `@name = value' has been used, all subsequent parameters must be passed in the form `@name = value'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
120
|
15
|
The SELECT list for the INSERT statement contains fewer items than the INSERT list. The number of SELECT values must match the number of INSERT columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
121
|
15
|
The SELECT list for the INSERT statement contains more items than the INSERT list. The number of SELECT values must match the number of INSERT columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
122
|
15
|
The debug option `%d' is larger than the maximum allowed. The highest option available is %d.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
123
|
15
|
Must attach a value to the binary prefix `0x'; zero-length binary value is not allowed.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
124
|
15
|
CREATE PROCEDURE contains no statements.
Explanation: Command failed. The CREATE PROCEDURE command must contain at
least one SQL statement.
|
126
|
15
|
Cannot nest CREATE PROCEDURE statements.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
127
|
15
|
This CREATE may only contain 1 statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
128
|
15
|
The name `%.*s' is illegal in this context. Only constants, constant expressions, or variables allowed here. Column names are illegal.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
129
|
15
|
Fillfactor `%d' is not a valid percentage; fillfactor must be between 1 and 100.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
130
|
15
|
The comparison operator `= ALL' is not currently supported.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
131
|
15
|
The size (%d) given to the %S_MSG `%.*s' exceeds the maximum. The largest size allowed is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
132
|
15
|
The label `%.*s': has already been declared. Label names must be unique within a query batch or stored procedure
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
133
|
15
|
A GOTO statment references the label `%.*s' but the label has not been declared.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
134
|
15
|
The variable name `%.*s' has already been declared. Variable names must be unique within a query batch or stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
135
|
15
|
Cannot use a BREAK statement outside the scope of a WHILE statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
136
|
15
|
Cannot use a CONTINUE statement outside the scope of a WHILE statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
137
|
15
|
Must declare variable `%.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
138
|
15
|
Illegal correlation clause in a subquery.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action. (This error is not raised
in Release 11.0 and higher.)
|
139
|
15
|
Cannot assign a default value to a local variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
140
|
15
|
Can only use IF UPDATE within a CREATE TRIGGER.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
141
|
15
|
A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
143
|
15
|
A compute-by item was not found in the order-by list. All expressions in the compute-by list must also be present in the order-by list
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
144
|
15
|
Cannot use an aggregate in an expression used for the by-list of a GROUP BY clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
145
|
15
|
A subquery with no aggregate functions may only contain expressions in its GROUP BY clause that are in the select-list.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
146
|
15
|
Cannot perform an aggregate function on a column from a table not declared in the same subquery.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
147
|
15
|
An aggregate function may not appear in a WHERE clause unless it is in a subquery that is in a HAVING clause, and the column being aggregated is in a table named in a FROM clause outside of the subquery.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
148
|
15
|
Incorrect time syntax in time string `%.*s' used with WAITFOR.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
149
|
15
|
Time value `%.*s' used with WAITFOR is not a legal value. Check date/time syntax.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
150
|
15
|
Both terms of an outer join must contain columns.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
151
|
15
|
`%.*s' is an invalid money value.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
152
|
15
|
Subqueries that use DISTINCT with a GROUP BY clause are not currently supported.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action. (This error is not raised
in Release 11.0 and higher.)
|
153
|
16
|
Variables/Parameters are not allowed in the ORDER BY clause.
Explanation: Adaptive Server could not perform the requested action. Rewrite
the command to conform to the requirement specified in the error
message.
|
154
|
15
|
%S_MSG is not allowed in %S_MSG.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
155
|
15
|
`%.*s' is not a recognized %s option.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
156
|
15
|
Incorrect syntax near the keyword `%.*s'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
158
|
15
|
Too many ORDER BY expressions. The maximum is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
159
|
15
|
For DROP INDEX, must give both the table and the index name, in the form tablename.indexname
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
160
|
15
|
Rule does not contain a variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
161
|
15
|
Rule contains more than one variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
162
|
15
|
The select list item identified by the order by number `%ld' is a `*', rather than a column name. When ordering by column number, a column name must appear in the select list position that corresponds to the order by number.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
163
|
15
|
The COMPUTE BY list does not match the ORDER BY list.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
164
|
15
|
GROUP BY expressions must refer to column names.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
165
|
16
|
Privilege %s may not be GRANTed or REVOKEd.
Explanation: Adaptive Server could not perform the requested action. The
command violates a permission or privilege restriction. Check the
command and working database context.
|
166
|
15
|
%s does not allow specifying the database name as a prefix to the object name.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
167
|
16
|
May not create a trigger on a temporary object.
Explanation: Adaptive Server could not perform the requested action. Check
your command for missing or incorrect database objects, variable
names, and/or input data.
|
168
|
15
|
The %S_MSG `%.*s' is out of the range of machine representation (%d bytes).
Explanation: Command failed. Check syntax and semantics.
|
169
|
15
|
Expression `%d' and `%d' in the ORDER BY list are same. Expressions in the ORDER BY list must be unique.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
171
|
15
|
Can't use SELECT INTO in Browse Mode.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
172
|
15
|
Can't use HOLDLOCK in Browse Mode
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
173
|
15
|
The definition for column `%.*s' must include a datatype.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
174
|
15
|
The function `%.*s' requires %d arguments.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
175
|
15
|
Functions may only be nested to level %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
176
|
15
|
Function `%.*s' is not yet implemented.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
177
|
15
|
%s cannot create a temporary object (with `#' as the first character name.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
178
|
15
|
A RETURN statement with a return status may only be used in a SQL stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
179
|
15
|
Can't use the OUTPUT option when passing a constant to a stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
180
|
15
|
There are too many parameters in this CREATE PROCEDURE statement. The maximum number is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
181
|
15
|
Can't use the OUTPUT option in a DECLARE statement.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
182
|
15
|
Table and column names must be supplied for the READTEXT or WRITETEXT utility.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
183
|
15
|
The scale (%d) for column `%.*s' must be within the range %d to %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
184
|
15
|
Invalid money datatype specification for column `%.*s'. Only money(19, 4) is allowed for non-external tables.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
185
|
15
|
Data stream is invalid for WRITETEXT command in bulk form.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
186
|
15
|
Data stream missing from WRITETEXT command.
Explanation: Command failed. Check the syntax of the WRITETEXT command.
|
187
|
15
|
Odd number of bytes in IMAGE data.
Explanation: While inserting text/image data, an upper limit
on the send may have been reached. Check the data sent and consider
using ct_command or other alternative.
|
188
|
15
|
Can't specify a log-device in a CREATE DATABASE statement without also specifying at least one non-log-device.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
189
|
15
|
Function `%.*s' requires %d to %d arguments.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
190
|
15
|
Can not update the global variable `%.*s'.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
191
|
15
|
Some part of your SQL statement is nested too deeply. Please re-write the query or break it up into smaller queries.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
192
|
15
|
Can't create a view inside a stored procedure.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
193
|
15
|
The object or column name starting with `%.*s' is too long. The maximum length is %d characters.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
195
|
15
|
`%.*s' is not a recognized %S_MSG.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
196
|
15
|
SELECT INTO must be the first query in a SQL statement containing set operators.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
197
|
15
|
WITH CHECK OPTION is not allowed in the definition of a union view.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
198
|
15
|
Browse mode is invalid for statements containing set operators.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
199
|
15
|
An INSERT statement may not contain a SELECT statement that assigns values to a variable.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|