Re: DBCC CHECKDB Errors

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/17/04 

Date: Wed, 17 Mar 2004 16:49:05 +0100

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
>
>
>
>
>
>

Relevant Pages

  • Re: Attempt to fetch logical page
    ... You have a corruption in your database. ... Second, if you are on SQL Server 2000, check the specific recommendations for your error. ... This error occurs when Microsoft® SQL ServerT detects database corruption. ... execute DBCC CHECKDB to determine the extent of the damage. ...
    (microsoft.public.sqlserver.server)
  • Re: Table Corrupt
    ... What is the version/edition of SQL Server you are using. ... Set the database to sincle user mode (Alter database Single_user ... Ensure that TEMPDB have enough space, because DBCC CHECKDB uses tempdb ...
    (microsoft.public.sqlserver.mseq)
  • RE: SQL server restore
    ... Could you please tell me why you cannot run dbcc checkdb to check the all ... the database in your SQL Server? ... This posting is provided "as is" with no warranties and confers no rights. ...
    (microsoft.public.sqlserver.server)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)