June 2, 2003 at 12:16 pm
I have a SQL 6.5 system whose hard drive crashed and we can not re-boot. We have no backups. However we were able to recover the .DAT files (master, myDB_data.dat, myDB_log.dat among others). Is there any way for me to get my database back? I have done some searching and tried a few things that did not work. I did the following:
1. Reinstalled SQL Server 6.5 on new machine.
2. Create the devices (myDB_data and myDB_log) and made sure that they were the same size as the recovered dat files.
3. Shut down SQL Server service.
4. Copied recovered dat files over new dat files.
5. Re-started SQL Server.
When SQL Server comes back up it shows my database in the list of databases but says that it is suspect. When I look in the event viewer I see the following two errors:
Error : 3403, Severity: 22, State: 2
Rec_init: Found that page 282378 had non-log object id 282378 while checking Syslogs allocation.
Error : 3414, Severity: 21, State: 1
Database 'myDB' (dbid 6): Recovery failed. Please contact Technical Support for further instructions.
I also found some possible things to do to try and fix a 'suspect' database. It involved using sp_resetstatus. I tried this and it did not help either.
I am not a SQL Server DBA. Any help would be appreciated.
Thanks
Corey Burnett
June 3, 2003 at 6:42 am
Any ideas out there? Or am I hosed?
Thanks in advance,
Corey
June 3, 2003 at 6:52 am
Can't remember much about 6.5 but could you not attach the file you have (.dat) to a blank database? You can then backup that BD and restore it onto your proper one.
Cheers,
Crispin
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
June 3, 2003 at 7:02 am
I don't believe that there is any sp_attach_db stored procedure in SQL 6.5.
June 3, 2003 at 11:42 pm
After asking around I was told that you can't attach a DB to a file. Sorry about that 🙂
Did you get it right?
Cheers,
Crispin
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
June 9, 2003 at 9:24 am
I finally figured it out. Here is what I did.
1. Reinstalled SQL Server 6.5 on new machine and applied all service packs. Made sure that I gave the machine the same name as the old machine. Also made sure that I installed on the same drive as the old macine. During install I made sure that the MASTER device was the same size as the MASTER device on the old server.
2. Created all devices and databases that were on the old machine. I made sure that they were all the same size as the devices on the old server and all had the same name.
3. Shut down the SQL Server service.
4. Copied ALL recovered dat files over new dat files (including MASTER and including databases that I did not care about)
5. Re-started SQL Server.
Everything came up fine and I was able to access my old database from the server that had crashed! Thanks for all help on this problem.
Corey
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply