In both instances I am using [ (String) _rs.getString("COLUMN_NAME") ] to
fetch what is actually a FIXED() column datatype value. What is strange is
that this has been this way for quite a while now but I am just now seeing
these errors in the tomcat logs.
com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot convert VDN number
[20546563686e].
at com.sap.dbtech.util.VDNNumber.number2string(VDNNumber.java:615)
at
com.sap.dbtech.jdbc.translators.NumericTranslator.getString(NumericTranslato
r.java:425)
at
com.sap.dbtech.jdbc.ResultSetSapDB.getString(ResultSetSapDB.java:1241)
at com.synfoserv.actions.CallAction.getListBean(CallAction.java:713)
at com.synfoserv.actions.CallAction.callSearch(CallAction.java:589)
com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot convert VDN number
[00000000000000000000].
at com.sap.dbtech.util.VDNNumber.number2string(VDNNumber.java:615)
at
com.sap.dbtech.jdbc.translators.NumericTranslator.getString(NumericTranslato
r.java:425)
at
com.sap.dbtech.jdbc.ResultSetSapDB.getString(ResultSetSapDB.java:1241)
at
com.synfoserv.actions.CompanyAction.getListBean(CompanyAction.java:548)
at
com.synfoserv.actions.CompanyAction.companyEdit(CompanyAction.java:367)
If I continue to see these errors I will change the statement to use
getInt() and see what comes about.
Thanks for the help Alexander.
Kevin
-----Original Message-----
From: Schroeder, Alexander [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2003 12:03 PM
To: Kevin Wilson; Sapdb General List (E-mail)
Subject: RE: VDN Number Errors in logs
Hello Kevin,
as you might have read, that exception is produced when the driver
reads a number in the internal format, that is corrupted somehow.
If you are certain that there is no loss of data because of a dirty restart
or some other hardware issue, try to isolate the offending statement,
and the offending row.
You might want to run that offending statement having vtrace
enabled, and send the trace output.
Regards
Alexander Schr�der
SAP DB, SAP Labs Berlin
> -----Original Message-----
> From: Kevin Wilson [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 05, 2003 6:51 PM
> To: Sapdb General List (E-mail)
> Subject: VDN Number Errors in logs
>
>
> I searched the list and found some mention that this was due
> to a dirty
> restart and that it was a bad bad bad error to receive.
> Unfortunately, our
> db has not had any dirty restarts that I am aware of nor does
> it seem to be
> functioning poorly.
>
> Is there somewhere I can go to track down what may be causing
> this error and
> what steps I can do to ensure the database does not become corrupted?
>
> com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB: Cannot
> convert VDN number
> [202020202020].
> at
> com.sap.dbtech.util.VDNNumber.number2string(VDNNumber.java:615)
> at
> com.sap.dbtech.jdbc.translators.NumericTranslator.getString(Nu
> mericTranslato
> r.java:425)
> at
> com.sap.dbtech.jdbc.ResultSetSapDB.getString(ResultSetSapDB.java:1241)
>
> <rest error message snipped>
>
>
> Thanks,
>
> Kevin
>
> "Those who would give up essential liberty to purchase a
> little temporary
> safety deserve neither liberty nor safety."
> -Benjamin Franklin, 1759
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
>
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
