steven

While trying to create a maintentance plan with log
shipping I get the following error: Error 208: "Invalid
object name 'msdb.dbo.log_shipping_monitor'." After I set
the log shipping threshholds and click next. This server
was recently restored from a backup tape and SQL server
reinstalled. Any ideas what causes this error?

petery

Hello Steven,

Thank you for you posting! If I understand this correctly, you are not able
to create a maintenance plan with log shipping after reinstall SQL server
and restoring the database.

First I would like to confirm you installed Enterprise Edition of SQL
server 2000.

Based on my research, this issue can occur if some log shipping tables and
stored procedures are missing. This may cause the following errors in two
different steps when you run the Database Maintenance wizard to configure
log shipping:

Error 208: Invalid Object name msdb.dbo.log_shipping_monitor


-and-

Error 2812 : could not find msdb.dbo.sp_define_log_shipping_monitor

In order to solve the issue, I suggest that you run the log shipping
installation script, instls.sql, which is located in the \Install folder of
the Enterprise edition CD.

You can refer to the following article for more related information.

295306.KB.EN-US BUG: Log Shipping Elements are Missing After You Upgrade
from Standard
http://support.microsoft.com/default.aspx?scid=KB;EN-US;295306

If you have further questions on the issue, please feel free to post back.

Thanks & Regards,

Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support

Get Secure! - http://www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
| Content-Class: urn:content-classes:message
| From: "Steven" <steven@woodwyn.com>
| Sender: "Steven" <steven@woodwyn.com>
| Subject: Log Shipping
| Date: Thu, 24 Jul 2003 07:27:30 -0700
| Lines: 6
| Message-ID: <003f01c351ef$b72a6b70$a101280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNR77cquWKwEveqT82V+92qvxHjjw==
| Newsgroups: microsoft.public.sqlserver.setup
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.setup:55810
| NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
| X-Tomcat-NG: microsoft.public.sqlserver.setup
|
| While trying to create a maintentance plan with log
| shipping I get the following error: Error 208: "Invalid
| object name 'msdb.dbo.log_shipping_monitor'." After I set
| the log shipping threshholds and click next. This server
| was recently restored from a backup tape and SQL server
| reinstalled. Any ideas what causes this error?
|

alex

hi

is Log Shipping only possible with 2K Enterprise Edition or also in Standard
Edition?


Alex

petery

Hello Alex,

Thank you for your posting. As per your question, Log shipping is only
available in Enterprise Edition. You can refer to the following article for
more related information:

323135.KB.EN-US INF: Microsoft SQL Server 2000 - How to Set Up Log Shipping
(White Paper)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;323135

Thanks & Regards,

Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support

Get Secure! - http://www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
| From: "alex" <ntnewsNO@SPAM.hrz3.hrz.tu-darmstadt.de>
| References: <003f01c351ef$b72a6b70$a101280a@phx.gbl>
<$Uz2DWnUDHA.1564@cpmsftngxa06.phx.gbl>
| Subject: Re: Log Shipping
| Date: Fri, 25 Jul 2003 10:14:18 +0200
| Lines: 9
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
| Message-ID: <e6idAToUDHA.1812@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.setup
| NNTP-Posting-Host: pd95220fe.dip.t-dialin.net 217.82.32.254
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP11.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.setup:55845
| X-Tomcat-NG: microsoft.public.sqlserver.setup
|
| hi
|
| is Log Shipping only possible with 2K Enterprise Edition or also in
Standard
| Edition?
|
|
| Alex
|
|
|

alex

from memory someone told me this is possible with Standard and a SQL
Resource Kit Tool... is this possible?


Alex

petery

Hello Alex,

Thank you for your reply. As per your question, Standard Edition of SQL
2000 does not implement Log Shipping, only Developer Edition or Enterprise
Edition do.

Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_ts_8d
bn.asp

SQL Mag January 2002 says that we provide an unsupported simple log
shipping tool with our Microsoft SQL 2000 Resource Kit

Simple Log Shipping in SQL Server 2000 Standard Edition
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=23231

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/
html/sql
01f1.asp
Simple Log Shipper
"One of the main features of the previous Resource Kit was LogShipping.
This is now a standard feature in SQL Server 2000, but in some scenarios,
this tool can be a bit too complex to use. The Simple Log Shipper tool is a
very simple solution, implemented entirely in T-SQL, and is suitable for
systems that require fault tolerance without very much administration
overhead."

If you have further questions on the issue, please feel free to post back.

