February 5, 2017 at 3:31 am
My msdb database went into suspect mode. How can i find the root cause of the issue?
February 5, 2017 at 3:56 am
Rechana Rajan - Sunday, February 5, 2017 3:31 AMMy msdb database went into suspect mode. How can i find the root cause of the issue?
Post here the full and unedited output of DBCC CheckDB ('msdb') WITH NO_INFOMSGS, ALL_ERRORMSGS
😎
February 5, 2017 at 5:15 am
Eirikur Eiriksson - Sunday, February 5, 2017 3:56 AMRechana Rajan - Sunday, February 5, 2017 3:31 AMMy msdb database went into suspect mode. How can i find the root cause of the issue?Post here the full and unedited output of
DBCC CheckDB ('msdb') WITH NO_INFOMSGS, ALL_ERRORMSGS
😎
Thanks Eirikur ,
Sorry cant provide you the result as one already restored the db with a backup. Our history is showing till third and there was no issue at that time.
February 5, 2017 at 6:22 am
Rechana Rajan - Sunday, February 5, 2017 5:15 AMEirikur Eiriksson - Sunday, February 5, 2017 3:56 AMRechana Rajan - Sunday, February 5, 2017 3:31 AMMy msdb database went into suspect mode. How can i find the root cause of the issue?Post here the full and unedited output of
DBCC CheckDB ('msdb') WITH NO_INFOMSGS, ALL_ERRORMSGS
😎Thanks Eirikur ,
Sorry cant provide you the result as one already restored the db with a backup. Our history is showing till third and there was no issue at that time.
Do you have a backup of the database in the corrupt / suspect state? Then restore and run the DBCC CHECKDB, think it is important to determine the cause, otherwise you are risking this to happen again. Also check any/all IO subsystem logs, OS logs, SQL Error logs, UPS logs etc. Restoring from a good backup gets you back up and running but it is not a fix if the problem lies undetexted elsewhere.
😎
February 5, 2017 at 6:27 am
Eirikur Eiriksson - Sunday, February 5, 2017 6:22 AMRechana Rajan - Sunday, February 5, 2017 5:15 AMEirikur Eiriksson - Sunday, February 5, 2017 3:56 AMRechana Rajan - Sunday, February 5, 2017 3:31 AMMy msdb database went into suspect mode. How can i find the root cause of the issue?Post here the full and unedited output of
DBCC CheckDB ('msdb') WITH NO_INFOMSGS, ALL_ERRORMSGS
😎Thanks Eirikur ,
Sorry cant provide you the result as one already restored the db with a backup. Our history is showing till third and there was no issue at that time.
Do you have a backup of the database in the corrupt / suspect state? Then restore and run the DBCC CHECKDB, think it is important to determine the cause, otherwise you are risking this to happen again. Also check any/all IO subsystem logs, OS logs, SQL Error logs, UPS logs etc. Restoring from a good backup gets you back up and running but it is not a fix if the problem lies undetexted elsewhere.
😎
Check DB after restore went clean.
This is what i got from SQL Logs
Error: 3414, Severity: 21, State: 1.
Error: 9004, Severity: 23, State: 6.
Also there was heartbeat failure at that time and file not found error in Cluster logs.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply