12.07.2015 Views

General Error Messages - InterSystems Documentation

General Error Messages - InterSystems Documentation

General Error Messages - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

TSQL <strong>Error</strong> <strong>Messages</strong><strong>Error</strong> Code89798980898189828983898489858986898789888989899089918992899389948995899689978998DescriptionTable error: Object ID %d, index ID %d. Page %S_PGID is missing referencesfrom parent (unknown) and previous (page %S_PGID) nodes. Possible bad rootentry in sysindexes.Table error: Object ID %d, index ID %d. Index node page %S_PGID, slot %drefers to child page %S_PGID and previous child %S_PGID, but they were notencountered.Table error: Object ID %d, index ID %d. The next pointer of %S_PGID refers topage %S_PGID. Neither %S_PGID nor its parent were encountered. Possiblebad chain linkage.Table error: Cross object linkage. Page %S_PGID->next in object ID %d, indexID %d refers to page %S_PGID in object ID %d, index ID %d but is not in thesame index.File %d. Extents %d, used pages %d, reserved pages %d, mixed extents %d,mixed pages %d.Object ID %d, index ID %d. Allocations for %S_PGID. IAM %S_PGID, extents%d, used pages %d, mixed pages %d.Could not locate file '%.*ls' in sysfiles.Too many errors found (%d) for object ID %d. To see all error messages rerunthe statement using "WITH ALL_ERRORMSGS".No help available for DBCC statement '%.*ls'.The schema for database '%ls' is changing. May find spurious allocation problemsdue to schema changes in progress.%.*ls found %d allocation errors and %d consistency errors in database '%ls'.%.*ls found %d allocation errors and %d consistency errors in table '%ls' (objectID %d).0x%.8x + 0x%.8x bytes is not a valid address range.Database ID %d, object '%ls' (ID %d). Loop in data chain detected at %S_PGID.Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID,slot %d. Did not encounter forwarded row. Possible allocation error.Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to byforwarding row page %S_PGID, slot %d. Did not encounter forwarding row.Possible allocation error.System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All systemtables must be in filegroup %d.IAM page %S_PGID for object ID %d, index ID %d controls pages in filegroup%d, that should be in filegroup %d.Single page allocation %S_PGID for object ID %d, index ID %d is in filegroup%d; it should be in filegroup %d.Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC toverify database ID %d pages from %S_PGID to %S_PGID. See other errors forcause.Caché <strong>Error</strong> Reference 169

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!