You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "mgroovy (JIRA)" <ji...@apache.org> on 2017/12/01 01:24:00 UTC
[jira] [Commented] (GROOVY-8397) ORA-01000: maximum open cursors
exceeded
[ https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273788#comment-16273788 ]
mgroovy commented on GROOVY-8397:
---------------------------------
You mean if I can call Sql#setEnableMetaDataChecking(false) for every Sql instance I use ? I have wrapped Sql in my own SqlExecutor class a few years back, so (without being able to check this in detail until next Monday) I do not expect this to be a problem.
> 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
> 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
(v6.4.14#64029)