Post reply

Table allocation error

  • March 16, 2003 at 9:33 pm

    #63268

    I run a weekly database integrity check (part of the Database Mantinenace plan). Everything was fine until Friday when I got the table allocation error shown below. Other than restoring an old copy of the database, then restoring the old table (and losing data) what would you do?

    TIA,

    Bill

    [21] Database Rapper: Check Data and Index Linkage...

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8946: [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Allocation page (1:347784) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space

    <<<< there is plenty of room in tempdb>>>>>

    or a system table is inconsistent. Check previous errors.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Could not read and latch page (1:347784) with latch type UP. VerifyPageId failed.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Extent (1:348248) object ID 309576141, index ID 0 is beyond the range of this database.

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors in table 'uSubProjectDepartment' (object ID 309576141).

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 1 consistency errors in database 'Rapper'.

  • March 19, 2003 at 8:00 am

    This was removed by the editor as SPAM

  • March 19, 2003 at 10:24 am

    #451463

    are you letting checkdb to fix the errors?

  • March 19, 2003 at 3:05 pm

    #451489

    Exactly... CHECKDB should be able to fix minor errors....

    .

  • March 19, 2003 at 8:22 pm

    #451516

    quote:

    Exactly... CHECKDB should be able to fix minor errors....

    Ya know ... I didn't try CHECKDB! I have never seen a database error like this one before and I almost felt afraid to use CHECKDB for fear of screwing up the database all the more (if that is possible). I'll try CheckDB and get back to you.

    Thanks,

    Bill

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply