Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello all,
We have switched to Qlik SAAS since 31/12.
To get the data from our on premise Progress database we are using the Qlik Direct Access Data Gateway.
The thing is that retrieving 1 table does not always succeed, sometimes it does, and after about 10 million lines gives an error message:
'Error:(Connector error: Status(StatusCode="Internal", Detail="Failed to read data at {0:9}") (DirectAccess-1512))'
In total, I am reading 17 fields from a table with about 17.5 million lines, good for a 300 MB QVD file.
There is another larger table that I read from and it works perfectly (QVD of 5 GB). Anyone who can deduce from the error message where my problem is?
Thanks in advance!
Peter
Hi @Mimiek
The issue is likely to a value that is not supported. The data types supported for Postgres are listed here https://help.qlik.com/en-US/cloud-services/Subsystems/ODBC_Connector_help/Content/Connectors_ODBC/Po...
If you don't see any specific column that has an invalid data type, best approach would be to narrow down to the value, as you have a lot of values probably best option would be to narrow down to a period (perhaps get data in a loop by moth to see at what point it fails), once you have that probably to narrow down to the row/field.
I believe you are using our connectors, other option could be to use Generic ODBC so you can use a third party driver, perhaps the one from the vendor and verify the outcome https://help.qlik.com/en-US/cloud-services/Subsystems/ODBC_Connector_help/Content/Connectors_ODBC/OD...
Hope it helps.
Hi @NadiaB ,
So it turned out that there was a field and line in a certain table that had too many characters. Fortunately on a line that I didn't actually need, so I could filter it out when retrieving the data.
Thank you for the assistance!
Hi @Mimiek
The issue is likely to a value that is not supported. The data types supported for Postgres are listed here https://help.qlik.com/en-US/cloud-services/Subsystems/ODBC_Connector_help/Content/Connectors_ODBC/Po...
If you don't see any specific column that has an invalid data type, best approach would be to narrow down to the value, as you have a lot of values probably best option would be to narrow down to a period (perhaps get data in a loop by moth to see at what point it fails), once you have that probably to narrow down to the row/field.
I believe you are using our connectors, other option could be to use Generic ODBC so you can use a third party driver, perhaps the one from the vendor and verify the outcome https://help.qlik.com/en-US/cloud-services/Subsystems/ODBC_Connector_help/Content/Connectors_ODBC/OD...
Hope it helps.
Hi @NadiaB ,
So it turned out that there was a field and line in a certain table that had too many characters. Fortunately on a line that I didn't actually need, so I could filter it out when retrieving the data.
Thank you for the assistance!
thanks for posting this, helped us when we got this same error today.