CRON JOB investigations w/c 16/12/13

Hi Stevie

Please find attached document that Greg and Paul prepared wrt the cron jobs.  You will see that there is only one of them that we think could be transferred without any code changes - however that one is ADMISMI. It would still need tested and from memory I think that can be problematic as this particular thing is prone to errors that would be nothing to do with the changes we had made. It fails due to data errors etc. So still not that simple and I would shy away from that one.

Most of them do involve file copies so we are recommending leaving those.

There are a couple that write files - these could be changed to write using utl_file instead - we have estimated 2 days to change the code in those and set up utl_file directories. Again, would need full testing though and that is not in the 2 days estimate.

There are a couple that would have been ok but for error handling. The sql script calls a procedure but the procedure has no error handling. That is dealt with by the shell script. Therefore would have to amend the code in the procedure to handle errors and issue emails. We have estimated a day each to do that (plus testing).

So in summary, we don't think there are any on the list that could be changed to scheduled db job without any effort.   We have noted about 7 days build I think for the ones we thought were do-able plus testing, for which you could add on another 2 or 3 days. Question is whether your project has those days.

We were certainly of the opinion that there was scope for a lot of tidying up for some of these and it might be worth trying to get a project together at some stage to look at this.  There were also a couple of the shell scripts that are not running as '/' user and have user and hard coded pwd in there......

Alyson

Attachment	Size
cron_migration.docx	34.7 KB