22
The OAM for object %ld, index %d, oam page %ld, database=%d, is currently allocated to another object.
The object allocation map (OAM) tracks information about the allocation and deallocation of storage space for tables and indexes. At least one OAM page exists for each table (except syslogs and sysgams) and for the table’s indexes. Each allocation page used by the object has an entry in the OAM page, showing the number of used and unused data/index pages on that allocation page.
Error 1131 is raised when Adaptive Server attempts to validate an OAM page belonging to an object, and determines that the page is actually allocated to a different object.
Error 1131 occurs with the following states:
State |
Meaning |
|---|---|
1 |
While updating the used and unused counts for an OAM entry, the OAM page is found to be allocated to a different object. This error is raised only by diagserver. |
2 |
(Version 15.0 and later) While checking the validity of an OAM page, the page is allocated to a different object. |
3 |
(Version pre-15.0) While checking the validity of an OAM page, the page is allocated to a different object. |
1131 errors are often seen when you use the system functions data_pgs, reserved_pgs, used_pgs, or rowcnt in a very active database, or a highly volatile database such as tempdb, where objects are being created and dropped frequently. The error can occur when:
You use and invalid <object id> in the function
The page is allocated to another object, or is uninitialized
Use trace flag 1116 to suppress the 1131 error when using these system functions in an active or volatile database environment.
See “Starting Adaptive Server with trace flags” in the “Other Useful Tasks” chapter of the most recent version of the Troubleshooting and Disaster Recovery guide.
All versions
