Running asynchronous processes in Oracle

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • skaushik
    New Member
    • Feb 2008
    • 6

    Running asynchronous processes in Oracle

    Hi all,

    I am using Oracle 9.2 version and I had to run a stored procedure asynchronously. I was researching a little bit on this and found that Oracle jobs was a way to do it. Is this the only way or is there a way to run a stored procedure asynchronously?

    Also, I had a question in using DBMS_JOBS package. Currently, if I decide to use jobs, I need to log new jobs every 6 minutes and the original transaction which logged the jobs has to continue without waiting for the jobs to finish. The problem with this is that the job queue can become very long after sometime. Is there a way to automatically remove the jobs from the job queue once it is finished?

    Any pointers to this would be greatly helpful.

    Thanks.
  • amitpatel66
    Recognized Expert Top Contributor
    • Mar 2007
    • 2358

    #2
    Originally posted by skaushik
    Hi all,

    I am using Oracle 9.2 version and I had to run a stored procedure asynchronously. I was researching a little bit on this and found that Oracle jobs was a way to do it. Is this the only way or is there a way to run a stored procedure asynchronously?

    Also, I had a question in using DBMS_JOBS package. Currently, if I decide to use jobs, I need to log new jobs every 6 minutes and the original transaction which logged the jobs has to continue without waiting for the jobs to finish. The problem with this is that the job queue can become very long after sometime. Is there a way to automatically remove the jobs from the job queue once it is finished?

    Any pointers to this would be greatly helpful.

    Thanks.
    Could you please clarify the following:

    1. Totally how many different jobs you have to execute?
    2. Are the jobs scheduled and are one time run or repeating?
    3. Do you want the jobs to be interdependent? (In the sense, if first completes Normal then start second else start third?)


    When the job completes its execution, you have something called auto_drop that will remove the job automatically once it completes and update the status in JOBS table to either next time when it has to run or just complete if it is one time run.

    Comment

    Working...