Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-01000 maximum open cursors exceeded after migration to Oracle 12c

David TissenNov 17 2017 — edited Feb 5 2018

We are running in the ORA-01000 issue since we migrated from Oracle Databes 11.2.0.4 to 12.2.0.1.

Our Testenvironent: A set of Virtual Machines:

1. Our Software, Java 1.8, jbossw wildfly Applicationserver with the database connection using ojdbc8.jar as the driver, oracle Database 11.2.0.4

1. Our Software, Java 1.8, jbossw wildfly Applicationserver with the database connection using ojdbc8.jar as the driver, oracle Database 12.2.0.1 (just migrated the oracle Database)

I mad a snapshot from both environment to switch the setting.

From our side it is the same Software. The issue now is:

whenever Fulltext changes are made our software makes an update in Oracle - 1 Open Cursor stays opened.

Im Using this statement to determine current open sessions:

select a.value, s.username, s.sid, s.serial# from v$sesstat a, v$statname b, v$session s where a.statistic# = b.statistic#  and s.sid=a.sid and b.name = 'opened cursors current' and s.username is not null ORDER by a.value desc;

Any Update on the fulltext leaves one Cursor opened... I allready increased the max open cursor from 300 (which was fine with oracle 11.2.0.4) to 1000.. Does not matter. It takes only a few more updates on the fulltext.

Since our Software is completly unchanged for both test environments, this is a oracle bug?

How can i find out the SQL Statement which leaves a cursor opened?

This post has been answered by David Tissen on Jan 8 2018
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 5 2018
Added on Nov 17 2017
2 comments
2,723 views