Article ID: 240039 - Last Review: March 14, 2006 - Revision: 2.1

FIX: DBCC OPENTRAN Does Not Report Replication Information

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q240039
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:
232570  (http://support.microsoft.com/kb/232570/ ) INF: 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.
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Back to the top
Keywords: 
kbbug kbfix kbsqlprog KB240039