Dtcxatm.log File Grows Unexpectedly Large

Article translations Article translations
Article ID: 229613 - View products that this article applies to.
This article was previously published under Q229613
Expand all | Collapse all

SYMPTOMS

When Microsoft SQL Server is used with an XA-compliant resource manager (for example, Oracle, IMB DB2, or Informix), the Dtcxatm.log file can grow quite large. For example, it is possible for files to reach several hundred MB in size. Therfore, when recovery is performed, Microsoft Distributed Transaction Coordinator (DTC) reads through the entire log file. This can lead to extremely long recovery times.

CAUSE

This problem occurs because of an error in the way that space is reclaimed in the log file.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
The following files were modified in Windows NT 4.0 Service Pack 5 to fix this problem:

Collapse this tableExpand this table
NameDateTimeSize
Dtccm.dll4/22/9912:04p110,864
Dtcxatm.dll4/22/9912:04p162,064
Logmgr.dll4/22/9912:04p59,664
Msdtcprx.dll4/22/9912:04p189,712
Msdtctm.dll4/22/9912:04p456,976
Mtxoci.dll4/22/9912:04p69,904

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5.

Properties

Article ID: 229613 - Last Review: November 1, 2006 - Revision: 1.1
APPLIES TO
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
Keywords: 
kbbug kbfix kbqfe KB229613

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com