SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


DB corrupted with event 17052 and Error: 823, Severity: 24, State: 2


DB corrupted with event 17052 and Error: 823, Severity: 24, State: 2

Author
Message
crazy4sql
crazy4sql
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1681 Visits: 4489
as mentioned earlier, the database is gone. Look for some backup if they have, if not then they can learn from this disaster.

----------
Ashish
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87205 Visits: 45271
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

There's far more wrong here than just a suspect DB. You've got access violations all over the error log. This is one sick server. I'd suggest calling CSS, but SQL 2000 is out of support so they won't help you.

Your also running on a very low service pack of SQL 2000. SQL 8.0.818. Offhand I don't know what service pack that is, but it's not the last one available. I strongly suggest you patch that server to the latest service pack and consider an upgrade to 2008.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


halifaxdal
halifaxdal
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1969 Visits: 1744
GilaMonster (9/13/2011)
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

There's far more wrong here than just a suspect DB. You've got access violations all over the error log. This is one sick server. I'd suggest calling CSS, but SQL 2000 is out of support so they won't help you.

Your also running on a very low service pack of SQL 2000. SQL 8.0.818. Offhand I don't know what service pack that is, but it's not the last one available. I strongly suggest you patch that server to the latest service pack and consider an upgrade to 2008.


I certainly will try your advise and for sure I will upgrade it to 08/05 if I will be designated to take over this server/db, for now, I just want to try my best effort to see how much I can get the data back.

818 is SP2, can't believe it, eh? Me too.
Ninja's_RGR'us
Ninja's_RGR'us
One Orange Chip
One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)

Group: General Forum Members
Points: 28843 Visits: 9671
halifaxdal (9/13/2011)
[quote]GilaMonster (9/13/2011)
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

There's far more wrong here than just a suspect DB. You've got access violations all over the error log. This is one sick server. I'd suggest calling CSS, but SQL 2000 is out of support so they won't help you.

Your also running on a very low service pack of SQL 2000. SQL 8.0.818. Offhand I don't know what service pack that is, but it's not the last one available. I strongly suggest you patch that server to the latest service pack and consider an upgrade to 2008.


I certainly will try your advise and for sure I will upgrade it to 08/05 if I will be designated to take over this server/db, for now, I just want to try my best effort to see how much I can get the data back.

818 is SP2, can't believe it, eh? Me too.[/quote

It's actually more Around SP3

http://www.aspfaq.com/sql2000builds.asp


You're only 5 years behind on the patches :-D.


Denali's coming out in a few months if you can wait it out Whistling
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87205 Visits: 45271
halifaxdal (9/13/2011)
GilaMonster (9/13/2011)
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

There's far more wrong here than just a suspect DB. You've got access violations all over the error log. This is one sick server. I'd suggest calling CSS, but SQL 2000 is out of support so they won't help you.

Your also running on a very low service pack of SQL 2000. SQL 8.0.818. Offhand I don't know what service pack that is, but it's not the last one available. I strongly suggest you patch that server to the latest service pack and consider an upgrade to 2008.


I certainly will try your advise and for sure I will upgrade it to 08/05 if I will be designated to take over this server/db, for now, I just want to try my best effort to see how much I can get the data back.

818 is SP2, can't believe it, eh? Me too.


p.s. That should not be done on the production server...

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


halifaxdal
halifaxdal
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1969 Visits: 1744
GilaMonster (9/13/2011)
halifaxdal (9/13/2011)
GilaMonster (9/13/2011)
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.

There's far more wrong here than just a suspect DB. You've got access violations all over the error log. This is one sick server. I'd suggest calling CSS, but SQL 2000 is out of support so they won't help you.

Your also running on a very low service pack of SQL 2000. SQL 8.0.818. Offhand I don't know what service pack that is, but it's not the last one available. I strongly suggest you patch that server to the latest service pack and consider an upgrade to 2008.


I certainly will try your advise and for sure I will upgrade it to 08/05 if I will be designated to take over this server/db, for now, I just want to try my best effort to see how much I can get the data back.

818 is SP2, can't believe it, eh? Me too.


p.s. That should not be done on the production server...


I wish I don't have to do this on prod, unfortunately now it's the prod that crashed, and no backup elsewhere, so other than doing this directly on prod, what can I do?Hehe
crazy4sql
crazy4sql
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1681 Visits: 4489

Denali's coming out in a few months if you can wait it out Whistling


As much I am aware about denali, you cant upgrade sql 2000 database to denali directly. You need to upgrade it to either 2005 or 2008 and then denali.

Microsoft gives the explanation for this:- We expect your environment should be upgraded to at least 2005 by now.

----------
Ashish
halifaxdal
halifaxdal
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1969 Visits: 1744


Denali's coming out in a few months if you can wait it out Whistling


That would be probably next year!

Those guys are chasing me and expecting me to make it working in one day!Crying
Ninja's_RGR'us
Ninja's_RGR'us
One Orange Chip
One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)

Group: General Forum Members
Points: 28843 Visits: 9671
halifaxdal (9/13/2011)


Denali's coming out in a few months if you can wait it out Whistling


That would be probably next year!

Those guys are chasing me and expecting me to make it working in one day!Crying


Time for a meeting about the sla, rpo & rto and buying more disk space and allotting the time you need to setup DR all over the place.
halifaxdal
halifaxdal
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1969 Visits: 1744
Ninja's_RGR'us (9/13/2011)
[quote]halifaxdal (9/13/2011)
[quote]GilaMonster (9/13/2011)
Run SP_configure and set allow updates to 1. Update sysdatabases for that database and set the status to 32767.

Then see if you can access the DB and run checkdb. Not repair, just with the no_infomsgs and all_errormsgs options.


can you elaborate? i thought before SP_configure i have to be in that db, and it won't let me in that db. meaning the following won't work? or I just need to use in master?

use sels
go
sp_configure 'Allow updates',1
go
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search