none
Error 9003 Log Scan is Invalid Error When Restoring Transaction Log After SQL2016 SP2 + CU8 Upgrade RRS feed

  • Question

  • We are using SQL 2016 Enterprise Edition and have recently applied SP2 + CU8. We were previously on SP1 + CU6. Since the update we are getting the following error when restoring transaction logs on our DR server.

    The log scan number (20913:512:1) passed to log scan in database '' is 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.

    The log restore succeeds if NORECOVERY is used and then later logs are applied successfully with STANDBY. But if the file that causes the error is applied with STANDBY future log restores fail when using either NORECOVERY or STANDBY. The only fix we have found is to do a full restore.

    Is there any other workaround other than a full restore?

    The frequency of the error is 2 times a day on 3 different databases. The log backups originated from an AlwaysOn secondary server.

    Thursday, September 12, 2019 4:54 AM

All replies

  • Hi dbadanptml,

    Could you please try to uninstall CU8? Please refer to https://support.microsoft.com/en-us/help/940126/fix-error-9003-is-logged-in-the-sql-server-error-log-file-when-you-use

    Best regards,
    Cathy 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, September 13, 2019 8:18 AM
  • Please upgrade SQL Server to latest SP and let us know if that fixes your issue

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Friday, September 13, 2019 10:28 AM
    Moderator
  • Thanks. I have done this successfully in our Test environment and will do this on Production next.  As a workaround we are now taking our log backups on the Primary server and did not see the error last night.
    Friday, September 13, 2019 4:57 PM
  • We have upgraded to the latest SP + CU.  That is what caused the error.
    Friday, September 13, 2019 4:58 PM
  • Uninstalled CU8 so are now on just SP2 and are still receiving this error when restoring log backups taken on the secondary server of a Synchronous always On Availability Group.  

    The workaround to take log backups on the primary has so far worked fine so we will have to do this until Microsoft come up with a fix. 

    Monday, September 16, 2019 8:34 AM
  • Uninstalled CU8 so are now on just SP2 and are still receiving this error when restoring log backups taken on the secondary server of a Synchronous always On Availability Group.  

    The workaround to take log backups on the primary has so far worked fine so we will have to do this until Microsoft come up with a fix. 

    Hi dbadanptml,

    You can submit your issue to the Microsoft feedback at this link https://feedback.azure.com/forums/908035-sql-server . This site will serve as a connecting point between you and Microsoft, and ultimately the large community for you and Microsoft to interact with. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft feedback.

    Best regards,
    Cathy 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, September 17, 2019 8:38 AM