Thanks & Regards,

Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support

Get Secure! - http://www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
| From: "alex" <ntnewsNO@SPAM.hrz3.hrz.tu-darmstadt.de>
| References: <003f01c351ef$b72a6b70$a101280a@phx.gbl>
<$Uz2DWnUDHA.1564@cpmsftngxa06.phx.gbl>
<e6idAToUDHA.1812@TK2MSFTNGP11.phx.gbl>
<3tyiydpUDHA.1760@cpmsftngxa06.phx.gbl>
| Subject: Re: Log Shipping
| Date: Fri, 25 Jul 2003 16:40:45 +0200
| Lines: 7
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
| Message-ID: <#AIO9qrUDHA.2568@tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.setup
| NNTP-Posting-Host: pd95220fe.dip.t-dialin.net 217.82.32.254
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.setup:55860
| X-Tomcat-NG: microsoft.public.sqlserver.setup
|
| from memory someone told me this is possible with Standard and a SQL
| Resource Kit Tool... is this possible?
|
|
| Alex
|
|
|

alex

hi

hm - sounds like a freaky admin game - geting this running and maybe i will
be the first - who will try this *g*. Are there any differences between this
Resource Kit "Simple Log Shipping" Tool and the Log Shipping in Enterprise
Version? I don't know on what this EE Version is based... it's nice to read
about this Simple Log Shipping is based on T-SQL... but this will not help
me anything :-).


Alex

petery

Hello Alex,

Thanks for your reply.

As per your question, Simple Log Shipper uses a linked-server relationship
between the primary server and the secondary server. The log shipping
activity is controlled from a stored procedure called sp_ShipLog, which you
run in a SQL Server Agent job on the primary server. This stored procedure
backs up the primary server database's transaction log to a Universal
Naming Convention (UNC) file location and makes a remote procedure call
(RPC) to sp_ApplyStandbyLog on the secondary server to restore the log file
to the secondary database. These stored procedures typically are located in
each server's master database, but that location (which the Simple Log
Shipper do***entation recommends) isn't a requirement. Simple Log Shipper
doesn't provide cleanup for transaction-log backup files, so you have to
archive them and delete the old ones manually.

Log shippting in Enterprise Edition automates the synchronization process
by using SQL server Agent jobs. The sequence of events includes backing up
transaction logs for the primary database, copying them to a secondary
location, and then restoring them to a secondary database. In details:

1. SQL server Agent backs up the transcation log on the primary server by
using a file name derived from the currnet date and time.

2. SQL server Agent on the standby server executes a copy job to copy the
primary transaction log backup file to a filder on the standby server.

3. SQL Server Agent on the standby server executes a load job to restore
the transaction log to the database on the standby server.

You can rerfer to Books online for more details about this log shipping and
its configuration.

If you have furhter questions on the issue, please feel free to post back.

Thanks & Regards,

Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support

Get Secure! - http://www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
| From: "alex" <ntnewsNO@SPAM.hrz3.hrz.tu-darmstadt.de>
| References: <003f01c351ef$b72a6b70$a101280a@phx.gbl>
<$Uz2DWnUDHA.1564@cpmsftngxa06.phx.gbl>
<e6idAToUDHA.1812@TK2MSFTNGP11.phx.gbl>
<3tyiydpUDHA.1760@cpmsftngxa06.phx.gbl>
<#AIO9qrUDHA.2568@tk2msftngp13.phx.gbl>
<WVYwy2NVDHA.592@cpmsftngxa06.phx.gbl>
| Subject: Re: Log Shipping
| Date: Mon, 28 Jul 2003 21:21:56 +0200
| Lines: 13
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
| Message-ID: <#XMBE2TVDHA.2316@TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.setup
| NNTP-Posting-Host: pd9522601.dip.t-dialin.net 217.82.38.1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.setup:55918
| X-Tomcat-NG: microsoft.public.sqlserver.setup
|
| hi
|
| hm - sounds like a freaky admin game - geting this running and maybe i
will
| be the first - who will try this *g*. Are there any differences between
this
| Resource Kit "Simple Log Shipping" Tool and the Log Shipping in Enterprise
| Version? I don't know on what this EE Version is based... it's nice to
read
| about this Simple Log Shipping is based on T-SQL... but this will not help
| me anything :-).
|
|
| Alex
|
|
|

alex

THX! :-)


Alex

michael.varriale

Hi Alex, I just set up SLS and it seems to work like a charm.
Wasn't to difficult. Let me knoe if I can help