Operational Defect Database
BugZero found this defect 617 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 14676488
Error 9003 occurs with the incorrect log sequence number (LSN) when you do a subsequent restore after specifying the LSN at the virtual log file (VLF) boundary by using the RESTORE WITH STANDBY statement. Here is the error message: Msg 3013, Level 16, State 1, Line <LineNumber> RESTORE DATABASE is terminating abnormally. Msg 9003, Level 17, State 11, Line <LineNumber> The log scan number (<LogScanNumber>) 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.
Last update date:
9/20/2022
Affected products:
SQL Server 2017 on Linux
SQL Server 2017 on Windows
Affected releases:
build lower than 14.0.3456.2
Fixed releases:
14.0.3456.2
Description:
Error 9003 occurs with the incorrect log sequence number (LSN) when you do a subsequent restore after specifying the LSN at the virtual log file (VLF) boundary by using the RESTORE WITH STANDBY statement. Here is the error message: Msg 3013, Level 16, State 1, Line <LineNumber> RESTORE DATABASE is terminating abnormally. Msg 9003, Level 17, State 11, Line <LineNumber> The log scan number (<LogScanNumber>) 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.
