<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
Data Corruption
»
DB corrupted with event 17052 and Error: 823,...
37 posts, Page 1 of 4
1
2
3
4
»
»»
DB corrupted with event 17052 and Error: 823, Severity: 24, State: 2
Rate Topic
Display Mode
Topic Options
Author
Message
halifaxdal
halifaxdal
Posted Monday, September 12, 2011 3:21 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, May 10, 2013 8:49 AM
Points: 661,
Visits: 1,187
I was approached today for a crashed SQL 2000 SP2 server with a single 800G database on it. Log is 20G. The database crashed due to the reason in the subject.
I successfully recovered another backup from the same server, unfortunately it was long long time ago and size is only 3G, but structure is the same.
I wonder how do I recover the rest of the data? Where should I start?
I checked sysdatabases, I don't see the damaged database, not even in suspect mode.
Any clue is greatly appreciated.
Post #1173804
Ninja's_RGR'us
Ninja's_RGR'us
Posted Monday, September 12, 2011 3:29 PM
SSC-Insane
Group: General Forum Members
Last Login: Yesterday @ 7:02 PM
Points: 21,376,
Visits: 9,584
Run this and LET IT FINISH
DBCC CHECKDB(DbName) WITH NO_INFOMSGS, ALL_ERRORMSGS
Did you try to restore that backup on a test server to see if it works and what data it contains?
Any way you can take a backup of the current <corrupt> db?
Any reason (after last time), that you couldn't setup backups on all servers and that you didn't cehck if the backups were usable (we need to know of your current limits)?
Post #1173806
GilaMonster
GilaMonster
Posted Monday, September 12, 2011 3:37 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:48 AM
Points: 38,073,
Visits: 30,367
Did someone detach or drop the DB? Only reasons it wouldn't be in sysdatabases.
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 #1173809
halifaxdal
halifaxdal
Posted Monday, September 12, 2011 3:43 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, May 10, 2013 8:49 AM
Points: 661,
Visits: 1,187
Ninja's_RGR'us (9/12/2011)
Run this and LET IT FINISH
DBCC CHECKDB(DbName) WITH NO_INFOMSGS, ALL_ERRORMSGS
Did you try to restore that backup on a test server to see if it works and what data it contains?
Any way you can take a backup of the current <corrupt> db?
Any reason (after last time), that you couldn't setup backups on all servers and that you didn't cehck if the backups were usable (we need to know of your current limits)?
the backup is really not a backup, i believe it was created several years ago and when the owner found it's growing too fast then he decided to create another data file and start growing there and reaches 800g now and crashed.
that "backup" is working fine now.
i spoke to the guy who is responsible for it, he said due to the db size too big, no backup have been made in the past but he is considering a bk solution but unfortunately it crashed b4 it is implemented.
due to the fact that moving the damaged db files to another server is not applicable now, i will have to do everything on site.
pls consider a relatively safer suggestion.
thanks lots.
Post #1173816
halifaxdal
halifaxdal
Posted Monday, September 12, 2011 3:44 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, May 10, 2013 8:49 AM
Points: 661,
Visits: 1,187
GilaMonster (9/12/2011)
Did someone detach or drop the DB? Only reasons it wouldn't be in sysdatabases.
i don't know, the guy did tell me he saw it was marked as suspect
Post #1173817
halifaxdal
halifaxdal
Posted Monday, September 12, 2011 3:48 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, May 10, 2013 8:49 AM
Points: 661,
Visits: 1,187
Ninja's_RGR'us (9/12/2011)
Run this and LET IT FINISH
DBCC CHECKDB(DbName) WITH NO_INFOMSGS, ALL_ERRORMSGS
this is not gonna work becoz the db is not even in sysdatabases
here is the error:
Server: Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'SELS'. No entry found with that name. Make sure that the name is entered correctly.
Post #1173819
Ninja's_RGR'us
Ninja's_RGR'us
Posted Monday, September 12, 2011 4:23 PM
SSC-Insane
Group: General Forum Members
Last Login: Yesterday @ 7:02 PM
Points: 21,376,
Visits: 9,584
halifaxdal (9/12/2011)
Ninja's_RGR'us (9/12/2011)
Run this and LET IT FINISH
DBCC CHECKDB(DbName) WITH NO_INFOMSGS, ALL_ERRORMSGS
this is not gonna work becoz the db is not even in sysdatabases
here is the error:
Server: Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'SELS'. No entry found with that name. Make sure that the name is entered correctly.
I got 1 idea left but it's not going to be pretty. I'm hoping Gail has a better option cause mine's going to require a heck of a lot of free space and quite certainly losing data and you won't be able to know what you lost.
What's your SLA, RTO & RPO on this DB? And when were you called in?
Post #1173826
GilaMonster
GilaMonster
Posted Monday, September 12, 2011 4:42 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:48 AM
Points: 38,073,
Visits: 30,367
halifaxdal (9/12/2011)
GilaMonster (9/12/2011)
Did someone detach or drop the DB? Only reasons it wouldn't be in sysdatabases.
i don't know, the guy did tell me he saw it was marked as suspect
A suspect database still appears in sysdatabases. If it's not in sysdatabases it's been detached or dropped and there's absolutely nothing that can be done unless you can find the files for that database.
If the DB has been dropped, it's gone.
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 #1173830
halifaxdal
halifaxdal
Posted Monday, September 12, 2011 5:38 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, May 10, 2013 8:49 AM
Points: 661,
Visits: 1,187
The guy said he saw the DB in suspect but now it's not even in sysdatabases; whether he dropped it or not, I have no idea. I tried to attach it, I got error 5159: Operating system error 2 (The system cannot find the file specified.) on device 'D:\SQL\SELS_Log.LDF' during ForwardLogBlockAHeadAsync. Could not open new database 'SELS'. CREATE DATABASE is aborted.
Maybe I can rename the mdf/ldf, create the DB, then replace the empty mdf/ldf with the crashed one?
Post #1173844
halifaxdal
halifaxdal
Posted Monday, September 12, 2011 6:31 PM
Say Hey Kid
Group: General Forum Members
Last Login: Friday, May 10, 2013 8:49 AM
Points: 661,
Visits: 1,187
I renamed the original two damaged mdf/ldf, I created the db with the same name so now I have 2 files that make the db up and running.
I then stopped the db, deleted the two empty files, renamed the damaged files back to the original names.
I tried to bring the db online, failed.
I checked the log file, please see the attachment.
Post Attachments
errorlog201109122030.txt
(
12 views,
76.92 KB
)
Post #1173854
« Prev Topic
|
Next Topic »
37 posts, Page 1 of 4
1
2
3
4
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
