Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


errors found by DBCC CHECKDB


errors found by DBCC CHECKDB

Author
Message
ashkan sirous
ashkan sirous
SSC-Enthusiastic
SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)

Group: General Forum Members
Points: 109 Visits: 255
Dear friends ,
I was wondering about this situation.
After some search i have find out that many people has this problem.
worst one has a Db about 6 Tera Byte and...

Do you know why this kind of errors happening?
I mean Why SQLServer makes pages with errors like this?

For example :
Page (1:1000698) in database ID 65 is allocated in the SGAM (1:511233) and PFS (1:994824), but was not allocated in any IAM.

Thanks and regards,
Ashkan
GilaMonster
GilaMonster
SSC Guru
SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)

Group: General Forum Members
Points: 54687 Visits: 44657
SQL Server doesn't. Corruption is, in the vast majority of cases due to a faulty IO subsystem. That means that there's a problem somewhere in your drives, san controller, fibre switch, firmware, cables, etc.

If you want help fixing, run the following and post the fill and unedited results

DBCC CHECKDB (<Database Name>Wink WITH NO_INFOMSGS, ALL_ERRORMSGS



Take a look at this article. http://www.sqlservercentral.com/articles/65804/

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


ashkan sirous
ashkan sirous
SSC-Enthusiastic
SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)

Group: General Forum Members
Points: 109 Visits: 255
Dear Gail,
Thanks for reply,

I have used that command and it returned about 3000 line of error code:
This is last lines.

Server: Msg 8948, Level 16, State 1, Line 1
Database error: Page (1:7335) is marked with the wrong type in PFS page (1:1). PFS status 0x70 expected 0x60.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:7335) with latch type SH. VerifyPageId failed.
CHECKDB found 1563 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 1563 allocation errors and 0 consistency errors in database 'FAQ'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (FAQ ).


Then I used this commands:
ALTER DATABASE FAQ
SET single_user WITH ROLLBACK IMMEDIATE;
go
DBCC checkdb ('FAQ', repair_allow_data_loss);
go
it returned 500 line of report (some errors and some repaired text) with this line at the end;

CHECKDB found 1000 allocation errors and 0 consistency errors in database 'FAQ'.
CHECKDB fixed 500 allocation errors and 0 consistency errors in database 'FAQ'.
repair_fast is the minimum repair level for the errors found by DBCC CHECKDB (FAQ repair_allow_data_loss).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

then i used :
ALTER DATABASE FAQ

SET single_user WITH ROLLBACK IMMEDIATE;

go

DBCC checkdb ('FAQ',repair_fast );

go

and it returned 500 line of report (some errors and some repaired text) with this line at the end(like before);
CHECKDB found 1000 allocation errors and 0 consistency errors in database 'FAQ'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (FAQ repair_fast).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

and the loop is continued.
what should i do now??!!?!?Sad


Thanks and regards,
Ashkan
ashkan sirous
ashkan sirous
SSC-Enthusiastic
SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)

Group: General Forum Members
Points: 109 Visits: 255
I think i should post a new topic for this errorSad

Thanks and regards,
Ashkan
GilaMonster
GilaMonster
SSC Guru
SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)

Group: General Forum Members
Points: 54687 Visits: 44657
ashkan siroos (10/16/2010)
Dear Gail,
Thanks for reply,

I have used that command and it returned about 3000 line of error code:


I need to see them ALL to give you any useful advice. Save the list in a text file, zip and attach to your post.

Then I used this commands:
ALTER DATABASE FAQ
SET single_user WITH ROLLBACK IMMEDIATE;
go
DBCC checkdb ('FAQ', repair_allow_data_loss);
go
it returned 500 line of report (some errors and some repaired text) with this line at the end;


*sigh* Repair is never the first resort for fixing corruption. Done is done I suppose, do you have any idea how much data the repair lost?



and the loop is continued.
what should i do now??!!?!?Sad


Without seeing all the errors, I can't give you a definitive answer, but likely either you have an IO subsystem that's producing corruption faster than you can fix it, or you have something that's irreparable.

Do you have a clean backup of this database?

I think i should post a new topic for this error


I think you should not. No point having multiple posts for the same problem, one will just get locked.

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


ashkan sirous
ashkan sirous
SSC-Enthusiastic
SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)

Group: General Forum Members
Points: 109 Visits: 255
Ok , i don't know how to upload text file here so i will paste it here:
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6836) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6836) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6837) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6837) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6838) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6838) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6839) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6839) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6840) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6840) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6841) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6841) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6842) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6842) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6843) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6843) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6844) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6844) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6845) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6845) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6846) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6846) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6847) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6847) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6848) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6848) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6849) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6849) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6850) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6850) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6851) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6851) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6852) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6852) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6853) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6853) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6854) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:6854) with latch type SH. VerifyPageId failed.
Server: Msg 8906, Level 16, State 1, Line 1
Page (1:6855) in database ID 11 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.

Thanks and regards,
Ashkan
ashkan sirous
ashkan sirous
SSC-Enthusiastic
SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)

Group: General Forum Members
Points: 109 Visits: 255
Sad I cant paste it allSad
how can i upload a file here?

Thanks and regards,
Ashkan
WayneS
WayneS
SSCertifiable
SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)SSCertifiable (7K reputation)

Group: General Forum Members
Points: 6975 Visits: 10434
When composing your post, look below, in the "Post Options" section. There is a section titled "Attachments", with a button on the right that says "Edit Attachments". Click that button. In the popup, click the "Browse" button, select the file to upload. Click the "Upload Attachments" button. Click the "Close Window" link.

Then, click on the "Post Reply" button.

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
Links: For better assistance in answering your questions, How to ask a question, Performance Problems, Common date/time routines,
CROSS-TABS and PIVOT tables Part 1 & Part 2, Using APPLY Part 1 & Part 2, Splitting Delimited Strings

GilaMonster
GilaMonster
SSC Guru
SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)

Group: General Forum Members
Points: 54687 Visits: 44657
Zip your text file and then attach it.

Also, what's the output of the following?
SELECT @@version

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


ashkan sirous
ashkan sirous
SSC-Enthusiastic
SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)SSC-Enthusiastic (109 reputation)

Group: General Forum Members
Points: 109 Visits: 255
I have attached the file and also the output of @@version is:

Microsoft SQL Server 2000 - 8.00.2055 (Intel X86) Dec 16 2008 19:46:53 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Thanks and regards,
Ashkan
Attachments
faqError.rar (13 views, 2.00 KB)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search