Server Error Messages 1100-1199


 Unable to allocate new page for database `%.*s'. There are no more pages available on valid allocation pages. Space can be created by dropping objects, extending the database, or dumping the log with no_log.
 Unable to locate allocation page %ld for database `%.*s'. This allocation page contains the extent that the target allocation page is in, but the allocation page is not in the translation table in the DBTABLE. Run DBCC CHECKTABLE on sysusages.
 Allocation page %ld in database `%.*s' has different segment id than that of the object to which we are allocating. Run DBCC CHECKALLOC.
 Conflict between number of extents marked in log record in the allocation bitmap and the allocation count. Allocation count is %d. Bitmap is 0x%lx 0x%lx 0x%lx 0x%lx.
 Can't allocate space for object `%.*s' in database `%.*s' because `%.*s' segment is full. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase size of the segment.  
 First pass through allocation page %ld found %d free extents. After logging, only found %d free extents.
 Cannot deallocate extent %ld, database %d. Object id %ld, index id %d, status %d in extent does not match object id %ld, index id %d, status %d in object being deallocated.  Run DBCC CHECKALLOC.
 Attempt to read allocation page %ld failed either because object ID is not correct (%ld) or the page ID is not correct (%ld).
 Attempt to resource lock allocation page %ld in database `%.*s' by process %d while allocating to non-syslogs object `%.*s'.
 Extent bitmap on allocation page %ld in database `%.*s' does not have extents marked that are being removed.
 Extent bitmap on allocation page %ld in database `%.*s' already has extents marked that are being added.
 Extent %ld already locked while allocating it in database `%.*s'.
 Attempt to resource lock page %ld in database `%.*s' by process %d failed because lock is already held by process %d.
 Attempt to transfer a resource lock to process ID 0 on allocation page %ld in database `%.*s'.
 Attempt to  backout the allocation of LOG page %ld, in database `%.*s'.
 Extent chain for object %ld is not correctly linked.
Adaptive Server failed to access page %ld in database ’%.*s’ because it is not an allocation page. 
 Attempt to read allocation page before openning SYSALLOCPGS.
 Failed to get lock on OAM pg.
 Failed to get lock on allocation page %ld.
 Attempting to allocate page %ld in database %d to extent %ld which belongs to another object.  Object id and index id in page are %ld, %ld.  Object id and index id in extent are %ld, %ld.
 Internal Error:  The OAM has no room for new inserts.  Check OAM for object %ld, index %d.
 The OAM entry for allocation page %ld is missing from the OAM which starts on page %ld.
 The requested update to the OAM for object %ld, dbid %ld, index %d, oam page %ld, would cause a negative page count.  allocation page: %ld, oamarray used: %ld, oamarray unused: %ld, deltaused: %ld, deltaunused: %ld, spid: %ld. Contact your System Admin.
 A dealloc log record has been detected which does not have an OAM page supplied.
The OAM for object %ld, index %d, oam page %ld, database=%d, is currently allocated to another object.
 Attempted to log allocation to the log.
 Page %ld was expected to be an OAM page for %ld and it is not.
 Failed to get lock on OAM page %ld.  This should never happen.
 Page %ld was given as a target page for allocation to object %ld index id %d and there is no entry in the OAM for this page.  This may indicate corruption of the OAM.  Please run checkalloc on database %.*s.
 `Please run the upgrade38 utility before attempting to upgrade your database to MP.'
 `There is insufficient space in database %.*s to run this upgrade.'
 `Failed to complete allocation of SYSGAMS in database %.*s.'
 Impossible deadlock on page mgr lock.
 `Page mgr lock should not already be held.'
 Unexpected value returned to page manager routine: %ld.
 Invalid OAM Page %ld. Found pstat=0x%x, object=%ld, database=%d, indid=%d.
 Invalid OAM Page %ld. Expected object=%ld. Found object=%ld, database=%d, pstat=0x%x, indid=%d.
 Page number %ld is higher than the highest page in database `%.*s':  %ld.
 ss %d was expected to hold logical lock on page %ld.
 Process %d was expected to hold logical lock on object %ld.
 Process %d trying to do a logged operation on a non-logged object %ld.
 Error: %d, Severity: %d, State: %dn
 A Log Run Deallocation routine was passed one or more bad parameters. The bad parameter is either %ld or %ld.
 Failed to get intent lock on object %ld.
 Object %ld passed to OAM builtin function no longer exists in database %d.
 Page %ld passed to OAM builtin function is not an OAM page for object %ld in database %d.
 OAM page %ld passed to rowcnt function is an unallocated page in database %d.
 WARNING!!! Attempt to do a prefetch of size %dK is not allowed. The prefetch request is reset to the maximum prefetch size of %dK.
Invalid page validation type, %d, requested for page %ld, object %S_OBJID, indid %d in database %S_DBID. 
Unable to update the page linkage status for the data only locked table %ld in database %d due to an internal error.
Insert free space value %d in page header of DOL datapage %ld belonging to object id %ld in database ’%.*s’ is incorrect. It has been recomputed and is now %d. 

Number	Severity	Text and Explanation
1101	17	Unable to allocate new page for database `%.s'. There are no more pages available on valid allocation pages. Space can be created by dropping objects, extending the database, or dumping the log with no_log. 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. (Not raised in Release 11.0 and higher.)
1102	22	Unable to locate allocation page %ld for database `%.s'. This allocation page contains the extent that the target allocation page is in, but the allocation page is not in the translation table in the DBTABLE. Run DBCC CHECKTABLE on sysusages. Explanation:* A table or index may be corrupt. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1103	21	Allocation page %ld in database `%.s' has different segment id than that of the object to which we are allocating. Run DBCC CHECKALLOC. Explanation:* Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run. (Not raised in Release 11.0 and higher.)
1104	20	Conflict between number of extents marked in log record in the allocation bitmap and the allocation count. Allocation count is %d. Bitmap is 0x%lx 0x%lx 0x%lx 0x%lx. 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 (dbcc checkalloc) can be run on the database.
1105	17	Can't allocate space for object `%.s' in database `%.s' because `%.s' segment is full. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase size of the segment. Explanation:* Refer to the writeup for this error.
1106	20	First pass through allocation page %ld found %d free extents. After logging, only found %d free extents. 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. (Not raised in Release 11.0 and higher.)
1108	21	Cannot deallocate extent %ld, database %d. Object id %ld, index id %d, status %d in extent does not match object id %ld, index id %d, status %d in object being deallocated. Run DBCC CHECKALLOC. Explanation: Refer to the writeup for this error.
1109	21	Attempt to read allocation page %ld failed either because object ID is not correct (%ld) or the page ID is not correct (%ld). Explanation: Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run. (Not raised in Release 11.0 and higher.)
1110	20	Attempt to resource lock allocation page %ld in database `%.s' by process %d while allocating to non-syslogs object `%.s'. 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.
1111	20	Extent bitmap on allocation page %ld in database `%.s' does not have extents marked that are being removed. 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.
1112	20	Extent bitmap on allocation page %ld in database `%.s' already has extents marked that are being added. 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.
1113	20	Extent %ld already locked while allocating it in database `%.s'. 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.
1114	20	Attempt to resource lock page %ld in database `%.s' by process %d failed because lock is already held by process %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.
1115	20	Attempt to transfer a resource lock to process ID 0 on allocation page %ld in database `%.s'. 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.
1116	20	Attempt to backout the allocation of LOG page %ld, in database `%.s'. 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.
1117	21	Extent chain for object %ld is not correctly linked. Explanation: Refer to the writeup for this error.
1120	20	Adaptive Server failed to access page %ld in database ’%.s’ because it is not an allocation page. Explanation:* Refer to the writeup for this error.
1122	20	Attempt to read allocation page before openning SYSALLOCPGS. 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.
1123	20	Failed to get lock on OAM pg. 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.
1124	20	Failed to get lock on allocation page %ld. 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.
1125	20	Attempting to allocate page %ld in database %d to extent %ld which belongs to another object. Object id and index id in page are %ld, %ld. Object id and index id in extent are %ld, %ld. 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.
1127	20	Internal Error: The OAM has no room for new inserts. Check OAM for object %ld, index %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.
1128	22	The OAM entry for allocation page %ld is missing from the OAM which starts on page %ld. Explanation: A table or index may be corrupt. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1129	10	The requested update to the OAM for object %ld, dbid %ld, index %d, oam page %ld, would cause a negative page count. allocation page: %ld, oamarray used: %ld, oamarray unused: %ld, deltaused: %ld, deltaunused: %ld, spid: %ld. Contact your System Admin. Explanation: Refer to the writeup for this error.
1130	22	A dealloc log record has been detected which does not have an OAM page supplied. Explanation: A table or index may be corrupt. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1131	22	The OAM for object %ld, index %d, oam page %ld, database=%d, is currently allocated to another object. Explanation: See the writeup for Error 1131.
1132	22	Attempted to log allocation to the log. Explanation: Report the error to your System Administrator. Adaptive Server must be restarted.
1133	22	Page %ld was expected to be an OAM page for %ld and it is not. Explanation: Refer to the writeup for this error.
1134	20	Failed to get lock on OAM page %ld. This should never happen. 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.
1135	10	Page %ld was given as a target page for allocation to object %ld index id %d and there is no entry in the OAM for this page. This may indicate corruption of the OAM. Please run checkalloc on database %.s. Explanation:* There may be a potential problem with a database or database object. Contact your System Administrator.
1136	21	`Please run the upgrade38 utility before attempting to upgrade your database to MP.' Explanation: Adaptive Server encountered an internal error affecting all processes using the current database. Report the error to your System Administrator.
1137	21	`There is insufficient space in database %.s to run this upgrade.' Explanation:* Adaptive Server encountered an internal error affecting all processes using the current database. Report the error to your System Administrator.
1138	21	`Failed to complete allocation of SYSGAMS in database %.s.' Explanation:* Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1139	20	Impossible deadlock on page mgr lock. 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.
1140	20	`Page mgr lock should not already be held.' 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.
1141	20	Unexpected value returned to page manager routine: %ld. 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 (tablealloc, checkalloc) can be run.
1142	22	Invalid OAM Page %ld. Found pstat=0x%x, object=%ld, database=%d, indid=%d. Explanation: Refer to the writeup for this error.
1143	22	Invalid OAM Page %ld. Expected object=%ld. Found object=%ld, database=%d, pstat=0x%x, indid=%d. Explanation: Refer to the writeup for this error.
1144	21	Page number %ld is higher than the highest page in database `%.s': %ld. Explanation:* Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1145	20	ss %d was expected to hold logical lock on page %ld. 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 (checkalloc, tablealloc) can be run.
1146	20	Process %d was expected to hold logical lock on object %ld. 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 (checkalloc, tablealloc) can be run.
1147	20	Process %d trying to do a logged operation on a non-logged object %ld. 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.
1148	16	Error: %d, Severity: %d, State: %dn Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1149	21	A Log Run Deallocation routine was passed one or more bad parameters. The bad parameter is either %ld or %ld. Explanation: Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
1150	20	Failed to get intent lock on object %ld. 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.
1151	11	Object %ld passed to OAM builtin function no longer exists in database %d. Explanation: An OAM-related system function such as ROWCNT was called with incorrect arguments, or called for an object which has been dropped.
1152	11	Page %ld passed to OAM builtin function is not an OAM page for object %ld in database %d. Explanation: An OAM-related system function such as ROWCNT was called with incorrect arguments.
1153	11	OAM page %ld passed to rowcnt function is an unallocated page in database %d. Explanation: Check the arguments passed to the system function ROWCNT.
1154	16	WARNING!!! Attempt to do a prefetch of size %dK is not allowed. The prefetch request is reset to the maximum prefetch size of %dK. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1155	20	Invalid page validation type, %d, requested for page %ld, object %S_OBJID, indid %d in database %S_DBID. 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.
1156	20	Unable to update the page linkage status for the data only locked table %ld in database %d due to an internal error. 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.
1157	10	Insert free space value %d in page header of DOL datapage %ld belonging to object id %ld in database ’%.s’ is incorrect. It has been recomputed and is now %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.