# Oracle Stored Procs & Named Queries

**URL:** <https://forum.inductiveautomation.com/t/oracle-stored-procs-named-queries/72675>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [April 19, 2023, 10:08pm UTC](https://forum.inductiveautomation.com/t/oracle-stored-procs-named-queries/72675 "2023-04-19T22:08:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [April 19, 2023, 10:08pm UTC](https://forum.inductiveautomation.com/t/oracle-stored-procs-named-queries/72675/1 "2023-04-19T22:08:13Z")

</div>

Hey folks,

I realize that this is not an Oracle support forum, but I am hoping someone has advice on how to do this...

We're migrating a series of stored procedures from MSSQL to Oracle per customer request. I've run into issues with the SELECT procs; specifically Ignition's DB engine doesn't seem to support the oracle cursor type, nor receiving a series of out params. Oracle doesn't appear to offer a standard dataset return

I have been able to execute stored procedures via scripting by defining OUT parameters.

I can run the contents of any stored procedure directly from Ignition's DB browser or a named query.

My ask: Is there any way to return an Ignition query-friendly dataset from an Oracle Stored Procedure? Or are they incompatible (as they appear thus far)?

Any assistance would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![Austin\_Dollar](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/austin_dollar/32/37052_2.png) [@Austin\_Dollar](https://forum.inductiveautomation.com/u/Austin_Dollar)\
**Post date:** [May 3, 2023, 9:50pm UTC](https://forum.inductiveautomation.com/t/oracle-stored-procs-named-queries/72675/2 "2023-05-03T21:50:46Z")

</div>

Hi @AIO,

This topic was actually fairly recently discussed on a previous thread here, and has some potential workarounds discussed:

> [@Getting result from Oracle stored proc into dataset](https://forum.inductiveautomation.com/t/getting-result-from-oracle-stored-proc-into-dataset/68743/2):
>
> Pretty sure you won't be able to do that. The Oracle JDBC examples require you to register the parameter as oracle.jdbc.OracleTypes.CURSOR, which is not available in Ignition. (Only generic JDBC types are supported in Ignition--the actual drivers are in isolated classloaders in order to make connection pooling transparent.) You'll probably have to wrap that procedure with another that explicitly SELECTs from that cursor. (Looks complicated--wrapping in a TABLE() function somehow. I've not u…

---

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [May 3, 2023, 11:30pm UTC](https://forum.inductiveautomation.com/t/oracle-stored-procs-named-queries/72675/3 "2023-05-03T23:30:36Z")

</div>

Thanks, Austin - I appreciate the reply.

I found that same post. From my experience, Oracle's method for stored procedures does not integrate well with Ignition unless you intend to script every stored procedure call.

Our solution was to put INSERT / UPDATE procs into scripts and pull heavy SELECT procs out of stored procedures and move them into named queries in Ignition.

It's been a pretty excellent headache in that regard. 😅

TL:DR - Would not recommend Oracle for integration with Ignition.