Hi All,

 we are using the log shipping for high aviability .But some tome we get an error that LSN missmatch error.We had temp. solution  that we manually restore the tranctional log.But i need some permanent solution ?Can any one help regarding this?

Which version of SQL server and SP are your working on ?

Some usefull links on smilar issue in case it is the same

http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3317433&SiteID=1

This is the most common issue, for some reason if the last t-log backup is not restored and another t-log backup has been taken and shipped to the standby server this will come up. Some times it happens that latency time is not set accordingly i.e. taking a t-log backup -> copying to standby -> restore requires 10 mins time and you have configured t-log backup for every 5 mins

IMO this error requires manual intervention, untill you set retry option in your restore job for t-log on standby server.

hth

Do you have any non-logged operations in between the log shipping schedule and changing the database options intermittently?

What is the schedule of log shipping restore on the standby server?

Yes, as Satya said if such non-logged or minimal logged operations happens between the two t-log backup it also lead to this behaviour, such as truncate opeartion