Hi, I'm not sure if this is a JDBC bug. In the past I got this error when the database kernel delivers corrupt data. The differences between the 7.5 and the 7.6 driver could come from a different communication protocol that they use. For a further analysis of this problem an order vtrace (http://sapdb.2scale.net/maxdb-wiki/VTrace) would be helpful. Could you please send me this trace.
Best regards, Marco > -----Original Message----- > From: Donatas Ciuksys [mailto:[EMAIL PROTECTED] > Sent: Freitag, 21. Juli 2006 01:54 > To: maxdb@lists.mysql.com > Subject: JDBC driver v7.6: UNION ALL corrupts ResultSet > > Hi, > > I have SQL that uses UNION ALL, and all the 7.6 JDBC drivers > that I have tried through this: > > com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot > convert VDN number [00000000000000000000000000000000000000c1]. > at > com.sap.dbtech.util.VDNNumber.number2BigDecimal(VDNNumber.java:243) > at com.sap.dbtech.util.VDNNumber.number2long(VDNNumber.java:363) > at > com.sap.dbtech.jdbc.translators.NumericTranslator.getLong(Nume > ricTranslator. > java:232) > at > com.sap.dbtech.jdbc.translators.NumericTranslator.getInt(Numer > icTranslator.j > ava:209) > at > com.sap.dbtech.jdbc.ResultSetSapDB.getInt(ResultSetSapDB.java:1107) > at > org.apache.tomcat.dbcp.dbcp.DelegatingResultSet.getInt(Delegat > ingResultSet.j > ava:236) > > Well the problem is not number format in DB (I spent a lot of > time till I clarified this) - problem is that v7.6 JDBC > drivers mess up ResultSet somehow. Everything is working OK > with v7.5.01 JDBC driver (sapdbc-7_5_01_00.jar). > > This is what DBVisualizer shows in its Debug window: > > 02:42:10 [ERROR Thread-11 E.ā] Error getting value for row/col 34/14 > (ISGNEPILNAMECIU): > com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot > convert VDN number [0061006c0069007a006100630069006a006f0073]. > 02:42:10 [ERROR Thread-11 E.ā] ... switching to getObject() > 02:42:10 [ERROR Thread-11 E.ā] Error getting value for row/col 34/14: > com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot > convert VDN number [0061006c0069007a006100630069006a006f0073]. > 02:42:10 [ERROR Thread-11 E.ā] Error getting value for > row/col 35/4 (KIEK): > com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot > convert VDN number [000000000000]. > 02:42:10 [ERROR Thread-11 E.ā] ... switching to getObject() > 02:42:10 [ERROR Thread-11 E.ā] Error getting value for row/col 35/4: > com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot > convert VDN number [000000000000]. > 02:42:10 [ERROR Thread-11 E.ā] Error getting value for row/col 35/13 > (PRAITIISGNEPILNAMECIU): > com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: > Cannot convert VDN number [00000000000000c23600000100560079006b0069]. > 02:42:10 [ERROR Thread-11 E.ā] ... switching to getObject() ... > ... and so on many times more... > ... > > With older (7.5) JDBC driver there are no problems - I get > result without exceptions (grid with one column as VARCHAR, > and others as numbers). But with 7.6 (even the latest one > from 7.6.00.32) I get squares, question marks, etc. (as > DBVisualizer possibly switches from getInt() to getObject()). > > So, I can use the old driver, but question is following - are > all the 7.6 drivers broken with respect to UNION ALL? And why > this is driver dependent - UNION is executed on the server > side, JDBC driver should just get ResultSet? > > Regards, > Donatas > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
