SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Db error
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

hadi354
Starting Member

4 Posts

Posted - 03/16/2012 :  06:58:52  Show Profile  Reply with Quote
i have not any back up from data base. my db has occuerd this error when i try to open it:
error 823:I/O error (bad page id)detected during read at offset ...
with DBCC checkdb(mydb,repair_allow_data_loss) this error:
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:17688) with latch type SH. sysobjects failed.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

is any way to restor my data

RickD
Slow But Sure Yak Herding Master

United Kingdom
3608 Posts

Posted - 03/16/2012 :  07:14:37  Show Profile  Reply with Quote
Why don't you have backups? There is a reason backups exist in databases and you have just found it.

How important is the data? I guess it can't be very as you haven't got a backup, in that case, just create a new db and re-create the objects. You do have object creation scripts, don't you?
Go to Top of Page

hadi354
Starting Member

4 Posts

Posted - 03/16/2012 :  07:51:52  Show Profile  Reply with Quote
The data are very important and must be recovery. there is no backup data. this db is for 5 year data entery. db admin forget to start sql agent to auto back or any other Solution
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/16/2012 :  11:13:42  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
There's no recovery from that error, one of the critical system tables is damaged. If you don't have a backup and you can't even open the database, the database is probably a complete loss.

SQL 2000 I assume?
What's the error you get when you try to query the DB?

--
Gail Shaw
SQL Server MVP

Edited by - GilaMonster on 03/16/2012 11:17:22
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 03/16/2012 :  13:02:10  Show Profile  Reply with Quote
Do you have a disk image?



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

hadi354
Starting Member

4 Posts

Posted - 03/16/2012 :  13:05:25  Show Profile  Reply with Quote
quote:
Originally posted by GilaMonster

There's no recovery from that error, one of the critical system tables is damaged. If you don't have a backup and you can't even open the database, the database is probably a complete loss.

SQL 2000 I assume?
What's the error you get when you try to query the DB?

--
Gail Shaw
SQL Server MVP


exactily sql 2000
when I try to query this error apeare:
Server: Msg 601, Level 12, State 3, Line 1
Could not continue scan with NOLOCK due to data movement.
in first my db was suspect. i dettach it then my db not attach and appear this error while attaching: "the error 823:I/O error (bad page id)detected during read at offset ..."
I read an article about the problem and the steps I followed it
http://www.sqlserverclub.com/articles/how-to-recover-from-a-corrupted-sql-server-database.aspx

in 16 step the abow error apeared.
(Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:17688) with latch type SH. sysobjects failed.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

)
Go to Top of Page

hadi354
Starting Member

4 Posts

Posted - 03/16/2012 :  13:10:18  Show Profile  Reply with Quote
no any disk image.
i have a back up but it is too old.
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 03/16/2012 :  13:29:41  Show Profile  Reply with Quote
Call Microsoft in any case

And what about RedGate and Lumigent to recover data from the log? Or is that a no go as well



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx


Want to help yourself?

http://msdn.microsoft.com/en-us/library/ms130214.aspx

http://weblogs.sqlteam.com/brettk/

http://brettkaiser.blogspot.com/


Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/16/2012 :  14:16:41  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
quote:
Originally posted by hadi354


exactily sql 2000
when I try to query this error apeare:
Server: Msg 601, Level 12, State 3, Line 1
Could not continue scan with NOLOCK due to data movement.
in first my db was suspect.


Yeah, that's a good sign of corrupt DB

quote:
i dettach it then my db not attach and appear this error while attaching: "the error 823:I/O error (bad page id)detected during read at offset ..."


That was probably the worst thing you could have done. Never, never, never detach a suspect database.

If it hadn't been detached we might have been able to get some data out. Now, probably not.


I read an article about the problem and the steps I followed it
http://www.sqlserverclub.com/articles/how-to-recover-from-a-corrupted-sql-server-database.aspx

quote:
(Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:17688) with latch type SH. sysobjects failed.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.


Ok, what is the EXACT state of the database?
Is it attached to an instance? If so, what are the values for status and status2 in sysdatabases for that DB?

Please, do NOTHING else, it's highly unlikely that the DB is recoverable at all anyway.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/16/2012 :  14:18:29  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
quote:
Originally posted by X002548

Call Microsoft in any case


Probably no point. CSS will tell him to restore from database, to run checkDB and when both of those are not an option, they'll tell him the DB is unrecoverable. They're not allowed to do more than that

quote:
And what about RedGate and Lumigent to recover data from the log? Or is that a no go as well


That'll just be the active portion of the log, and if there's never been a backup or the DB was in simple recovery, that'll be minutes or hours of data changes, nothing more.


--
Gail Shaw
SQL Server MVP
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 03/16/2012 :  14:18:51  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
quote:
Originally posted by hadi354

no any disk image.
i have a back up but it is too old.



It's better than nothing.

--
Gail Shaw
SQL Server MVP
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000