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

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

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:

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.

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.