Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««45678

Why is my transaction log full? Expand / Collapse
Author
Message
Posted Tuesday, September 4, 2012 9:06 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:14 AM
Points: 42,460, Visits: 35,520
As you identified, the cause of the log being full is the active backup. The checkDB errors are all a result of the log being full, nothing else.

You need to identify why the backups are running so much longer than usual. Immediate thought - IO subsystem contention.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1353977
Posted Tuesday, September 4, 2012 9:13 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, July 22, 2014 8:44 PM
Points: 358, Visits: 901
Forgot to mention the tlog growth from the start as I was pretty sure that was also an issue. The log file growth was set to 10 % and the free space on the drive was about 10% of the entire drive. Obviously that's an issue. Changed that to 10 MB and am running another backup.


Gail, I think it's a combination of issues. I think they deleted a backup file that was still in progress. Is there any way to stop this backup operation that the sys.databases table thinks is still in progress?

Correction: The backup failed b/c the tlog ran out of space 2 days ago. There is no backup run Sunday night/Monday morning. Then a backup attempted to run this morning with the previous backup showing as still active in sys.databases. Ugh what a mess.
Post #1353982
Posted Tuesday, September 4, 2012 9:30 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, July 22, 2014 8:44 PM
Points: 358, Visits: 901
I guess the question still is:

Is there any way to stop this backup operation that the sys.databases table thinks is still in progress?


A previous job was stopped and a job that followed that failed. It appears that SQL Server thinks the stopped job is still running. I can see no other indication of this other than ACTIVE_BACKUP_OR_RESTORE as the log_wait_reuse_desc in sys.databases. Even the location of the backup files is empty.
Post #1353995
Posted Tuesday, September 4, 2012 10:15 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:14 AM
Points: 42,460, Visits: 35,520
New thread please. The discussion thread of an article is not the best place for a problem that isn't directly related to the article.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1354025
Posted Thursday, November 22, 2012 6:35 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 5:24 AM
Points: 826, Visits: 2,662
Hi Gail,

Can I please ask a quick question. In your article you say the following:

Log backup

The log backup wait reason will never appear in Simple Recovery.


Now I do agree this is a valid statement, however:

SELECT  database_id,
recovery_model_desc,
log_reuse_wait_desc
FROM sys.databases
WHERE log_reuse_wait_desc <> 'NOTHING'

database_id recovery_model_desc log_reuse_wait_desc
46 SIMPLE LOG_BACKUP

Why would I be seeing this?

Thanks




The SQL Guy @ blogspot

@SeanPearceSQL

About Me
Post #1387871
Posted Thursday, November 22, 2012 11:23 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:14 AM
Points: 42,460, Visits: 35,520
Has the DB just been switched from full or bulk-logged recovery? If so, run a checkpoint, sys.databases is not updated immediately, hence you can get 'log backup' occurring for a very short period after the DB has been switched to simple recovery model.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1387957
Posted Thursday, November 22, 2012 1:07 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, July 25, 2014 10:16 AM
Points: 1,612, Visits: 1,537
Artoo22 (11/22/2012)


Log backup

The log backup wait reason will never appear in Simple Recovery.


Now I do agree this is a valid statement, however:


Actually, that's not an accurate statement. This column records the reason the log file could not be truncated the last time it tried to do so. In simple recovery model, this means that it gets updated, if there is a reason, when a checkpoint occurs.

For example:





My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server 2008
Principal DBA: Outerwall, Inc.
Also available for consulting: SQL DBA Master
Post #1387977
« Prev Topic | Next Topic »

Add to briefcase «««45678

Permissions Expand / Collapse