September 21, 2009 at 9:36 am
I haver a maintenance plan that also has a step to take the full backup of a database whiich seems to be failing and I never being notifiied about the failure even though I have Notify operator task.
The job ends as success even thouugh one of the steps failed in the maintenance plan. The notify operator task works fine . I have tested it and seems to be able to send a test mail but not in this case.
Here is the maintenance plan.
September 21, 2009 at 9:46 am
Maybe this is not the answer that you are looking for, but I from my experience, if I have a maintenance job that fails each time that it runs, it is much easier to create a new maintenance job, then trying to find out what went wrong suddenly with the original plan.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
September 21, 2009 at 9:50 am
Earlier we had a maintennace plan that we had some issues with ...so I created this new maintenance plan with a step to execute a SQL serer job and then perform the full backup of the db. Look like the step to execute the SQL serve job goes through pretty well but if doesnt execute the next step to take the backup of the db and still reports a success. This is a index rebuild job and is is very important for me to figure it how I can take a full backup after I am finished execute the SQl server job.
September 21, 2009 at 1:50 pm
Looking at the picture, it is actually very easy to figure out why this happens. Your dependencies are not correct:
What you have set up is your Execute SQL Server Agent Task job must complete successfully for the next task, AND the Notify Operator task must complete successfully. That situation will never occur because the Notify Operator task will only run when the first task fails.
Based upon those dependencies - there is no way any other tasks can be completed successfully.
So, how do you fix this? Easy, remove one of the Notify Operator tasks - hook up each task to the Notify Operators task on failure, then edit the properties of one of the contraints and change from AND to OR (at the bottom). This will change the precedence contraints to dashed lines - which is showing that if any of the tasks connected fail - the notify operator task will run.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
September 21, 2009 at 3:01 pm
Thanks for your suggestion , I will try that out.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply