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.
Author |
Topic |
ddamico
Yak Posting Veteran
76 Posts |
Posted - 2008-11-05 : 15:27:33
|
Good afternoonThis should be under SQL SERVER 2000 Forum... My BadI 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. |
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
|
ddamico
Yak Posting Veteran
76 Posts |
Posted - 2008-11-05 : 15:48:08
|
RickDI 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
216 Posts |
Posted - 2008-11-05 : 15:52:18
|
1)Have you upgraded the service pack recently?2)Run DBCC Checkdb against msdbThanks Tara for pointing it out. My bad. I had something else running in my mind and I didn't realize that. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
ddamico
Yak Posting Veteran
76 Posts |
Posted - 2008-11-06 : 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
38200 Posts |
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2008-11-07 : 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
38200 Posts |
|
|
|
|