| Author |
Topic  |
|
|
ddamico
Yak Posting Veteran
75 Posts |
Posted - 11/05/2008 : 15:27:33
|
Good afternoon
This should be under SQL SERVER 2000 Forum... My Bad
I have an error showing up in my maintenance plan logs. It appears that the job is completing successfully and transaction logs are generated but I receive the following
[Microsoft SQL-DMO (ODBC SQLState: 42S02)] Error 208: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'msdb.dbo.log_shipping_databases'. [9] Database <dbname>: Transaction Log Backup... Destination: [E:\Microsoft SQL Server\MSSQL\BACKUP\Transaction Log\<dbname>.TRN]
Has anyone seen this and know what is up. These errors just started cropping up about 1 week ago and hte maintenance plan has been in use for the last 3 years without any error like this. |
Edited by - tkizer on 11/07/2008 13:47:19
|
|
|
RickD
Slow But Sure Yak Herding Master
United Kingdom
3560 Posts |
|
|
ddamico
Yak Posting Veteran
75 Posts |
Posted - 11/05/2008 : 15:48:08
|
RickD
I did find that. Now I am wondering what happened to those objects if I was never receiving these errors before last week. I thought maybe there was more to this than the fact that these were missing.
|
 |
|
|
saurabhsrivastava
Posting Yak Master
USA
216 Posts |
Posted - 11/05/2008 : 15:52:18
|
1)Have you upgraded the service pack recently?
2)Run DBCC Checkdb against msdb
Thanks Tara for pointing it out. My bad. I had something else running in my mind and I didn't realize that. |
Edited by - saurabhsrivastava on 11/05/2008 17:01:20 |
 |
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
|
|
ddamico
Yak Posting Veteran
75 Posts |
Posted - 11/06/2008 : 08:36:06
|
We have been at SP4 for over since the inception of this instance of SQL back in March of 2006.
Storage is all local disk and I don't notice any comments about external RAID in the replies. |
 |
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
|
|
RickD
Slow But Sure Yak Herding Master
United Kingdom
3560 Posts |
Posted - 11/07/2008 : 07:57:54
|
ddamico - Not sure, but something must have changed to cause this to happen, please check ALL of your updates, including Windows updates. If nothing obvious, open a call with Microsoft.
Tara - The OP does say in the first post that this shouls have been posted in the SQL 2000 forum. |
 |
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
|
| |
Topic  |
|