?
Solved

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

Posted on 2014-02-25
5
Medium Priority
?
1,915 Views
Last Modified: 2014-03-29
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
0
Comment
Question by:dcadler
  • 3
  • 2
5 Comments
 
LVL 27

Accepted Solution

by:
Zberteoc earned 2000 total points
ID: 39886520
0
 

Author Comment

by:dcadler
ID: 39887598
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
0
 
LVL 27

Expert Comment

by:Zberteoc
ID: 39888448
Read to the bottom the "Using Transact-SQL" section. There are other links there.
0
 

Author Comment

by:dcadler
ID: 39899355
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
0
 
LVL 27

Expert Comment

by:Zberteoc
ID: 39900575
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?
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
One of the most important things in an application is the query performance. This article intends to give you good tips to improve the performance of your queries.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

616 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question