Home Forums SQL Server 2005 Administering My log file became not available and the database went into Recovery Pending mode RE: My log file became not available and the database went into Recovery Pending mode

  • tjaybelt (12/24/2013)


    Log entry:Error: 3314, Severity: 21, State: 1.

    During undoing of a logged operation in database 'ILCentralDataEnt', an error occurred at log record ID (386988:95874:18). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

    And that's the bummer.

    It may be a bug where SQL didn't reserve enough space to roll back. Shouldn't ever happen, but there could be a bug. Try freeing up some space and trying again to bring the DB online. From the error log it's running out of space during the undo phase of recovery, which shouldn't ever happen. You may need to move one of the other logs to another drive temporarily to make space.

    If you get the same errors when there is enough space (error during undo/redo), locate your backups and start restoring (or emergency mode repair, but I'd recommend the restore).

    btw, you seem to have a problem with Distribution too. That may be why the replication wait, if the log reader agent wasn't working properly, log would have grown as it would not be able to reuse space.

    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