Number
|
Severity
|
Text and Explanation
|
7301
|
15
|
FOR UPDATE has been incorrectly specified for a READ ONLY cursor.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7302
|
15
|
The row number specification for a SET CURSOR ROWS statement must be an integer value greater than 0.The given value is `%d'.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7303
|
15
|
FOR BROWSE can not be used in the declaration of a cursor.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7304
|
15
|
FOR READ ONLY can not be used in a SELECT which is not part of the declaration of a cursor or which is not inside a stored procedure.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7305
|
15
|
FOR UPDATE can not be used in a SELECT which is not part of the declaration of a cursor or which is not inside a stored procedure.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7307
|
15
|
COMPUTE clause can not be used in the declaration of a cursor.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7308
|
15
|
SELECT-INTO can not be used in the declaration of a cursor.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7309
|
10
|
SQL statement on line number %d contains %S_MSG. The error is caused due to the use of %s.
Explanation: Check command syntax and semantics.
|
7310
|
10
|
SQL statement on line number %d contains %S_MSG. The error is caused due to the use of non-ANSI option: %S_MSG.
Explanation: Check command syntax and semantics.
|
7311
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Sybase declared global/local variables.
Explanation: Check command syntax and semantics.
|
7312
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Sybase built-in function: %.*s.
Explanation: Check command syntax and semantics.
|
7313
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of non-standard control flow: %s.
Explanation: Check command syntax and semantics.
|
7314
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of non-standard transaction key word(s): %S_MSG.
Explanation: Check command syntax and semantics.
|
7315
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI conversion function(s).
Explanation: Check command syntax and semantics.
|
7316
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of database prefix.
Explanation: Check command syntax and semantics.
|
7317
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of %S_MSG %S_MSG.
Explanation: Check command syntax and semantics.
|
7318
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI drop object functionality: %S_MSG.
Explanation: Check command syntax and semantics.
|
7319
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI operator: %S_MSG.
Explanation: Check command syntax and semantics.
|
7320
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI pattern matching character(s).
Explanation: Check command syntax and semantics.
|
7321
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of column name(s) in a select list with aggregates but column name(s) not in group by list.
Explanation: Check command syntax and semantics.
|
7322
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of set operations in an insert select: %S_MSG.
Explanation: Check command syntax and semantics.
|
7323
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of column headings.
Explanation: Check command syntax and semantics.
|
7324
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of compute statement.
Explanation: Check command syntax and semantics.
|
7325
|
16
|
Nulls not allowed in a primary key column.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7326
|
10
|
Line number %d contains %S_MSG. The error is caused due to the use of Non-ANSI escaping of `[` or `]' in a LIKE ESCAPE.
Explanation: Check command syntax and semantics.
|
7327
|
10
|
Length or precision specification %d is not within the range of 1 to %d.
Explanation: Check command syntax and semantics.
|
7328
|
10
|
Specified scale %d is not within the range of 0 to 255.
Explanation: Check command syntax and semantics.
|
7329
|
15
|
There are too many parameters given with function `%.*s'. The maximum number of parameters allowed is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7330
|
15
|
Within %s, you are not allowed to specify the database name prefix for the new object name in %s. All new objects must be created in the current database.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7331
|
15
|
Within %s, you can't create an object owned by another user. The specified object owner is `%.*s', but the schema authorization id is `%.*s'.
Explanation: Command failed due to invalid or illegal request. Adaptive
Server cannot perform the requested action.
|
7332
|
15
|
%S_MSG is allowed only in %S_MSG
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7333
|
15
|
%s does not allow specifying the user name as a prefix to the object name.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7334
|
16
|
Subqueries are not allowed in a RAISERROR.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7335
|
15
|
A SELECT statement that assigns a value to a variable must not be combined with a COMPUTE clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7336
|
10
|
Line number %d contains non-ANSI identifier. Length of identifier `%.*s' is greater than 18.
Explanation: Check command syntax and semantics.
|
7337
|
10
|
FIPS WARNING: Truncation when inserting long char/varchar/unichar/univarchar into shorter char/varchar/unichar/univarchar.
Explanation: Check command syntax and semantics.
|
7338
|
10
|
FIPS WARNING: Union of exact numeric with different precision or scale.
Explanation: Check command syntax and semantics.
|
7339
|
10
|
FIPS WARNING: Union of chars or of literals with different lengths.
Explanation: Check command syntax and semantics.
|
7340
|
10
|
FIPS WARNING: Union of chars with literal.
Explanation: Check command syntax and semantics.
|
7341
|
10
|
FIPS WARNING: Inserted approximate numeric into exact numeric.
Explanation: Check command syntax and semantics.
|
7342
|
15
|
Keyword SHARED can not be used in a SELECT statement which is not part of the declaration of a cursor.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7343
|
15
|
The value (%d) given to the %S_MSG is not within the allowed range. The allowed range is between %d and %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7344
|
16
|
DECLARE CURSOR must be the only statement in a query batch.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7345
|
16
|
SELECT is not allowed in a dynamic EXECUTE IMMEDIATE statement.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7346
|
16
|
Invalid arguments for RAISERROR extended error data.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7347
|
16
|
The IDENTITY function should be used only when the SELECT statement has an INTO clause.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7348
|
16
|
Select expression results in more than one column having same name. Column name `%.*s' is specified more than once
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7349
|
16
|
FIPS WARNING: Due to usage of the name of an expression in the ORDER BY clause which has a correlation name in the select list
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7350
|
16
|
FIPS_WARNING: Use of implicit or explicit ALL in COUNT aggregate function. Only COUNT(*) or COUNT( DISTINCT <expression> ) is allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7351
|
16
|
Local or global variables not allowed in view definition
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7352
|
16
|
The SET option with ARITH_OVERFLOW is allowed only in SET ARITHABORT or SET ARITHIGNORE.
Explanation: See `set arithabort/arithignore' command
restrictions.
|
7353
|
16
|
The SET option with NUMERIC_TRUNCATION is allowed only in SET ARITHABORT.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7354
|
16
|
The SET can have option restrictions only when there is one option in the command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7355
|
16
|
Table (or view) `%.*s' created by SELECT INTO or CREATE VIEW results in a column with no name. Please specify a column name for computed columns.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7356
|
16
|
Aggregates or subqueries are not allowed in check constraints.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7357
|
15
|
Label options (CURREAD, CURWRITE) cannot be used with non-label SET options in a single SET commmand.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7358
|
16
|
Invalid type argument specified for the %s builtin function. Argument must either be SENSITIVITY or SENSITIVITY_BOUNDARY.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7359
|
16
|
SYB_IDENTITY is not allowed in READ or WRITE TEXTS commands.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7360
|
16
|
Explicit updates/inserts cannot be done on sensitivity or information columns.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7361
|
16
|
FIPS WARNING: GROUP BY clause specified when all the items in select list are aggregate functions or none of the items in select list are aggregate functions.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7362
|
16
|
FIPS WARNING: Select list contains aggregate function(s) but GROUP BY clause not specified.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7363
|
16
|
You can not have variable assignments in a SELECT statement with the UNION operation.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7364
|
16
|
Tables `%.*s' and `%.*s' have same exposed names. Use correlation names to distinguish them.
Explanation: Refer to the writeup for this error.
|
7365
|
16
|
A column in the FOR UPDATE OF list can only be qualified by a table or correlation name. Column `%.*s' is qualified by an table owner and/or database name.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7366
|
16
|
A column in the FOR UPDATE OF list can only be qualified by an exposed table or correlation name. `%.*s' is not an exposed name in the select statement.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7367
|
16
|
Expected row size '%d' is not a valid value; expected row size must be greater th an 9 or can be either 0 or 1.
Explanation: Check command parameters.
|
7368
|
16
|
Can not create column by name `SYB_IDENTITY_COL'. This name has special meaning when `auto_identity' option is ON.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7369
|
15
|
Procedure Grouping is not allowed.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7370
|
16
|
Specified precision %d is more than the maximum precision %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7371
|
16
|
Specified scale %d is more than the specified precision %d.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7372
|
15
|
Cursor FOR UPDATE cannot be specified at isolation level 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7373
|
15
|
Browse mode cannot be specified at isolation level 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7374
|
15
|
Invalid isolation level specified.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7375
|
15
|
SELECT INTO cannot be specified with isolation level clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7376
|
15
|
Select in a CREATE VIEW cannot be specified with isolation level clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7377
|
15
|
SELECT INSERT cannot be specified with isolation level clause.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7378
|
15
|
HOLDLOCK/NOHOLDLOCK/SHARED/READPAST conflicts with AT ISOLATION LEVEL 0.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7379
|
14
|
Permission denied. You must have the `Replication' role to set %.*s ON or OFF. Please contact a user with System Security Officer (SSO) role for help.
Explanation: Command failed. Certain SET commands require replication
role.
|
7380
|
10
|
WARNING: Line %d. Invalid value for `%S_MSG' specified. This value will be ignored, default value will be used instead.
Explanation: When you specify a prefetch size on select, update and delete
statements, but the value you specified is not available, the ASE
Buffer Manager raises this warning message. Processing continues
with the prefetch size that the optimizer determines to be the "best"
value.
|
7381
|
10
|
prefetch size
Explanation: This is an informational message. Unless otherwise specified,
no action is required. Contact your System Administrator about any
warning issued in the message.
|
7382
|
16
|
Subqueries are not allowed in an ORDER BY clause.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7383
|
16
|
Subqueries are not allowed in a GROUP BY clause.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7384
|
16
|
Subqueries are not allowed in a COMPUTE clause.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7385
|
16
|
The number of subqueries in the query exceeds the maximum allowed (%d).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7386
|
10
|
Set dup_in_subquery is no longer supported. To get similar performance and semantics, rewrite the subquery as a join.
Explanation: The set_dup_in_subquery command
existed in pre-11 server versions as a temporary way to avoid changes
needed for ANSI-compliant duplicate handling. It is not supported
as of version 11.0, which contains better subquery processing features. Rewrite
the subquery as a join.
|
7387
|
15
|
The maximum number of parameters in a dynamic SQL statement is %d.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7388
|
16
|
An aggregate of an aggregate produces a scalar value. Any further nesting of aggregates has no effect. Remove the aggregates beyond level two.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7389
|
16
|
A HAVING clause with aggregates of different levels is not allowed.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
7391
|
15
|
The table count specification for a SET TABLE COUNT statement must be an integer value greater than 0. The given value is `%d'.
Explanation: Command failed. Check syntax and semantics. Rewrite the command
to satisfy the condition indicated in the message.
|
7392
|
15
|
Procedure Grouping is not allowed. Please contact a user with System Security Officer (SSO) role for help.
Explanation: Command failed. Check syntax and semantics.
|
7393
|
16
|
The value of forced parallel degree cannot be negative.
Explanation: Check command parameters.
|
7394
|
15
|
Duplicate specification of '%S_MSG' clauses for one table is not allowed.
Explanation: Check command syntax.
|
7395
|
10
|
forced index
Explanation: This is informational text.
|
7396
|
10
|
forced parallel
Explanation: This is informational text.
|
7397
|
10
|
forced lru/mru
Explanation: This is informational text.
|
7398
|
10
|
forced prefetch
Explanation: This is informational text.
|
7399
|
15
|
Reserved page gap '%d' is not a valid value; reserved page gap must be between 0 and 255
Explanation: Command error. Check parameters.
|