BUG: DBCC OPENTRAN Reports Incorrect Database Name

 Last reviewed: July 30, 1997
Article ID: Q171944
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 17016 (WINDOWS: 6.5)

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.

CAUSE

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

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.

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. 
Keywords          : kbbug6.50 SSrvGen kbusage
Version           : 6.5
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.