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

  • well, after some much needed sleep, and some review by the goddess of databases, i awoke to a few messages (see above) from Gail that indicated i could try 1 thing, after making more room, or start over. Obviously the first task would be better on my damaged soul.

    I had previously freed up 5G of space, and then this morning i freed up some more, as much as I could, (it was about 12G in total) and told the DB to come online. As I watched the disk to see if it would report being consumed (it did not) I also watched the log by manically refreshing it until it finished restoring the DB. The DB came online, DBCC checkdb finished successfully and it picked up where it left off, chugging through its log file and replicating data elsewhere.

    I added another log file onto another lun that has more room (so i think now, similar to my thinking before with the lun where the log resided). So there are now 2 log files, one with the potential to outgrow its container, and the other less so.

    Replication is chugging along, data is moving, things seem to be ok at the moment.

    Review of our processes that allow such a massive amount of data movement need to occur. But that may need to wait for another day. Bandaids are in place now, and fingers are crossed that it will all continue to go well. I will continue to monitor it until it is done doing its stuff, settles down to normalcy and then my heart rate can go back down.

    Until then, fingers crossed.