Results 1 to 3 of 3

Thread: Killing job

  1. #1
    Join Date
    Nov 2003
    Location
    India
    Posts
    114

    Unanswered: Killing job

    There is a unix batch job which further establishes connection with Oracle.
    There are times when I need to kill the job manually. In such cases should the sql session which job had established should be killed first or job can be killed directly.

    Is it safe to kill the job directly. What Happens to the SQL Session , does it gets killed as soon as job is killed.

  2. #2
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    You need to understand what the job is doing, but .... When you kill a job
    in the job queue, it will perform a rollback and then be removed from the
    session. If may appear as "killed", but still processing (performing it's rollback).

    HTH
    Gregg

  3. #3
    Join Date
    Nov 2004
    Location
    Temple University
    Posts
    36

    Cool License to Kill - RE: 007

    Varun;
    this is probably a matter of preference. Personally, I choose to kill the oracle session first, and then the job at the OS level. This way, I am sure that there are no ghost processes running at the oracle level. This may create a ZOMBIE process at the OS level, so you will need to check for them as well.

    I am sure there are a lot of people, that will tell you just the opposite, to Kill the OS job first. This is really application dependent, and you will need to see which works best for your application.

    HTH
    Peter

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •