Within the first hour after the proxy restarts, ODBC items whose SQL queries with Chinese search conditions return incorrect results.
The targeting database here is MSSQL (Microsoft SQL Server).

Steps to reproduce:

1. To compare query results for the same record, three ODBC items were created, using different SQL query statement:

    Query with Chinese search condition:

select count(*) from ... where [job].[description] like '%无描述%' 

    Query with English search condition:

select count(*) from ... where [job].[job_id] like '%-DA86-%' 

    Query for content:

select [job].[job_id], [job].[description] from ... 

    refer screenshots: item-odbc-chinese.jpg, item-odbc-english.jpg, item-odbc-detail.jpg

2. Confirm that the above three items can synchronously get correct query results before the proxy restarts.

    Due to the presence of actual data records, whether using Chinese or English search conditions, the returned row count consistently shows as 1.

    refer screenshots: data-beforeRestart-odbc-chinese.jpg, data-beforeRestart-english.jpg, data-beforeRestart-odbc-detail.jpg

3. restart proxy

sudo systemctl restart zabbix-proxy 

Result:

• Item with Chinese search condition, the returned row count sometimes showing as 0 (incorrect result) and other times as 1.
• Item with English search condition, the returned row count consistently shows as 1. 
• Item with content consistently shows the presence of record.

  refer screenshots: data-afterRestart-odbc-chinese.png, data-afterRestart-odbc-english.png, data-afterRestart-odbc-detail.png

Expected:

  In our environment, business monitoring usually involves Chinese search conditions, and it is essential that the returned results are accurate.