The transaction log sequence for a database is about to run out of available file names
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-09-29
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
514 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
The transaction log sequence for a database is about to run out of available file names. |
Explanation
This Error event indicates that approximately 131,000 log file names are remaining. The maximum number of transaction log files that can be generated in a single sequence is 2,147,486,647 (0x7FFFFFFF). It would require dozens to hundreds of years of operation to generate this many log files.
You can calculate how long it will take you to exhaust the remaining supply of log file names by determining how many logs are generated on a typical day, then dividing 131,000 by that number for the approximate number of days that remain. This calculation provides a very rough estimate, and it is valid only the first time that this event occurs.
However, you should immediately schedule a maintenance window during which you can resolve the problem and prevent the storage group from disconnecting by itself when the available supply of log file names is exhausted.
The transaction log file names have the following format: E0100012345.log, E01000ABCDE.log, E01000FFF00.log. The last eight characters of each log file name is the number of the log in the sequence. If ESE were to reach the last log generation number (0x7FFFFFFF), it would not be able to create another log file. Therefore, the database would be forced to shut down in a Dirty Shutdown state. To prevent this from occurring, all databases in the storage group will stop and generate a Jet_errLogSequenceEnd error message when log generation 0x7FFFFFEC is reached (16 logs before the maximum). The process stops this far before the end of the sequence so that it can create sufficient additional logs for the database to be returned to a Clean Shutdown state.
User Action
To recover from this problem, you must reset the log file sequence. To do this, you must remove all existing transaction logs. After you do this, a new sequence of log files, starting with 0x00000001 are generated.
Before you remove transaction logs, you must verify that all databases in the storage group are in a Clean Shutdown state.
For more information about how to reset the log file sequence, follow the steps in the Workaround section of Microsoft Knowledge Base article 830408, Store databases are dismounted without warning or users cannot log on to their mailboxes in Exchange Server 2003 or in Exchange 2000 Server.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.