Oracle process continue even after the jobs are stopped

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
vintipa
Participant
Posts: 136
Joined: Wed May 07, 2008 11:26 am
Location: Sydney, Australia
Contact:

Oracle process continue even after the jobs are stopped

Post by vintipa »

hi friends,

Even after the jobs are stopped the query executed by the jobs
carry on and utilize CPU resources. Any option in Datastge to ensure all the processes end when jobs are stopped?
Vinay
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

If by "stopped" you mean using the Stop button while the job is running, yes - that can happen. I only do that when the sql is actively delivering rows, if it is still "building the cursor" then you'll have issues, best to have a DBA kill the Oracle SID in that case.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Sathishkumarins
Premium Member
Premium Member
Posts: 41
Joined: Tue Jul 08, 2008 5:45 am
Location: Columbus

Post by Sathishkumarins »

If you are running a job with high volume of data and when you stop the job may be the oracle might try to commit those rows. So the query might still run. In that case you can't avoid that.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

... short of killing the Oracle session.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Yup. While Oracle may not notice you stopping the job, DataStage will notice you killing the Oracle session. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply