Opencart query fails thru jdbc t4 with ids_unknown_reply_error exception

Bug #1386340 reported by Aruna Sadashiva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trafodion
Invalid
High
RuoYu Zuo

Bug Description

The opencart queries work ok from sqlci and jdbc t2 driver, but fails thru t4 with this error in ResultSet.close method:

SQL read from file is: SELECT tr2.tax_rate_id, tr2.name, tr2.rate, tr2."type", tr1.priority FROM oc_tax_rule tr1 LEFT JOIN oc_tax_rate tr2 ON (tr1.tax_rate_id = tr2.tax_rate_id) INNER JOIN oc_tax_rate_to_customer_group tr2cg ON (tr2.tax_rate_id = tr2cg.tax_rate_id) LEFT JOIN oc_zone_to_geo_zone z2gz ON (tr2.geo_zone_id = z2gz.geo_zone_id) LEFT JOIN oc_geo_zone gz ON (tr2.geo_zone_id = gz.geo_zone_id) WHERE tr1.tax_class_id = '9' AND tr1.based = 'shipping' AND tr2cg.customer_group_id = '1' AND z2gz.country_id = '223' AND (z2gz.zone_id = '0' OR z2gz.zone_id = '3624') ORDER BY tr1.priority ASC;

SQL string length is: 575

Exception occurred..The message id: ids_unknown_reply_error With parameters: -1,572
org.trafodion.jdbc.t4.HPT4Exception: The message id: ids_unknown_reply_error With parameters: -1,572
        at org.trafodion.jdbc.t4.HPT4Messages.createSQLException(HPT4Messages.java:304)
        at org.trafodion.jdbc.t4.HPT4Messages.createSQLException(HPT4Messages.java:227)
        at org.trafodion.jdbc.t4.odbc_SQLSvc_Close_exc_.extractFromByteArray(odbc_SQLSvc_Close_exc_.java:63)
        at org.trafodion.jdbc.t4.CloseReply.<init>(CloseReply.java:36)
        at org.trafodion.jdbc.t4.T4ResultSet.Close(T4ResultSet.java:121)
        at org.trafodion.jdbc.t4.InterfaceResultSet.close(InterfaceResultSet.java:841)
        at org.trafodion.jdbc.t4.TrafT4ResultSet.close(TrafT4ResultSet.java:4151)
        at org.trafodion.jdbc.t4.TrafT4ResultSet.close(TrafT4ResultSet.java:253)
        at JDBCOpenCart.main(JDBCOpenCart.java:78)

Revision history for this message
Aruna Sadashiva (aruna-sadashiva) wrote :

This is working now, although nothing was fixed from dcs side. So marking it invalid, as there is no other option to show that this is not reproducible anymore.

Changed in trafodion:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.