InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 21:44:55 GMT20http://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspx[quote][b]Hemant.R (12/12/2012)[/b][hr]hi mahesh,This error occurs when someone has run a process that has broken the log chain. Probably ran the command BACKUP LOG [Jul_Reports] WITH TRUNCATE_ONLY, or the database was switched to SIMPLE recovery and then back to FULL.if someone using backup log with truncate_only command in their job please set below trace flag30313231it wont break lsn chain of database.you will get explaination for traceflag on google. [/quote] A month old post :hehe:Wed, 12 Dec 2012 02:30:18 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspxhi mahesh,This error occurs when someone has run a process that has broken the log chain. Probably ran the command BACKUP LOG [Jul_Reports] WITH TRUNCATE_ONLY, or the database was switched to SIMPLE recovery and then back to FULL.if someone using backup log with truncate_only command in their job please set below trace flag30313231it wont break lsn chain of database.you will get explaination for traceflag on google. Wed, 12 Dec 2012 00:59:49 GMTHemant.Rhttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspx[quote][b]sanket kokane (10/31/2012)[/b][hr]you have scheduled transactional log backup then why there is job for truncate log file :blink:[/quote] +1Fri, 09 Nov 2012 03:33:39 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspxyou have scheduled transactional log backup then why there is job for truncate log file :blink:Wed, 31 Oct 2012 06:14:55 GMTsanket kokanehttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspx[quote][b]mahesh.dasoni (10/30/2012)[/b][hr]I got it there is job which runs at 1:45 which truncates the log and so the log backup starts failing and it resumes once differential is completed at 3:00 am after 3 am log backup are successfull.[/quote]Don't manually truncate your log. You're breaking your log chain and reducing the options you have for restoring that DB in the case of a disaster.Please read through this - [url=http://www.sqlservercentral.com/articles/64582/]Managing Transaction Logs[/url]Wed, 31 Oct 2012 01:54:52 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspxThis error occurs when someone has run a process that has broken the log chain. Probably ran the command BACKUP LOG [Jul_Reports] WITH TRUNCATE_ONLY, or the database was switched to SIMPLE recovery and then back to FULL.Once the log chain is broken, you cannot perform transaction log backups until the log chain has been re-established. To do that, you need to perform either a full or diff backup on that database.If you don't need the database in full recovery, switch to simple and stop performing transaction log backups.Tue, 30 Oct 2012 22:39:00 GMTprettsonshttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspxI got it there is job which runs at 1:45 which truncates the log and so the log backup starts failing and it resumes once differential is completed at 3:00 am after 3 am log backup are successfull.Tue, 30 Oct 2012 21:01:51 GMTmahesh.dasonihttp://www.sqlservercentral.com/Forums/Topic1379122-357-1.aspxI have full backup scheduled daily at evening 5 PM.Differential occurs daily after every 3 hours throughout the day.Log backups are scheduled after every 15 minutes.But the scheduled after 2 am till 3 am for log backup starts failing stating the following error:"BACKUP LOG cannot be performed because there is no current database backup.BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.Tue, 30 Oct 2012 19:32:09 GMTmahesh.dasoni