Oracle load script parameter for timeout is being ignored for the following:
- 'x' seconds within SQL_ATTR_QUERY_TIMEOUT
- 'x' seconds within QueryTimeout
Oracle's documentation provides instruction for using this parameter during the connection to set the timeout.Attribute
The number of seconds for the default query timeout for all statements that are created by a
connection. To override the value set by this connection option for an individual statement, set a
different value in the SQL_ATTR_QUERY_TIMEOUT statement attribute on the SQLSetStmtAttr()
-1 | 0 | x
is a positive integer that specifies a number of seconds.
- Third Party: http://knowledgebase.progress.com/articles/Article/000028010
- Third Party: http://knowledgebase.progress.com/articles/Article/000073400
- Oracle: http://www.oracle.com/technetwork/database/windows/odbcfaq-128251.pdf
The observed behavior within Qlik Sense is as follows:
- When set to 0, Qlik will ignore this and use the Oracle value. Example: 30 seconds.
- When set to -1, the query will run as long as necessary.
- When set to x seconds, the attribute is ignored within Qlik, again, the Oracle timeout will be used. It is expected to be able to set this at the connection string level but it is being ignored.
The functionality has not been provided at the driver level.
Currently SQL_ATTR_QUERY_TIMEOUT for 'x' seconds is not supported with our old drivers or current drivers and we have added this as an enhancement request for the current driver provider.
No ETA on when this will be added, check internal documentation for updates.