[
https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442181#comment-16442181
]
Saravanan Subiramaniam commented on GROOVY-8397:
------------------------------------------------
Hi,
I also ran into this issue after upgrading to 2.4.13 (and using 12.1.0.2
jdbc driver). It seems that the issue is in JDBC driver. For example, see:
[https://confluence.atlassian.com/confkb/upgrade-to-version-6-1-x-failed-with-error-ora-01000-maximum-open-cursors-exceeded-922914154.html.|https://confluence.atlassian.com/confkb/upgrade-to-version-6-1-x-failed-with-error-ora-01000-maximum-open-cursors-exceeded-922914154.html]
I'm no longer seeing this issue after upgrading jdbc driver to 12.2.0.1.
> ORA-01000: maximum open cursors exceeded
> ----------------------------------------
>
> Key: GROOVY-8397
> URL: https://issues.apache.org/jira/browse/GROOVY-8397
> Project: Groovy
> Issue Type: Bug
> Components: SQL processing
> Affects Versions: 2.4.9, 2.4.10, 2.4.11, 2.4.12, 2.4.13
> Environment: Oracle 12.1.0.2.0
> Java 8 64bit
> Reporter: mgroovy
> Priority: Major
> Labels: cursor, oracle, sql
>
> * Evolving Oracle 12.1.0.2.0 DB schema with many objects from Groovy code
> based on Groovy Sql class worked up to groovy-2.4.7
> * From 2.4.9 up to 2.4.13 after some time during table creation/update schema
> evolver throws
> {code}
> java.sql.SQLException: ORA-01000: Maximale Anzahl offener Cursor überschritten
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
