| Silly thing came unlinked. and forgot to tell me. we were puzzled as to why the job wasn't running when everything indicated that it *Should* be running. (All predecessors had completed) All the job was suppose to do was detect that the Db was up. A manual check showed it was up, but the job wouldn't start. Even a manual `force' failed to get it to work.
Again I state It's your fault. Ended up killing the job, and faking a `success flag' on the schedule level. *sigh* we're still going to blame you Merlin, but but someone will have to see what you did in the morning. :-)
Enjoy your sleep before we come and get you. |
