Post reply

Suspect mode error

  • November 8, 2012 at 8:48 am

    #270746

    Hi Experts,

    Getting below error when tried to recover db from suspect mode..dbcc checkdb didnt give any error but when tried to make it online give this

    The log scan number (256603:182:1) passed to log scan in database 'PRD_dis not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

    Msg 3414, Level 21, State 1, Line 1

    An error occurred during recovery, preventing the database 'PRD_d(database ID 6) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

  • November 8, 2012 at 9:12 am

    #1557236

    What can be the cause for this?

  • November 8, 2012 at 9:18 am

    #1557240

    Restore from backup.

    IO problems, like most causes of corruption, or someone tried something stupid like replacing the data or log files with older ones, or maybe a HA/DR 'solution' like SAN snapshots that doesn't support SQL and hence is more a gamble than a solution

    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

  • November 14, 2012 at 3:01 am

    #1558819

    Thanks Gail

  • November 25, 2012 at 11:29 pm

    #1562074

    I would suggest you to try third party utility such as recoveryfix for sql database repair software. This company providing a free trial version of software. You can get this software by performing search on Google.

    Thanks

  • November 29, 2012 at 2:18 pm

    #1564046

    If only the Log File is corrupt you could try to attach only the Data File with:

    sp_attach_single_file_db [@dbname=] 'dbname', [@physname=]'physical_name'

    Example:

    sp_attach_single_file_db @dbname='DataBaseName', @physname='C:\SQLServer\Data\DataBaseName_Data.mdf'

    Edit :w00t::

    you must Stop the Production SQL Server Instance in order to copy the mdf file to another location and attach to a Test SQL Server Instance.

    Hope it help you

  • November 30, 2012 at 12:09 am

    #1564172

    Highly unlikely to work. SQL can only recreate the log file if the DB was cleanly shut down prior to the log being damaged/lost.

    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

  • November 30, 2012 at 7:42 am

    #1564364

    Hello Gail, you are right... I completely forgot about that. :(... I remember that I had to put it on Emergency Mode in order to recover data, because, we did not have a backup that help us to recover our data... we did not lost data, but I lost a lot of time due to our past backup process.

  • March 2, 2013 at 12:15 pm

    #1592703

    Hey Guys before few days my data source dropped into suppose method.I set data source using dbcc check db in urgent method and now it seems ok. But I don't know why this incident happens. does anybody know possible reason?

  • March 2, 2013 at 1:48 pm

    #1592713

    Corruption most likely, meaning something wrong with the IO subsystem. Can't say more without more info.

    btw, checkDB is the last resort for fixing suspect databases, you should rather have restored a 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

Viewing 10 posts - 1 through 9 (of 9 total)

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