This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 470638 (SHILOH_BUGS)
If you have implemented log shipping solutions in Microsoft SQL Server 2000 and you try to apply a transaction log to a server, it is not successful. You receive the following error message:
Msg 3456, Level 21, State 1, Server '<Server Name>', Line 4 Could not redo log record (15:40:4), for transaction ID (0:5033), on page (1:24), database '<Database Name>' (11). Page: LSN = (15:29:2), type = 1. Log: OpCode = 9, context 2, PrevPageLSN: (14:503:4).
This problem typically occurs in log shipping scenarios that involve database role switching. For this problem to occur, you must have issued a backup database with the NORECOVERY option.
Note This hotfix does not correct problems with the current transaction log. However, it does stop this problem in future transaction logs.
SQL Server may permit logging after you issue the backup log with the NORECOVERY option. This problem generally involves internal transactions (synchronizing sysindexes with a row count for a particular table after many insert operations or delete operations occur on the table, for example).
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.