Hi all, fairly new to FME and can't find much about this topic. I am using an FME workbench to move over a lot of data from an oracle database to a Microsoft SQL server. This is done by using a lot of SQL creators. It has been working fine but I think I have reached the limit of the Oracle I am using. My error is "did not succeed; error was `ORA-01000: maximum open cursors exceeded". I was trying to keep this all in one workbook - but I am not sure how with this error? I tried creating a separate database instance but that didn't work.
Question
Cursor error when mass reading from an Oracle database
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+26- Contributor
In the settings for the Oracle database a setting exists to define the number of open cursors (queries that the database can perform at a certain time).
This is by default 150.
The solution is to set this setting to a higher number (e.g. 250) and restart the database.
This is usually a task for a DBA.
Hi,
maybe you should try to reduce the SQL creators in some way, maybe you can perform a query that is more general an do filtering with FME transformers.
Or you can toggle off the option for permanent Connection. That can be found in the parameters of the Oracle Connection and should close the connection when querying finished.
In the settings for the Oracle database a setting exists to define the number of open cursors (queries that the database can perform at a certain time).
This is by default 150.
The solution is to set this setting to a higher number (e.g. 250) and restart the database.
This is usually a task for a DBA.
Hi,
maybe you should try to reduce the SQL creators in some way, maybe you can perform a query that is more general an do filtering with FME transformers.
Or you can toggle off the option for permanent Connection. That can be found in the parameters of the Oracle Connection and should close the connection when querying finished.
+26- Contributor
Thanks, I figured that was the case. Was hoping to find a way to somehow close these when done or wait until they are available. Working on a second workbench has fixed this for now but not my ideal soloution. Thanks for the reply.