Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Database suspect

Author  Topic 

RoyalSher
Yak Posting Veteran

95 Posts

Posted - 2004-04-29 : 07:28:25
Hi

I have a database under suspect mode in one of the prod servers. The below is the error after digging the large error log

2004-04-28 18:17:53.89 kernel udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device E:\Data\SQLData\MSSQL7\Data\OneSight_log.ldf.
2004-04-28 18:17:53.89 kernel FCB::Open failed: Could not open device E:\Data\SQLData\MSSQL7\Data\OneSight_log.ldf for virtual device number (VDN) 2.
2004-04-28 18:17:53.91 spid12 Attempting to rebuild primary log file for database OneSight.
2004-04-28 18:17:53.91 spid12 FCB::CreateFile() failed with error 80 for file E:\Data\SQLData\MSSQL7\Data\OneSight_log.LDF.

I search the whole of net to find the straight solution and the possible problem of the error and I see that nothing straightforward. Can any body tell me how can this be troubleshooted in time pl.

Can restarting of sql server service first option ?

Thanks in advance.


RoyalSher.
*********
The world is the great gymnasium where we come to make ourselves strong.

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-29 : 08:43:23
Have you tried to see if:
sp_resetstatus 'OneSight'
works?

If not, try this first. If it doesn't work, you can try rebooting, but that doesn't really ever work. :) You will need to restore from a backup if the reboot doesn't work.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2004-04-29 : 09:06:18
First option...take a backup

At least you can start from here if things go very wrong...

and speaking of backups, what do you have? What's your recovery model?

And what is your E: drive? IS it logical or physical. Did it somehow get disconnected?

My guess is sql server is trying to write to it's log and it can't



Brett

8-)
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-04-29 : 12:35:41
Is it possible that the tape backup software has control of those files? I've seen that happen a while back.

Tara
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-29 : 14:27:15
Just curious. What did you end up doing?

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

RoyalSher
Yak Posting Veteran

95 Posts

Posted - 2004-05-03 : 06:28:26
Thanks to everybody for their time and replies!

Tara, you were correct tape backup was holding the files (.ldf). And derrick, the final solution was I just restarted the Sql server service .. and the database was set to normal mode. Let me know if there cd have been any other possible solutions.

RoyalSher.
*********
The world is the great gymnasium where we come to make ourselves strong.
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-05-03 : 08:27:33
Not really. It's a good thing Tara mentioned that. You need to have your backups going to a backup directory. In your backup software, you need to exclude all MS SQL Server directories from your backup software. Just backup the "backup" directory.

Make sure you backup up all the system databases when you do this. I don't know of any backup software that really interacts well with SQL Server. That's why it's recommended you backup the backup files to tape.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page
   

- Advertisement -