August 16, 2012 at 5:45 am
Hi, I am pretty new to sql and in my company I was asked to study and try to configure a "log shipping". So, I have understood the subject and I just set up my first log shipping in order to do some tests, using the gui of management studio. It runs correctly because secondary database are updated with new changes. However, I need to call this procedure on demand, so I created a custom jobs which has 3 steps: backup, copy and restore. I copied the code of these steps from the related log shipping jobs (created by sql) so I am sure that the code is correct. Then I disabled the "official" log shipping jobs and I manually started my custom job. This custom job performs correctly too, because secondary databases are updated with changes; however, the three steps ends with SUCCESS, but the exit code of the overall job is FAIL. The three steps are set up with "failure action" --> "Quit the job reporting failure" so I'm really sure that no error is raised because the task ends correctly and updates databases. I'm happy that my log shipping performs well, but I'm disappointed because it reports me always a fail and I can't know when it really fails! Can you help me?
August 16, 2012 at 6:57 am
What do the reporting options for success say, how are they set?
August 16, 2012 at 7:47 am
Thank you, I found the problem. It was set with "go to the next step". Probably it won't found any next step and raised a generic error.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply