Databases are under "Suspect" Mode

Question

Post reply

Databases are under "Suspect" Mode

SQLisAwe5oMe

SSChampion

Points: 14047
More actions
January 8, 2013 at 2:38 pm

#268596

All,
I have couple of the databases are under suspect mode.
What are some of the process you should follow under this circumstance. Please advise.
Thanks,
SueTons.
Regards,
SQLisAwe5oMe.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

george sibbald SSC Guru Points: 104210 More actions · Answer 1

firstly check the SQL errorlog for error messages - next steps depend on the errors.

---------------------------------------------------------------------

SQLisAwe5oMe SSChampion Points: 14047 More actions · Answer 2

Thanks, I did that.

I ran dbcc chekcdb(dbname)....and looked at the error, I see an error 'An error occurred in the service broker manager, error:823, state 2.

I also see another error says 'The operating system returned error 21(the device is not ready.) to sql server during at offset 0x0000..........etc.

I know we can reset the status to recovery.....but I am more looking at what exactly the cause for this so, it won't happen again.

Thanks,

SueTons.

Regards,
SQLisAwe5oMe.

SQLRNNR SSC Guru Points: 281334 More actions · Answer 3

SQLCrazyCertified (1/8/2013)
Thanks, I did that.
I ran dbcc chekcdb(dbname)....and looked at the error, I see an error 'An error occurred in the service broker manager, error:823, state 2.
I also see another error says 'The operating system returned error 21(the device is not ready.) to sql server during at offset 0x0000..........etc.
I know we can reset the status to recovery.....but I am more looking at what exactly the cause for this so, it won't happen again.
Thanks,
SueTons.

The operating system returned error 21(the device is not ready.)

This message is an operating system error. It is more of a generic message letting you know there is an issue with the disk subsystem. It can be caused by a number of things such as:

LUNS not being available for the OS

the SAN was unplugged

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

SQLisAwe5oMe SSChampion Points: 14047 More actions · Answer 4

Thanks Jason. Will look into it.

SueTons.

Regards,
SQLisAwe5oMe.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

Post the exact errors from the SQL error log (all of them), then switch the DB into Emergency mode and run

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

and post those errors

You can't just reset the status on a suspect DB to normal. Suspect means damaged, has to be restored (prefered) or repaired (if there's no backup)

If it's just the error 21, then a restart of SQL might fix it, and then you need to identify why the disks are disappearing underneath SQL.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQLisAwe5oMe SSChampion Points: 14047 More actions · Answer 6

alexandert680@gmail.com1/9/2013)[/b]

Post the exact errors from the SQL error log (all of them), then switch the DB into Emergency mode and run

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

and post those errors

You can't just reset the status on a suspect DB to normal. Suspect means damaged, has to be restored (prefered) or repaired (if there's no backup)

If it's just the error 21, then a restart of SQL might fix it, and then you need to identify why the disks are disappearing underneath SQL.[/quote]

One of my colleague reboot the server and it solved the issue. Anyway, I had contacted the windows/storage team to investigate further.

Thanks for all your valuable inputs.

SueTons.

Regards,
SQLisAwe5oMe.