MSSQLSERVER_3456
Applies to: 
SQL Server
Details
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 3456 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | REC_REDOLSNMISMATCH |
| Message Text | Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (database ID %d). Page: LSN = %S_LSN, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore from a backup of the database, or repair the database. |
Explanation
The restore operation was unable to redo the transaction log. This error has placed the database into the SUSPECT state. The primary filegroup, and possibly other filegroups, are suspect and may be damaged. The database cannot be recovered during startup of SQL Server and is therefore unavailable. User action is required to resolve the problem.
Note that if this error occurs for tempdb, the SQL Server instance shuts down.
User Action
This error can be caused by a transient condition that existed on the system during a given attempt to start up the server instance or to recover a database. This error can also be caused by a permanent failure that occurs every time that you attempt to start the database. For information about the cause, examine the Windows Event Log for a previous error that indicates the specific failure.
For information about the cause of this occurrence of error 3456, examine the Windows Event Log for a previous error that indicates the specific failure. The appropriate user action depends on whether the information in the Windows Event Log indicates that the SQL Server error was caused by a transient condition or a permanent failure. For information about the user actions for troubleshooting error 3456, see SQL Server Books Online.
See Also
ALTER DATABASE (Transact-SQL)
DBCC CHECKDB (Transact-SQL)
Complete Database Restores (Simple Recovery Model)
MSSQLSERVER_824
sys.databases (Transact-SQL)