SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Gaps in tlogs


Gaps in tlogs

Author
Message
j2cagle
j2cagle
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 22
Ok, so here's the issue. We have a report server database that has been correctly been updating tlogs for years. A couple days ago, we shrunk the live database/log, and now we continue to receive "gaps" in the tlogs. Does anyone have any suggestions on how to resolve this? Should we somehow restore the entire report server database with the live database...and the tlog shipping will just kick in from there??
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87845 Visits: 45274
What do you mean by 'gaps in the tlogs'?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10386 Visits: 13687
how did you shrink the log, what commands did you issue?

Are you saying log shipping is now broken due to missing lsns?

If so and you have not issued a full backup of the live database since the log truncate you can restart log shipping using a differential backup, else you will need to restore the secondary from a full backup (with norecovery), log shipping will then pick up again.

---------------------------------------------------------------------
j2cagle
j2cagle
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 22
You hit the nail on the head. I ended up taking the full backup of the live DB (that occurred last night), restoring it to the report server DB, then restoring the log files up to the present. All seems good now! I'll keep an eye on it.

FYI: For me, the real secret was to RESTORE WITH STANDBY!!
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10386 Visits: 13687
j2cagle (8/3/2013)
You hit the nail on the head. I ended up taking the full backup of the live DB (that occurred last night), restoring it to the report server DB, then restoring the log files up to the present. All seems good now! I'll keep an eye on it.

FYI: For me, the real secret was to RESTORE WITH STANDBY!!

thought I might have, The first log restore run via the log shipping jobs would have put the database into whatever mode you had set before (restoring or standby mode).

---------------------------------------------------------------------
j2cagle
j2cagle
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 22
george sibbald (8/3/2013)
The first log restore run via the log shipping jobs would have put the database into whatever mode you had set before (restoring or standby mode).


I was thinking that it would do that, but I was impatient so forced it myself...
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search