ODBC Importer data trimmed

Deepakbn

Member
I am working to perform ODBC import while creating DSN to access data from HDFS JSON files. The DSN is created through Drill ODBC.
Currently the ODBC import works fine to display data from Mapr FS but trims data while displaying from ODBC import.

What is the maximum length allowed to display on the selected columns and what is the option of changing to increase or decrease it.
Do we support JSON data imports?
 
There is no limit to the data size. The preview grid does limit the column width though. Is the data also truncated when you perform the import?
 
Yes, The data is truncated with the import to Oracle. Do we have options to increase or decrease?
Will be a good help if I get to know how this can be handled to display the entire dataset
 
Last edited:
I have imported a column 'data' to Oracle with the value - '{
"dom" : {
"viewport_height" : "909",
"referrer" : "https://www.tv.com/show/jtv-live",
"viewport_width" : "1920",
"domain" : "www.tv.com",
"title" : "TV Current On-Air Item - Buy Jewelry Live Online | TV.com",
"url" : "https'

The value is getting truncated around 260 characters. The column at the target Oracle table has datatype 'CLOB' and we need entire string to populate in Oracle.
 
Last edited:
Can anyone please provide an update about this column data truncate issue observed for ODBC imports. Do we have any options of increasing or decreasing the limit or the max allowed column limit set around 260 characters?
 
Thank you Marco for your response. I have PL/SQL Developer version '14.0.6.1988'. Do you recommend different version to handle this issue?
 
Marco, do you have any suggestion how to handle column data truncate issue observed for ODBC imports. Should I install any other version of PL/SQL Developer than my current one(14.0.6). Thank you!
 
We're looking in to this. Note that there are no limitation in PL/SQL Developer, so it may be an issue with the specific ODBC driver.
 
Thanks Marco for the response. The ODBC driver(Mapr Drill ODBC) seems to be working fine with Fly speed Sql query (free version) when I queried it by accessing it through system DSN. I was able to query and view the entire json data column without getting data truncated.
Could you please help to analyze data truncate issue happening through PL/SQLODBC imports and suggest how could we resolve it.
 
Marco, Just wanted to check if you get a chance to look into the options to resolve the data trim issues observed for ODBC importer. Appreciate if you could help us to get this issue resolved.
 
Back
Top