Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Update to monitor uncommitted transaction log files


View products that this article applies to.

Summary

This article discusses an Exchange 2000 update that you can use to create a new performance counter that monitors uncommitted transaction log files (checkpoint log file depth in generations).

↑ Back to the top


More information

Cumulative Rollup Information

For additional information about a hotfix rollup that contains this update, click the following article number to view the article in the Microsoft Knowledge Base:
824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
The Log Generation Checkpoint Depth performance counter reports uncommitted transaction log files in the number of log files (generations) instead of the number of bytes. The Log Generation Checkpoint Depth performance counter reports how many Extensible Storage Engine (ESE) transaction log files have content that has not yet been committed to the ESE database. This number represents the number of transaction log files that must be added or committed (rolled forward) to the ESE database if the Information Store process (Store.exe) stops responding (hangs). As the log file generation depth increases, the information store startup time increases.

If the transaction log file depth reaches 1000, ESE dismounts all the databases that are in the affected storage group. The transaction log file depth may grow during periods when the server is very busy. However, very large values typically occur when there is a failure. For example, during a backup operation, the backup program may request that Exchange 2000 not roll forward transaction log files so that a consistent backup may be performed. However, if the backup program stops responding, Exchange 2000 may not be instructed to resume rolling forward the transaction log files. In this case, the number of uncommitted transaction log files increases. To resolve this issue, stop and then restart the Information Store service.

A supported feature that modifies the default behavior of the product is available from Microsoft. However, this feature is intended to modify only the behavior that this article describes. Apply this feature only to systems that specifically require it.

If the feature is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the feature.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific feature. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the feature is available. If you do not see your language, it is because the feature is not available for that language.
Component: Extensible Storage Engine

The English version of this update has the file attributes (or later) 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.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   06-Jun-2003  22:04  6.0.6473.0      2,183,168  Ese.dll          
   06-Jun-2003  22:04  6.0.6473.0         40,960  Eseperf.dll      
   22-May-2003  20:01                      6,991  Eseperf.hxx
   22-May-2003  20:01                    107,477  Eseperf.ini   
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to Obtain the Latest Exchange 2000 Server Service Pack
After you install the update that is described in this article, you must unload and then reload the ESE performance counters to enable the Log Generation Checkpoint Depth counter. To do so:
  1. Start a command prompt, and then locate the folder that contains the Eseprf.ini file and the Eseprf.hxx file.

    Typically, these files are in the following folder:
    C:\Program Files\Exchsrvr\Bin
  2. Type unlodctr.exe ese, and then press ENTER.
  3. Type lodctr.exe eseperf.ini, and then press ENTER.
  4. Quit the command prompt, and then restart the Exchange 2000 computer.
  5. Verify that the new performance counter is installed:
    1. Click Start, point to Programs, point to Administrative Tools, and then click Performance.
    2. Click the Add (+) button.
    3. In the Select counters from computer list, click your Exchange 2000 computer.
    4. In the Performance object list , click Database ==> Instances.
    5. In the Select counters from list list, make sure that the Log Generation Checkpoint Depth item appears.

↑ Back to the top


Keywords: KB819771, kbbug, kbexchange2000presp4fix, kbfix, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 819771
Revision : 7
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 205