About Ora-01000:maximum open cursors exceeded in WebSphere

There are a lot of online, forget about this.

ORA-01000 This parameter determines the number of maximum open cursor for a session.
It may be an abnormal interrupt without close, or there is a problem with the program writing, or there are so many cusor to apply at the same time.
First check the DB parameter, select value
From V$parameter
The WHERE name = ' Open_cursors ' recommends a large application of at least 1000. Then, check the Select O.sid, Osuser, Machine, COUNT (*) num_curs
From V$open_cursor O, v$session s
where user_name = ' username ' and o.sid=s.sid
Group by O.sid, Osuser, machine
ORDER BY num_curs Desc; There must be a session near ' open_cursors ' to get SID.            Finally, see what SQL these ' open_cursors ' are. Select Q.sql_text
From V$open_cursor o, V$sql q
where q.hash_value=o.hash_value and o.sid = XXXXX; It should now be possible to navigate to that page or module causing the problem.

In WebSphere, there is a parameter statement cache size, which is also used for caching.
See if the setting is large with Oracle.
In WebSphere application Server V5, navigate to the "the" data source in the Admin Console. The Statement Cache SizeAppears on the main data source configuration panel. In WebSphere application Server V6, navigate to the "the" data source in the Admin Console. Under Additional Properties, select WebSphere application Server data source properties. The the "listed on" the resulting screen is the Statement Cache Size. Another can also set the cursor_sharing = Force, but it depends on the circumstances.

Procedural questions, such as:
Java code in the execution of Conn.createstatement () and conn.preparestatement () is actually quite the same as opening a cursor in the database. In particular, if your createstatement and preparestatement are in a loop, this problem will be very easy to come by. Because the cursor is constantly open and not closed.
Also see the itpub on a case is a storage space problem, the key is to find which SQL OPEN cursor, and then the right remedy.