I am getting log shipping errors referring to a database that has been deleted

dcadler
dcadler used Ask the Experts™
on
I have been given an existing MS SQL 2008 R2 database to oversee. IN the event log, I keep getting this error.

The log shipping primary database ACI-SQL1.ACI_Test has backup threshold of 60 minutes and has not performed a backup log operation for 221465 minutes. Check agent log and logshipping monitor information.
Error: 14420, Severity: 16, State: 1.

I was told that the ACI_Text database was deleted. How do I stop the server from trying to do log shipping on a non-existing database?

Thanks,

Dave
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
Zberteoc - The database, ACI_Test, had been deleted by the admin before me. So, I can't right-click on it and select properties, as the Technet article suggests. That is the reason I am seeking help on this forum. I do not know why I am getting the error message when the database is not in the list of databases. I assume that there is a reference in a system database I need to manually remove.

Any other ideas?

Thanks,

Dave
Read to the bottom the "Using Transact-SQL" section. There are other links there.

Author

Commented:
Zberteoc - Using the T-SQL commands did not fix the issue.

I think that there is an entry in a system table for log shipping on the database that has been deleted. The database doesn't exist, but the Log Shipping Alert job, which has the step;

exec sys.sp_check_log_shipping_monitor_alert

against the master database, is generating the error.

So, is there a way to manually remove the record from the master database so that the alert does not get tripped? If so, which table(s) do I need to look at.

Or is there some kind of orphaned database cleanup utility that will remove the orphaned records in the master table when a user database is not properly deleted?

Thanks,

Dave
Exactly that was supposed to do the stored procedures in the link. Similar situations happens with replication but when you execute remove replication db every trace is removed.

Did you run the queries on both sides?

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial