Server Error Messages 12900 - 12999


This command is not allowed on an offline database '%S_DBID'. 
 Mime page chain starting at page %d has %d parts in it's header %d parts were found.
 Mime page chain starting at page %d has %d bytes in it's header %d bytes were found.
Cannot find object with ID '%d'. Check the object ID and retry the command. 
Index %ld of object %ld corrupt; key values in child page %ld inconsistent for parent page %ld. Drop and recreate the index.
Index %ld of object %ld has wrong level %d for page %ld, parent %ld is at level %d
The total number of data and control pages in this table is %d. 
Index %ld of object %ld has orphan leaf page %ld. Drop and recreate the index. 
Table with object id=%ld (name = %S_OBJID) inconsistent after Large Scale Allocation. %ld pages in extent %ld were found reserved.
Page %ld in extent %ld in Table with object id %ld (name = %S_OBJID) and index %ld is in the process of being allocated. To verify if the page is indeed allocated, run TABLEALLOC with the FIX option when there are no active transactions.
The extended header bit is not set in page %ld of object '%.*s' (ID %d) in database '%.*s' (ID %d). 
Incorrect offset entry(s) in the offset table of row %d in page %ld of object '%. *s' (ID %d) in database '%.*s' (ID %d).
Incorrect column type in the offset table of row %d in page %ld of object '%.*s' (ID %d) in database '%.*s' (ID %d).
EXP_ROW_SIZE value of %d is invalid. It must be between %d and %d. 
Invalid Cachelet ID %d. Valid Cachelet ID values are between %d and %d. 
Fixed spacebits (on allocation page) for DOL datapage %ld, with insfs %d and expected row length %d. Were expected to be 0x%x, but were found to be 0x%x.
Non-contiguous free space %d in page header of DOL datapage %ld is incorrect. This value cannot be negative.
Verifying faults for '%.*s'.
The last completed DBCC CHECKSTORAGE for this database has been processed. You must perform another DBCC CHECKSTORAGE before you can use CHECKVERIFY or CHECKREPAIR. Use sp_dbcc_summary_report to view the DBCC operations performed.
A problem was encountered while accessing the faults recorded in the dbccdb database. Please check the dbcc_faults and dbcc_fault_params tables in the dbccdb database.
A problem was encountered while updating the fault status in the dbcc_faults table. Please check the dbcc_faults and dbcc_fault_params tables in the dbccdb database.
Failed to get an '%s' lock on table '%.*s'. The faults for this table will not be processed.
DBCC CHECKVERIFY for database '%.*s' encountered an error. Correct the reported problem reported and execute the CHECKVERIFY command again.
DBCC CHECKVERIFY for database '%.*s' sequence %d completed at %s. %d suspect conditions were resolved as faults, and %d suspect conditions were resolved as harmless. %d objects could not be checked.
DBCC CHECKVERIFY could not acquire a lock on the target database. 
Performing QUICK repairs to database '%.*s'.
DBCC CHECKREPAIR with the QUICK_REPAIRS option does not accept an object name. The parameter '%.*s' will be ignored.
DBCC CHECKREPAIR for database '%.*s' sequence %d completed at %s. %d faults were repaired, and %d faults were resolved without repair. %d objects could not be processed and %d faults remain unrepaired. 
DBCC CHECKREPAIR for database '%.*s' encountered an error. Correct the problems reported and execute the CHECKREPAIR command again.
The total number of empty pages (with all deleted rows) in this table is %ld. 
The total number of pages which could be garbage collected to free up some space is %ld.
DBCC CHECKSTORAGE not supported in this release of Adaptive Server Enterprise. 
Page %ld of object %ld, indid %ld undergoing change. Some pages of indid %ld may not be checked, retry the command later.
Engine zero can not be offline.
Failed to (re)build the st-node. Please issue the command ’dbcc rebuild_text (%ld, %d, %ld)’ to (re)build the st-node. (objid=%ld, colid=%d, FTP=%ld). 
The text page back pointer on text page %d appears to be incorrect. Expected %d, byt got %d. 
 Engine number must be between %d and (maxonline - 1) %d.
The minimum number of online engines is %d. No more engine can be offlined. 
Cannot find database ’%.*s’ for constraint ID %d in sysreferences. 
Table ID %d, index ID %d in sysreferences does not have a matching entry in sysindexes in database %d. 
Table ID %d, column ID %d in sysconstraints does not have a matching entry in syscolumns. 
Mismatch found in an entry in sysreferences between the database ID %d and database name ’%.*s’. The actual database ID is %d. 
Insert free space value in page header of DOL datapage %ld has been corrected to %d. 
Mismatch found. Current database ID %d, appears in sysreferences with database ID %d. 
Syslogs free space is currently %ld pages but DBCC counted %ld pages. This descrepancy may be spurious if this count was done in multi-user mode. Please run DBCC TABLEALLOC(syslogs, full, fix) to correct it.
Syslogs free space count has been successfully recalculated. It has been corrected to %ld pages.
This command is only allowed for databases having a separate log segment.
 The following task(s) will affect the offline process:
