Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

DBCC CheckDb Error Message Expand / Collapse
Author
Message
Posted Wednesday, February 12, 2014 2:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 12, 2014 4:04 AM
Points: 7, Visits: 28
Hi,

I'm trying to recover a database which unfortunately we don't have any backups of.

I have ran the following command "DBCC CHECKDB ('CustomerAccounts') WITH TABLOCK, ALL_ERRORMSGS, NO_INFOMSGS;"

And I'm getting this error:

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 8968, Level 16, State 1, Line 1
Table error: SinglePage page (0:249856) (object ID 485576768, index ID 2, partition ID 72057594097827840, alloc unit ID 72057594105167872 (type In-row data)) is out of the range of this database.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'CTL_DBCONFIG' (object ID 485576768).
CHECKDB found 1 allocation errors and 0 consistency errors in database 'CustomerAccounts'.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x369dfd27; actual: 0xd5f0c896). It occurred during a read of page (1:1599) in database ID 7 at offset 0x00000000c7e000 in file 'D:\Act Database Files\CustomerAccounts.ADF'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Please could someone advise.
Post #1540597
Posted Wednesday, February 12, 2014 4:03 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:03 AM
Points: 41,548, Visits: 34,470
You are not going to like the answer...

That's not repairable. Script all objects (and hope that none fail), export all data (and some may fail), recreate the database.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1540616
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse