Server Error Messages 300 - 399


 Query contains an illegal outer-join request.
 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.
 The table `%.*s' is outer-joined with itself.
 The column `%.*s' (user type:%.*s) is joined with `%.*s' (user type:%.*s).  The user types are not compatible:  underlying types must be identical in order to join.
 TEXT and IMAGE datatypes may not be used in a WHERE clause, except with the LIKE expression.
 Index `%.*s' specified as optimizer hint in the FROM clause of table `%.*s' does not exist.  Optimizer will choose another index instead.
 Table not open for range table entry `%d', objid `%ld', dbid `%d'.
 Wrong sdes for range table entry `%d'. Expected object `%ld', dbid `%d', got object `%ld', dbid `%d'.
 Index id %d on table id %d cannot be used in the optimization of a query as it is SUSPECT. Please have the SA run DBCC REINDEX on the specified table.
 The optimizer could not find a unique index which it could use to scan table `%.*s' for cursor `%.*s'.
 Index id %d on table `%.*s' is explicitly specified in cursor `%.*s' declared for update. This index is either not unique or its key includes a column in the for update of list. This cursor my be closed on an update or a delete.
 The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table `%.*s'.
WARNING: A non-unique clustered index has been forced on an isolation level 0 scan on table ’%.*s’. If the scan must restart, the scan will be repositioned at the beginning of the duplicate key group. Thus, it is possible that this can infinitely loop. 
Internal error - The SQL Server was unable to find a join order to run this query.  Please inform technical su pport.
 Cannot compile the query because the space required for the search arguments (%d bytes) exceeds the maximum amount of memory that can be granted.  Try reducing the number of search arguments.
 A subquery in this query is correlated to an inner table of an outerjoin. This is not allowed in TSQL semantics.
sysstatistics catalog was read and an inconsistency was found, please run update statistics and contact Sybase Technical Support
Statistics cannot be read for table '%.*s', column '%.*s' due to previous errors
Index id %d on table id %d cannot be used in the optimization of a query as it is SUSPECT. Please drop and re- create the index on the specified table.
Internal statistics calculation inconsistency. Please contact Sybase technical support
Internal error: systabstats statistics could not be read, please contact Sybase Technical Support.
WARNING: Edited statistics are overwritten. Table: '%.*s' (objectid %ld), column: '%.*s'.
Invalid simulated value (%ld) ignored for %S_MSG '%.*s'. Actual value (%ld) used instead.
Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, please contact Sybase Technical Support.
ALTER TABLE ’%.*s’ failed. The table is %d-way partitioned, and a %d-way parallel plan was generated due to lack of parallel resources. Increase the value of ’max parallel degree’ and ’number of worker processes’ to at least %d, and try again.

Number	Severity	Text and Explanation
301	16	Query contains an illegal outer-join request. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
303	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:* Semantic error in query. Inner join and outer join were mixed.
304	16	The table `%.s' is outer-joined with itself. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
305	16	The column `%.s' (user type:%.s) is joined with `%.s' (user type:%.s). The user types are not compatible: underlying types must be identical in order to join. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
306	16	TEXT and IMAGE datatypes may not be used in a WHERE clause, except with the LIKE expression. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
307	10	Index `%.s' specified as optimizer hint in the FROM clause of table `%.s' does not exist. Optimizer will choose another index instead. Explanation: This is an informational message but may require follow-up action. Contact your System Administrator.
308	20	Table not open for range table entry `%d', objid `%ld', dbid `%d'. Explanation: Refer to the writeup for Error 308.
309	20	Wrong sdes for range table entry `%d'. Expected object `%ld', dbid `%d', got object `%ld', dbid `%d'. Explanation: Incorrect sdes was obtained due to an Adaptive Server problem. Contact Sybase Technical Support to upgrade to a version in which the problem is resolved.
310	10	Index id %d on table id %d cannot be used in the optimization of a query as it is SUSPECT. Please have the SA run DBCC REINDEX on the specified table. Explanation: There may be a potential problem with a database or database object. Contact your System Administrator.
311	16	The optimizer could not find a unique index which it could use to scan table `%.s' for cursor `%.s'. Explanation: Refer to the writeup for Error 311.
312	16	Index id %d on table `%.s' is explicitly specified in cursor `%.s' declared for update. This index is either not unique or its key includes a column in the for update of list. This cursor my be closed on an update or a delete. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
313	16	The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table `%.s'. Explanation:* Refer to the writeup for Error 313.
314	16	WARNING: A non-unique clustered index has been forced on an isolation level 0 scan on table ’%.s’. If the scan must restart, the scan will be repositioned at the beginning of the duplicate key group. Thus, it is possible that this can infinitely loop. Explanation:* Refer to the writeup for Error 314.
315	16	Internal error - The SQL Server was unable to find a join order to run this query. Please inform technical su pport. Explanation: Internal Adaptive Server error. A table may be circularly dependent upon itself. Contact Sybase Technical Support.
316	17	Cannot compile the query because the space required for the search arguments (%d bytes) exceeds the maximum amount of memory that can be granted. Try reducing the number of search arguments. Explanation: Reduce number of sargs. Try breaking up the query into multiple queries.
317	16	A subquery in this query is correlated to an inner table of an outerjoin. This is not allowed in TSQL semantics. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
318	18	sysstatistics catalog was read and an inconsistency was found, please run update statistics and contact Sybase Technical Support Explanation: There was an internal Adaptive Server problem. Perform the diagnostic action indicated in the message. (Version 11.9.2 and higher.)
319	18	Statistics cannot be read for table '%.s', column '%.s' due to previous errors Explanation: There was an internal Adaptive Server problem. (Version 11.9.2 and higher.)
320	10	Index id %d on table id %d cannot be used in the optimization of a query as it is SUSPECT. Please drop and re- create the index on the specified table. Explanation: Use sp_helpindex to obtain index information, then drop and recreate the index. (Version 11.9.2 and higher.)
321	18	Internal statistics calculation inconsistency. Please contact Sybase technical support Explanation: (Version 11.9.2 and higher.)
322	18	Internal error: systabstats statistics could not be read, please contact Sybase Technical Support. Explanation: (Version 11.9.2 and higher.)
323	10	WARNING: Edited statistics are overwritten. Table: '%.s' (objectid %ld), column: '%.s'. Explanation: (Version 11.9.2 and higher.)
324	10	Invalid simulated value (%ld) ignored for %S_MSG '%.s'. Actual value (%ld) used instead. Explanation:* (Version 11.9.2 and higher.)
325	18	Adaptive Server finds no legal query plan for this statement. If an Abstract Plan is forcing the query plan, check its correspondence to the query. If not, 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.
326	16	ALTER TABLE ’%.s’ failed. The table is %d-way partitioned, and a %d-way parallel plan was generated due to lack of parallel resources. Increase the value of ’max parallel degree’ and ’number of worker processes’ to at least %d, and try again. Explanation:* Adaptive Server could not perform the requested action. Modify your command to meet the Adaptive Server requirement for the objects or variables shown in the error message.