Database in suspected mode

  • Hello,

    Can some one please help

    My production database in suspected mode. How can I fix it?

    Thank you

  • What does the SQL error log say?

    What backups do you have?

    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
  • I have a Redgate backup,[298] SQLServer Error: 4060, Cannot open database requested in login 'DatabaseName'. Login fails. [SQLSTATE 42000]

  • There will be messages in the SQL error log saying why the DB was marked suspect. Have a look through the error log, look for messages relating to the database, login failures are uninteresting and useless in identifying the cause.

    I didn't ask what you're using for your backups. What backups of this database do you have?

    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
  • ldf,mdf,ndf

  • If you don't want help, that's fine. If you do, please answer my questions. I can't help you without information.

    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
  • I have differential from yesterday

  • Once more with feeling...

    Error log entries relating to the database please. SQL will log why the DB was marked suspect. Take a read through the error log and post any error messages relating to the DB (not login failures, they are uninteresting).

    What exact backups do you have, full, differential and log? I hope you have more than just a single differential.

    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
  • error message,I have differential and full backup

  • A database in suspect mode may not be recoverable. That's why Gail is asking about backups. But, to understand what is wrong with the database we need more information than you've provided. Remember, we're not sitting there and can't see what you can see. The error message looks to be from when SQL Server was shutting down at 08:47 this morning. There is an error regarding closing CRS_Financial, but it doesn't indicate the origin of the corruption, which must be elsewhere in your error messages. The error you do have, 9004, indicates a problem with the log. Here is a troubleshooting page from Microsoft Developers Network, MSDN (the documentation for SQL Server) that might help. But we still don't know the original error. That may be in other error logs. It appears you may be starting & stopping the server in an attempt to fix things. Don't do that. Instead, investigate your error logs to see if you can find an error reference to CRS_Financial. But, you may have to go that backup and run a restore. But, if you don't know when the error occurred, you may have backed up the error along with your database.

    Just remember, a differential is only good if you also have the full backup that matches with it. Otherwise, you will not be able to restore (unless you also have log backups). But either way, you need to have a "good" backup. This means a backup that doesn't have the corruption in it. Test your restore to a different database and validate that it can come online before you overwrite the existing database.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Krasavita (7/1/2013)


    error message,I have differential and full backup

    You do realize that most of the files in your attachment are empty, right?

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • I suspect you're going to have to restore from your last good backup.

    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
  • hello,

    I restored database to a new name and want to delete bads one,get error messa:

    Cannot drop the database because it is being used for replication,how can I remove it?

  • May I suggest you speak with the senior DBA there, get his help.

    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
  • Krasavita (7/1/2013)


    hello,

    I restored database to a new name and want to delete bads one,get error messa:

    Cannot drop the database because it is being used for replication,how can I remove it?

    Not knowing what the error message is, it's hard to suggest a solution.

    If a database is being used for replication, then you'll need to remove the replication first, then drop it. But, are we talking about dropping the test restore? Why would it suddenly get used for replication? It shouldn't be. I suspect you have a lot more going on there than you're informing us. If you want help, you have to be as clear as you possibly can. Remember, we can't see what you can see and can't know things about your system that you know. All the information we have is what you tell us.

    For example, just saying you have an error message. It could be a security error because you tried to login without permission. It could be a syntax error because of a typo. It could be that your backups are corrupt, so you restored a corrupt database and are still having problems. It could be a deadlock with some other transaction. It could be almost anything. See? So please, we're trying to help, but you've got to provide enough information for us to attempt to suggest useful answers.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 15 posts - 1 through 15 (of 26 total)

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