ava.sql.SQLFeatureNotSupportedException: DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream

http://www-01.ibm.com/support/docview.wss?uid=swg21590188

 

Caused by: java.sql.SQLFeatureNotSupportedException: DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream
at com.ibm.ws.rsadapter.AdapterUtil.notSupportedX(AdapterUtil.java:1466)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.setBinaryStream(WSJdbcPreparedStatement.java:1424)
at com.ibm.icm.da.portable.common.sql.PPreparedStatement.setBinaryStream(PPreparedStatement.java:423)
at com.ibm.icm.da.portable.data.WideTableData.bindValue(WideTableData.java:1582)
at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:596)
at com.ibm.icm.da.portable.data.WideTableData.bindValue(WideTableData.java:1582)
at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:596)
… 63 more
Caused by: java.lang.AbstractMethodError: java/sql/PreparedStatement.setBinaryStream(ILjava/io/InputStream;)V
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.setBinaryStream(WSJdbcPreparedStatement.java:1408)
… 66 more

Cause

The Resource Manager of the WebSphere Application Server configures the classpath of an enterprise application to provide access to datasource/JDBC provider classes referenced by the application. It does so by placing the associated jar files configured in the resource provider on the classpath. Because the names of JDBC 3.0 and JDBC 4.0 implementation classes are the same, the application classloader will load the classes from whichever JDBC provider jar file is placed on the classpath first. The order of the JDBC provider jars on the classpath is non-deterministic and as a result the application may load the JDBC 3.0 version of the class first, causing later attempts by the application code to call class methods specific to the JDBC 4.0 API to fail with an exception. Alternatively, but typically less problematic because of backward compatibility between the JDBC specification levels, the application may load a JDBC 4.0 version of a driver class instead of the expected JDBC 3.0 version.

 

Resolve:

Update your oracle jdbc driver with latest driver match with your Oracle DB version.

i.e For Oracle 12 you need ojdbc7.jar and xdb6.jar

  •  
  •  
  •  
  •  

Viet Luu has written 210 articles

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

Buy Me A Coffee

We are thankful for your never ending support.

Leave a Reply