SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Databases are under "Suspect" Mode


Databases are under "Suspect" Mode

Author
Message
SQLisAwE5OmE
SQLisAwE5OmE
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1054 Visits: 3068
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.
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687
firstly check the SQL errorlog for error messages - next steps depend on the errors.

---------------------------------------------------------------------
SQLisAwE5OmE
SQLisAwE5OmE
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1054 Visits: 3068
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
SQLRNNR
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32196 Visits: 18552
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

SQLisAwE5OmE
SQLisAwE5OmE
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1054 Visits: 3068
Thanks Jason. Will look into it.

SueTons.

Regards,
SQLisAwe5oMe.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86997 Visits: 45267
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>Wink 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
SQLisAwE5OmE
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1054 Visits: 3068
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>Wink 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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search