Clean Oracle scheduled jobs

[dan-nawrocki]

I'm using flyway on a very large Oracle schema. One of the issues I found was that a clean didn't remove existing scheduled jobs; this pull request fixes it. Let me know if there's anything you'd like me to add in order to get this in to 3.1.

[lukaseder]

I've recently been doing some work for a client who is using jobs. I think that if you want to go this way, you really have to clean up and correctly handle all sorts of job-related artefacts. In other words, all artefacts that can be created with the DBMS_SCHEDULER package should be dropped:

• chains (with chain rules, chain steps)
• credentials
• database destinations
• file watchers
• groups
• jobs
• job classes
• programs (with arguments)
• schedules
• windows

I wonder, though, if there's a one-size-fits-all solution here. If you're using jobs with queues, maybe you'd also want Oracle AQ / Streams packages to be managed by this Flyway clean function?

[axelfontaine]

Hi Dan,

thanks for submitting the pull request. Could you add a test case for this as well?

Cheers
Axel

[dan-nawrocki]

Test case added.

@lukaseder I couldn't find anything simple to clean up everything related to the dbms_scheduler -- it looks like everything in that package would require a different DROP statement (dbms_scheduler.drop_job vs dbms_scheduler.drop_chain vs etc). We'd probably need separate code blocks to dynamically create all those DROPs individually.

AQ streams do appear to be cleaned by 3.1 out of the box. This was one of the selling points I used to push for adoption of flyway over the incomplete homegrown clean/migrate solution at my company.

Thanks!

[axelfontaine]

Thank you very much Dan! Merged. Should be part of 3.1 due out before the end of the month.

Cheers
Axel

[axelfontaine]

@dan-nawrocki Could you please get in touch with me via email? (axel at boxfuse.com) Thanks!