JCAPS 5.1.2 issue with 5.1.2 Oracle eWay.
I have a JCD that executes stored procedures against an Oracle database. At some point in time, the open cursors in the database can go as high as 200.
Does anybody know why are these cursors being left open in the Oracle box? and how to go about fixing it?
Yup, explicit commit inside the JCD is the way to deal with this. i've encountered the same with DB2 and it's related to the underlying DataDirect drivers and the allocated space in the "Dynamic SQL Segment" where prepares statements are being handled.
For some reasons it didn't all work right with DB2 (as it was a pretty old version) and after increasing the number from 200 to 2000 but still hitting this limit, we switched to the DB2Connect eWay, using JDBC Type 4. That worked marvelous.
Good luck
Paul
A select with a ? in it ?
That's recognized by the database as dynamical SQL and will be treated in a different memory space. The problem i had was due to the DataDirect drivers for DB2, but at the time i found the same for DataDirect for Oracle.
http://knowledgebase.datadirect.com/KBase.nsf/SupportLink+Online/2552436PG?Open Document
Can you set the eWay to non-transactional in the Environment settings and the Connectivity Map ?
If that doesn't work i'm not seeing any simple way to allow you to use the Type4 JDBC features, aside from using the JDBC eWay with the Oracle Drivers, but you can CAPS-Support and they should be able to provide you pretty quickly with a re-issue of the DataDirect drivers.
Good luck
Paul