EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB438829: Error: Certain Datatypes not supported the Amazon Athena JDBC driver in MicroStrategy Web


Community Admin

• Strategy


Issue

When you access the tables from Data import in Strategy Web, for all INT datatypes(int, bigint, tinyint, smallint), you will get an error message:
There is an error on the server.
We are sorry for the inconvenience. Please contact your administrator for help.
Hide Details
Database error <32>: JdbcResultWrapper::Fetch failed. Error type: Jdbc error. Jdbc operation attempted: FetchTable. [:0: on SQLHANDLE] Invalid int format
DSSERROR log will say:
2017-10-26 15:45:05.174 [HOST:FARAH109][SERVER:][PID:8384][THR:9104][JdbcWrapper][Error] JdbcSQLException occur. Error Message: Invalid int format, Java Trace: java.sql.SQLException: Invalid int format
    at com.amazonaws.athena.jdbc.AthenaResultSet.getInt(AthenaResultSet.java:245)
    at com.amazonaws.athena.jdbc.AthenaResultSet.getObject(AthenaResultSet.java:560)
    at com.Strategy.database.Jdbc.JdbcResultSet.getObject(Unknown Source)
    at com.Strategy.database.Jdbc.JdbcResultSet._fetch(Unknown Source)
    at com.Strategy.database.Jdbc.JdbcResultSet.fetch(Unknown Source)
Caused by: java.lang.NumberFormatException: For input string: "null"
    at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
    at java.lang.Integer.parseInt(Integer.java:580)
    at java.lang.Integer.parseInt(Integer.java:615)
    at com.amazonaws.athena.jdbc.AthenaResultSet.getInt(AthenaResultSet.java:242)
    ... 4 more
 

Resolution

Use the latest Amazon JDBC driver, it has to be JDBC41-1.1.0.jar or above. This issue is seen with the JDBC Driver version JDBC41-1.0.1 KB438829


Comment

0 comments

Details

Knowledge Article

Published:

November 3, 2017

Last Updated:

December 31, 2018