Page 1 of 1
Does ODBC query gets killed, when your reset a Job
Posted: Sun May 22, 2005 10:02 pm
by talk2shaanc
If a huge SQL query is submitted in the ODBC stage and the job is reset/stopped, is the query killed or does it keep running on the DB. If yes, what is the solution? Recompile the job?
Re: Does ODBC query gets killed, when your reset a Job
Posted: Sun May 22, 2005 11:36 pm
by tcj
talk2shaanc wrote:If a huge SQL query is submitted in the ODBC stage and the job is reset/stopped, is the query killed or does it keep running on the DB. If yes, what is the solution? Recompile the job?
I have found that most of the time on an oracle server that yes the query is still running. Contact your DBA to kill the query if it is still running unless you have access to do it yourself.
Posted: Mon May 23, 2005 12:09 am
by Prashantoncyber
Is there any way that we can find it out wether querry is running or not either thro' DS or Orcle DB?
Posted: Mon May 23, 2005 12:15 am
by talk2shaanc
Through Oracle front-end Tool(Quest Central or Toad) you can trace session and see which user ? , what query is running ? and how many resources are consumed for running a query?. Well I had tested it in my case it was killed. But wanted to know from people out here on forum, if they came across such instances where it was not killed and what steps they took thereafter.
Posted: Mon May 23, 2005 12:58 am
by tcj
talk2shaanc wrote:Through Oracle front-end Tool(Quest Central or Toad) you can trace session and see which user ? , what query is running ? and how many resources are consumed for running a query?. Well I had tested it in my case it was killed. But wanted to know from people out here on forum, if they came across such instances where it was not killed and what steps they took thereafter.
Yes there will be instances where it was not killed. I have had weird things happen with datastage jobs in that queries have returned data back to the datastage designer after it has stopped or aborted. Or people that have stopped and started their job a couple of times and there has been multiple threads left on the DB.
Posted: Mon May 23, 2005 1:03 am
by talk2shaanc
Sorry for not submitting my last thread in proper format.
Below potion was answer to "Prashantoncyber " question
"Through Oracle front-end Tool(Quest Central or Toad) you can trace session and see which user ? , what query is running ? and how many resources are consumed for running a query?."
and
"Well I had tested it in my case it was killed. But wanted to know from people out here on forum, if they came across such instances where it was not killed and what steps they took thereafter."
was reason for posting this thread.[/list]
Posted: Mon May 23, 2005 5:51 am
by ray.wurlod
Usually have the DBA kill the session. No-one else has the privileges necessary.