search cancel

Policy Server will not honor the timeout value in ODBC connections when the data source is an oracle database.


Article ID: 54248


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On



We are experiencing problems in production due to excessively long timeouts on the connections to a Oracle user-directory and excessively long timeouts on the execution of queries.

According to the documentation the registry key QueryTimeout under HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\Database represents the amount of time a query will be allowed to run before it is terminated. This prevents long running queries from tying up a database connection.

I need to close the connections to the database when the Database has a very slow response. The registry key QueryTimeout should finalize any connection that runs for more than the specified time, however it is not happening.


This is a restriction of the Data Direct Wire protocol driver. It does not support the timeout for statements.

This feature (SQL_ATTR_QUERY_TIMEOUT ) is presently not supported with this product version. Data Direct has also tested this feature with the Connect for ODBC 5.2 and 5.3 product lines and discovered this functionality is not implemented with these versions either.


Component: SMPLC