Post reply

Transaction Log Restore Error

  • February 2, 2004 at 9:25 am

    #106873

    My production database suffered from a database inconsistency error this morning. This involved a block of data being duplicated, effectively trashing the primary key index (a clustered index at that). I was able to recover with no loss of data by deleting the affected rows, reinserting them from an archive database (which holds a full copy of ALL inserted or updated rows), and finally rebuilding all the indexes.

    So far so good. However, an hour later, a problem occured on the warm standby server, which failed to load the trnsaction logs for the period when I was fixing the production box. I got this error message:

    Processed 23219 pages for database 'isco4live', file 'isco4_log' on file 14.

    Server: Msg 3456, Level 21, State 1, Line 1

    Could not redo log record (3031:40619:11), for transaction ID (0:51759526),

    on page (1:695441), database 'isco4live' (8).

    Page: LSN = (3020:36876:2), type = 1. Log: OpCode = 3, context 1, PrevPageLSN: (3020:26121:7).

    Connection Broken

    Unfortunately, I can find no reference to Msg 3456 in BOL or on MSDN-on-line.

    Can anone offer any help? As a last resort I can do a full backup of the production database and restore that, but I don't want that performance hit during working hours if I can help it.


    Tony

  • February 5, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • February 10, 2004 at 6:59 am

    #493368

    Hy Tony !

    I´m having the same problem as you; I posted a question today with the same problem ... Could Not Redo Log Record ....

    I found a answer at Microsoft Knowledge base at http://support.microsoft.com/default.aspx?scid=kb;en-us;831950&Product=sql2k, but when you click at "Resolution" appears a form with "Contact Us Pane" .....

    I don´t know if you have any contract with Microsoft ... If you have any, you could try at this URL and, please CONTACT ME IF YOU HAVE A CLUE 

    []s

    Paulo Ribeiro

     

     

     

  • February 10, 2004 at 7:18 am

    #493371

    Hi Paulo,

    I checked out that URL, and it does provide an expanation for what happened; between shipping logs I had done some SERIOUS rebuilding work on indexes etc, to fix the original cause of my problem. As I have now resolved the problem myself (by restoring a new complete backup), I guess I will wait for the next SP rather than try to get a hot fix out of Microsoft (I do have a support contract, but is it worth the hassle?)


    Tony

  • February 10, 2004 at 7:51 am

    #493380

    Hi, Tony!

    I´ve been having this problem with high frequency and I always solve as you did: restoring a full backup but; but I have some databases with 30GB and sometimes it takes a long period and spends a lot of net resources to restore it !

    Yes, this URL does not provides a good explanation BUT THERE´S A HOTFIX ! As you have a contract, I´d be very, but very grateful if you contact them and send me a copy

    Thanks,

    Paulo Ribeiro

     

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

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