April 29, 2005 at 5:48 am
Good Afternoon everybody
One of my database get Corrupted and in suspect mode now.I don't know waht exactly caused the problem.It is serving as back end to an ERP package.I am planning to restore the DB from backup.But before that can any one help me what are the other procedures i can perform to check and bring back the DB before doing restore from back up as a last resort ? procedures to do in chronological order are most welocmed....
April 29, 2005 at 6:04 am
1. Try to check if there is enough space available on the drive where your data files are located (.mdf and .ldf files). It might be that the space is used up and there is no space for your files to grow.
2. If point 1 is fine, then try this : sp_resetstatus [ @DBName = ] 'database'. This shoudl get your database to normal state.
3. If still, it does not work, then probably you will have to restore from backup.
--Kishore
April 29, 2005 at 7:43 am
We need you examine following logs for any possible errors before telling you what are the causes and how to resolve it.
1. server application log
2. server system log
3. SQL Server errorlog
4. Do you see any dump files created in SQL Server log folder?
April 30, 2005 at 2:00 am
Thank u kishore and Allen!
Allen, I have examined the logs as directed and it found out that
Server Application Log
Logwriter : Operating System error 112 [There is not enough space on the disk] encountered.
Sql server Error Log
Error 9001,Severity 21, State:4
Also Dump file is created at the time of error occured in the sql folder
I think this problem is caused due to out of disk space while running the scheduled back up.Now dB is in Suspect mode and can u suggest any idea other than restoring the DB to bring this DB up.
NOTE: At the time of this error All the DB in particular Disk get failed to suspect mode and i restored important and active DB's from back up.
April 30, 2005 at 10:52 am
Free some disk spaces in the drive your log file resides and restart SQL Server, If the database is still in suspect mode, follow Kishore's suggestions.
"NOTE: At the time of this error All the DB in particular Disk get failed to suspect mode and i restored important and active DB's from back up."
It looks like you had problem at the drives in hardware level, Do some hardware diagnoses.
May 1, 2005 at 11:23 am
One of the possible reasons why the database is in suspect mode is that there is not enough space for the transactions to be committed/rollbacked. You can copy the data files to an alternate location(with enough room) and then attach the files.
May 4, 2005 at 2:18 am
To All,
Thank u for all the comments and suggestions.It all are useful and valid...
Rafi-
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply