| Author |
Topic |
|
serrano
Starting Member
6 Posts |
 Posted - 2011-10-03 : 19:11:22
|
| Hello guys, im in a bit of a bind:A partitioned database got wiped and then block-restored (no other backup available), it's now attached but wont go online since the log files are gone.Upon starting SQL service, the db went in suspect mode, so i put it in emergency & single_user and executed dbcc checkdb('dbname',repair_allow_data_loss).After a few seconds i get the result that there is not enough of database data to begin restoring the log.The database is again put in suspect-mode and i'm back where i started.Is the situation beyond all hope of repair? Biting nails here, any ideas? |
|
|
Sachin.Nand
2937 Posts |
Posted - 2011-10-04 : 00:38:42
|
What is the exact error statement returned ?Also what does this return dbcc checkdb('YourDB') with estimateonlyPBUH |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2011-10-04 : 01:42:00
|
| 1) have you checked logs \ event viewer for any clues?2) firstly, don't attempt to change status , untill you've assessed everything3) Have you tried a server restart?Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
serrano
Starting Member
6 Posts |
Posted - 2011-10-04 : 02:50:43
|
| As i started dbcc checkdb('YourDB') with estimateonly, some errors were written to event log:SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:8743947; actual 0:0). It occurred during a read of page (1:8743947) in database ID 6 at offset 0x000010ad816000 in file 'F:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\db_name.mdf'. 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.the statement returned in SSMS: Msg 0, Level 11, State 0, Line 0A severe error occurred on the current command. The results, if any, should be discarded. |
|
|
|
serrano
Starting Member
6 Posts |
Posted - 2011-10-04 : 02:52:03
|
quote:
Originally posted by jackv
1) have you checked logs \ event viewer for any clues?2) firstly, don't attempt to change status , untill you've assessed everything3) Have you tried a server restart?Jack Vamvas--------------------http://www.sqlserver-dba.com
Server was shutdown during the restore, when started up the db was automaticly attached but put in suspect mode. |
|
|
|
serrano
Starting Member
6 Posts |
Posted - 2011-10-04 : 03:10:29
|
quote:
Originally posted by Sachin.Nand
What is the exact error statement returned ?Also what does this return PBUH
Msg 5028, Level 16, State 4, Line 1The system could not activate enough of the database to rebuild the log.DBCC results for 'db_name'.CHECKDB found 0 allocation errors and 0 consistency errors in database 'db_name'.Msg 926, Level 14, State 1, Line 1Database 'db_name' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. |
|
|
|
serrano
Starting Member
6 Posts |
Posted - 2011-10-04 : 03:56:52
|
| Properties cannot be viewed for the db either:Cannot show requested dialog. (SqlMgmt)------------------------------Property Size is not available for Database '[dbname]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1777.0+((KJ_RTM_QFE-CU).110408-1400+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=Size&LinkId=20476 |
|
|
|
serrano
Starting Member
6 Posts |
Posted - 2011-10-04 : 05:44:57
|
| Just running DBCC CHECKDB('dbname') returned a lot of this:Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:2491104) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).Msg 8998, Level 16, State 2, Line 1Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 6 pages from (1:2491104) to (1:2499191). See other errors for cause.Msg 8909, Level 16, State 1, Line 1 |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-10-04 : 05:55:41
|
| I'm going to only answer this at SSC. I would advice that you pick one person's advice to follow and follow that. Multiple 'cooks' for a corruption question are not a good thing in general.--Gail ShawSQL Server MVP |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2011-10-04 : 06:34:07
|
| Can you provide a link Gail? - I'd be interested to follow the conversation. |
|
|
|
Sachin.Nand
2937 Posts |
|
|
|
dbcc checkdb fails (nightmare scenario)