November 30, 2007 at 11:41 am
We have a SQL agent job which basically calls a maintenanceplan. the maintenanceplan does a full back up of a database.
The strange thing is-
the job runs and succeeds everyday.
but when you check the maintenanceplan history, it is never executed. therefore i can nerver see the .bak file
I don't see any unusual configuration. it says when job succeed quit the job and report success, when it fails quit job and report failure.
If the maintenanceplan failed then at least when view history it should some error msg.
this maintenance plan was created by a dba who left company and the job owner is him too. but the job runs as SQL server Agent account. could it be related to loging/security issues? but even so if there is any problem the job should not report success. this is strange, does someone got some clue?
Thanks,
'Bug'
November 30, 2007 at 11:55 am
Was the job created by the maintenance plan and have you checked what the plan is doing in each step (I sometimes run it and watch in profiler)? But in any case you might first try deleting the plan and recreating to see if that cares for the problem if does simple quick and done, if not then you have a problem.
November 30, 2007 at 12:04 pm
Thanks, I'm going to run profiler. by the way, what event in profiler I should choose to monitor this?
November 30, 2007 at 12:16 pm
I would look at batch and statment for transaction, all you are looking for is the backup stuff being executed. Also, looks for errors.
November 30, 2007 at 1:40 pm
In Backup Database Task, there is option for connection- local server connection and target server connection
I find that the problem plan was using target server connction that's not even kick off when you hit execute
when I change to local server connection, it runs fine now. so what is the difference using target or local? since the we didn;t define this, it's provided automatically. and when you check connection, you see they are configured exactly same. Now I know the problem comes from using target but I don't know why?
December 1, 2007 at 11:36 am
Target servers are typically remote servers sharing the plan, not the local server. The server you are connected to is the local server.
December 6, 2007 at 10:32 am
Have you tried looking through the job history of the job that runs the maintenance plan? Do any of your steps continue on error?
You should be able to look through the history of the job and determine if a particular step failed. You should be able to isolate when the maintenance plan is called and if an error occured.
December 7, 2007 at 7:42 am
Thanks for help. I even ran the maintenance plan itself and it ran and finish within 2 second and did nothing.
but it report success. I checked all steps inside the plan(actually it is a full back up of mutiple databases, which should normally take about 10 minutes to finish.) this is so strange and I couldn't figure out why. the only thing
I can imagine is that the people who created this plan has left the company maybe the access problems? but it did run and report no failure! I made a duplicate plan exactly same as this one simply the owner is myself, everything works fine. so finally I gave up diagnose the problem with the old one and just went ahead to create my own.
Thanks for all the posts trying to help!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply