Application Server Jobs or Database Jobs?

Question

In my java-based application, I need a job to read data from a set of tables and insert them into another table. In my first design, I created a oracle job and scheduled it to do the process frequently. Unfortunately, when the job fails, there is not enough info available about the root causes of the failure. In addition. deploying the system for many system instances has made the work harder. As an alternative work, I am trying to move the job into my application server, as a Weblogic job. Is this a good design or not?

Answer 1

Having moved my jobs into application server, I have faced the following advantages:

1. Tracking the job failure is easier.
2. Non-DBA users can easily read the application Server logs and fix the issues. (Many users do not have access to DB in production line. )
3. The logic of the job has been moved from my data access layer into my business logic layer and it is more acceptable due to design patterns.