Quantcast
Channel: Forum SQL Server Database Engine
Viewing all articles
Browse latest Browse all 15889

Cannot add new transaction log file, or grow existing one, because transaction log is full

$
0
0

My database (SQL2012SP1 EE) is in simple recovery model. My free space on the disk is at least 10 times the size of my database.

It seems I cannot make any changes to the database because the transaction log is full due to 'CHECKPOINT'.

What puzzles me, is that this includes adding a new log file or growing the existing one -- wouldn't one expect to be able to add more transaction log space even though the existing transaction log is full?

Summary:

    I cannot add a new transaction log file
    I cannot grow the existing one
    I cannot take a backup (not even copy-only)
    I cannot take a database snapshot
    I cannot run a DBCC CHECKDB
    I cannot run a manual CHECKPOINT
    I have a lot of VLFs in the log (some 200+, all in state 2)
    DBCC OPENTRAN  shows no open transactions
    I have 4.5M rows in fn_dblog (NULL, NULL)

However, I can make a copy of all the data using SSIS Import/Export wizard, so it seems that the data is fine?

I have posted this to a couple places looking for suggestions. Perhaps the thread with the most info is this one: (forum will not allow me to post link -- if you are curious, see sqlservercentral forum topic 1451836-2799-1)



Viewing all articles
Browse latest Browse all 15889

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>