checkdb error - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

checkdb error

Author

Topic

vcanez
Starting Member

3 Posts

Posted - 2008-08-08 : 13:35:08

Hi, i'm running accpac on sql server 2005. I had a power failure while doing a day end in accpac and now I have the following error when i do a dbcc checkdb.... what can i do to fix this problem. I need help please. thank you
......
Msg 8946, Level 16, State 12, Line 1
Table error: Allocation page (1:2264640) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
DBCC results for 'VCZDAT'.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:2264640) to (1:2272727). See other errors for cause.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page (1:2264640). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270729 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page (1:2264640). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270729 and -4.
CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 2 allocation errors and 1 consistency errors in database 'VCZDAT'.

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2008-08-08 : 14:52:18

Looks like you will have to restore the database from the latest backup. The GAM page (Global Allocation Map) corruption is not curable, as far as I know.

If you can do a select * from each of the tables, you can probably export the data to a new (clean) database. Not sure what state the data would be in, since the day end procedure was caught in the middle, though.

vcanez
Starting Member

3 Posts

Posted - 2008-08-08 : 15:46:41

I also ran a checkalloc and this is part of the message. There's definitely no solution to fix this problem. I have no other choice to restore from a backup.

DBCC results for 'VCZDAT'.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:2264640) to (1:2272727). See other errors for cause.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page (1:2264640). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 79825161 and -4.
CHECKALLOC found 2 allocation errors and 0 consistency errors not associated with any single object.
***************************************************************
Table sys.sysrowsetcolumns Object ID 4.
Index ID 1, partition ID 262144, alloc unit ID 262144 (type In-row data). FirstIAM (1:139). Root (1:66). Dpages 0.
Index ID 1, partition ID 262144, alloc unit ID 262144 (type In-row data). 239 pages used in 29 dedicated extents.

.....

The total number of extents = 313976, used pages = 2422742, and reserved pages = 2511766 in this database.
(number of mixed extents = 830, mixed pages = 6598) in this database.
CHECKALLOC found 2 allocation errors and 0 consistency errors in database 'VCZDAT'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Total number of extents is 29.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2008-08-09 : 04:25:31

Find your latest backup and restore. If you're in full recovery mode and are doing transaction log backups make sure to backup the tail of the log first. That way you can get 0 data loss.

Corruption in the allocation pages or system objects is not fixable by checkDB.

--
Gail Shaw
SQL Server MVP

vcanez
Starting Member

3 Posts

Posted - 2008-08-09 : 10:29:28

My latest backup before the power failure is wednesday night, if I restore that one, I loss 3 days of work (thurs, frid, sat. Is there a way for me to recuperate the data from the backups of (thurs, frid, sat) and tranfer the data over.

What is my situation if I continue using this database as is.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2008-08-09 : 14:03:40

What recovery model is your database in? Are you doing transaction log backups?

That database is unusable. I doubt it will take long before SQL marks it as suspect if it isn't already. There will be data that you can't access, queries that throw severity 23 or higher errors and other massive problems.

Bear in mind that the longer you wait, the more data you stand to lose. There is no chance of having a clean backup made after this.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources