IBM MDM v11-- MDMSE : ORA-01000: maximum open cursors exceeded in SystemOut.log

Symptom

One scenario for this problem happening is loading data. While attempting to load data into engine, customer is experiencing problems with maximum open cursors on the database. This happens at random periods when loading data.

Cause

JDBC connection pool management issue in WAS

Diagnosing the problem

When checking in the database, the SQL with excessive open cursors is "select 1 from dual" statement, which is done by WAS to verify data source connections.

Resolving the problem

WAS has problem in JDBC connection pool management. As a workaround, in the data source definition page of WAS console, choose "WebSphere Application Server data source properties", and enable "Validate existing pooled connections", and select "Validation by JDBC driver", pick an appropriate timeout, then save.

For an Oracle datasource, Validation by JDBC Driver appears on the administrative console only after the validateNewConnectionTimeout property is added to the custom properties of the datasource. 

 Name: validateNewConnectionTimeout 

Value =0

Type: "java.lang.Integer"