Symptoms
If you try to rebuild an index in Microsoft SQL Server 2012 and the transaction log fills during the rebuilding process, you receive the following error messages:
Msg 9002, Level 17, State 2, Line 1The transaction log for database 'DatabaseName' is full due to 'LOG_BACKUP'. Msg 9002, Level 17, State 2, Line 1The transaction log for database 'DatabaseName' is full due to 'LOG_BACKUP'. Msg 3314, Level 21, State 3, Line 1During undoing of a logged operation in database 'DatabaseName', an error occurred at log record ID (78:420:37). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.Msg 9001, Level 21, State 5, Line 1The log for database 'DatabaseName' is not available. Check the event log for related error messages. Resolve any errors and restart the database.Msg 3314, Level 21, State 3, Line 1During undoing of a logged operation in database 'DatabaseName', an error occurred at log record ID (78:446:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.Msg 3314, Level 21, State 5, Line 1During undoing of a logged operation in database 'DatabaseName', an error occurred at log record ID (78:420:13). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.Msg 0, Level 20, State 0, Line 0A severe error occurred on the current command. The results, if any, should be discarded.
Additionally, the database is taken offline, and its status is changed to "In Recovery."
Resolution
Cumulative update information
Cumulative update package 1 for SQL Server 2012 Service Pack 1
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2765331 Cumulative update package 1 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 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
SQL Server 2012
The fix for this issue was first released in Cumulative Update 4. 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:
2758687 Cumulative update package 4 for SQL Server 2012 Note 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.
