Post reply

Allocation page error

  • February 14, 2010 at 2:52 am

    #219113

    Hi All

    Could someone help me please?

    Intance: SQL Server 2000

    I ran a dbcc checkdb because an insert job failed and I got the next msg:

    Server: Msg 8946, Level 16, State 12, Line 2

    Table error: Allocation page (1:4197672) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.

    Server: Msg 7995, Level 16, State 1, Line 1

    Database 'Database_Name' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKDB processing.

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    I don't know if a DBCC CHECKALLOC could repair this problem, could someone help me?

    Thanks in advance.

    Best Regards

  • February 14, 2010 at 3:47 am

    #1118549

    Did you check with Gails wonderful article ?

    http://www.sqlservercentral.com/articles/Corruption/65804/

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • February 14, 2010 at 5:19 am

    #1118552

    Looking into the article.

    I'll let you know what about it.

    Thanks for replying.

    Regards

  • February 14, 2010 at 7:15 am

    #1118564

    You've got damage to the allocation structures in this database. It's bad enough that CheckDB can't even check the entire database because it can't tell how things are supposed to be.

    There is no fix for this error. Get out your latest backup. If the DB is in full recovery and you have an unbroken chain of log backups then take a tail log backup before you start to restore, restore the full, all the log backups and end with the tail log. That way you'll lose nothing.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • February 14, 2010 at 3:01 pm

    #1118617

    You've got a damaged PFS allocation page - that's an error that I couldn't write a 100% correct all the time repair for. As Gail says, you must restore from your backups - there's a 64MB chunk of the database that can't be accessed properly.

    Thanks

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • February 15, 2010 at 12:40 am

    #1118685

    Hi all

    Thanks for the tips.

    I did the next:

    1. I took the last good backup and I retored it in another server.

    2. Got my incremental tables and send it to the new server.

    3. Make a new backup from the new server.

    4. Restored it in the old server.

    5. I got the same error running the dbcc checkdb.

    I thought that it was a problem with the hardware, so I did the next:

    1. I took the last good backup and I retored it in another server.

    2. Got my incremental tables and send it to the new server.

    3. Make a new backup from the new server.

    4. Created a new DB in the old server in another drive.

    5. Rename my DB.

    5. Rename my new DB as the old one.

    6. Everything looks ok after running the dbcc.

    I hope not receive another issue with this.

    Best regards

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

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