When using Qlik Data Gateway - Direct Access, sometimes reloads will fail with an error message:
"Incomplete data reload has been detected (DirectAccess-4025)"
Cause
From DGDA version1.6.3 onward, the Direct Access gateway will automatically reconnect to the Qlik Cloud as needed.
To prevent data loss, a summary of each data load will be verified at the end of each load request. If data loss is detected, the reload will fail and the user will be presented with the error message "Incomplete data reload has been detected (DirectAccess-4025)".
In previous versions, to prevent potential data loss, the Direct Access gateway did not automatically reconnect to the data source during a reload, where instead the user will be presented with a more generic error message: "Connection to Qlik Cloud was lost during load request. Please upgrade the gateway to the latest version to enable automatic reconnect. (DirectAccess-4027)".
Resolution
DirectAccess-4025 errors are currently expected by design. This more specific error is returned starting with 1.6.3, versus a more generic data loading error, after the network connection between the customer's gateway and QCS is broken and data loss is detected following automatic reconnect. Customers experiencing this error frequently, or for critical app reloads, should implement an automatic retry mechanism.
Additional Information about DGDA 1.6.3:
In rare scenarios, the reload session would stay alive indefinitely. To prevent such occurrences, this version introduces a three-hour timeout for reload sessions.
Reloads would sometimes fail with the following errors:
Connector error: The session does not exist (DirectAccess-1509) Connector error: The stream session expired for the load data request (DirectAccess-1012)
To mitigate this issue, an EXTEND_FIRST_REQUEST_TIMEOUT parameter (for extending the load request timeout) was added to the configuration.properties file. The default is "0". Customers who frequently encounter these errors should try setting the timeout to 5-10 minutes.
Added support for viewing detailed connection error messages when using ODBC-based via Direct Access gateway connectors. Customers can now set the ShowErrorDetailMessage parameter in the Advanced connector settings to "true" to see the full error returned by the ODBC driver.
From this version, the engine session ID will be used to distinguish between multiple reloads with the same reload ID. This will prevent potential conflicts, resulting in reloads failing with the following error:
Connector error: data loading error (DirectAccess-4008)
