Record Locks: failure

Showing posts with label failure. Show all posts

Friday, March 30, 2012

Recovery of a corrupted Database due to power failure

On the plus side, nothing makes you start thinking about backups like losing
(or almost losing) a bunch of critical data because you didn't bother
backing it up in the first place

Recovery of a corrupted Database due to power failure

On the plus side, nothing makes you start thinking about backups like losing
(or almost losing) a bunch of critical data because you didn't bother
backing it up in the first place

sql

Recovery of a corrupted Database due to power failure

Hi,
Iam looking for some tools or methods to recover a corrupted mdf file (SQL
-MSDE 2000)..please help me and I have tried the following :
1. used osql to open the master database and run the DBCC checkdb with
specified database name and given the following message :
Database 'RubyDB' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information.
... i didn't find any useful information in the error log and looked in the
msdn articles and tried to reset the status using sp_resetstatus and didn't
helped. also tried to used the update to change the suspect flag status.
didn't helped
2. also tried to detach the database using the sp_detach_db and tried to
re-attach the particular db by using :
sp_attach_db @.dbname = N'RubyDB', @.filename1 = N'C:\Program Files\Microsoft
SQL Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Data.MDF', @.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Log.LDF' ;
An got a message :
Msg 9003, Level 20, State 6, Server ADDSV1WD67Z461\RUBYMSDEINSTANCE, Line 1
The LSN (742:208:1) passed to log scan in database 'RubyDB' is invalid.
Please help me if there are any tools to analyze the database problem (in
the .mdf file) and a way to get back the data (at least in partial)...
Thanks in advance
Hari"Got Backup?"
If you're against restoring from your last good backup for some reason, then
Google up on suspect databases. There are "unofficial" ways to reset
suspect databases. They're not 100% though, and you may end up having to
restore from backup anyway.
"Hari" <Hari@.discussions.microsoft.com> wrote in message
news:3AB6DE2D-FE0A-450C-A8CF-8E597C97ED5B@.microsoft.com...
> Hi,
> Iam looking for some tools or methods to recover a corrupted mdf file (SQL
> -MSDE 2000)..please help me and I have tried the following :
> 1. used osql to open the master database and run the DBCC checkdb with
> specified database name and given the following message :
> Database 'RubyDB' cannot be opened. It has been marked SUSPECT by
> recovery.
> See the SQL Server errorlog for more information.
> ... i didn't find any useful information in the error log and looked in
> the
> msdn articles and tried to reset the status using sp_resetstatus and
> didn't
> helped. also tried to used the update to change the suspect flag status.
> didn't helped
> 2. also tried to detach the database using the sp_detach_db and tried to
> re-attach the particular db by using :
> sp_attach_db @.dbname = N'RubyDB', @.filename1 = N'C:\Program
> Files\Microsoft
> SQL Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Data.MDF', @.filename2 => N'C:\Program Files\Microsoft SQL
> Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Log.LDF' ;
> An got a message :
>
> Msg 9003, Level 20, State 6, Server ADDSV1WD67Z461\RUBYMSDEINSTANCE, Line
> 1
> The LSN (742:208:1) passed to log scan in database 'RubyDB' is invalid.
>
> Please help me if there are any tools to analyze the database problem (in
> the .mdf file) and a way to get back the data (at least in partial)...
>
> Thanks in advance
> Hari
>|||Mike C# wrote:
> "Got Backup?"
>
What is this "backup" of which you speak? :-)
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Mike, could you give me more deatils on this unoffical way of resetting the
suspect database.
hari
"Mike C#" wrote:
> "Got Backup?"
> If you're against restoring from your last good backup for some reason, then
> Google up on suspect databases. There are "unofficial" ways to reset
> suspect databases. They're not 100% though, and you may end up having to
> restore from backup anyway.
> "Hari" <Hari@.discussions.microsoft.com> wrote in message
> news:3AB6DE2D-FE0A-450C-A8CF-8E597C97ED5B@.microsoft.com...
> > Hi,
> >
> > Iam looking for some tools or methods to recover a corrupted mdf file (SQL
> > -MSDE 2000)..please help me and I have tried the following :
> >
> > 1. used osql to open the master database and run the DBCC checkdb with
> > specified database name and given the following message :
> >
> > Database 'RubyDB' cannot be opened. It has been marked SUSPECT by
> > recovery.
> > See the SQL Server errorlog for more information.
> >
> > ... i didn't find any useful information in the error log and looked in
> > the
> > msdn articles and tried to reset the status using sp_resetstatus and
> > didn't
> > helped. also tried to used the update to change the suspect flag status.
> > didn't helped
> >
> > 2. also tried to detach the database using the sp_detach_db and tried to
> > re-attach the particular db by using :
> >
> > sp_attach_db @.dbname = N'RubyDB', @.filename1 = N'C:\Program
> > Files\Microsoft
> > SQL Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Data.MDF', @.filename2 => > N'C:\Program Files\Microsoft SQL
> > Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Log.LDF' ;
> >
> > An got a message :
> >
> >
> > Msg 9003, Level 20, State 6, Server ADDSV1WD67Z461\RUBYMSDEINSTANCE, Line
> > 1
> > The LSN (742:208:1) passed to log scan in database 'RubyDB' is invalid.
> >
> >
> > Please help me if there are any tools to analyze the database problem (in
> > the .mdf file) and a way to get back the data (at least in partial)...
> >
> >
> > Thanks in advance
> >
> > Hari
> >
> >
>
>|||I haven't had to do it in a long time, but basically you try to trick SQL
Server into thinking the database is no longer suspect. As I mentioned, my
good buddies Larry Page and Sergey Brin have a ton of information on it over
at their website (GOOGLE.COM).
If you do get it to work, then I would recommend immediately copying
everything to a NEW database and immediately starting to take daily BACKUPS
so you don't have to go through this again.
"Hari" <Hari@.discussions.microsoft.com> wrote in message
news:BB4CE1FD-CC3C-4DFA-A1D2-6BA056CBFA79@.microsoft.com...
> Mike, could you give me more deatils on this unoffical way of resetting
> the
> suspect database.
> hari
> "Mike C#" wrote:
>> "Got Backup?"
>> If you're against restoring from your last good backup for some reason,
>> then
>> Google up on suspect databases. There are "unofficial" ways to reset
>> suspect databases. They're not 100% though, and you may end up having to
>> restore from backup anyway.
>> "Hari" <Hari@.discussions.microsoft.com> wrote in message
>> news:3AB6DE2D-FE0A-450C-A8CF-8E597C97ED5B@.microsoft.com...
>> > Hi,
>> >
>> > Iam looking for some tools or methods to recover a corrupted mdf file
>> > (SQL
>> > -MSDE 2000)..please help me and I have tried the following :
>> >
>> > 1. used osql to open the master database and run the DBCC checkdb with
>> > specified database name and given the following message :
>> >
>> > Database 'RubyDB' cannot be opened. It has been marked SUSPECT by
>> > recovery.
>> > See the SQL Server errorlog for more information.
>> >
>> > ... i didn't find any useful information in the error log and looked in
>> > the
>> > msdn articles and tried to reset the status using sp_resetstatus and
>> > didn't
>> > helped. also tried to used the update to change the suspect flag
>> > status.
>> > didn't helped
>> >
>> > 2. also tried to detach the database using the sp_detach_db and tried
>> > to
>> > re-attach the particular db by using :
>> >
>> > sp_attach_db @.dbname = N'RubyDB', @.filename1 = N'C:\Program
>> > Files\Microsoft
>> > SQL Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Data.MDF', @.filename2 =>> > N'C:\Program Files\Microsoft SQL
>> > Server\MSSQL$RUBYMSDEINSTANCE\Data\RubyDB_Log.LDF' ;
>> >
>> > An got a message :
>> >
>> >
>> > Msg 9003, Level 20, State 6, Server ADDSV1WD67Z461\RUBYMSDEINSTANCE,
>> > Line
>> > 1
>> > The LSN (742:208:1) passed to log scan in database 'RubyDB' is invalid.
>> >
>> >
>> > Please help me if there are any tools to analyze the database problem
>> > (in
>> > the .mdf file) and a way to get back the data (at least in partial)...
>> >
>> >
>> > Thanks in advance
>> >
>> > Hari
>> >
>> >
>>|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45AF77C7.8000807@.realsqlguy.com...
> Mike C# wrote:
>> "Got Backup?"
> What is this "backup" of which you speak? :-)
It's them high-falutin' words I done heard the DBA's slangin' around the
uther day :)
On the plus side, nothing makes you start thinking about backups like losing
(or almost losing) a bunch of critical data because you didn't bother
backing it up in the first place :)

Monday, March 26, 2012

Recovery from windows failure

Hi all,

We've got a problem with our server in that Windows has totally died - a routine upgrade appears to have gone wrong and the repair function of the Windows installer keeps getting stuck in a loop so I've given up on that front. What I was wondering is:

1. If I install a fresh copy of Windows 2003 R2 over the top of the existing install will that kill MSSQL Sever 2005 and/or Windows Sharepoint Services?
2. If so, is there a simple way to get them back?
3. If I install another copy of Windows on the D: drive is there a recommended way to move the MSSQL databases & Sharepoint to the newer install or a way of pointing the new install at the old databases?

I'm not an admin person (i'm a developer normally) so I haven't got a lot of background in this stuff so any tips, pointers or ideas are welcome. If this is covered somewhere on the MS site I'm happy to read but I'm just getting lost at the moment.

And, yes, I realise that backups are a good thing but the latest backups are not new enough for some items. The backup process has been adjusted accordingly.

Thanks
Michael.serious problem...sympathizing...|||

Howdy,

I am also a newbie; and have run into a similar problem as you "Mycle". I am trying not to lose all my info / data a my C: drive aswell. My system just keeps looping , and looping in the setup / upgrade installation process; and stops at the 39min mark. Then i get this "Fatal" error msg. I cannot even get into the recovery screen.

"The signature windows XP Pro upgrade is invalid, code error 426. The service is not started.

and then we continue to dance and boot / loop again.

I've exhausted my eyes for nearly half a day now and nothing.

If you find something could you hopefully send me in the right direction, please and thanks, this also goes out to anyone else that may also have some insite, thanks again.

'Ruff'

specs: Running Windows XP Pro; the upgrade was on the account of windows crashing and not booting back up. ( 100 times)

|||

Have you had any luck yet? I'm almost at the point where i have to format the drive.

please help if you have any ideas for myself, please and thanks inadvance.

Ruffnready

Recovery from windows failure

Hi all,

And, yes, I realise that backups are a good thing but the latest backups are not new enough for some items. The backup process has been adjusted accordingly.

Thanks
Michael.
serious problem...sympathizing...|||

Howdy,

"The signature windows XP Pro upgrade is invalid, code error 426. The service is not started.

and then we continue to dance and boot / loop again.

I've exhausted my eyes for nearly half a day now and nothing.

If you find something could you hopefully send me in the right direction, please and thanks, this also goes out to anyone else that may also have some insite, thanks again.

'Ruff'

specs: Running Windows XP Pro; the upgrade was on the account of windows crashing and not booting back up. ( 100 times)

|||

Have you had any luck yet? I'm almost at the point where i have to format the drive.

please help if you have any ideas for myself, please and thanks inadvance.

Ruffnready

Recovery from crash

Greetings,

I had a hard-drive failure this week and lost my root drive, with
operating system and SQL Server 2000.

Fortunately my data was on another volume and still exists.

I know about sp_attach_db, but looking at BOL, it says that sp_attach_db
only works with databases that were previously detached with
sp_detach_db.

How do I reattach my existing mdf and ldf files?

-- Rick

P.S. I know that the dbs are not corrupt because when the hard drive
failed SQL Server was offline.Guinness Mann (GMann@.dublin.com) writes:
> I had a hard-drive failure this week and lost my root drive, with
> operating system and SQL Server 2000.
> Fortunately my data was on another volume and still exists.
> I know about sp_attach_db, but looking at BOL, it says that sp_attach_db
> only works with databases that were previously detached with
> sp_detach_db.
> How do I reattach my existing mdf and ldf files?
> P.S. I know that the dbs are not corrupt because when the hard drive
> failed SQL Server was offline.

I would first try with sp_attach_db. If SQL Server was shut down cleanly,
I would expect the database files to be available.

