Number
|
Severity
|
Text and Explanation
|
11001
|
10
|
Row count exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor
were exceeded.
|
11002
|
10
|
Estimated IO cost exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor
were reached.
|
11003
|
10
|
Actual IO cost exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor
were reached.
|
11004
|
10
|
Query batch running time exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor
were reached.
|
11005
|
10
|
Transaction's running time exceeded limit of %d.
Explanation: Indicates that resource limits defined with Resource Governor
were reached.
|
11006
|
17
|
Unable to set a kernel alarm; timerange manager is unable to run.
Explanation: Resource Governor could not set an alarm. Check alarm resources.
|
11007
|
17
|
Unable to set a kernel alarm; time limit alarm cannot be set.
Explanation: Resource Governor could not set an alarm. Check alarm resources.
|
11008
|
20
|
An attempt to get a free cache member from the Resource Governor's pool has failed. This is a system error -- contact a user with System Administrator (SA) role.
Explanation: Adaptive Server encountered an internal error affecting the
current process. Reconnect to Adaptive Server. Report the error
to your System Administrator so DBCC diagnostics can be run.
|
11009
|
16
|
Syntax error converting to DATETIME from BINARY/VARBINARY string.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by the message.
|
11010
|
10
|
Unknown limit type %d encountered -- limit will be ignored.
Explanation: Illegal limit type was defined with Resource Governor.
|
11011
|
10
|
Unknown limit scope 0x%x encountered -- limit will be ignored.
Explanation: Illegal limit range was defined with Resource Governor.
|
11012
|
10
|
Unknown limit enforcement time %d encountered -- limit will be ignored.
Explanation: There may be a potential problem with a database or database
object. Contact your System Administrator.
|
11013
|
16
|
Correlated columns are not allowed in the outer join clause of the subquery.
Explanation: Refer to the writeup for Error 301.
|
11014
|
16
|
Insufficient worker processes available. Query executed using current available worker processes. Inform the system administrator (SA) that the value of worker processes m ay be too low.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
11015
|
16
|
Insufficient worker processes available. To execute, wait until the system is less busy or set process_limit_action to quiet or warning, or increase the value of worker processes.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
11016
|
16
|
Cannot disable the role '%.*s' since you don't have it enabled.
Explanation: Adaptive Server could not perform the requested action. Contact
your System Administrator.
|
11017
|
20
|
DLL for the extended stored procedure '%1!' is not found. This is an internal error. Please contact Sybase Technical Support.
Explanation: Adaptive Server encountered an internal error affecting the
current process. Reconnect to Adaptive Server. Report the error
to your System Administrator so DBCC diagnostics can be run.
|
11018
|
10
|
XP Server must be up for ESP to execute.
Explanation: There may be a potential problem with a database or database
object. Contact your System Administrator.
|
11019
|
16
|
Parameters to extended stored procedure must be passed all by name or all by position.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11020
|
16
|
Pseudo-column SYB_IDENTITY is referenced from a stored procedure after the identity column has changed. Please drop/recreate the stored procedure.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11021
|
16
|
Function %s invoked with wrong number or type of argument(s).
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11022
|
16
|
Internal structure for cursor ’%.*s’ could not be located. This is a severe error. Please check for other errors preceding this one in the errorlog
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11023
|
16
|
An internal structure for the cursor could not be created. This is deemed to be a serious error.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11026
|
10
|
Warning: The statement on line %d uses the '%.*s' option with the view '%.*s'. Performance hint options are valid only for tables. This hint will be ignored.
Explanation: There may be a potential problem with a database or database
object. Contact your System Administrator.
|
11029
|
16
|
An index was found on table '%.*s' created via SELECT INTO. Parallel inserts into indexed tables is unsupported. Drop the table and retry the command.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11030
|
16
|
Execution of %S_MSG %.*s failed because the server was unable to change the owner context in database %S_DBID when upgrading the compiled object.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11031
|
16
|
Execution of %S_MSG %.*s failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11032
|
16
|
Execution of %S_MSG %.*s failed because the upgrade processing found incorrect source text in syscomments. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11033
|
16
|
Execution of %S_MSG %.*s failed because the upgrade processing did not find source text in syscomments. Please drop and recreate %.*s.
Explanation: ommand failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated
by message.
|
11034
|
16
|
Execution of %S_MSG %.*s failed because the hidden source text could not be decrypted during upgrade. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11035
|
16
|
Execution of %S_MSG %.*s failed because upgrade found no entry in syscomments for this object. Please drop and recreate %.*s.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11036
|
16
|
Your password will expire in %.*s days.
Explanation: This is an informational message or a message header. No action
is required.
|
11037
|
16
|
You specified an incorrect datatype for the variable containing the ’execute immediate’ command string.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11038
|
16
|
Your password will expire in %.*s days.
Explanation: This is an informational message or a message header. No action
is required.
|
11039
|
16
|
Another Execute Immediate statement cannot be executed inside an Execute Immediate statement.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11040
|
16
|
Adaptive Server cannot perform the requested action because column ’%.*s’ is not within the scope of the joined table expression. Check your command for missing or incorrect database objects, variable names, and/or input data.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11041
|
16
|
Adaptive Server cannot perform the requested action. Sybase outer joins and ANSI joins cannot be mixed in the same query. Rewrite the command as specified in the error message.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11042
|
18
|
Internal Error: Adaptive Server cannot find the ANSI outer join. The query tree may be corrupted. Please contact Sybase Technical Support.
Explanation: Command failed due to internal Adaptive Server problem. Perform
any diagnostic action indicated by the message. Report the error
to your System Administrator.
|
11044
|
16
|
Warning: Ignoring rule/check constraint ’%.*s’ specified on table ’%.*s’ because it refers to TEXT, IMAGE, or offrow Java datatype columns.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11045
|
16
|
%s command not allowed within the current running mode of the companion server
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11046
|
10
|
Warning: The results of the statement on line %d are join-order independent. Results may differ on pre-12.0 releases, where the query is potentially join-order dependent.
Explanation: There may be a potential problem with a database or database
object. Contact your System Administrator.
|
11047
|
17
|
Insufficient number (%d) of ’worker processes’ available at execution time to alter %d-way partitioned table ’%.*s’. Increase the number of ’worker processes’ or wait until the system is less busy.
Explanation: Command failed due to resource limitation. Modify the command
to fit available resources, retry when the resource is available,
or contact your System Administrator to address the resource problem.
|
11048
|
17
|
ALTER TABLE ’%.*s’ failed. Cursor ’%.*s’ is still open. Close this and any other open cursors on this table before this schema change operation.
Explanation: Command failed due to resource limitation. Modify the command
to fit available resources, retry when the resource is available,
or contact your System Administrator to address the resource problem.
|
11049
|
16
|
Cannot add column with duplicate name. A column with name ’%.*s’ already exists in this table.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11050
|
16
|
Adaptive Server cannot process this ALTER TABLE statement due to one or more preceding errors. If there are no preceding errors, please contact Sybase Technical Support.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11051
|
20
|
ALTER TABLE ’%.*s’ failed. Table is currently being used by one or more other tasks.
Explanation: Adaptive Server encountered an internal error affecting the
current process. Reconnect to Adaptive Server. Report the error
to your System Administrator so DBCC diagnostics can be run.
|
11052
|
16
|
The ’select into’ database option is not enabled for database ’%.*s’. ALTER TABLE with data copy cannot be done. Set the ’select into’ database option and re-run.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11053
|
16
|
Cannot alter table ’%.*s’ because the database option ’allow nulls by default’ has been changed by concurrent users.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11054
|
16
|
The table ’%.*s’ is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause.
Explanation: Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
|
11055
|
16
|
Query contains an illegal outer-join request.
Explanation: Refer to the writeup for Error 301.
|
11056
|
16
|
Exceeded tempdb space limit of %ld pages.
Explanation: Rewrite the query or contact your System Administrator to
address the resource limitation.
|
11057
|
16
|
Execute cursor ’%.*s’ may not be declared on a SQLJ procedure.
Explanation: Command failed due to invalid or illegal request.
|
11058
|
16
|
Statement contains ’%d’ columns/expessions in the target list. This exceeds the maximum limit of ’%d’.
Explanation: Rewrite the query or split into multiple queries to conform
to the server limits.
|
11059
|
16
|
Too many tables in the query. The maximum allowable is %d.
Explanation: Rewrite the query or split into multiple queries to conform
to the server limits.
|
11060
|
16
|
This statement has exceeded the maximum number of recompilations (%d). This indicates an internal error. Please note the error prior to this one and contact Sybase Technical Support.
Explanation: Normally, a given statement in a stored procedure is recompiled
only once, but due to lack of resources or other factors, it might
need to be recompiled more than one time. This error is raised if
the procedure is recompiled more than the specified number of times,
and is an indication of an internal error.
|