# Active queries problem

**URL:** <https://forum.inductiveautomation.com/t/active-queries-problem/2408>\
**Category:** Ignition\
**Created:** [December 9, 2010, 7:59pm UTC](https://forum.inductiveautomation.com/t/active-queries-problem/2408 "2010-12-09T19:59:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![apimente](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/apimente/32/4030_2.png) [@apimente](https://forum.inductiveautomation.com/u/apimente)\
**Post date:** [December 9, 2010, 7:59pm UTC](https://forum.inductiveautomation.com/t/active-queries-problem/2408/1 "2010-12-09T19:59:24Z")

</div>

Hi,

I would like to know if someone know how to solve this problem. I’m using ORACLE and sometimes i have some stored procedures that stay frozen and they don’t die. So, if I call a new instance of the same procedure, This enter to the active queries tail.

To solve this problem I’d like to use some kind of timeout for the procedure. In rssql this characteristic is possible to configure.

I attach a screenshot showing the procedures that don’t run.

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/1X/ee3a5a47d46db304b819c210c3b32ba242e449d2.jpg)

---

<div class="post-metadata">

**Author:** ![Robert.McKenzie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert.mckenzie/32/4134_2.png) [@Robert.McKenzie](https://forum.inductiveautomation.com/u/Robert.McKenzie)\
**Post date:** [December 10, 2010, 5:05pm UTC](https://forum.inductiveautomation.com/t/active-queries-problem/2408/2 "2010-12-10T17:05:30Z")

</div>

There is no way to kill a query through Ignition, but you can do that through your database. A quick Google search yielded this info on doing it automatically.

[dbasupport.com/forums/archiv … 23463.html](http://www.dbasupport.com/forums/archive/index.php/t-23463.html)

---

<div class="post-metadata">

**Author:** ![apimente](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/apimente/32/4030_2.png) [@apimente](https://forum.inductiveautomation.com/u/apimente)\
**Post date:** [December 10, 2010, 6:53pm UTC](https://forum.inductiveautomation.com/t/active-queries-problem/2408/3 "2010-12-10T18:53:52Z")

</div>

Thank you very much,

I’ve been looking for something like that (set a timeout to my oracle SQL queries) unsuccessfully.

I’ll try to implement this and I tell you how it works.

---

<div class="post-metadata">

**Author:** ![apimente](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/apimente/32/4030_2.png) [@apimente](https://forum.inductiveautomation.com/u/apimente)\
**Post date:** [December 17, 2010, 12:28pm UTC](https://forum.inductiveautomation.com/t/active-queries-problem/2408/4 "2010-12-17T12:28:07Z")

</div>

Yesterday I noticed that when i have this problem always also I have the SQLDEVELOPER opened (the ORACLE DB tool provided by Oracle) and when I close it, the query finish its execution.

I don’t know if somebody else have seen this behavior.

---

<div class="post-metadata">

**Author:** ![Robert](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@Robert](https://forum.inductiveautomation.com/u/Robert)\
**Post date:** [December 17, 2010, 3:44pm UTC](https://forum.inductiveautomation.com/t/active-queries-problem/2408/5 "2010-12-17T15:44:47Z")

</div>

Sounds like a locking problem.

I would look at what tables/rows your stored procedure is changing and compare to rows/tables your looking at in SQLDEVELOPER.

My guess is something your doing in SQLDEVELOPER is locking a table(s) required by the stored procedure.