LsAlert job is failing on Primary Instance

Question

LsAlert job is failing on Primary Instance

juniorDBA13

Ten Centuries

Points: 1052
More actions
October 28, 2016 at 7:07 am

#331381

I have reconfigured logshipping but my LSAlert job on the primary is still failing.
On the secondary the transaction log shipping status report is showing OK, logs are being copied and restored.
The transaction log shipping status report on the primary is showing restore/copied information from before it was recreated logshipping.
Please advise how i can resolve this?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Sue_H SSC Guru Points: 90860 More actions · Answer 1

juniorDBA13 (10/28/2016)
I have reconfigured logshipping but my LSAlert job on the primary is still failing.
On the secondary the transaction log shipping status report is showing OK, logs are being copied and restored.
The transaction log shipping status report on the primary is showing restore/copied information from before it was recreated logshipping.
Please advise how i can resolve this?

The tables used for monitoring could be stale. You can try updating those by executing sp_refresh_log_shipping_monitor on the secondary server.

Sue

juniorDBA13 Ten Centuries Points: 1052 More actions · Answer 2

I ran the following on the secondary

execute sp_refresh_log_shipping_monitor

@agent_id = 'B7EE4B00-364A-49F4-AC4A-391722F0E66D',

@agent_type = 1,

@database = 'Database',

@mode = 1

Getting agent ID from the below query

select *

from msdb.dbo.log_shipping_secondary_databases as sd

join msdb.dbo.log_shipping_secondary as s

on sd.secondary_id = s.secondary_id

The query executed but hasn't updated the report

Sue_H SSC Guru Points: 90860 More actions · Answer 3

Have you verified all the backup logs are in the shared folder?

Have the latest logs been applied to the secondary?

Are there issues with the copy, restore jobs?

Sue

juniorDBA13 Ten Centuries Points: 1052 More actions · Answer 4

Yes backup log are in the shared folder.

The logs are being applied to the secondary.

No issues with copy/restore jobs.

Transaction log report showing correctly on the secondary.

On the primary, transaction log report is showing restore/copy information. Should it be showing this since this is completed on the secondary?

Would an instance restart fix the issue?

Perry Whittle SSC Guru Points: 234013 More actions · Answer 5

check the step history carefully, although theyre marked as successful there'll likely be a message indicating logs cannot be applied

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