Log Shipping Issue

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.

Log shipping from SQL2000EE SP3 to SP4

Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrb
That config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug surprises).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
zrajbun@.hotmail.com wrote:

>Hi,
>Source ==> SQL Server 2000 EE SP3
>Target ==> SQL Server 2000 EE SP4
>Does automated log shipping work for this configuration? Or log
>shipping requires same service pack levels?
>Thanks,
>zrb
>
>
|||Thank you Mike. I think I'll go with the same service pack levels,
keeping SP3.
b4n
zrb

Log shipping from SQL2000EE SP3 to SP4

Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrbThat config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug surprises).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
zrajbun@.hotmail.com wrote:

>Hi,
>Source ==> SQL Server 2000 EE SP3
>Target ==> SQL Server 2000 EE SP4
>Does automated log shipping work for this configuration? Or log
>shipping requires same service pack levels?
>Thanks,
>zrb
>
>|||Thank you Mike. I think I'll go with the same service pack levels,
keeping SP3.
b4n
zrb

Log shipping from SQL2000EE SP3 to SP4

Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrbThis is a multi-part message in MIME format.
--090403030908040509010200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
That config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug surprises).
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
zrajbun@.hotmail.com wrote:
>Hi,
>Source ==> SQL Server 2000 EE SP3
>Target ==> SQL Server 2000 EE SP4
>Does automated log shipping work for this configuration? Or log
>shipping requires same service pack levels?
>Thanks,
>zrb
>
>
--090403030908040509010200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>That config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug
surprises).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:zrajbun@.hotmail.com">zrajbun@.hotmail.com</a> wrote:
<blockquote
cite="mid1124169030.671658.100080@.g49g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrb
</pre>
</blockquote>
</body>
</html>
--090403030908040509010200--|||Thank you Mike. I think I'll go with the same service pack levels,
keeping SP3.
b4n
zrb