I had log shipping set up from serverA to serverB. One day, I start getting the automated SQL Server job failure messages.
JOB RUN: 'Log Shipping Restore for ServerA.db_nm_logshipping' was run on 10/19/2007 at 10:15:46 AM
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. Unable to retrieve steps for job Log Shipping Restore for ServerA.db_nm_logshipping.
After a few troubleshooting steps, I eventually removed and remade the maintenance plan and all associated log shipping jobs (or so I thought). For some reason, even though the new log shipping job is working properly, I'm still getting error messages from an old job.
I've ran a number of queries trying to find rogue entries still in system tables that could possibly still be trying to execute this job:
select * from dbo.log_shipping_databases where database_name = 'db_nm'
select * from dbo.log_shipping_monitor
select * from dbo.log_shipping_plan_databases where source_database = 'db_nm'
select * from dbo.log_shipping_plan_history where source_database = 'db_nm'
select * from dbo.log_shipping_plans where plan_name like '%db_nm%'
select * from dbo.log_shipping_primaries where primary_database_name = 'db_nm'
select * from dbo.log_shipping_secondaries where secondary_database_name = 'db_nm'
select * from dbo.sysdbmaintplan_databases where database_name = 'db_nm'
select * from dbo.sysdbmaintplan_jobs
select * from dbo.sysdbmaintplans where plan_name like '%db_nm%'
select * from dbo.sysjobs where name like '%db_nm%'
I couldn't find anything!
Does anyone have any idea what could be transpiring here? Any assistance would be GREATLY appreciated.
Thanks in advance!
-JoeAs a follow-up:
I ended up restarting SQL Agent. That somehow cleared out the issue.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment