Post reply

Mirror - 824 Corruption

  • December 12, 2013 at 6:13 am

    #302245

    Hi all

    We've had a database mirroring session stop due to an error 824, mirror is in restoring state, I am trying to apply the latest t-log so I can bring it online and run a check db but I receive a could not redo log record error.

    Now we have full backups so I can bring it back and resume mirroring, in fact only had to do this the other day but I would prefer to get the mirror online so I can at least see what the problem is! Any ideas?

    Much appreciated as always.

    D

    'Only he who wanders finds new paths'

  • December 12, 2013 at 6:58 am

    #1672935

    If you're getting an error that a log record can't be redone, then that DB probably won't be coming online, except maybe in SUSPECT state. Try recovering the DB without restoring more logs (RESTORE DATABASE ... WITH RECOVERY)

    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

  • December 12, 2013 at 7:18 am

    #1672946

    Gail you are by far my favourite superhero!

    Yes I tried that initially and that didn't work and doing it since shows that a restore was interrupted and errors again.

    I was trying to get online to DBCC Checkdb as this is now the second time that this has happened (to the mirror only) in a few days. I suspect there may be an issue with the IO subsystem on the mirror but need more details...which I cant get.

    Thanks ever so much for the reply!

    'Only he who wanders finds new paths'

  • December 12, 2013 at 7:21 am

    #1672949

    This will probably fail, but try ALTER DATABASE ... SET EMERGENCY. If it works you can run a CheckDB in that state (not with repair)

    But any checksum failure is an indication of IO subsystem problems, the message in the error log will give you the file name.

    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

  • December 12, 2013 at 7:29 am

    #1672953

    Thanks Gail, sadly it gives a not permitted error. Looks like it is the restores then, although presumably as it error sits in IO its only a matter of time until it happens again. I'll have a word with the system admins!

    Thanks again

    D

    'Only he who wanders finds new paths'

Viewing 5 posts - 1 through 4 (of 4 total)

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