# Oracle Stored Procs & Named Queries **URL:** \ **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:** 1\ **Showing post:** 2
**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")
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… --- _[View the full topic](https://forum.inductiveautomation.com/t/oracle-stored-procs-named-queries/72675)._