Dtcxatm.log File Grows Unexpectedly Large
This article was previously published under Q229613
This article has been archived. It is offered "as is" and will no longer be updated.
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.
This problem occurs because of an error in the way that space is reclaimed in the log file.
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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service PackThe following files were modified in Windows NT 4.0 Service Pack 5 to fix this problem:
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.
Article ID: 229613 - Last Review: 01/06/2015 04:42:54 - Revision: 1.1
Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition
- kbnosurvey kbarchive kbbug kbfix kbqfe KB229613