Incorrect Info on Log Shipping Monitor

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

Incorrect Info on Log Shipping Monitor

Author

Topic

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2002-10-30 : 18:55:08

Hello,
Even though both databases are in sync and log shipping monitor shows 'In Sync' status and the copy/load history (View History screen) is also accurate, the copy and load time information are shown incorrectly in Enterprise Mgr for Log Shipping Monitor. Why is the monitor not getting updated with correct info? The table sysjobservers and log_shipping_monitor also show correct time in Query Analyzer.
Any ideas?
Sarat.

AjarnMark
SQL Slashing Gunting Master

3246 Posts

Posted - 2002-10-30 : 19:53:49

Not sure if this applies to your situation, but I've had numerous times where I had to manually refresh my Enterprise Manager screen to get it to display current info. Oftentimes I can only do a refresh when I'm in the left pane of the window, and not in the right.

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2002-11-01 : 17:15:26

Here is what I did to fix log shipping monitor which was showing incorrect info: I think there is an easier way though! Refreshing EM didn't help in this case!

-- 1. delete log shipping monitor (not log shipping itself).
EXEC sp_delete_log_shipping_monitor_info

-- 2. define log shipping monitor
EXEC sp_define_log_shipping_monitor

-- 3. add primary server
EXEC sp_add_log_shipping_primary

-- 4. add secondary server
EXEC sp_add_log_shipping_secondary

Thanks,
Sarat.

Sarat
Constraint Violating Yak Guru

265 Posts

Posted - 2002-11-11 : 18:24:58

Hello,
I also found there is a bug with Log Shipping in SQL 2K.
Bug #: 353349, 353719.
The bug states all changes may not be rolled back when log shipping wizard fails. So it is a good idea to run some stored procedures to make sure all log shipping details are cleared from msdb tables before recreating a new one on the server!
You may have to run the following:
1. sp_remove_log_shipping_monitor
2. sp_delete_log_shipping_primary
3. sp_delete_log_shipping_plan
4. sp_delete_log_shipping_secondary

Thanks,
Sarat.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources