Re: DBCC CHECKDB Errors

From: Prasad Koukuntla (prasad.koukuntla_at_scapromo.com)
Date: 03/17/04 

Date: Wed, 17 Mar 2004 10:39:00 -0600

Thank you Tibor.

"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in
message news:%23SPFgdDDEHA.2804@tk2msftngp13.phx.gbl...
> Here's a start if you have corruption of a suspect database:
>
> http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
>
> "Prasad Koukuntla" <prasad.koukuntla@scapromo.com> wrote in message
> news:erelMZDDEHA.3784@TK2MSFTNGP10.phx.gbl...
> > Yesterday, we noticed that one of our RAID 5 drives failed.
> >
> > Then, I got the following errors when I ran the DBCC Checkdb on my
> database.
> >
> > Server: Msg 2533, Level 16, State 1, Line 1
> > Table error: Page (1:199065) allocated to object ID 1006626629, index ID
0
> > was not seen. Page may be invalid or have incorrect object ID
information
> > in its header.
> > Server: Msg 2533, Level 16, State 1, Line 1
> > Table error: Page (1:199066) allocated to object ID 1006626629, index ID
0
> > was not seen. Page may be invalid or have incorrect object ID
information
> > in its header.
> > Server: Msg 8976, Level 16, State 1, Line 1
> > Table error: Object ID 1006626629, index ID 1. Page (1:199065) was not
> seen
> > in the scan although its parent (1:198489) and previous (1:199064) refer
> to
> > it. Check any previous errors.
> > Server: Msg 8980, Level 16, State 1, Line 1
> > Table error: Object ID 1006626629, index ID 1. Index node page
(1:198489),
> > slot 177 refers to child page (1:199066) and previous child (1:199065),
> but
> > they were not encountered.
> > Server: Msg 8978, Level 16, State 1, Line 1
> > Table error: Object ID 1006626629, index ID 1. Page (1:199067) is
missing
> a
> > reference from previous page (1:199066). Possible chain linkage problem.
> > CHECKDB found 0 allocation errors and 5 consistency errors in table
> > 'INT_AUX_LST_CUSTOM' (object ID 1006626629).
> > CHECKDB found 0 allocation errors and 5 consistency errors in database
> > 'sca_master'.
> > repair_allow_data_loss is the minimum repair level for the errors found
by
> > DBCC CHECKDB (sca_master ).
> >
> >
> > I found nothing on error 2533.
> > I found the following on other errors and suggest that these errors were
> > correctd in service pack 1. However, I am already running SQL SERVER
SP3,
> > with hotfix.
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;291566
> >
> > I think the above errors occurred because of the drive failure. We
replace
> > the failed drive but these errors are still coming up.
> > The server is still online and being used by the users.
> >
> > Questions:
> > If I run the DBCC CHECKDB with repair_allow_data_loss option, is
there
> > any way of finding how much data is lost?
> > Is there any way to avoid no data loss?
> >
> > Thanks in advance.
> >
> > Prasad Koukuntla
> >
> >
> >
> >
> >
> >
>
>