Error “System Assertion Check has failed” Msg 3624, Level 17, State 1 when trying to do a log restore with the STOPATMARK option in SQL 2008

By tom on June 23rd, 2011

Recently our operational team had to do a restore of a database for BizTalk. These databases require a special restore routine, to let the BizTalk components in sync with the DB.

First they restored the latest full backup, which went without problems.

Then they needed to restore the transaction log backups, with the STOPATMARK option set:

RESTORE LOG [Database] FROM

DISK = N’LocationOfBackupFile’

WITH FILE = 1, NOUNLOAD, STATS = 10,

STOPATMARK = N’BTS_2011_06_06_00_00_29_087′ AFTER N’2011-06-06T02:00:32′

GO

which results in an error:

100 percent processed.

Processed 0 pages for database ‘Database’, file ‘Database’ on file 1.

Processed 2 pages for database ‘Database’, file ‘Database_log’ on file 1.

Location:     diskio.c:1769

Expression:   filepos + cBytes <= (DWORDLONG) m_size << PAGESIZEBITS

SPID:         65

Process ID:   1908

Msg 3013, Level 16, State 1, Line 1

RESTORE LOG is terminating abnormally.

Msg 3624, Level 17, State 1, Line 1

A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

When restoring the log without the STOPATMARK option, no problems are encountered.

The log mark entries where all filled in correctly. You can see this by querying the dbo.logmarkhistory table in msdb.

We opened a case at Microsoft and they confirmed that this is a bug and is fixed in CU4 for SQL 2008 SP2 (http://support.microsoft.com/kb/2527180). I’ve asked for more information, but they cannot provide it for the moment as it is confidential. I still hope to find some more information though, I’ll update this post with the details.

Tom

New cumulative update packs for SQL 2008 SP1 and SP2

By tom on June 1st, 2011

Microsoft recently released two new cumulative updates: CU14 for SQL 2008 SP1 and CU4 for SQL 2008 SP2.

This makes following build table:

Version Service Pack (SP) / Cumulative Update (CU)
10.50.1777.0 R2 CU7
10.50.1765.0 R2 CU6
10.50.1753.0 R2 CU5
10.50.1746.0 R2 CU4
10.50.1734.0 R2 CU3
10.50.1720.0 R2 CU2
10.50.1702.0 R2 CU1
10.50.1600.1 SQL 2008 R2 RTM

 

Current Cumulative Update Packs for SQL 2008:

10.0.4285.0 SP2 CU4
10.0.4279.0 SP2 CU3
10.0.4272.0 SP2 CU2
10.0.4266.0 SP2 CU1
10.0.4000.0 SP2
10.0.2821.0 SP1 CU14
10.0.2816.0 SP1 CU13
10.0.2808.0 SP1 CU12
10.0.2804.0 SP1 CU11
10.0.2799.0 SP1 CU10
10.0.2789.0 SP1 CU9
10.0.2775.0 SP1 CU8
10.0.2766.0 SP1 CU7
10.0.2757.0 SP1 CU6
10.0.2746.0 SP1 CU5
10.0.2734.0 SP1 CU4
10.0.2723.0 SP1 CU3
10.0.2714.0 SP1 CU2
10.0.2710.0 SP1 CU1
10.0.2531.0 SP1
10.0.1835.0 CU10
10.0.1828.0 CU9
10.0.1823.0 CU8
10.0.1818.0 CU7
10.0.1812.0 CU6
10.0.1806.0 CU5
10.0.1798.0 CU4
10.0.1787.0 CU3
10.0.1779.0 CU2
10.0.1763.0 CU1
10.0.1600.0 SQL 2008 RTM