[ZBX-25542] Request to Add SQL_ATTR_QUERY_TIMEOUT Parameter for ODBC Monitoring in Zabbix 6.0 Created: 2024 Nov 14 Updated: 2024 Dec 08 Resolved: 2024 Dec 08 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 6.0.35 |
Fix Version/s: | 6.0.37rc1 |
Type: | Problem report | Priority: | Major |
Reporter: | Itsuki Karimata | Assignee: | Sergejs Boidenko |
Resolution: | Fixed | Votes: | 0 |
Labels: | odbc, oracle | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | 2h | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||
Team: | |||||
Sprint: | S24-W46/47, S24-W48/49 | ||||
Story Points: | 1 |
Description |
We have encountered a situation where monitoring of Oracle databases did not time out as expected, resulting in a halt in monitoring operations. Upon consulting with Oracle's technical support, we were informed that the SQL_LOGIN_TIMEOUT parameter currently used in Zabbix 6.0 is not supported, while SQL_ATTR_QUERY_TIMEOUT is supported. As SQL_ATTR_QUERY_TIMEOUT has been implemented in Zabbix 7.0 through |
Comments |
Comment by Sergejs Boidenko [ 2024 Dec 06 ] |
Available in versions:
|