Server Error Messages 9900 - 9999


 Permission denied.  Only a user with curread set to @@data_high can perform the DBCC command `%.*s'.
 Only users with SA and SSO roles can run this dbcc dbrepair command for the database %S_DBID.
 Only users with SA and SSO roles having their curread dominating the maxhold of the database can run this dbcc dbrepair command for the database `%S_DBID'.
 Total (# of text chains = %ld  text pages = %ld) in this table.
 Processed %ld tables. Found %ld good text entries, %ld bad text entries in this database
 Unrecognized option.  Available options: dbcc engine(net, show, engine#), dbcc engine(net, showall), dbcc engine(net, netengine)
 Syspartitions system table does not exist in database id %S_DBID.
 The total number of data pages in partition %d is %d.
 Object %ld has one row in Syspartitions
 Object %ld has partition %ld instead of %ld in Syspartitions
 MAX_ROWS_PER_PAGE value of %d is invalid. It must be between 0 and %d.
 Amount of memory transferred (%dk) is less than the amount of memory requested (%dk).
 I/O size must be a power of 2.
 I/O size must be a power of 2.
 Can't find database id for %.*s. Check that this database exists and re-run the command.
 Encountered error using dbid %d.
 Can't find object id for %.*s.  Check the object name and re-run this command.
 Index id %d not found for object id %d, dbid %d.
 Index %.*s not found for object id %d dbid %d.
 The first page %ld in sysindexes for table `%.*s' does not match with first page %ld for the table's first partition in Syspartitions.
 The first page %ld in syspartitions for partition %ld of table `%.*s' has previous page # %ld in its page header. The previous page # should be NULL.
 The last page %ld in syspartitions for partition %ld of table `%.*s' has next page # %ld in its page header. The next page # should be NULL.
 This option has been converted to the configuration parameter `%s'. Use `sp_configure' to set it.
 This option requries a table name as the third parameter. Use `sp_configure `%s'' to set the option serverwide.
 This option has been disabled. Use `sp_poolconfig' instead.
 Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run DBCC TEXTALLOC command.
 The %S_MSG page (%ld) found in the page chain does not match with the %S_MSG page (%ld) found in the slice control page (%ld), for table `%.*s', on slice %ld. The table may be corrupt.
The %S_MSG page (%d) found in the page chain doesn’t match with the %S_MSG page (%d) stored in the Sysindexes for table ’%.*s’. The table may be corrupt.
 The option max_rows_per_page cannot be set for a text/image index (%d) on table `%.*s'.
Invalid index ID %d. Values for index ID must be between 0 and %d.  
SQL Server will not refresh index descriptor as the object descriptor for objid % ld in dbid %d is not installed in cache. 
Error while trying to refresh sysindexes row within index descriptor with indid % d objid %ld and dbid %d. 
Table with ID %d not found; check sysobjects.
DBCC %s command is not supported anymore.  
The source text of object named '%s' with object id '%d' has already been hidden.
The source text of object named '%s' with object id '%d' is missing and it is not hidden.
Failed to hide the source text.
The hidden text of object named '%s' with object id '%d' does not exist.
Too many errors have been detected on device '%.*s' (physical device: %.*s). Page  and object checking on that device has been discontinued. (The CHECKSTORAGE operation stops when more than 25%% of the checks are abandoned.) 
Too many errors have been detected on table '%.*s' index '%.*s'. Checking for that object will be discontinued. (The CHECKSTORAGE operation stops when more than 25 %% of the checks are abandoned.) 
An attempt to reserve a %dK buffer failed. Increase the size of the %dK buffer pool in the buffer cache ’%.*s’.
An attempt to allocate memory failed due to insufficient SQL Server memory.  
The CHECKSTORAGE operation failed to cache a scan workspace row because of a cache overflow. This is an internal error. Please contact Sybase Technical Support. 
An I/O in a workspace failed, page %d in database %d. Check your hardware for problems that could cause I/O failures. 
Workspace '%.*s' is incorrectly allocated. Use sp_dbcc_createws to create a new workspace. 
Workspace '%.*s' is too fragmented to be used. Use sp_dbcc_createws and sp_dbcc_updateconfig to correct the problem. 
Workspace '%.*s' is too small to permit the CHECKSTORAGE operation to proceed. Use sp_dbcc_alterws and sp_dbcc_updateconfig to correct the problem. 
SQL Server failed to synchronize the activity of a worker process with the coordinating process. This is an internal error. Please contact Sybase Technical Support. 
Storage checks for '%.*s' are complete. DBCC is now recording the results in the dbccdb database. 
A worker process could not access database '%.*s'. This is an internal error. Please contact Sybase Technical support. 
A worker process failed to complete its assigned work during the scan phase. The results of the CHECKSTORAGE operation will be incomplete. 
A worker process failed to complete its assigned work during the page chain check phase. The results of the CHECKSTORAGE operation will be incomplete. 
A worker process failed to complete its assigned work during the OAM check phase. The results of the CHECKSTORAGE operation will be incomplete. 
The CHECKSTORAGE operation has aborted. 
A non-recoverable error has occurred in the CHECKSTORAGE operation. The operation has been aborted. 
DBCC failed to connect to the requested number of worker processes. The number of workers configured is insufficient, or the number of workers exceeds 128. Use sp_dbcc_updateconfig to reduce 'max worker processes' for this database. 
Access to table '%.*s' index '%.*s' in the target database failed.  
An error occurred while attempting to insert a row into the dbcc_faults table or the dbcc_fault_params table.  
Database '%.*s' was not found. Use sp_helpdb to list the available databases.  
The entries in dbcc_config for database '%.*s' are either missing or invalid. Use  sp_dbcc_evaluatedb to determine appropriate values for the entries and sp_dbcc_updateconfig to set them. 
DBCC could not access the scan workspace '%.*s'. Verify that the workspace exists . 
DBCC could not access the text workspace '%.*s'. Verify that the workspace exists . 
DBCC could not evaluate SQL Server's device configuration. Check the contents of the dbcc_dev_info table. 
The operation sequence number update for database '%.*s' in the dbcc_config table  failed. 
DBCC failed to either insert or update the row in the dbcc_operation_log table for this check of database '%.*s'. 
DBCC failed to schedule work for the worker processes. This is an internal error. Please contact Sybase Technical Support. 
An error occurred while inserting the results into the dbcc_counters table.  
An error occurred while inserting the results into the dbcc_operation_results table. 
DBCC CHECKSTORAGE for database '%.*s' sequence %d completed at %s. %d faults and %d suspect conditions were located. %d checks were aborted. You should investigate the recorded faults, and plan a course of action that will correct them. 
DBCC CHECKSTORAGE for database '%.*s' encountered an error. Some results may not be available. Correct the problems reported and reexecute the CHECKSTORAGE command. 
There is an inconsistency between the dbcc_dev_info table and the sysdevices table. Use DBCC CHECKDEVINFO to regenerate the dbcc_dev_info table. 
The cache '%.*s' specified in the dbcc_config table does not exist.  
The %dK buffer pool in the configured cache is too small. %dK is the minimum size . 
Too many worker processes (%d) are configured for the available %dK buffer pool. This buffer pool can only support %d workers. 
%d text column values were not checked because the text workspace was too small. Use sp_dbcc_alterws to increase its size by %dK. 
Correct syntax is:
dbcc createws({dbccdb|dbccalt}, segment name, workspace name, {scan|text}, size) dbcc alterws({dbccdb|dbccalt}, workspace name, {scan|text}, size)
The minimum size for a DBCC workspace is %d pages.  
DBCC failed to create the workspace '%.*s'.  
DBCC could not expand the size of workspace '%.*s' in database '%.*s' to %d pages .  
DBCC could not truncate the size of workspace '%.*s' in database '%.*s' by %d pages.  
Suspect conditions are to be treated as faults if the same suspect condition persists in subsequent CHECKSTORAGE operations, or if they are also detected by other DBCC functions.  
DOL datapage %d of object %d does not have extended page header bits set correctly. 
NCFS value %ld in DOL datapage %ld is larger than available space %ld in the page  
Number of deleted rows %ld in page header of DOL datapage %ld is incorrect. This value cannot be negative. 
Insert free space value %ld in page header of DOL datapage %ld is greater than sum of cfs and ncfs (%ld) in the page 
Orphan row at offset %ld in page %ld of object %ld must be marked committed delete and is not 
Actual #rows %ld in DOL datapage %ld and count of #rows - nextrno - %ld in page header do not match 
There is a mismatch between value of ncfs counter %ld in page header of DOL datapage %ld and the actual amount of garbage %ld in the page 
There is a mismatch between count of #deleted rows %ld in page header of DOL data page %ld and the actual # deleted rows %ld in the page 
There is a mismatch between value of insert free space %ld in page header of DOL datapage %ld and actual value of insert free space %ld computed from the page with expected row size as %ld  
Keys of index id %d for table '%.*s' in %S_MSG not in proper order. Drop and recreate the index. (index page %ld) 
Root page %ld in index id %ld of object id %ld does not have BT_ROOT bit set  
Index page %ld has object id %ld which is different from object id %ld  
Rids not in ascending order in index page %ld for row %ld at offset %ld (indid %l d, object %ld). Drop and recreate the index. 

Number	Severity	Text and Explanation
9901	14	Permission denied. Only a user with curread set to @@data_high can perform the DBCC command `%.s'. Explanation:* You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
9902	14	Only users with SA and SSO roles can run this dbcc dbrepair command for the database %S_DBID. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
9903	14	Only users with SA and SSO roles having their curread dominating the maxhold of the database can run this dbcc dbrepair command for the database `%S_DBID'. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
9904	10	Total (# of text chains = %ld text pages = %ld) in this table. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
9905	10	Processed %ld tables. Found %ld good text entries, %ld bad text entries in this database Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
9906	16	Unrecognized option. Available options: dbcc engine(net, show, engine#), dbcc engine(net, showall), dbcc engine(net, netengine) Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9908	16	Syspartitions system table does not exist in database id %S_DBID. 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.
9909	10	The total number of data pages in partition %d is %d. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
9911	10	Object %ld has one row in Syspartitions Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
9912	10	Object %ld has partition %ld instead of %ld in Syspartitions Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
9913	16	MAX_ROWS_PER_PAGE value of %d is invalid. It must be between 0 and %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9914	16	Amount of memory transferred (%dk) is less than the amount of memory requested (%dk). Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9915	16	I/O size must be a power of 2. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9916	16	I/O size must be a power of 2. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9917	16	Can't find database id for %.s. Check that this database exists and re-run the command. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9918	16	Encountered error using dbid %d. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
9919	16	Can't find object id for %.s. Check the object name and re-run this command. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9920	16	Index id %d not found for object id %d, dbid %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9921	16	Index %.s not found for object id %d dbid %d. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9922	16	The first page %ld in sysindexes for table `%.s' does not match with first page %ld for the table's first partition in Syspartitions. Explanation:* There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
9923	16	The first page %ld in syspartitions for partition %ld of table `%.s' has previous page # %ld in its page header. The previous page # should be NULL. Explanation:* There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
9924	16	The last page %ld in syspartitions for partition %ld of table `%.s' has next page # %ld in its page header. The next page # should be NULL. Explanation:* There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
9926	16	This option has been converted to the configuration parameter `%s'. Use `sp_configure' to set it. Explanation: There may be possible corruption in a database or a database object. Take any corrective action indicated by the message. Consult the Adaptive Server System Administration Guide and the Troubleshooting Guide.
9927	16	This option requries a table name as the third parameter. Use `sp_configure `%s'' to set the option serverwide. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9928	16	This option has been disabled. Use `sp_poolconfig' instead. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9929	14	Only the DBO of database %S_DBID or a user with System Administrator (SA) role can run DBCC TEXTALLOC command. Explanation: You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
9931	22	The %S_MSG page (%ld) found in the page chain does not match with the %S_MSG page (%ld) found in the slice control page (%ld), for table `%.s', on slice %ld. The table may be corrupt. Explanation:* A table or index may be corrupt. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
9932	22	The %S_MSG page (%d) found in the page chain doesn’t match with the %S_MSG page (%d) stored in the Sysindexes for table ’%.s’. The table may be corrupt. Explanation:* A table or index may be corrupt. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
9933	16	The option max_rows_per_page cannot be set for a text/image index (%d) on table `%.s'. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message. Not raised in 11.9.2.
9934	16	Invalid index ID %d. Values for index ID must be between 0 and %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9935	10	SQL Server will not refresh index descriptor as the object descriptor for objid % ld in dbid %d is not installed in cache. Explanation: There may be a potential problem with a database or database object. Contact your System Administrator.
9936	20	Error while trying to refresh sysindexes row within index descriptor with indid % d objid %ld and dbid %d. 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.
9938	16	Table with ID %d not found; check sysobjects. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9939	16	DBCC %s command is not supported anymore. Explanation: Refer to the System Administration Guide for details on supported dbcc commands and usage.
9940	16	The source text of object named '%s' with object id '%d' has already been hidden. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9941	16	The source text of object named '%s' with object id '%d' is missing and it is not hidden. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9942	16	Failed to hide the source text. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9943	16	The hidden text of object named '%s' with object id '%d' does not exist. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
9944	10	Too many errors have been detected on device '%.s' (physical device: %.s). Page and object checking on that device has been discontinued. (The CHECKSTORAGE operation stops when more than 25%% of the checks are abandoned.) Explanation: This is an informational message but may require follow-up action. Contact your System Administrator.
9945	10	Too many errors have been detected on table '%.s' index '%.s'. Checking for that object will be discontinued. (The CHECKSTORAGE operation stops when more than 25 %% of the checks are abandoned.) Explanation: Run dbcc checktable to determine the state of this object.
9946	17	An attempt to reserve a %dK buffer failed. Increase the size of the %dK buffer pool in the buffer cache ’%.s’. 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.
9947	17	An attempt to allocate memory failed due to insufficient SQL Server memory. 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.
9948	17	The CHECKSTORAGE operation failed to cache a scan workspace row because of a cache overflow. This is an internal error. Please contact Sybase Technical Support. 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.
9949	24	An I/O in a workspace failed, page %d in database %d. Check your hardware for problems that could cause I/O failures. Explanation: Hardware error detected. Report the error to your System Administrator. The database may have to be reloaded. It may be necessary to contact your hardware vendor.
9950	17	Workspace '%.s' is incorrectly allocated. Use sp_dbcc_createws to create a new workspace. 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.
9951	17	Workspace '%.s' is too fragmented to be used. Use sp_dbcc_createws and sp_dbcc_updateconfig to correct the problem. 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.
9952	17	Workspace '%.s' is too small to permit the CHECKSTORAGE operation to proceed. Use sp_dbcc_alterws and sp_dbcc_updateconfig to correct the problem. 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.
9953	20	SQL Server failed to synchronize the activity of a worker process with the coordinating process. This is an internal error. Please contact Sybase Technical Support. Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
9954	10	Storage checks for '%.s' are complete. DBCC is now recording the results in the dbccdb database. Explanation:* This is an informational message or a message header. No action is required.
9955	20	A worker process could not access database '%.s'. This is an internal error. Please contact Sybase Technical support. Explanation:* Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
9956	10	A worker process failed to complete its assigned work during the scan phase. The results of the CHECKSTORAGE operation will be incomplete. Explanation: Informational message but may impact outcome of dbcc checkstorage.
9957	10	A worker process failed to complete its assigned work during the page chain check phase. The results of the CHECKSTORAGE operation will be incomplete. Explanation: Informational message but may impact outcome of dbcc checkstorage.
9958	10	A worker process failed to complete its assigned work during the OAM check phase. The results of the CHECKSTORAGE operation will be incomplete. Explanation: Informational message but may impact outcome of dbcc checkstorage.
9959	10	The CHECKSTORAGE operation has aborted. Explanation: Problem impacts outcome of dbcc checkstorage.
9960	10	A non-recoverable error has occurred in the CHECKSTORAGE operation. The operation has been aborted. Explanation: Problem impacts outcome of dbcc checkstorage.
9961	17	DBCC failed to connect to the requested number of worker processes. The number of workers configured is insufficient, or the number of workers exceeds 128. Use sp_dbcc_updateconfig to reduce 'max worker processes' for this database. Explanation: Problem impacts outcome of dbcc checkstorage.
9962	17	Access to table '%.s' index '%.s' in the target database failed. Explanation: Problem impacts outcome of dbcc checkstorage.
9963	16	An error occurred while attempting to insert a row into the dbcc_faults table or the dbcc_fault_params table. Explanation: Problem impacts outcome of dbcc checkstorage.
9964	16	Database '%.s' was not found. Use sp_helpdb to list the available databases. Explanation:* Problem impacts outcome of dbcc checkstorage.
9965	16	The entries in dbcc_config for database '%.s' are either missing or invalid. Use sp_dbcc_evaluatedb to determine appropriate values for the entries and sp_dbcc_updateconfig to set them. Explanation:* Problem impacts outcome of dbcc checkstorage.
9966	16	DBCC could not access the scan workspace '%.s'. Verify that the workspace exists . Explanation:* Problem impacts outcome of dbcc checkstorage.
9967	16	DBCC could not access the text workspace '%.s'. Verify that the workspace exists . Explanation:* Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9968	16	DBCC could not evaluate SQL Server's device configuration. Check the contents of the dbcc_dev_info table. Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9969	16	The operation sequence number update for database '%.s' in the dbcc_config table failed. Explanation:* Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9970	16	DBCC failed to either insert or update the row in the dbcc_operation_log table for this check of database '%.s'. Explanation:* Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9971	20	DBCC failed to schedule work for the worker processes. This is an internal error. Please contact Sybase Technical Support. Explanation: Internal error affecting the current process. Contact your SA.
9972	16	An error occurred while inserting the results into the dbcc_counters table. Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9973	16	An error occurred while inserting the results into the dbcc_operation_results table. Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9974	10	DBCC CHECKSTORAGE for database '%.s' sequence %d completed at %s. %d faults and %d suspect conditions were located. %d checks were aborted. You should investigate the recorded faults, and plan a course of action that will correct them. Explanation:* This is an informational message but may require follow-up action. Contact your System Administrator.
9975	10	DBCC CHECKSTORAGE for database '%.s' encountered an error. Some results may not be available. Correct the problems reported and reexecute the CHECKSTORAGE command. Explanation:* This is an informational message but may require follow-up action. Contact your System Administrator.
9976	10	There is an inconsistency between the dbcc_dev_info table and the sysdevices table. Use DBCC CHECKDEVINFO to regenerate the dbcc_dev_info table. Explanation: This is an informational message but may require follow-up action. Contact your System Administrator.
9977	16	The cache '%.s' specified in the dbcc_config table does not exist. Explanation:* Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9978	16	The %dK buffer pool in the configured cache is too small. %dK is the minimum size . Explanation: Check the System Administration Guide for assistance.
9979	10	Too many worker processes (%d) are configured for the available %dK buffer pool. This buffer pool can only support %d workers. Explanation: Check the SA Guide for assistance.
9980	10	%d text column values were not checked because the text workspace was too small. Use sp_dbcc_alterws to increase its size by %dK. Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9981	16	Correct syntax is: dbcc createws({dbccdb\|dbccalt}, segment name, workspace name, {scan\|text}, size) dbcc alterws({dbccdb\|dbccalt}, workspace name, {scan\|text}, size) Explanation: Adaptive Server could not perform the requested action. Rewrite the command to conform to the requirement specified in the error message.
9982	16	The minimum size for a DBCC workspace is %d pages. Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9983	16	DBCC failed to create the workspace '%.s'. Explanation:* Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9984	16	DBCC could not expand the size of workspace '%.s' in database '%.s' to %d pages . Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9985	16	DBCC could not truncate the size of workspace '%.s' in database '%.s' by %d pages. Explanation: Problem impacts outcome of dbcc checkstorage. Check the SA Guide for assistance.
9986	10	Suspect conditions are to be treated as faults if the same suspect condition persists in subsequent CHECKSTORAGE operations, or if they are also detected by other DBCC functions. Explanation: This is an informational message but may require follow-up action. Contact your System Administrator.
9987	16	DOL datapage %d of object %d does not have extended page header bits set correctly. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9988	16	NCFS value %ld in DOL datapage %ld is larger than available space %ld in the page Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9989	16	Number of deleted rows %ld in page header of DOL datapage %ld is incorrect. This value cannot be negative. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9990	10	Insert free space value %ld in page header of DOL datapage %ld is greater than sum of cfs and ncfs (%ld) in the page Explanation: This is an informational message but may require follow-up action. Contact your System Administrator.
9991	16	Orphan row at offset %ld in page %ld of object %ld must be marked committed delete and is not Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9992	16	Actual #rows %ld in DOL datapage %ld and count of #rows - nextrno - %ld in page header do not match Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9993	16	There is a mismatch between value of ncfs counter %ld in page header of DOL datapage %ld and the actual amount of garbage %ld in the page Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9994	16	There is a mismatch between count of #deleted rows %ld in page header of DOL data page %ld and the actual # deleted rows %ld in the page Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9995	16	There is a mismatch between value of insert free space %ld in page header of DOL datapage %ld and actual value of insert free space %ld computed from the page with expected row size as %ld Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9996	16	Keys of index id %d for table '%.s' in %S_MSG not in proper order. Drop and recreate the index. (index page %ld) Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9997	16	Root page %ld in index id %ld of object id %ld does not have BT_ROOT bit set Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9998	16	Index page %ld has object id %ld which is different from object id %ld Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
9999	16	Rids not in ascending order in index page %ld for row %ld at offset %ld (indid %l d, object %ld). Drop and recreate the index. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.