If that fails, I would try sp_attach_single_file_db.

If that fails, there is an undocumented and unsupported method, that
I am not telling about in a newsgroup, because that methods is just
simply far too dangerous. I have no problem sharing it by mail. But
please try sp_detach_db first.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||In article <Xns93F5E2EFD74Yazorman@.127.0.0.1>, sommar@.algonet.se says...
> > I know about sp_attach_db, but looking at BOL, it says that sp_attach_db
> > only works with databases that were previously detached with
> > sp_detach_db.
> I would first try with sp_attach_db. If SQL Server was shut down cleanly,
> I would expect the database files to be available.

sp_attach_db worked great, Erland. Thank you.

-- Rick

Friday, March 23, 2012

recovering from a clustered node failure

We are running SQL Server 2000 and we had a node failure
on one of our secondary nodes. The node was evicted from
the cluster, and the hardware was rebuilt. When we try to
re-setup the node, we follow the steps listed below.
1. Insert the SQL Server 2000 Enterprise Edition compact
disc in your CD-ROM drive. Select Install SQL Server 2000
Components.
2. Click Install SQL Server 2000 Components, click Install
Database Server, and then click Next.
3. On the Computer Name dialog box, select Virtual Server,
and enter the name of an existing clustered instance of
SQL Server 2000.
4. On the Installation Selection dialog box, select
Advanced options, and then click Next.
5. On the Advanced Options dialog box, select Maintain a
Virtual Server for Failover Clustering, and then click
Next.
6. On the Failover Clustering dialog box, click Next.
7. On the Cluster Management dialog box, select node 2 to
add back into the cluster so that both your nodes show up
on the right pane window.
8. On the Remote Information dialog box, enter the user
name and password for the domain administrator account
used for the clustered instance of SQL Server 2000, and
then click Next.
9. When the process is complete, click Finish.
Having clicked Next after step 8, the installation just
dissappears and SQL never gets installed on the secondary
node. Any thoughts?
Also - can you confirm that it's possible to recover a node without having to de-install the virtual servers (active/active setup) and re-install, as this would mean extended outage on the databases..
Thanks indeed.
Yes, you can recover from a node failure. There are precise step-by-step
instructions in BOL for exactly this scenario. Look under 'Maintaining a
Failover Cluster' for Recovering from Failover Cluster Failure. The key
step that you may have to redo is to run the install app to remove the
failed node from the SQL virtual server. This is in addition to the node
eviction and replacemnet you have already done. Once the node is
uninstalled, you can then install SQL on the replacement node.
You can also re-apply Service packs to the new node only without taking the
Virtual SQL instance offline. Check the Service Pack README file for
details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Martyn Cavett" <anonymous@.discussions.microsoft.com> wrote in message
news:8D25D32F-7ECF-4BCC-8827-BFBE4D973844@.microsoft.com...
> We are running SQL Server 2000 and we had a node failure
> on one of our secondary nodes. The node was evicted from
> the cluster, and the hardware was rebuilt. When we try to
> re-setup the node, we follow the steps listed below.
> 1. Insert the SQL Server 2000 Enterprise Edition compact
> disc in your CD-ROM drive. Select Install SQL Server 2000
> Components.
> 2. Click Install SQL Server 2000 Components, click Install
> Database Server, and then click Next.
> 3. On the Computer Name dialog box, select Virtual Server,
> and enter the name of an existing clustered instance of
> SQL Server 2000.
> 4. On the Installation Selection dialog box, select
> Advanced options, and then click Next.
> 5. On the Advanced Options dialog box, select Maintain a
> Virtual Server for Failover Clustering, and then click
> Next.
> 6. On the Failover Clustering dialog box, click Next.
> 7. On the Cluster Management dialog box, select node 2 to
> add back into the cluster so that both your nodes show up
> on the right pane window.
> 8. On the Remote Information dialog box, enter the user
> name and password for the domain administrator account
> used for the clustered instance of SQL Server 2000, and
> then click Next.
> 9. When the process is complete, click Finish.
> Having clicked Next after step 8, the installation just
> dissappears and SQL never gets installed on the secondary
> node. Any thoughts?
> Also - can you confirm that it's possible to recover a node without having
to de-install the virtual servers (active/active setup) and re-install, as
this would mean extended outage on the databases..
> Thanks indeed.
>

