FIX: DBCC OPENTRAN Does Not Report Replication Information

Article translations Article translations
Article ID: 240039 - View products that this article applies to.
This article was previously published under Q240039
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53840(SQLBUG_70)
Expand all | Collapse all

Symptoms

The DBCC OPENTRAN command does not report replication information if there are no active open transactions. If there are any active transactions, it prints information about the oldest active transaction as well as replicated transactions. A sample output from this command looks like:
   Transaction information for database 'pubs'.

   Oldest active transaction:
   SPID (server process ID) : 12
   UID (user ID) : 1
   Name          : user_transaction
   LSN           : (16:67:1)
   Start time    : Aug 18 1999 10:51:37:967AM

   Replicated Transaction Information:
   Oldest distributed LSN     : (0:0:0)
   Oldest non-distributed LSN : (16:47:1)
   DBCC execution completed. If DBCC printed error messages, contact your system administrator.
				

Status

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 240039 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbsqlprog KB240039

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