spid: %d has outstanding %s connections.
The total number of wrong st-node back references to first text page chains in this table is %d.
Invalid external st-node first text page value %ld stored in first text page %ld.
Invalid first text page value %d in data row text pointer %s for TEXT/IMAGE column %d in row %d of page %d, object id %d.
Incorrect partition ID %d found in extent ID %d for object ID %d.
The reserved status was found to be improperly set in %ld pages. That status has been cleared by DBCC.
 Start dbcc stacktrace...
 dbcc stacktrace finished.

Number	Severity	Text and Explanation
12901	16	This command is not allowed on an offline database '%S_DBID'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12902	16	Mime page chain starting at page %d has %d parts in it's header %d parts were found. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
12903	16	Mime page chain starting at page %d has %d bytes in it's header %d bytes were found. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
12904	16	Cannot find object with ID '%d'. Check the object ID and retry the command. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12905	16	Index %ld of object %ld corrupt; key values in child page %ld inconsistent for parent page %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.
12906	16	Index %ld of object %ld has wrong level %d for page %ld, parent %ld is at level %d Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12907	16	The total number of data and control pages in this table is %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12908	16	Index %ld of object %ld has orphan leaf page %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.
12909	16	Table with object id=%ld (name = %S_OBJID) inconsistent after Large Scale Allocation. %ld pages in extent %ld were found reserved. Explanation: Since 11.9.x, the Page Manager uses some bits in the allocation page extent structure for internal bookkeeping, specially during operations like bcp that use large scale allocation. These bits are called reserve bits. After you upgrade to 12.0, dbcc checkalloc may report 12909 errors on your database if it finds reserve bits set (this may happen if these bits were set during some page allocation but were not cleaned up). Correct the error by running checkalloc with fix.
12910	16	Page %ld in extent %ld in Table with object id %ld (name = %S_OBJID) and index %ld is in the process of being allocated. To verify if the page is indeed allocated, run TABLEALLOC with the FIX option when there are no active transactions. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12911	10	The extended header bit is not set in page %ld of object '%.s' (ID %d) in database '%.s' (ID %d). Explanation: This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12912	10	Incorrect offset entry(s) in the offset table of row %d in page %ld of object '%. s' (ID %d) in database '%.s' (ID %d). Explanation: This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12913	10	Incorrect column type in the offset table of row %d in page %ld of object '%.s' (ID %d) in database '%.s' (ID %d). Explanation: This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12914	16	EXP_ROW_SIZE value of %d is invalid. It must be between %d and %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12915	16	Invalid Cachelet ID %d. Valid Cachelet ID values are between %d and %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12916	16	Fixed spacebits (on allocation page) for DOL datapage %ld, with insfs %d and expected row length %d. Were expected to be 0x%x, but were found to be 0x%x. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12917	16	Non-contiguous free space %d 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.
12919	10	Verifying faults for '%.s'. Explanation:* This is an informational message. No action is required.
12920	16	The last completed DBCC CHECKSTORAGE for this database has been processed. You must perform another DBCC CHECKSTORAGE before you can use CHECKVERIFY or CHECKREPAIR. Use sp_dbcc_summary_report to view the DBCC operations performed. Explanation: Adaptive Server could not perform the requested action. A completed and unverified CHECKSTORAGE operation must exist before CHECKVERIFY can execute.
12921	16	A problem was encountered while accessing the faults recorded in the dbccdb database. Please check the dbcc_faults and dbcc_fault_params tables in the dbccdb database. Explanation: Adaptive Server could not perform the requested action. Contact your System Administrator.
12922	16	A problem was encountered while updating the fault status in the dbcc_faults table. Please check the dbcc_faults and dbcc_fault_params tables in the dbccdb database. Explanation: Adaptive Server could not perform the requested action. Contact your System Administrator.
12923	10	Failed to get an '%s' lock on table '%.s'. The faults for this table will not be processed. Explanation:* dbcc checkstorage could not verify the faults for this table and its indexes because it was unable to block updates to the table. Contact your System Administrator.
12924	10	DBCC CHECKVERIFY for database '%.s' encountered an error. Correct the reported problem reported and execute the CHECKVERIFY command again. Explanation:* This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12925	10	DBCC CHECKVERIFY for database '%.s' sequence %d completed at %s. %d suspect conditions were resolved as faults, and %d suspect conditions were resolved as harmless. %d objects could not be checked. Explanation:* This is an informational message. No action is required.
12926	20	DBCC CHECKVERIFY could not acquire a lock on the target database. Explanation: Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
12927	10	Performing QUICK repairs to database '%.s'. Explanation:* This is an informational message. No action is required.
12928	10	DBCC CHECKREPAIR with the QUICK_REPAIRS option does not accept an object name. The parameter '%.s' will be ignored. Explanation:* This is an informational message. The optional object parameter should not be used with this command option.
12929	10	DBCC CHECKREPAIR for database '%.s' sequence %d completed at %s. %d faults were repaired, and %d faults were resolved without repair. %d objects could not be processed and %d faults remain unrepaired. Explanation:* This is an informational message. No action is required.
12930	10	DBCC CHECKREPAIR for database '%.s' encountered an error. Correct the problems reported and execute the CHECKREPAIR command again. Explanation:* This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12931	10	The total number of empty pages (with all deleted rows) in this table is %ld. Explanation: This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12932	10	The total number of pages which could be garbage collected to free up some space is %ld. Explanation: This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12933	10	DBCC CHECKSTORAGE not supported in this release of Adaptive Server Enterprise. Explanation: This dbcc feature is not supported in your version of Adaptive Server.
12934	16	Page %ld of object %ld, indid %ld undergoing change. Some pages of indid %ld may not be checked, retry the command later. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12935	16	Engine zero can not be offline. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12936	10	Failed to (re)build the st-node. Please issue the command ’dbcc rebuild_text (%ld, %d, %ld)’ to (re)build the st-node. (objid=%ld, colid=%d, FTP=%ld). Explanation: This is an informational message. The optional object parameter should not be used with this command option.
12937	16	The text page back pointer on text page %d appears to be incorrect. Expected %d, byt got %d. Explanation: Report the error to your System Administrator so DBCC diagnostics can be run.
12938	16	Engine number must be between %d and (maxonline - 1) %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12939	16	The minimum number of online engines is %d. No more engine can be offlined. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12940	16	Cannot find database ’%.s’ for constraint ID %d in sysreferences. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12941	16	Table ID %d, index ID %d in sysreferences does not have a matching entry in sysindexes in database %d. Explanation: Command failed due to invalid or illegal request.
12942	16	Table ID %d, column ID %d in sysconstraints does not have a matching entry in syscolumns. Explanation: Command failed due to invalid or illegal request.
12943	16	Mismatch found in an entry in sysreferences between the database ID %d and database name ’%.s’. The actual database ID is %d. Explanation:* Command failed due to invalid or illegal request.
12944	10	Insert free space value in page header of DOL datapage %ld has been corrected to %d. Explanation: This is an informational message. Correct the problem indicated in the preceeding messages or in the errorlog before re-executing the command. Contact your System Administrator for assistance.
12945	16	Mismatch found. Current database ID %d, appears in sysreferences with database ID %d. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by the message.
12947	16	Syslogs free space is currently %ld pages but DBCC counted %ld pages. This descrepancy may be spurious if this count was done in multi-user mode. Please run DBCC TABLEALLOC(syslogs, full, fix) to correct it. Explanation: Take any corrective action indicated by the message.
12948	10	Syslogs free space count has been successfully recalculated. It has been corrected to %ld pages. Explanation: This is an informational message.
12949	16	This command is only allowed for databases having a separate log segment. Explanation: For more information on this topic, see the writeup for Error 4205.
12950	10	The following task(s) will affect the offline process: Explanation: This is an informational message.
12951	10	spid: %d has outstanding %s connections. Explanation: This is an informational message.
12952	10	The total number of wrong st-node back references to first text page chains in this table is %d. Explanation: This is an informational message.
12953	16	Invalid external st-node first text page value %ld stored in first text page %ld. Explanation: Command failed due to invalid or illegal request. Check syntax and semantics.
12954	16	Invalid first text page value %d in data row text pointer %s for TEXT/IMAGE column %d in row %d of page %d, object id %d. Explanation: dbcc command found an error in an internal structure of the specified object. Contact your System Administrator.
12955	16	Incorrect partition ID %d found in extent ID %d for object ID %d. Explanation: dbcc command found an error in an extent for the specified object. Contact your System Administrator.
12956	10	The reserved status was found to be improperly set in %ld pages. That status has been cleared by DBCC. Explanation: The dbcc command found and corrected the page status error.
12957	10	Start dbcc stacktrace... Explanation: This is an informational message.
12958	10	dbcc stacktrace finished. Explanation: This is an informational message.