Server Error Messages 7900 - 7999


 Page %ld was expected to be the first page of a TEXT/IMAGE value.
 Data size mismatch occurred while checking TEXT/IMAGE values. The first page for this value is: %ld. There were %ld bytes found, which is different from the expected data length of %ld bytes.
 Page %ld was expected to be a TEXT/IMAGE page. This occurred when link number %ld was examined.
 The total number of TEXT/IMAGE pages in this table is %d.
 The number of rows in sysindexes for this table was %ld.  It has been corrected to %ld.
 The number of data pages in sysindexes for this table was %ld.  It has been corrected to %ld.
 The status in the first page (%ld) of the no_log table %.*s and the status in the sysobjects row, do not match.
 The table %.*s was created with the no_log option.
 A transaction involving the no_log table %.*s was undone. This may have left the table in an inconsistent state. Rebuild the table.
 Page %ld allocated (Alloc page: %ld Extent ID: %ld Alloc mask: 0x%x)
 Page %ld deallocated (Alloc page: %ld Extent ID: %ld Alloc mask: 0x%x)
 EXTID:%ld (Alloc page: %ld) is initialized.  Extent follows:
PTNID=%d SPARE=%d OBJID=%ld RESERVE=0x%x FORWARD=0x%x ALLOC=0x%x DEALLOC=0x%x IND ID=%d STATUS=0x%x
 Allocation page %ld extid %ld is not referenced, but there are referenced pages within this extent.  Contact Technical Support for assistance on object %ld.
 Allocation page %ld extid %ld is referenced, but there are no referenced pages within this extent.  Contact Technical Support for assistnace on object %ld.
 Total (# alloc pages = %ld, # of alloc pages modified = %ld).
 Total (# pages allocated=%ld pages deallocated=%ld extents deleted=%ld).
 Alloc page %ld (pgs allocated=%ld pgs deallocated=%ld extents deleted=%ld).
 Fix_al not processed.  Database needs to be in SINGLE USER mode.
 Processed %ld entries in the sysindexes for dbid %d.
 Found %ld bad entries in the sysindexes.
 ***************************************************************
 TABLE: %.*s OBJID = %ld
 INDID=%ld FIRST=%ld ROOT=%ld SORT=%d
 Indid : %d.  %ld Index pages allocated and %ld Extents allocated.
 Data level: %d.  %ld Data pages allocated and %ld Extents allocated.
 TOTAL # of extents = %ld
Index %.*s is not consistent; found %d leaf rows but %ld data rows. Drop and recreate the index. 
 Table has %d data rows.
Table Corrupt: keys in left child do not precede the parent key; check left child page %ld.
Table Corrupt: keys in right child precede the parent key; check right child page  %ld.
 The indexes for `%.*s' are already correct.  They will not be rebuilt.
 One or more indexes are corrupt.  They will be rebuilt.
 The table `%.*s' has no indexes.
 REINDEX received an exception - command aborted.
 Checktable on sysgams is not allowed.
 The data in table `%.*s' is possibly corrupt - DBCC REINDEX aborted.  Run DBCC CHECKTABLE and report errors to a user with System Administrator (SA) role.
 Table Corrupt: The oam entry for object %ld, indid %ld, alloc pg %ld, has a used count of %d and an unused count of %d.  The used count should be %d and the unused count should be %d.
 Table Corrupt: The entry is missing from the OAM for object id %ld indid %d for allocation page %ld.
 The counts in the OAM are incorrect.  This implies that there are entries missing.  Run tablealloc utility with the FIX option on the table with the inaccurate OAM counts.
 Couldn't find table %.*s.
 The missing OAM entry has been inserted.
 Attempt to insert missing OAM entry failed.
 *** NOTICE:  Space used on the log segment is %s Mbytes, %s%%.
 *** NOTICE:  Space free on the log segment is %s Mbytes, %s%%.
 *** NOTICE:  Notification of log space used/free cannot be reported because the log segment is not on its own device.
 The sortorder and character set ID's for index %d on this table were %d:%d in sysindexes.  They have been corrected to %d:%d.
 Page %ld, object %ld, index %d, level %d, was found with fixed-row status improperly set.  That status has been cleared by DBCC.
 The number of pages used and unused for object %ld index %d on allocation page %ld do not match the counts in the OAM entry.
 Unable to %.*s engine.  Check sysengines count and max online engines config value.
 Data size mismatch occurred while checking a TEXT value. The first page for this value is: %ld. There were %ld characters found, which is different from the expected length of %ld characters.
 A TEXT value with an invalid MAGIC NUMBER has been found on page %ld. TEXT values will no longer be checked for this table. Note because of this, the TEXT page count will be inaccurate. Use DBCC FIX_TEXT to fix the TEXT values.
 Unable to acquire an exclusive lock on text page %ld. This text value has not been recalculated.  In order to recalculate those TEXT pages you must release the lock and reissue the DBCC FIX_TEXT command.
 There are no TEXT pages in table %.*s to be updated.
 Not all of the TEXT pages in table %.*s have been successfully updated, however, DBCC FIX_TEXT is restartable. Please issue the command again once any other errors have been addressed.
 Remapping utility - Column descriptor should have been remapped earlier. This is an internal system error.
 Remapping utility - procedure is corrupted in Sysprocedures. Recreate this procedure.
 Remapping utility - a pointer exists in a tree when it should not.
 Remapping utility - unable to locate the given procedure %.*s in Sysprocedures.
 Remapping utility - Procedure needs to be recreated for this port.
 Remapping utility - Wrong kind of node passed to tree remapping. This is an internal system error.
 Upgrade requires the SQL Server to be booted in single user mode. Reboot the SQL Server with the -m flag.
 Upgrade encountered a fatal error. Please check the SQL Server errorlog.
 Permission denied.  You do not have the necessary role to run this command.  Please contact Sybase Technical Support for assistance in running this command.
 The `fix' option has been ignored for this command. To use the `fix' option with system tables, run the command from the database where the table is located. The database must be in single user mode.
 The global space allocation report requires an exclusive lock on object 99.  This process does not hold this lock in database %d.  This report is cancelled.
 Allocation page %ld in database %d does not hold the address lock required for initializing the diagnostic bitmaps or correcting its allocation errors.
 The object allocation map for tabid %d indid %d is corrupt, therefore the optimized report cannot be generated.  Contact Technical Support for assistance.
 Allocation reports cannot be generated for object %ld in database %d.
 The default report option of %.*s is used for this run.
 The default fix option of %.*s is used for this run.
 The oam counts for objid %ld indid %d are corrected.
 The optimized report may generate erroneous messages due to the missing OAM entry.  Run the optimized report with the fix option, to correct this error.
 ILLEGAL use of module %.*s.  See the errorlog for detail information.
 System catalog entrie(s) for Object %d, Database %d are corrupted.
 Object %d in database %d does not have any TEXT/IMAGE data.
 First page %ld and Root page %ld are not same.
 One or more text chain(s) for object %ld in database %ld is corrupt.
 Text chain linkage corrupted for Page %ld of Object %ld.
 Unreferenced text chain found for page %ld, nextpage %ld, prevpage %ld.
 The new transaction mode must be unchained, chained or anymode.
 The specified object `%.*s' is not a stored procedure in database `%.*s'.
 You must be either the system administrator (SA), the database administrator (dbo), or the owner of this stored procedure to change its transaction mode.
Server name ’%.*s’ not found in system catalog.
 You can not change the mode of a remote stored procedure.
 User named `%.*s' not found; check sysusers.
 The specified object `%.*s' is not found in database `%.*s'.  Check sysobjects to make sure you own the object.
 The serial allocation flag was found to be improperly set in allocation unit %ld, at extent ID %ld, with alloc map = %d and objid = %ld.  This flag has been cleared by DBCC.
 Permission denied.  User's operating system session label must dominate database maxhold to use the DBCC command `%.*s'.
 Label consistency check for database `%S_DBID' failed.
 The user needs to be in the master database to execute this command.
 Either the execution of the `DBCC SECURITY (LABEL_CHECK)' command failed or one or more databases have been detected to have inconsistent security labels.
 Database `%.*s' has references to other databases. Drop those references and try again
 Permission denied. Only the Database Owner (DBO) or a user with the System Administrator (SA), System Security Officer (SSO), or Oper role can execute this command for database `%S_DBID'.
 Permission denied.  Object `%S_OBJID' not found.
 Permission denied.  User's curwrite does not match the sensitivity label of object `%S_OBJID'.
 Permission denied.  Database `%S_DBID' not found.
 Permission denied.  User's curwrite does not match the sensitivity label of database `%S_DBID'.

Number	Severity	Text and Explanation
7901	16	Page %ld was expected to be the first page of a TEXT/IMAGE value. 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.
7902	16	Data size mismatch occurred while checking TEXT/IMAGE values. The first page for this value is: %ld. There were %ld bytes found, which is different from the expected data length of %ld bytes. Explanation: Refer to the writeup for this error.
7903	16	Page %ld was expected to be a TEXT/IMAGE page. This occurred when link number %ld was examined. 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.
7904	10	The total number of TEXT/IMAGE pages in this table 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.
7905	10	The number of rows in sysindexes for this table was %ld. It has been corrected to %ld. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7906	10	The number of data pages in sysindexes for this table was %ld. It has been corrected to %ld. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7907	16	The status in the first page (%ld) of the no_log table %.s and the status in the sysobjects row, do not match. 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.
7908	10	The table %.s was created with the no_log option. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7909	10	A transaction involving the no_log table %.s was undone. This may have left the table in an inconsistent state. Rebuild the 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.
7910	16	Page %ld allocated (Alloc page: %ld Extent ID: %ld Alloc mask: 0x%x) Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7911	16	Page %ld deallocated (Alloc page: %ld Extent ID: %ld Alloc mask: 0x%x) Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7912	16	EXTID:%ld (Alloc page: %ld) is initialized. Extent follows: Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7913	16	PTNID=%d SPARE=%d OBJID=%ld RESERVE=0x%x FORWARD=0x%x ALLOC=0x%x DEALLOC=0x%x IND ID=%d STATUS=0x%x Explanation: This is an informational message.
7914	10	Allocation page %ld extid %ld is not referenced, but there are referenced pages within this extent. Contact Technical Support for assistance on object %ld. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7915	10	Allocation page %ld extid %ld is referenced, but there are no referenced pages within this extent. Contact Technical Support for assistnace on object %ld. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7916	10	Total (# alloc pages = %ld, # of alloc pages modified = %ld). Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7917	16	Total (# pages allocated=%ld pages deallocated=%ld extents deleted=%ld). Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7918	16	Alloc page %ld (pgs allocated=%ld pgs deallocated=%ld extents deleted=%ld). Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7919	16	Fix_al not processed. Database needs to be in SINGLE USER mode. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7920	16	Processed %ld entries in the sysindexes for dbid %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7921	16	Found %ld bad entries in the sysindexes. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7922	16	************************************************************* Explanation:** This is an informational message or a message header. No action is required.
7923	16	TABLE: %.s OBJID = %ld Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7924	16	INDID=%ld FIRST=%ld ROOT=%ld SORT=%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.
7925	16	Indid : %d. %ld Index pages allocated and %ld Extents allocated. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7926	16	Data level: %d. %ld Data pages allocated and %ld Extents allocated. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7927	16	TOTAL # of extents = %ld Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7928	16	Index %.s is not consistent; found %d leaf rows but %ld data rows. Drop and recreate the index. Explanation:* Refer to the writeup for this error.
7929	16	Table has %d data rows. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7930	16	Table Corrupt: keys in left child do not precede the parent key; check left child page %ld. Table Corrupt: keys in left child do not precede the parent key; check left child page %ld. Explanation: Refer to the writeup for this error.
7931	16	Table Corrupt: keys in right child precede the parent key; check right child page %ld. Explanation: There may be possible corruption in a database or a database object. Consult the Error Messages and Troubleshooting Guide to see how to locate the table, and run dbcc diagnostics.
7932	16	The indexes for `%.s' are already correct. They will not be rebuilt. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7933	16	One or more indexes are corrupt. They will be rebuilt. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7934	16	The table `%.s' has no indexes. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7935	16	REINDEX received an exception - command aborted. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7936	10	Checktable on sysgams is not allowed. Explanation: Check command syntax and semantics.
7937	16	The data in table `%.s' is possibly corrupt - DBCC REINDEX aborted. Run DBCC CHECKTABLE and report errors to a user with System Administrator (SA) role. 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.
7938	16	Table Corrupt: The oam entry for object %ld, indid %ld, alloc pg %ld, has a used count of %d and an unused count of %d. The used count should be %d and the unused count should be %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.
7939	16	Table Corrupt: The entry is missing from the OAM for object id %ld indid %d for allocation page %ld. Explanation: Refer to the writeup for this error.
7940	22	The counts in the OAM are incorrect. This implies that there are entries missing. Run tablealloc utility with the FIX option on the table with the inaccurate OAM counts. Explanation: Refer to the writeup for this error.
7941	16	Couldn't find table %.s. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7942	10	The missing OAM entry has been inserted. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7943	10	Attempt to insert missing OAM entry failed. Explanation: There may be a potential problem with a database or database object. Contact your System Administrator.
7944	10	* NOTICE: Space used on the log segment is %s Mbytes, %s%%. Explanation:** This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7945	10	* NOTICE: Space free on the log segment is %s Mbytes, %s%%. Explanation:** This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7946	10	* NOTICE: Notification of log space used/free cannot be reported because the log segment is not on its own device. Explanation:** This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7947	16	The sortorder and character set ID's for index %d on this table were %d:%d in sysindexes. They have been corrected to %d:%d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7948	16	Page %ld, object %ld, index %d, level %d, was found with fixed-row status improperly set. That status has been cleared by DBCC. Explanation: This informational message is displayed by dbcc checktable or dbcc checkdb (which calls dbcc checktable) when a page status bit in a page header is set on when it should not be. This bit is normally set on when there are no variable-length columns for this object (the rows are all fixed-length). If dbcc checktable finds that this bit is set on and there are variable display rows, the bit is turned off and the 7948 message is displayed. dbcc checktable (or dbcc checkdb) corrects this problem so no further action is required.
7949	16	The number of pages used and unused for object %ld index %d on allocation page %ld do not match the counts in the OAM entry. Explanation: Refer to the writeup for this error.
7950	16	Unable to %.s engine. Check sysengines count and max online engines config value. 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.
7951	16	Data size mismatch occurred while checking a TEXT value. The first page for this value is: %ld. There were %ld characters found, which is different from the expected length of %ld characters. Explanation: This error may be seen after upgrading from 11.x to 12.0 when tables contain one or more text columns. Contact Sybase Technical Support to upgrade to a version in which the problem is resolved.
7952	10	A TEXT value with an invalid MAGIC NUMBER has been found on page %ld. TEXT values will no longer be checked for this table. Note because of this, the TEXT page count will be inaccurate. Use DBCC FIX_TEXT to fix the TEXT values. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7953	10	Unable to acquire an exclusive lock on text page %ld. This text value has not been recalculated. In order to recalculate those TEXT pages you must release the lock and reissue the DBCC FIX_TEXT command. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7954	10	There are no TEXT pages in table %.s to be updated. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7955	10	Not all of the TEXT pages in table %.s have been successfully updated, however, DBCC FIX_TEXT is restartable. Please issue the command again once any other errors have been addressed. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7956	16	Remapping utility - Column descriptor should have been remapped earlier. This is an internal system error. 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.
7957	25	Remapping utility - procedure is corrupted in Sysprocedures. Recreate this procedure. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
7958	16	Remapping utility - a pointer exists in a tree when it should not. 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.
7959	16	Remapping utility - unable to locate the given procedure %.s in Sysprocedures. 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.
7960	16	Remapping utility - Procedure needs to be recreated for this port. 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.
7961	16	Remapping utility - Wrong kind of node passed to tree remapping. This is an internal system error. Explanation: Adaptive Server was unable to reclaim space following query remapping. See the writeup for Error 7783 for more information.
7962	16	Upgrade requires the SQL Server to be booted in single user mode. Reboot the SQL Server with the -m flag. 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.
7963	16	Upgrade encountered a fatal error. Please check the SQL Server errorlog. 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.
7964	14	Permission denied. You do not have the necessary role to run this command. Please contact Sybase Technical Support for assistance in running this 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.
7965	10	The `fix' option has been ignored for this command. To use the `fix' option with system tables, run the command from the database where the table is located. The database must be in single user mode. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7966	20	The global space allocation report requires an exclusive lock on object 99. This process does not hold this lock in database %d. This report is cancelled. 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.
7967	20	Allocation page %ld in database %d does not hold the address lock required for initializing the diagnostic bitmaps or correcting its allocation errors. 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.
7968	20	The object allocation map for tabid %d indid %d is corrupt, therefore the optimized report cannot be generated. Contact Technical Support for assistance. 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.
7969	10	Allocation reports cannot be generated for object %ld in database %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.
7970	10	The default report option of %.s is used for this run. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7971	10	The default fix option of %.s is used for this run. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7972	10	The oam counts for objid %ld indid %d are corrected. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7973	10	The optimized report may generate erroneous messages due to the missing OAM entry. Run the optimized report with the fix option, to correct this error. Explanation: This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
7974	16	ILLEGAL use of module %.s. See the errorlog for detail information. 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.
7975	20	System catalog entrie(s) for Object %d, Database %d are corrupted. 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.
7976	16	Object %d in database %d does not have any TEXT/IMAGE data. 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.
7977	16	First page %ld and Root page %ld are not same. 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.
7978	20	One or more text chain(s) for object %ld in database %ld is corrupt. 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.
7979	16	Text chain linkage corrupted for Page %ld of Object %ld. 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.
7980	16	Unreferenced text chain found for page %ld, nextpage %ld, prevpage %ld. 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.
7981	16	The new transaction mode must be unchained, chained or anymode. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7982	16	The specified object `%.s' is not a stored procedure in database `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7983	16	You must be either the system administrator (SA), the database administrator (dbo), or the owner of this stored procedure to change its transaction mode. Explanation: Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
7985	16	Server name ’%.s’ not found in system catalog. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7986	16	You can not change the mode of a remote stored procedure. Explanation: Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
7987	16	User named `%.s' not found; check sysusers. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7988	16	The specified object `%.s' is not found in database `%.s'. Check sysobjects to make sure you own the object. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7989	16	The serial allocation flag was found to be improperly set in allocation unit %ld, at extent ID %ld, with alloc map = %d and objid = %ld. This flag has been cleared by DBCC. Explanation: Refer to the detailed writeup for Error 7989 in the chapter titled “Error Message Writeups”.
7990	16	Permission denied. User's operating system session label must dominate database maxhold to use the DBCC command `%.s'. Explanation:* Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
7991	18	Label consistency check for database `%S_DBID' failed. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
7992	14	The user needs to be in the master database to execute this command. Explanation: Command failed due to invalid or illegal request. Adaptive Server cannot perform the requested action. Take any corrective action indicated by the message.
7993	18	Either the execution of the `DBCC SECURITY (LABEL_CHECK)' command failed or one or more databases have been detected to have inconsistent security labels. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
7994	16	Database `%.s' has references to other databases. Drop those references and try again Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
7995	14	Permission denied. Only the Database Owner (DBO) or a user with the System Administrator (SA), System Security Officer (SSO), or Oper role can execute this command for 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.
7996	14	Permission denied. Object `%S_OBJID' not found. 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.
7997	14	Permission denied. User's curwrite does not match the sensitivity label of object `%S_OBJID'. 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.
7998	14	Permission denied. Database `%S_DBID' not found. 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.
7999	14	Permission denied. User's curwrite does not match the sensitivity label of 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.