June 28, 2004 at 9:43 pm
I am fiddling with grave problem although, I solved it once but still came back today morning on weekend ..with a new Dragon Head...
HISTORY:-
It happened that some of the critical databses of our client went into Suspect mode ..Clienmt ahd no back .... Db Size is 125 GB ..I was ablt to restore on one occasion.. based on the normal SOP of sp_configure and putting the DB in Emergency Mode and BCP out data ..
But for some unknown reasons it Failed on other server where also someother DB was in Suspect mode..The previous Error log is also not mainatined so as such couldnt find much on the error
History..Finally I had to delete the Entry of this Db in Sysdatabases and attach is as a normal DB with LDF..Then All was up and working , But Today morning after the Serevr was restarted we came to know that Prod server is throwing Error 5173 which is not allowing to make any new database and niether letting to attach any DBs ....
It asks for some Junk LDF file
"Msg 5173 Cnnot associate the files with diffrent database
Even same error comes If we create the new Db..Serverice pack 3 is installed."
There is one more Error 5180 that is occuring if we attach the DBs
"Couldnt open the FCB for invalid File ID 5 in the Database"
I ahve done a lot of research on FCB and got to know abt its nature how ever to fix the above errors I ahve no solutions as of now.
MoreOver the Yesterdays 2nd DB has gone back into SuspectMode...Although I have tried lots of options but no result till now.. IF any one has actually worked on this issues..please let me know about it as it is very urgent
Please mail me ASAP ...veerw@hclcomnet.co.in
June 28, 2004 at 9:57 pm
You need to call your hardware vendor. It sounds like you have faulty hardware somewhere. I would take the server down at night and run a complete diagnostic on it.
Derrick Leggett
Mean Old DBA
When life gives you a lemon, fire the DBA.
June 30, 2004 at 10:35 am
If you are using Raid, make sure nothing else, such as external disk or tape drive, is attached to the Raid controller. It can mess up the Raid configuration and cause hard disk failure, like Derrick said. Had a similiar problem once. Spent 4 hours on the phone with Microsoft before someone decided to reboot the box without the tape drive that was attached to the Raid controller. It came back to normal after the reboot.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply