Error: 3041, Severity: 16, State: 1 ;Backup detected log corruption in database DatabaseName. Context is FirstSector

There is a Transaction log backup scheduled on my production server. On one bad day the Transaction log backup sql agent job throwing error and the error was like below. And I have found this error in the ERROR path(Eg:C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG)
 
Error: 3041, Severity: 16, State: 1   
Backup detected log corruption in database DatabaseName. Context is FirstSector. LogFile: 2 'E:\MSSQL\DATA\DatabaseName.ldf' VLF SeqNo: x541af1 VLFBase: x42e20000 LogBlockOffset: x43785c00 SectorStatus: 2 LogBlock.StartLsn.SeqNo: x6320656c LogBlock.StartLsn.
Blk: x6f6e6e61 Size: x656e

And the steps I have done to fix this issue is:
However Transaction log backup is not working.
1) Take the database full backup
2) Change the Data base recovery model from FULL to Simple(breaking the log backup chain and removing the requirement that the damaged portion of log must be backed up)
3) Run CHECKPOINT
4) Again change the recovery model from Simple to FULL
5) Again take FULL Backup in order to successful backups of Transaction logs

After doing above steps my transaction log backup started working successfully.

Comments

Unknown said…
What a fantastic post! This is so chock full of users information and the resources you provided was helpful to me.
This is comprehensive and helpful list. There I found one more very informative article describing about SQL Server Backup Detected Corruption In the Database Log. You may also have a look on this:
http://www.sqlmvp.org/backup-detected-corruption-in-the-database-log/
December 26, 2016 at 12:18 PM
Techie said…
One solution is to fix this error is SQL database repair software. Stellar Repair for MS SQL software easily fixes all types of corruption of SQL database. To read more about the software, please visit the official website: https://www.stellarinfo.com/sql-database-repair.php
April 9, 2019 at 3:23 PM
Post a Comment

Popular posts from this blog

System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

I got this error in one of my client's production environment, this type of issues might come up when we are not properly updating statistics. System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out Workaround: Please run UPDATE STATISTICS command in all the tables on a particular database EXEC sp_updatestats So in my scenario UPDATE STATISTICS on all the tables resolved the issue.
Read more

Pre login Handshake or Connection Timeout Period

Image
Service was unable to open new database connection when requested. SqlException: Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=16225; handshake=14840; Connection string - Data Source=sqlserverintancenamehere;Initial Catalog=CatalogNamehere;Integrated Security=True;Persist Security Info=False;Max Pool Size=1000;Connect Timeout=20;Load Balance Timeout=120;Packet Size=4096;Application Name=Applicationname hereBusinessLayerHost.exe;Workstation ID=HostnameHere setspn -a MSSQLSvc/hostname.doaminname.net:1433 ServiceAccountNameHere need to run the above command in a command prompt, most of the time you would NOT have permissions to run this, please check with Active Directory Team or Wi...
Read more

Transparent Data Encryption(TDE) with Master Key and Certificate in SQL Server

Image
/*  There is only one master key, you can not create  multiple */ use master go CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'StrongPasswordHere' GO /*  Creating certificate in the master database, after creating  master key */ use master GO CREATE CERTIFICATE MyFirstCert WITH SUBJECT = 'TDECertificate' ; GO /* Enable databse encryption key but you can not see under this specific user database. */ USE G GO CREATE DATABASE ENCRYPTION KEY WITH ALGORITHM = AES_128 ENCRYPTION BY SERVER CERTIFICATE MyFirstCert GO ALTER DATABASE G SET ENCRYPTION ON;  /*  Backing up certificate */ use master go BACKUP CERTIFICATE MyFirstCert TO FILE = 'C:\Certificates\MyFirstCert' WITH PRIVATE KEY ( FILE = 'C:\Certificates\MyFirstCertKey' , ENCRYPTION ...
Read more