Problem with resultsets fields after migrate to JDBC6.5

, ,
1

Hi,
After we migrate our JDBC adapter from 6.0.3 to 6.5 , some operations based on StoredProcedureWithSignature template using Resultsets started to give the following error:

com.wm.app.b2b.server.ServiceException: [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service CST.Log.adapterOp:teste.
[ADA.1.316] Cannot execute the SQL statement “{?= call dbo.sp_eai_getAllLogs_HIST;1( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}”. "
(S1093/0) The column name t is not valid."
The column name t is not valid

This is due to the fact that resultset fields do not match with the name defined in the Stored Procedure.

In the previous version the resultset fields did not have to match with the field name defined in the SP so the impact can be enormous.

Is there any way to have the previous behavior ?

João Caseiro

2

I’m also noticing this as well for a result set that uses an oracle cursor. Not sure what all is affected at this point but if anyone can confirm the upgrade breaks this behavior, and if there’s any fix without changing all the services it would be appreciated.