Error Message 823 - bad page id

Hi,
we have problem with a corrupted database. The story is that accidentally
through restoring another database we have deleted this particular database.
We managed to recover the MDF and LDF file with GetDataBack, but the file
seems to be corrupted - both of them. When trying to attach this database but
we are getting the Error Message 823 - bad page id ... The worst is that we
have one month old backup. With MSSQLRecovery 2.1 we recovered 65% of the
data.
We have tried with DBCC CHECKDB( 'database_name' ,REPAIR_ALLOW_DATA_LOSS),
but no success.
Is there a possibility of getting all of the datas from the corrupted
database - please suggest ?
PLEASE CONSIDER THIS AS URGENT!
Rgds,
Bani.Might consider calling Microsoft Product Support at this point - see if
anything else is possible.
HTH
Jerry
"BaniSQL" <BaniSQL@.discussions.microsoft.com> wrote in message
news:1E07A841-84AC-40D0-938C-F37E11C32E12@.microsoft.com...
> Hi,
> we have problem with a corrupted database. The story is that accidentally
> through restoring another database we have deleted this particular
> database.
> We managed to recover the MDF and LDF file with GetDataBack, but the file
> seems to be corrupted - both of them. When trying to attach this database
> but
> we are getting the Error Message 823 - bad page id ... The worst is that
> we
> have one month old backup. With MSSQLRecovery 2.1 we recovered 65% of the
> data.
> We have tried with DBCC CHECKDB( 'database_name' ,REPAIR_ALLOW_DATA_LOSS),
> but no success.
> Is there a possibility of getting all of the datas from the corrupted
> database - please suggest ?
>
> PLEASE CONSIDER THIS AS URGENT!
> Rgds,
> Bani.
>|||Did you make a backup of the saved .mdf/.ldf before you started running dbcc
checkdb with repair_allow_data_loss? If not, you should do that now before
doing anything else to the files/database.
When you run checkdb with no parameters, what errors do you receive? When
you run it with the repair option, do any errors get repaired? If so, keep
running it iteratively until it corrects everything it can. Remember
though, this option will try to remove corrupted data, so you will most
likely lose that data.
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:%23IJoe32zFHA.2312@.TK2MSFTNGP14.phx.gbl...
> Might consider calling Microsoft Product Support at this point - see if
> anything else is possible.
> HTH
> Jerry
> "BaniSQL" <BaniSQL@.discussions.microsoft.com> wrote in message
> news:1E07A841-84AC-40D0-938C-F37E11C32E12@.microsoft.com...
>> Hi,
>> we have problem with a corrupted database. The story is that accidentally
>> through restoring another database we have deleted this particular
>> database.
>> We managed to recover the MDF and LDF file with GetDataBack, but the file
>> seems to be corrupted - both of them. When trying to attach this database
>> but
>> we are getting the Error Message 823 - bad page id ... The worst is that
>> we
>> have one month old backup. With MSSQLRecovery 2.1 we recovered 65% of the
>> data.
>> We have tried with DBCC CHECKDB( 'database_name'
>> ,REPAIR_ALLOW_DATA_LOSS),
>> but no success.
>> Is there a possibility of getting all of the datas from the corrupted
>> database - please suggest ?
>>
>> PLEASE CONSIDER THIS AS URGENT!
>> Rgds,
>> Bani.
>>
>|||Post the output from the following and I'll tell you what's wrong (I wrote
CHECKDB) and why repair isn't working:
DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:eSR0$%232zFHA.2312@.TK2MSFTNGP14.phx.gbl...
> Did you make a backup of the saved .mdf/.ldf before you started running
> dbcc checkdb with repair_allow_data_loss? If not, you should do that now
> before doing anything else to the files/database.
> When you run checkdb with no parameters, what errors do you receive? When
> you run it with the repair option, do any errors get repaired? If so,
> keep running it iteratively until it corrects everything it can. Remember
> though, this option will try to remove corrupted data, so you will most
> likely lose that data.
> "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> news:%23IJoe32zFHA.2312@.TK2MSFTNGP14.phx.gbl...
>> Might consider calling Microsoft Product Support at this point - see if
>> anything else is possible.
>> HTH
>> Jerry
>> "BaniSQL" <BaniSQL@.discussions.microsoft.com> wrote in message
>> news:1E07A841-84AC-40D0-938C-F37E11C32E12@.microsoft.com...
>> Hi,
>> we have problem with a corrupted database. The story is that
>> accidentally
>> through restoring another database we have deleted this particular
>> database.
>> We managed to recover the MDF and LDF file with GetDataBack, but the
>> file
>> seems to be corrupted - both of them. When trying to attach this
>> database but
>> we are getting the Error Message 823 - bad page id ... The worst is
>> that we
>> have one month old backup. With MSSQLRecovery 2.1 we recovered 65% of
>> the
>> data.
>> We have tried with DBCC CHECKDB( 'database_name'
>> ,REPAIR_ALLOW_DATA_LOSS),
>> but no success.
>> Is there a possibility of getting all of the datas from the corrupted
>> database - please suggest ?
>>
>> PLEASE CONSIDER THIS AS URGENT!
>> Rgds,
>> Bani.
>>
>>
>|||Hi Paul,
results from this statement are around 58 pages, so below I'm sending you
some lines:
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2130072865, index ID 12305, page ID (1:1114). The
PageId in the page header = (284:-212301230).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2091533571, index ID 11843, page ID (1:1032). The
PageId in the page header = (6850:1456308804).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2079391744, index ID 23016, page ID (1:255). The
PageId in the page header = (65280:1230385313).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2079326456, index ID 35669, page ID (1:273). The
PageId in the page header = (33807:556419).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2076457321, index ID 15901, page ID (1:1083). The
PageId in the page header = (42499:-766674058).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2059797435, index ID 34185, page ID (1:260). The
PageId in the page header = (0:2395407).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2054488064, index ID 1, page ID (1:268). The PageId
in the page header = (47125:-11534198).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2054291457, index ID 0, page ID (1:270). The PageId
in the page header = (65535:-1408243632).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID -2130072865)' (object ID -2130072865).
...........
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object
ID -2054488064)' (object ID -2054488064).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -2046820369, index ID 3840, page ID (1:252). The
PageId in the page header = (34238:251658240).
----
I will send you the results from DBCC
REBUILD_LOG(ABC,'C:\ABC\ABC_MS\1\ABC_log.LDF') as well:
Warning: The log for database 'ABC' has been rebuilt. Transactional
consistency has been lost. DBCC CHECKDB should be run to validate physical
consistency. Database options will have to be reset, and extra log files may
need to be deleted.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
----
And results from execute sp_resetstatus 'ABC':
Prior to updating sysdatabases entry for database 'ABC', mode = 0 and status
= 2048 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already
correctly reset. No error and no changes made.
----
From DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS if necessary I
can send you all the lines, but it was too much. If required I can send you
in this way or to your mail if you like.
Regards.
BaniSQL
"Paul S Randal [MS]" wrote:
> Post the output from the following and I'll tell you what's wrong (I wrote
> CHECKDB) and why repair isn't working:
> DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Lori Clark" <lclark@.dbadvisor.com> wrote in message
> news:eSR0$%232zFHA.2312@.TK2MSFTNGP14.phx.gbl...
> > Did you make a backup of the saved .mdf/.ldf before you started running
> > dbcc checkdb with repair_allow_data_loss? If not, you should do that now
> > before doing anything else to the files/database.
> >
> > When you run checkdb with no parameters, what errors do you receive? When
> > you run it with the repair option, do any errors get repaired? If so,
> > keep running it iteratively until it corrects everything it can. Remember
> > though, this option will try to remove corrupted data, so you will most
> > likely lose that data.
> >
> > "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
> > news:%23IJoe32zFHA.2312@.TK2MSFTNGP14.phx.gbl...
> >> Might consider calling Microsoft Product Support at this point - see if
> >> anything else is possible.
> >>
> >> HTH
> >>
> >> Jerry
> >> "BaniSQL" <BaniSQL@.discussions.microsoft.com> wrote in message
> >> news:1E07A841-84AC-40D0-938C-F37E11C32E12@.microsoft.com...
> >> Hi,
> >> we have problem with a corrupted database. The story is that
> >> accidentally
> >> through restoring another database we have deleted this particular
> >> database.
> >> We managed to recover the MDF and LDF file with GetDataBack, but the
> >> file
> >> seems to be corrupted - both of them. When trying to attach this
> >> database but
> >> we are getting the Error Message 823 - bad page id ... The worst is
> >> that we
> >> have one month old backup. With MSSQLRecovery 2.1 we recovered 65% of
> >> the
> >> data.
> >> We have tried with DBCC CHECKDB( 'database_name'
> >> ,REPAIR_ALLOW_DATA_LOSS),
> >> but no success.
> >> Is there a possibility of getting all of the datas from the corrupted
> >> database - please suggest ?
> >>
> >>
> >> PLEASE CONSIDER THIS AS URGENT!
> >>
> >> Rgds,
> >> Bani.
> >>
> >>
> >>
> >>
> >
> >
>
>|||It doesn't matter. Your data file looks like total garbage and now that
you've rebuilt the transaction log you've lost any semblance of
transactional consistency you may have been able to salvage.
You have no choice but to use your backup and learn from the lesson.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"BaniSQL" <BaniSQL@.discussions.microsoft.com> wrote in message
news:9DDC8C35-DED4-4277-9E1D-4AE34DEDB8F9@.microsoft.com...
> Hi Paul,
> results from this statement are around 58 pages, so below I'm sending you
> some lines:
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2130072865, index ID 12305, page ID (1:1114). The
> PageId in the page header = (284:-212301230).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2091533571, index ID 11843, page ID (1:1032). The
> PageId in the page header = (6850:1456308804).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2079391744, index ID 23016, page ID (1:255). The
> PageId in the page header = (65280:1230385313).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2079326456, index ID 35669, page ID (1:273). The
> PageId in the page header = (33807:556419).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2076457321, index ID 15901, page ID (1:1083). The
> PageId in the page header = (42499:-766674058).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2059797435, index ID 34185, page ID (1:260). The
> PageId in the page header = (0:2395407).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2054488064, index ID 1, page ID (1:268). The
> PageId
> in the page header = (47125:-11534198).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2054291457, index ID 0, page ID (1:270). The
> PageId
> in the page header = (65535:-1408243632).
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> '(Object
> ID -2130072865)' (object ID -2130072865).
> ...........
> CHECKDB found 0 allocation errors and 1 consistency errors in table
> '(Object
> ID -2054488064)' (object ID -2054488064).
> Server: Msg 8909, Level 16, State 1, Line 1
> Table error: Object ID -2046820369, index ID 3840, page ID (1:252). The
> PageId in the page header = (34238:251658240).
> ----
> I will send you the results from DBCC
> REBUILD_LOG(ABC,'C:\ABC\ABC_MS\1\ABC_log.LDF') as well:
> Warning: The log for database 'ABC' has been rebuilt. Transactional
> consistency has been lost. DBCC CHECKDB should be run to validate physical
> consistency. Database options will have to be reset, and extra log files
> may
> need to be deleted.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> ----
> And results from execute sp_resetstatus 'ABC':
> Prior to updating sysdatabases entry for database 'ABC', mode = 0 and
> status
> = 2048 (status suspect_bit = 0).
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
> ----
> From DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS if necessary I
> can send you all the lines, but it was too much. If required I can send
> you
> in this way or to your mail if you like.
> Regards.
> BaniSQL
> "Paul S Randal [MS]" wrote:
>> Post the output from the following and I'll tell you what's wrong (I
>> wrote
>> CHECKDB) and why repair isn't working:
>> DBCC CHECKDB (dbname) WITH ALL_ERRORMSGS, NO_INFOMSGS
>> --
>> Paul Randal
>> Dev Lead, Microsoft SQL Server Storage Engine
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Lori Clark" <lclark@.dbadvisor.com> wrote in message
>> news:eSR0$%232zFHA.2312@.TK2MSFTNGP14.phx.gbl...
>> > Did you make a backup of the saved .mdf/.ldf before you started running
>> > dbcc checkdb with repair_allow_data_loss? If not, you should do that
>> > now
>> > before doing anything else to the files/database.
>> >
>> > When you run checkdb with no parameters, what errors do you receive?
>> > When
>> > you run it with the repair option, do any errors get repaired? If so,
>> > keep running it iteratively until it corrects everything it can.
>> > Remember
>> > though, this option will try to remove corrupted data, so you will most
>> > likely lose that data.
>> >
>> > "Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
>> > news:%23IJoe32zFHA.2312@.TK2MSFTNGP14.phx.gbl...
>> >> Might consider calling Microsoft Product Support at this point - see
>> >> if
>> >> anything else is possible.
>> >>
>> >> HTH
>> >>
>> >> Jerry
>> >> "BaniSQL" <BaniSQL@.discussions.microsoft.com> wrote in message
>> >> news:1E07A841-84AC-40D0-938C-F37E11C32E12@.microsoft.com...
>> >> Hi,
>> >> we have problem with a corrupted database. The story is that
>> >> accidentally
>> >> through restoring another database we have deleted this particular
>> >> database.
>> >> We managed to recover the MDF and LDF file with GetDataBack, but the
>> >> file
>> >> seems to be corrupted - both of them. When trying to attach this
>> >> database but
>> >> we are getting the Error Message 823 - bad page id ... The worst is
>> >> that we
>> >> have one month old backup. With MSSQLRecovery 2.1 we recovered 65% of
>> >> the
>> >> data.
>> >> We have tried with DBCC CHECKDB( 'database_name'
>> >> ,REPAIR_ALLOW_DATA_LOSS),
>> >> but no success.
>> >> Is there a possibility of getting all of the datas from the corrupted
>> >> database - please suggest ?
>> >>
>> >>
>> >> PLEASE CONSIDER THIS AS URGENT!
>> >>
>> >> Rgds,
>> >> Bani.
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>