Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsTimeOutCheckJob is defined as the number of seconds of inactivity before checking if background job is still running. This parameter has been introduced in 6.3.0 release. Although, this is not visible in the connection dialog, however, this can be override thru the connection string manually.
The default value is 60 seconds, and that means that after 60 seconds of inactivity the client will set a parameter for checking the job in the next invocation, this will trigger a check on the back-end which will let the client know if the job has dumped.
Invocation is defined as the packet which is logged as read xxx data rows, from the QvSAPSqlConnector-<timestamp>-<arbitrary numbers>.log
To define the TimeOutCheckJob parameter one can easily add this to the existing Connection String as for instance:
CUSTOM CONNECT TO "Provider=QvSAPSqlConnector.exe;.............;FetchBuffers=99999999;....;TimeOutCheckJob=120;BatchJobName=/QTQVC/READ_DATA;SenseVersion=11, 20, 13206, 0;XUserId=xxxxx;";
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us