Sybase 11.9.x-12.5 - Manual (Page 526)

Server Error Messages 12900 - 12999
1200
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.
Number Severity Text and Explanation