FIX: DTC Log File Corruption or Growth Problems (197812)
The information in this article applies to:
- Microsoft Transaction Server 2.0
This article was previously published under Q197812 SYMPTOMS
This hotfix corrects several DTC log problems:
- When Microsoft Distributed Transaction Coordinator (DTC) is used with an
XA-compliant resource manager such as Oracle, IBM DB2, or Informix, the
Dtcxatm.log file can grow to an extremely large size. In some cases the
log file may consume several hundred megabytes of disk space. The size
of the log file may also affect recovery time. When recovery is
performed, MS DTC reads through the entire log file which 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. This problem has
been corrected.
- The MS DTC service may fail to start because the Msdtc.log file was
corrupted. There were two circumstances under which this could occur.
- If MS DTC recovery occurs just after MS DTC reaches the end of the
log file and resumes writing at the beginning of the log file.
-or-
- If MS DTC recovery is performed twice in very quick succession.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Transaction
Server version 2.0.
This bug was corrected in COM+.
Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbBug kbDTC kbfix KB197812 |
---|
|