Results 1 to 1 of 1

Thread: ERROR: java.lang.NumberFormatException: For input string: "???????"

  1. #1
    Costi Zaboura is offline World Wide Support Manager
    Join Date
    Aug 2006
    Posts
    300
    Rep Power
    8

    Default Jdbc for Vsam - ERROR: java.lang.NumberFormatException: For input string: "???????"

    Description

    The VSAM file can be successfully retrieved using the Attunity Studio Query tool.

    Connecting via JDBC and querying a flat file is successful but when attempting to query a VSAM file this error occurs.

    java.lang.NumberFormatException: For input string: "???????"
    at java.lang.NumberFormatException.forInputString(Unk nown Source)
    at java.lang.Integer.parseInt(Unknown Source)
    at java.math.BigInteger.(Unknown Source)
    at java.math.BigInteger.(Unknown Source)
    at java.math.BigDecimal.(Unknown Source)
    at com.attunity.comm.DynFile.dynfGetDecimal(Unknown Source)
    at com.attunity.navapi.DecimalVariant.readData(Unknow n Source)
    at com.attunity.navapi.RowCur.getNextRow(Unknown Source)
    at com.attunity.navapi.RowCur.getFirstRows(Unknown Source)
    at com.attunity.navapi.RowCur.getRows(Unknown Source)
    at com.attunity.navapi.RowCur.getRows(Unknown Source)
    at com.attunity.jdbc.NvResultSetBase.next(Unknown Source)
    at
    org.apache.commons.dbcp.DelegatingResultSet.next(D elegatingResultSet.
    java:196)
    at com.platogroup.camouflage.gui.l.f.ib.b(ib.java)
    at com.platogroup.camouflage.gui.l.f.q.c(q.java)
    at com.platogroup.camouflage.gui.a.o.run(o.java)
    at java.awt.event.InvocationEvent.dispatch(Unknown Source)
    at java.awt.EventQueue.dispatchEvent(Unknown Source)
    at java.awt.EventDispatchThread.pumpOneEventForHierar chy(Unknown
    Source)

    at java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown
    Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.run(Unknown Source)



    Solution

    The issue is related to the initial value of certain fields.

    By initializing the fields with high values (hex FF), this causes a problem in numeric fields being retrieved though the JDBC interface.

    Our suggested solution to this would be to add the nullValue attribute to the ADD field element where this situation applies. You can find the Null Value field on the column properties window from the field in question. To get to the fields you need to edit the table from the Metadata tab.

    (eg nullValue=”BINARY:\FF\FF\FF”)
    Last edited by Admin; 08-31-2006 at 12:40 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •