Microsoft KB Archive/158291

= BUG: Problem Using 'Create Table' When Transaction Log Is Full =

Article ID: 158291

Article Last Modified on 3/1/2005

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q158291



BUG #: 15980 (6.50)



SYMPTOMS
When the transaction log is full, using 'Create table' may leave the table in an unreachable state.

You can see the table in SQL Server Enterprise Manager, but the sysstat column in the sysobjects table shows a value of 195 instead of 67. Attempting to drop the table fails with the following error:

Msg 3701, Level 11, State 1, Server bp71092, Line 1

Cannot drop the table '%s', because it doesn't exist in the system catalogs.

The 'Create table' command also fails, with the following error:

Msg 2714, Level 16, State 1, Server bp71092, Line 1 There is already an

object named '%' in the database.



WORKAROUND
To work around this problem, use the following commands to run sp_configure 'allow':

go  reconfigure with override go  update sysobjects set sysstat=67 where id=table_id

Then drop the table.



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

Keywords: kbbug kbusage KB158291

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.