recovering from a clustered node failure

We are running SQL Server 2000 and we had a node failure
on one of our secondary nodes. The node was evicted from
the cluster, and the hardware was rebuilt. When we try to
re-setup the node, we follow the steps listed below.
1. Insert the SQL Server 2000 Enterprise Edition compact
disc in your CD-ROM drive. Select Install SQL Server 2000
Components.
2. Click Install SQL Server 2000 Components, click Install
Database Server, and then click Next.
3. On the Computer Name dialog box, select Virtual Server,
and enter the name of an existing clustered instance of
SQL Server 2000.
4. On the Installation Selection dialog box, select
Advanced options, and then click Next.
5. On the Advanced Options dialog box, select Maintain a
Virtual Server for Failover Clustering, and then click
Next.
6. On the Failover Clustering dialog box, click Next.
7. On the Cluster Management dialog box, select node 2 to
add back into the cluster so that both your nodes show up
on the right pane window.
8. On the Remote Information dialog box, enter the user
name and password for the domain administrator account
used for the clustered instance of SQL Server 2000, and
then click Next.
9. When the process is complete, click Finish.
Having clicked Next after step 8, the installation just
dissappears and SQL never gets installed on the secondary
node. Any thoughts?
Also - can you confirm that it's possible to recover a node without having t
o de-install the virtual servers (active/active setup) and re-install, as th
is would mean extended outage on the databases..
Thanks indeed.Yes, you can recover from a node failure. There are precise step-by-step
instructions in BOL for exactly this scenario. Look under 'Maintaining a
Failover Cluster' for Recovering from Failover Cluster Failure. The key
step that you may have to redo is to run the install app to remove the
failed node from the SQL virtual server. This is in addition to the node
eviction and replacemnet you have already done. Once the node is
uninstalled, you can then install SQL on the replacement node.
You can also re-apply Service packs to the new node only without taking the
Virtual SQL instance offline. Check the Service Pack README file for
details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Martyn Cavett" <anonymous@.discussions.microsoft.com> wrote in message
news:8D25D32F-7ECF-4BCC-8827-BFBE4D973844@.microsoft.com...
> We are running SQL Server 2000 and we had a node failure
> on one of our secondary nodes. The node was evicted from
> the cluster, and the hardware was rebuilt. When we try to
> re-setup the node, we follow the steps listed below.
> 1. Insert the SQL Server 2000 Enterprise Edition compact
> disc in your CD-ROM drive. Select Install SQL Server 2000
> Components.
> 2. Click Install SQL Server 2000 Components, click Install
> Database Server, and then click Next.
> 3. On the Computer Name dialog box, select Virtual Server,
> and enter the name of an existing clustered instance of
> SQL Server 2000.
> 4. On the Installation Selection dialog box, select
> Advanced options, and then click Next.
> 5. On the Advanced Options dialog box, select Maintain a
> Virtual Server for Failover Clustering, and then click
> Next.
> 6. On the Failover Clustering dialog box, click Next.
> 7. On the Cluster Management dialog box, select node 2 to
> add back into the cluster so that both your nodes show up
> on the right pane window.
> 8. On the Remote Information dialog box, enter the user
> name and password for the domain administrator account
> used for the clustered instance of SQL Server 2000, and
> then click Next.
> 9. When the process is complete, click Finish.
> Having clicked Next after step 8, the installation just
> dissappears and SQL never gets installed on the secondary
> node. Any thoughts?
> Also - can you confirm that it's possible to recover a node without having
to de-install the virtual servers (active/active setup) and re-install, as
this would mean extended outage on the databases..
> Thanks indeed.
>

Friday, March 30, 2012

Recovery of a corrupted Database due to power failure

Recovery of a corrupted Database due to power failure

Recovery of a corrupted Database due to power failure

Monday, March 26, 2012

Recovery from windows failure

Recovery from windows failure

Recovery from crash

Friday, March 23, 2012

recovering from a clustered node failure

recovering from a clustered node failure

Record Locks

Blog Archive

About Me