KB4466994 - FIX: "3414" and "9003" errors and a .pmm log file grows large in SQL Server 2016 and 2017

Applies To
SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use) SQL Server 2017 Developer on Windows SQL Server 2017 Enterprise on Windows SQL Server 2017 Enterprise Core on Windows SQL Server 2017 Standard on Windows

Symptoms

Assume that a .pmm log file grows large in Microsoft SQL Server 2016 and 2017. If you restart the SQL Server database, you notice that the server that is running SQL Server does not come online. Additionally, you may receive the following error messages:

Note

Msg 5181, Level 16, State 5, Line LineNumber
Could not restart database DatabaseName. Reverting to the previous status.
Msg 5069, Level 16, State 1, Line LineNumber
ALTER DATABASE statement failed.
Msg 9003, Level 20, State 9, Line LineNumber
The log scan number (44:33024:0) passed to log scan in database DatabaseName 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.
Msg 3414, Level 21, State 4, Line LineNumber
An error occurred during recovery, preventing the database DatabaseName (5:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

Cumulative Update 13 for SQL Server 2017

Cumulative update 4 for SQL Server 2016 SP2

About cumulative updates for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2017

Latest cumulative update for SQL Server 2016

This problem is fixed in the following on-demand hotfix for Cumulative Update 3 for SQL Server 2016 Service Pack 2:

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the English (en-US) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the German (de-DE) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Spanish (es-ES) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the French (fr-FR) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Italian (it-IT) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Japanese (jp-JP) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Korean (ko-KO) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Portuguese (pt-PT) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Russian (ru-RU) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Simplified Chinese (zh-CN) on-demand hotfix now.

2d4e4a79-700a-8d0b-daea-cb25f86a295b Download the Traditional Chinese (zh-TW) on-demand hotfix now.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.