BUG: DBCC OPENTRAN Reports Incorrect Database Name

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q171944

BUG #: 17016 (WINDOWS: 6.5)

Expand all | Collapse all

SYMPTOMS

If you execute DBCC OPENTRAN against a database, the first line, which identifies the name of the database, reports an incorrect database name. However, the results show the correct open transaction information for the database specified in the DBCC statement.

Back to the top

CAUSE

The sp_renamedb procedure had previously been used to rename the database.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Back to the top

MORE INFORMATION

The name reported by DBCC OPENTRAN is the name of the database at the time it was created.

For example, if you run DBCC OPENTRAN(pubsdb), you will get the following results:

Transaction Information for database: pubs
Oldest active transaction:

        SPID          : 11
        UID           : 1
        SUID          : 1
        Name          : user_transaction
        RID           : (1365 , 7)
        Time Stamp    : 0001 0000A95F
        Start Time    : Jun 11 1997 10:35:57:086AM

DBCC execution completed. If DBCC printed error messages, see your System Administrator.

Back to the top

APPLIES TO

Microsoft SQL Server 6.5 Standard Edition

Back to the top

kbbug kbpending kbusage KB171944

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top