Symptoms
Assume that you use database mirroring in high-performance mode in Microsoft SQL Server 2012. When you try to add new file groups to the principal database, new files in the new file groups are not synchronized on the mirror server. Additionally, you receive the following error message on the mirror server:
<Date><Time> spid# Error: 3456, Severity: 21, State: 1.
<Date><Time> spid# Could not redo log record (132:975:2), for transaction ID (0:15811), on page (4:10), allocation unit 72057594043498496, database ‘<Databasename>’ (database ID 10). Page: LSN = (103:1130:2), allocation unit = 72057594043498496, type = 1. Log: OpCode = 4, context 1, PrevPageLSN: (103:1130:24). Restore from a backup of the database, or repair the database.
<Date><Time> spid# Error: 1454, Severity: 16, State: 1.
<Date><Time> spid# Database mirroring will be suspended. Server instance ‘Domain\servername’ encountered error 3456, state 1, severity 21 when it was acting as a mirroring partner for database ‘<Databasename>’. The database mirroring partners might try to recover automatically from the error and resume the mirroring session.
Note This issue only occurs in Microsoft SQL Server 2012.
Resolution
Cumulative update information
Cumulative Update 3 for SQL Server 2012 SP1
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412 Cumulative update package 3 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative Update 6 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2728897 Cumulative update package 6 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
